Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
szCompany | CO | char | REQ | INPUT |
A code that identifies a specific organization, fund, or other reporting entity. The company code must already exist in the Company
Constants table (F0010) and must identify a reporting entity that has a complete balance sheet. At this level, you can have intercompany
transactions.
Note: You can use company 00000 for default values such as dates and automatic accounting instructions. You cannot use company 00000
for transaction entries.
|
szObjectAccount | OBJ | char | REQ | INPUT |
The portion of a general ledger account that refers to the division of the Cost Code (for example, labor, materials, and equipment) into
subcategories. For example, you can divide the Cost Code for labor into regular time, premium time, and burden.
Note: If you use a flexible chart of
accounts and the object account is set to 6 digits, J.D. Edwards recommends that you use all 6 digits. For example, entering 000456 is not
the same as entering 456 because if you enter 456 the system enters three blank spaces to fill a 6-digit object. |
szSubsidiary | SUB | char | REQ | INPUT |
A subset of an object account. Subsidiary accounts include detailed records of the accounting activity for an object account.
|
cGLPostedCode | POST | char | REQ | INPUT |
A code the system uses to determine whether a transaction is available for the post process. Valid codes
are:
Blank
Unposted.
D
Posted.
P
Posted or posting. Depending on the type of transaction, this code has different meanings. If the code is assigned to an Account Ledger
record (F0911), it indicates a posted status. If the code is assigned to any other transaction, it indicates that the system attempted to post the
record but failed, due to an error it encountered.
M
Model. The transaciton is a model journal entry.
|
mnDocVoucherInvoiceE | DOC | MATH_NUMERIC | REQ | INPUT |
A number that identifies the original document, such as a voucher, invoice, or journal entry. On entry forms, you can assign the document
number or let the system assign it using the Next Numbers program (P0002). Matching document numbers (DOCM) identify related documents
in the Accounts Receivable and Accounts Payable systems. Examples of original and matching documents are:
Accounts Payable
o
Original document - voucher
o Matching document - payment
Accounts Receivable
o Original document - invoice
o Matching document -
receipt
Note: In the Accounts Receivable system, the following transactions simultaneously generate original and matching documents:
deductions, unapplied receipts, chargebacks, and drafts. |
szDocumentType | DCT | char | REQ | INPUT |
A user defined code (00/DT) that identifies the origin and purpose of the transaction. PeopleSoft reserves several prefixes for document
types, such as, vouchers, invoices, receipts, and timesheets. The reserved document type prefixes for codes are:
P
Accounts payable
documents
R
Accounts receivable documents
T
Time and Pay documents
I
Inventory documents
O
Purchase order documents
S
Sales order
documents
|
szCompanyKey | KCO | char | REQ | INPUT |
A number that, with the document number, document type and G/L date, uniquely identifies an original document, such as invoice, voucher,
or journal entry.
If you use the Next Numbers by Company/Fiscal Year feature, the Automatic Next Numbers program (X0010) uses the
document company to retrieve the correct next number for that company.
If two or more original documents have the same document number and
document type, you can use the document company to locate the desired document. |
jdDateForGLandVoucherJULIA | DGJ | JDEDATE | REQ | INPUT |
A date that identifies the financial period to which the transaction will be posted. You define financial periods for a date pattern code that you
assign to the company record. The system compares the date that you enter on the transaction to the fiscal date pattern assigned to the
company to retrieve the appropriate fiscal period number, as well as to perform date validations. |
mnJournalEntryLineNo | JELN | MATH_NUMERIC | REQ | INPUT |
A number that designates a line within a journal entry. The system uses this field to sequence the journal entry lines for inquiry purposes. |
szLineExtensionCode | EXTL | char | REQ | INPUT |
Line Extension Code |
cBatchRearEndPostCode | BRE | char | REQ | OUTPUT |
The valid post codes for fixed asset transactions are as follows:
Blank
Unposted. Transaction has not yet been posted to the Asset Account
Balances File table (F1202).
P
Pass. Transaction does not fall within the FX range of accounts as set up in automatic accounting instructions
(AAIs) and will not post to fixed assets. You can manually update this field to P through the Revise Unposted Entries program (P12102). Use
P in this field when the account number is within the fixed asset range of accounts, but you do not want the transaction to post to fixed assets.
You can change this field from blank to P or from P to blank.
*
Posted. Transaction has been posted to the Item Balances table. You cannot
change this value. |
szLedgerType | LT | char | REQ | INPUT |
A user defined code (09/LT) that specifies the type of ledger, such as AA (Actual Amounts), BA (Budget Amount), or AU (Actual Units). You
can set up multiple, concurrent accounting ledgers within the general ledger to establish an audit trail for all transactions.
|