JRNL_UP_H_VW(SQL View) |
Index Back |
---|---|
JRNL Header for Fluid ApprovalJournal Header for Fluid Journal Upost Approval |
SELECT AF.BUSINESS_UNIT , AF.JOURNAL_ID , AF.JOURNAL_DATE , AF.BUSINESS_UNIT_LN , H.LEDGER_GROUP , H.FISCAL_YEAR , H.ACCOUNTING_PERIOD , %NumToChar(H.FISCAL_YEAR) %Concat ' / ' %Concat %NumToChar(H.ACCOUNTING_PERIOD) , H.JRNL_TOTAL_DEBITS , H.JRNL_TOT_CREDITS , H.CURRENCY_CD , H.DESCR , H.DESCR254 , H.OPRID , OP.OPRDEFNDESC , %DatePart(H.JRNL_CREATE_DTTM) , H.ATTACHMENT_EXIST , H.ADJUSTING_ENTRY , H.JRNL_PROCESS_REQST , AF.EOAWTHREAD_ID , AF.EOAWPRCS_ID , AF.EOAWREQUESTOR_ID , AF.EOAWTHREAD_STATUS , H.LEDGER , H.ADB_DATE , H.POSTED_DATE , H.JOURNAL_DATE_ORIG , H.AUTO_GEN_LINES , H.JRNL_TOTAL_LINES , H.JRNL_NET_UNITS , H.SOURCE , H.JOURNAL_CLASS , H.SYSTEM_SOURCE , H.ACCTG_DEF_NAME , H.GL_ADJUST_TYPE , H.DATE_CODE_JRNL , H.BUDGET_HDR_STATUS , H.KK_AMOUNT_TYPE , H.KK_TRAN_OVER_FLAG , H.KK_TRAN_OVER_OPRID , H.KK_SKIP , H.REVERSAL_CD , H.REVERSAL_DATE , H.REVERSAL_ADJ_PER , H.REVERSAL_CD_ADB , H.REVERSAL_DATE_ADB , H.DOC_TYPE , H.DOC_SEQ_NBR , H.DOC_SEQ_DATE , H.DOC_SEQ_STATUS , UPDT.UNPOST_JRNL_DATE FROM PS_JRNL_HEADER H LEFT OUTER JOIN PS_GL_WC_UNPOST_DT UPDT ON UPDT.BUSINESS_UNIT = H.BUSINESS_UNIT_IU AND UPDT.JOURNAL_ID=H.JOURNAL_ID AND UPDT.JOURNAL_DATE=H.JOURNAL_DATE AND UPDT.UNPOST_SEQ= H.UNPOST_SEQ AND UPDT.BUSINESS_UNIT_LN = H.BUSINESS_UNIT , PS_JRNL_UP_AF_XREF AF , PSOPRDEFN OP WHERE AF.BUSINESS_UNIT = H.BUSINESS_UNIT_IU AND AF.JOURNAL_ID = H.JOURNAL_ID AND AF.JOURNAL_DATE = H.JOURNAL_DATE AND AF.BUSINESS_UNIT_LN = H.BUSINESS_UNIT AND OP.OPRID = H.OPRID AND H.UNPOST_SEQ = 0 |
# | PeopleSoft Field Name | PeopleSoft Field Type | Database Column Type | Description |
---|---|---|---|---|
1 | BUSINESS_UNIT | Character(5) | VARCHAR2(5) NOT NULL |
Business Unit
Prompt Table: SP_BU_GL_NONVW |
2 | JOURNAL_ID | Character(10) | VARCHAR2(10) NOT NULL | Identifies a journal entry, consisting of a header and one or more lines. The Journal ID itself does not have to be unique, but together with the journal business unit and journal date, it forms a unique journal identifier. |
3 | JOURNAL_DATE | Date(10) | DATE | Specifies the date the journal was created. |
4 | BUSINESS_UNIT_LN | Character(5) | VARCHAR2(5) NOT NULL |
Line Business Unit
Prompt Table: SP_BU_GL_NONVW |
5 | LEDGER_GROUP | Character(10) | VARCHAR2(10) NOT NULL | Ledger Group |
6 | FISCAL_YEAR | Number(4,0) | SMALLINT NOT NULL | Fiscal Year |
7 | ACCOUNTING_PERIOD | Number(3,0) | SMALLINT NOT NULL | Identifies a time period to which you post transactions. Typically, an accounting period represents a month, but it can also represent a week, a day, or any user-defined interval. An accounting period has a beginning date and an ending date, and is defined in the calendar table. |
8 | YEAR_PERIOD | Character(10) | VARCHAR2(10) NOT NULL | Combination Field of ChartField year and period |
9 | JRNL_TOTAL_DEBITS | Signed Number(28,3) | DECIMAL(26,3) NOT NULL | Represents a running total of the debit amounts in a journal entry. It is maintained by PeopleSoft General Ledger as lines are entered. |
10 | JRNL_TOT_CREDITS | Signed Number(28,3) | DECIMAL(26,3) NOT NULL | Represents a running total of the credit amounts in a journal entry. It is maintained by PeopleSoft General Ledger as lines are entered. |
11 | CURRENCY_CD | Character(3) | VARCHAR2(3) NOT NULL | Currency Code |
12 | JRNL_DESCR | Character(30) | VARCHAR2(30) NOT NULL | Journal Description |
13 | DESCR254 | Character(254) | VARCHAR2(254) NOT NULL | Description of length 254 |
14 | OPRID | Character(30) | VARCHAR2(30) NOT NULL | A user's ID (see PSOPRDEFN). |
15 | ENTERED_BY | Character(30) | VARCHAR2(30) NOT NULL | Entered by |
16 | ENTERED_DT | Date(10) | DATE | Entered on |
17 | ATTACHMENT_EXIST | Character(1) | VARCHAR2(1) NOT NULL |
Attachments Exist
N=N Y=Y |
18 | ADJUSTING_ENTRY | Character(1) | VARCHAR2(1) NOT NULL |
Adjusting Entry
C=Fiscal Year Close N=Non-Adjusting Entry Y=Adjusting Entry |
19 | JRNL_PROCESS_REQST | Character(1) | VARCHAR2(1) NOT NULL |
A flag that determines when a journal is ready for posting. Some examples of the request flag are Approved to Post, Denied, and Pending Approval.
D=Default E=Denied G=Pending Approval N=None P=Approved to Post Q=Pending for Unpost Approval R=Replace S=Security Denied T=Terminated U=Pending Request to Unpost W=Approved to Post X=Delete |
20 | EOAWTHREAD_ID | Number(15,0) | DECIMAL(15) NOT NULL | Approval Framework Thread ID |
21 | EOAWPRCS_ID | Character(30) | VARCHAR2(30) NOT NULL | Approval Process ID |
22 | REQUESTOR_ID | Character(30) | VARCHAR2(30) NOT NULL | Requestor id |
23 | EOAWTHREAD_STATUS | Character(1) | VARCHAR2(1) NOT NULL |
Thread Status
A=Approved C=Complete D=Denied E=Pending Denial H=Hard Deny I=Initial N=Not Active P=Pending S=Awaiting Further Approvals T=Terminated W=Canceled X=Suspended/Pending Denial |
24 | LEDGER | Character(10) | VARCHAR2(10) NOT NULL | Ledger |
25 | ADB_DATE | Date(10) | DATE | Specifies the daily date to use when Average Daily Balancing is activated. The date is determined by the daily calendar associated with the General Ledger Business Unit to which the journal is posted. When ADB processing is not activated, the ADB_Date defaults to the date on the Journal Header (JOURNAL_DATE). |
26 | POSTED_DATE | Date(10) | DATE | Specifies the date that a journal entry is posted. This field is maintained by the posting program of PeopleSoft General Ledger. |
27 | JOURNAL_DATE_ORIG | Date(10) | DATE | Orignial Journal Date |
28 | AUTO_GEN_LINES | Character(1) | VARCHAR2(1) NOT NULL | A flag that indicates whether or not (Y or N) journal lines should be automatically generated for other ledgers in a ledger group. This option is automatically on if the Keep Ledgers in Sync option is on for the specified ledger group. You can select the Auto Generate Lines option for a multibook ledger group specified on a journal header. |
29 | JRNL_TOTAL_LINES | Number(9,0) | DECIMAL(9) NOT NULL | Represents a running total of the number of lines in a journal entry. It is maintained by PeopleSoft General Ledger as lines are entered. |
30 | JRNL_NET_UNITS | Signed Number(27,2) | DECIMAL(25,2) NOT NULL | Represents a running total of the statistical units in a journal entry. It is a hash total since there may be different types of units of measure reflected in a single journal. It is maintained by PeopleSoft General Ledger as lines are entered. |
31 | SOURCE | Character(3) | VARCHAR2(3) NOT NULL | Identifies the origin of a journal entry and defines journal entry error handling options. The journal source provides a means of selectively tracking, reporting, and inquiring on journal entries. It can be almost anything within the enterprise - a subsystem that generates transactions, a department, or even an individual. |
32 | JOURNAL_CLASS | Character(10) | VARCHAR2(10) NOT NULL | Journal Class |
33 | SYSTEM_SOURCE | Character(3) | VARCHAR2(3) NOT NULL | Identifies the application or source system that generated a journal entry. Release 8.80 - 11/14/2002 - RVlasic - Removed GDM (JrnlGen - Deduction Management) from Translate Values. SUJ---Included a label as Product. Release 8.9 - 05/11/2005 - RVlasic - Added PRV (Variance Pricing) and PKK (KK Budget Journal) and deleted GLK for Project Costing per Brian Cohen. |
34 | ACCTG_DEF_NAME | Character(10) | VARCHAR2(10) NOT NULL | Defines the content and source of the accounting transactions that the Journal Generator program of PeopleSoft General Ledger uses to create journal entries. Accounting transactions are populated by PeopleSoft applications or third-party systems for input to the general ledger. |
35 | GL_ADJUST_TYPE | Character(4) | VARCHAR2(4) NOT NULL | Adjustment Type |
36 | DATE_CODE_JRNL | Character(1) | VARCHAR2(1) NOT NULL | This field defines codes for Date field used in Journal lines record. The Different date fields can be used as the basis for alternate Posting to satisfy Trade Date/Settlement date requirements. |
37 | BUDGET_HDR_STATUS | Character(1) | VARCHAR2(1) NOT NULL |
Budget Checking Header Status
E=Error in Budget Check I=Document In Processing N=Not Budget Checked P=Provisionally Valid V=Valid |
38 | KK_AMOUNT_TYPE | Character(1) | VARCHAR2(1) NOT NULL |
Commitment Control Amount Type
0=Budget 1=Actuals and Recognized 2=Encumbrance 3=Pre-Encumbrance 4=Collected Revenue 5=Planned 7=Actuals, Recognize and Collect 9=Dynamic |
39 | KK_TRAN_OVER_FLAG | Character(1) | VARCHAR2(1) NOT NULL |
Commitment Control source transaction override flag
N=No Y=Yes |
40 | KK_TRAN_OVER_OPRID | Character(30) | VARCHAR2(30) NOT NULL | Commitment Control source transaction override operator |
41 | KK_SKIP | Character(1) | VARCHAR2(1) NOT NULL |
The field is used in Journal Header record. If its value is '1', the journal will skip commitment control budget checking. Usually, the journal created from Journal Generator for accounting entries which have been budget checked already will have '1' populated in this field.
0=Commitment Control in GL 1=Skip Commitment Control in GL |
42 | REVERSAL_CD | Character(1) | VARCHAR2(1) NOT NULL |
A flag that indicates if a journal entry should be automatically reversed, and if so, with what date. When associated with a reversal entry, it indicates that the entry was created automatically by the reversal process.
B=Beginning of Next Period D=On Date Specified By User E=End of Next Period N=Do Not Generate Reversal R=Created by Reversal Process U=Adjustment Period X=Next Day |
43 | REVERSAL_DATE | Date(10) | DATE | Specifies the date for an automatic reversal journal entry. The date must be within the calendar of the target (posting) ledger. PeopleSoft General Ledger automatically creates and populates a journal entry with this date. |
44 | REVERSAL_ADJ_PER | Number(3,0) | SMALLINT NOT NULL | Adjustment Period |
45 | REVERSAL_CD_ADB | Character(1) | VARCHAR2(1) NOT NULL |
ADB Reversal Code
D=On Date Specified By User S=Same As Journal Reversal |
46 | REVERSAL_DATE_ADB | Date(10) | DATE | ADB Reversal Date |
47 | DOC_TYPE | Character(8) | VARCHAR2(8) NOT NULL | Specifies the business purpose of a financial transaction in countries that require all financial transactions to be tracked as "documents". A Document Type is associated with one and only one Journal Code. |
48 | DOC_SEQ_NBR | Character(12) | VARCHAR2(12) NOT NULL | Specifies the sequence number assigned to each financial transaction (a document). The sequence number may be manually entered or system-generated. |
49 | DOC_SEQ_DATE | Date(10) | DATE | Specifies the date that a document sequence number is assigned to a document or the date the document was created. |
50 | DOC_SEQ_STATUS | Character(1) | VARCHAR2(1) NOT NULL |
A flag that indicates a document sequencing error. If there is no error the field is blank and document is considered valid for posting.
1=Document Sequencing Disabled A=GL BU Undefined B=GL BU Blank C=Accounting Date blank D=Doc Type Blank E=Jrnl Type, Code, Doc Undefine F=Sequence Range Undefine G=Max. Sequence Number Reached H=Manual Nbr for Auto Doc Type I=No Manual Number Entered J=Duplicate Manual Number K=Invalid Ledger L=Invalid Ledger Group N=No Status |
51 | UNPOST_JRNL_DATE | Date(10) | DATE | Unpost Date |