JRNL_HDR_IU_VW(SQL View) |
Index Back |
---|---|
SrchRec Journal Hdrs |
SELECT business_unit_iu ,journal_id ,journal_date ,unpost_seq ,doc_seq_nbr ,business_unit ,jrnl_hdr_status ,budget_hdr_status ,ledger_group ,source ,currency_cd ,jrnl_total_lines ,jrnl_total_debits ,jrnl_net_units ,descr ,oprid ,attachment_exist ,journal_class FROM PS_JRNL_HEADER a WHERE EXISTS ( SELECT 'X' FROM PS_JRNL_HEADER B WHERE B.BUSINESS_UNIT_IU=A.BUSINESS_UNIT_IU AND B.BUSINESS_UNIT=A.BUSINESS_UNIT_IU AND B.JOURNAL_ID=A.JOURNAL_ID AND B.JOURNAL_DATE=A.JOURNAL_DATE AND A.UNPOST_SEQ=B.UNPOST_SEQ) |
# | PeopleSoft Field Name | PeopleSoft Field Type | Database Column Type | Description |
---|---|---|---|---|
1 | BUSINESS_UNIT | Character(5) | VARCHAR2(5) NOT NULL |
Business Unit
Default Value: OPR_DEF_TBL_FS.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 | UNPOST_SEQ | Number(2,0) | SMALLINT NOT NULL | Identifies the sequence of journal entries when a journal is "unposted". When a journal is posted the UnPost Sequence is automatically set to "0". When a journal is unposted, a new reversing entry is automatically created with an UnPost Sequence of "1". |
5 | 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. |
6 | BUSINESS_UNIT_LN | Character(5) | VARCHAR2(5) NOT NULL |
Line Business Unit
Prompt Table: SP_BU_GL_NONVW |
7 | JRNL_HDR_STATUS | Character(1) | VARCHAR2(1) NOT NULL |
A flag that indicates the processing status of a journal entry.
D=Deleted E=Journal Has Errors I=Posting Incomplete M=Valid SJE Model -- Do Not Post N=No Status - Needs to be Edited P=Posted to Ledger(s) T=Journal Entry Incomplete U=Unposted V=Valid Journal - Edits Complete X=Cancelled Z=Upgrade Journal - Can't Unpost Default Value: N |
8 | 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 |
9 | LEDGER_GROUP | Character(10) | VARCHAR2(10) NOT NULL | Ledger Group |
10 | 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.
Default Value: OPR_DEF_TBL_FS.SOURCE Prompt Table: SOURCE_TBL |
11 | CURRENCY_CD | Character(3) | VARCHAR2(3) NOT NULL | Currency Code |
12 | 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. |
13 | 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. |
14 | 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. |
15 | JRNL_DESCR | Character(30) | VARCHAR2(30) NOT NULL | Journal Description |
16 | OPRID_ENTERED_BY | Character(30) | VARCHAR2(30) NOT NULL |
Entered By
07/25/2011 MRAD 12383033 :Ensured that OPRID_ENTERED_BY is set with format type of MixedCase.
03/22/2013 GL 16482301: Switched OPRID_ENTERED_BY back to MixedCase again. Please don't change it to UpperCase!!!
FYI - The alternatives to use a User ID as uppercase:
1) Create your own User ID, add comments in the Field Properties, and fill out the Owner ID
2) Use %Upper meta-SQL in SQL statements
3) Use Upper function in peoplecodes
Prompt Table: OPRID_VW |
17 | ATTACHMENT_EXIST | Character(1) | VARCHAR2(1) NOT NULL |
Attachments Exist
N=N Y=Y |
18 | JOURNAL_CLASS | Character(10) | VARCHAR2(10) NOT NULL |
Journal Class
Prompt Table: JRNL_CLASS_TBL |