| # |
PeopleSoft Field Name |
PeopleSoft Field Type |
Database Column Type |
Description |
| 1 |
 BUSINESS_UNIT |
Character(5) |
VARCHAR2(5) NOT NULL |
Business Unit
|
| 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 |
BUSINESS_UNIT_IU |
Character(5) |
VARCHAR2(5) NOT NULL |
Specifies the Business Unit for which InterUnit activity is being generated.
|
| 6 |
ADJUSTING_ENTRY |
Character(1) |
VARCHAR2(1) NOT NULL |
Adjusting Entry
C=Fiscal Year Close
N=Non-Adjusting Entry
Y=Adjusting Entry
|
| 7 |
FISCAL_YEAR |
Number(4,0) |
SMALLINT NOT NULL |
Fiscal Year
|
| 8 |
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.
|
| 9 |
FISCAL_YEAR2 |
Number(4,0) |
SMALLINT NOT NULL |
Fiscal Year
|
| 10 |
ACCOUNTING_PERIOD2 |
Number(3,0) |
SMALLINT NOT NULL |
Accounting Period
|
| 11 |
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).
|
| 12 |
LEDGER_GROUP |
Character(10) |
VARCHAR2(10) NOT NULL |
Ledger Group
|
| 13 |
LEDGER |
Character(10) |
VARCHAR2(10) NOT NULL |
Ledger
|
| 14 |
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.
|
| 15 |
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
|
| 16 |
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.
|
| 17 |
REVERSAL_ADJ_PER |
Number(3,0) |
SMALLINT NOT NULL |
Adjustment Period
|
| 18 |
REVERSAL_CD_ADB |
Character(1) |
VARCHAR2(1) NOT NULL |
ADB Reversal Code
D=On Date Specified By User
S=Same As Journal Reversal
|
| 19 |
REVERSAL_DATE_ADB |
Date(10) |
DATE |
ADB Reversal Date
|
| 20 |
UNPOST_JRNL_DATE |
Date(10) |
DATE |
Unpost Date
|
| 21 |
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.
|
| 22 |
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.
|
| 23 |
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.
|
| 24 |
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.
|
| 25 |
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.
|
| 26 |
TRANS_REF_NUM |
Character(8) |
VARCHAR2(8) NOT NULL |
Identifies a document, person, invoice, date, or any other piece of information that is associated with a journal entry. The journal reference is helpful if you need to trace back to the source of the transaction.
|
| 27 |
JRNL_BALANCE_STAT |
Character(1) |
VARCHAR2(1) NOT NULL |
A flag that indicates whether or not a journal is in balance. A balanced journal is one in which the debit and credit lines net to zero. This field is maintained by the journal edit program of PeopleSoft General Ledger.
E=Error - Journal Out of Balance
V=Valid - Journal in Balance
|
| 28 |
CONTROL_TOTAL_STAT |
Character(1) |
VARCHAR2(1) NOT NULL |
A flag that indicates whether or not the control totals match the entry totals for a journal entry. The status is either (E) indicating an error or (V) indicating that the match is OK.
E=Error - Control Totals
V=Valid - Control Totals
|
| 29 |
JRNL_EDIT_ERR_STAT |
Character(1) |
VARCHAR2(1) NOT NULL |
A flag that indicates whether or not there are edit errors in a journal entry.
E=Error - Edit Error(s)
N=No Status
V=Valid - No Edit Errors
|
| 30 |
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
|
| 31 |
SUSP_RECON_STATUS |
Character(1) |
VARCHAR2(1) NOT NULL |
A flag that indicates whether or not there are suspense transactions in a journal, and if so, whether or not they have been corrected and posted.
0=No Suspense Transactions
1=Suspense Transactions
2=Correction Journal Created
3=Correction Journal Posted
|
| 32 |
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
|
| 33 |
JRNL_SUMLED_REQST |
Character(1) |
VARCHAR2(1) NOT NULL |
Post to Summary Ledger
|
| 34 |
SJE_TYPE |
Character(1) |
VARCHAR2(1) NOT NULL |
A flag that indicates the type of Standard Journal Entry (SJE), which can be either Template or Recurring. If the type is Recurring you must also specify a schedule (SCHEDULE).
M=Model -- Do Not Post
P=Spread Daily Proration
R=Recurring on a Schedule
S=Spread Amounts from SJE Model
T=Template to be Completed
|
| 35 |
SCHEDULE |
Character(10) |
VARCHAR2(10) NOT NULL |
Schedule ID
|
| 36 |
EVENT_OCCURRENCE |
Number(3,0) |
SMALLINT NOT NULL |
Identifies a user-defined event on a schedule for automatically creating standard and recurring journal entries. Event Occurrence is a number associated with a date for creation of the journal.
|
| 37 |
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.
|
| 38 |
PROCESS_INSTANCE |
Number(10,0) |
DECIMAL(10) NOT NULL |
Process Instance
|
| 39 |
SOURCE_INSTANCE |
Number(15,4) |
DECIMAL(14,4) NOT NULL |
Identifies a Process Instance (PROCESS_INSTANCE), and is used by the PeopleSoft Process Scheduler to save this identifier.
|
| 40 |
TRANSACTION_DATE |
Date(10) |
DATE |
Transaction Date
|
| 41 |
LAST_LN_COMMITTED |
Number(6,0) |
INTEGER NOT NULL |
Last Line Committed
|
| 42 |
OPRID |
Character(30) |
VARCHAR2(30) NOT NULL |
A user's ID (see PSOPRDEFN).
|
| 43 |
DTTM_STAMP_SEC |
DateTime(26) |
TIMESTAMP |
Specifies the date and time of the last update to an entry. This field is maintained by PeopleSoft and is used in a variety of contexts.
|
| 44 |
DESCR |
Character(30) |
VARCHAR2(30) NOT NULL |
Description
|
| 45 |
CURRENCY_CD |
Character(3) |
VARCHAR2(3) NOT NULL |
Currency Code
|
| 46 |
FOREIGN_CURRENCY |
Character(3) |
VARCHAR2(3) NOT NULL |
Foreign Currency Code
|
| 47 |
RT_TYPE |
Character(5) |
VARCHAR2(5) NOT NULL |
Defines a category of market rates for currency conversion. Some examples of rate types are commercial, average, floating, and historical.
|
| 48 |
CUR_EFFDT |
Date(10) |
DATE |
Specifies the effective date associated with the currency used as the base currency for the Business Unit on the Journal Entry Header.
|
| 49 |
RATE_DIV |
Number(16,8) |
DECIMAL(15,8) NOT NULL |
Rate Divisor
|
| 50 |
RATE_MULT |
Signed Number(17,8) |
DECIMAL(15,8) NOT NULL |
Rate Multiplier
|
| 51 |
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.
|
| 52 |
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.
|
| 53 |
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.
|
| 54 |
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.
|
| 55 |
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
|
| 56 |
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.
|
| 57 |
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
|
| 58 |
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
|
| 59 |
KK_TRAN_OVER_FLAG |
Character(1) |
VARCHAR2(1) NOT NULL |
Commitment Control source transaction override flag
N=No
Y=Yes
|
| 60 |
KK_TRAN_OVER_OPRID |
Character(30) |
VARCHAR2(30) NOT NULL |
Commitment Control source transaction override operator
|
| 61 |
KK_TRAN_OVER_DTTM |
DateTime(26) |
TIMESTAMP |
Commitment Control source transaction override datetime
|
| 62 |
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
|
| 63 |
JOURNAL_LOCKED |
Character(1) |
VARCHAR2(1) NOT NULL |
Journal Locked for Change
|
| 64 |
PROC_PART_ID |
Character(10) |
VARCHAR2(10) NOT NULL |
Process Partition ID
|
| 65 |
GL_ADJUST_TYPE |
Character(4) |
VARCHAR2(4) NOT NULL |
Adjustment Type
|
| 66 |
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.
Y/N Table Edit
Default Value: N
|
| 67 |
JOURNAL_DATE_ORIG |
Date(10) |
DATE |
Orignial Journal Date
|
| 68 |
JOURNAL_CLASS |
Character(10) |
VARCHAR2(10) NOT NULL |
Journal Class
|
| 69 |
KK_TRAN_BYPAS_FLAG |
Character(1) |
VARCHAR2(1) NOT NULL |
Bypass Budget Checking
|
| 70 |
EE_HDR_STATUS |
Character(1) |
VARCHAR2(1) NOT NULL |
Entry Event Header Status
|
| 71 |
IU_SYS_TRAN_CD |
Character(8) |
VARCHAR2(8) NOT NULL |
System Transactions are delivered system data, representing the activities that can require interunit or intraunit accounting entries.
|
| 72 |
IU_TRAN_CD |
Character(8) |
VARCHAR2(8) NOT NULL |
Transaction Codes are user-defined. They are mapped to the delivered System Transactions. InterUnit and IntraUnit Templates are keyed by Transaction code, allowing users to vary their accounting by transaction.
|
| 73 |
JRNL_CREATE_DTTM |
DateTime(26) |
TIMESTAMP |
Journal Creation Date Time
|
| 74 |
ALC |
Character(8) |
VARCHAR2(8) NOT NULL |
Agency Location Code
|
| 75 |
FED_DISTRIB_STATUS |
Character(1) |
VARCHAR2(1) NOT NULL |
GL Federal Reporting distribution status for SF 224.
0=Original Distribution
1=Supplemental 1 Distribution
2=Supplemental 2 Distribution
3=Supplemental 3 Distribution
4=Supplemental 4 Distribution
5=Supplemental 5 Distribution
6=Supplemental 6 Distribution
7=Supplemental 7 Distribution
8=Supplemental 8 Distribution
9=Supplemental 9 Distribution
N=Not Distributed
Default Value: N
|
| 76 |
DESCR254 |
Character(254) |
VARCHAR2(254) NOT NULL |
Description of length 254
|
| 77 |
ATTACHMENT_EXIST |
Character(1) |
VARCHAR2(1) NOT NULL |
Attachments Exist
N=N
Y=Y
|
| 78 |
SCE_ID |
Character(10) |
VARCHAR2(10) NOT NULL |
Scenario ID
|
| 79 |
SOURCE_DATA |
Character(1) |
VARCHAR2(1) NOT NULL |
Source Data Flag
|
| 80 |
GL_CTA |
Character(1) |
VARCHAR2(1) NOT NULL |
Classification Transactions
Default Value: N
|