Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
szCompany | CO | char | OPT | NONE |
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.
|
mnDocVoucherInvoiceE | DOC | MATH_NUMERIC | OPT | NONE |
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 | OPT | NONE |
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
|
mnAddressNumber | AN8 | MATH_NUMERIC | OPT | NONE |
A number that identifies an entry in the Address Book system, such as employee, applicant, participant, customer, supplier, tenant, or
location.
|
cActionCode | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
szGlClassByTaxArea1 | GL01 | char | OPT | NONE |
A code that indicates how to locate the tax account for general ledger entries. This field points to automatic accounting instructions (AAIs)
that, in turn, point to the tax account.
Examples are:
PTyyyy - for A/P (VAT only)
RTyyyy - for A/R (VAT only)
GTyyyy - for G/L (VAT
only)
4320 - for Sales Orders
4400 and 4410 - for Purchase Orders
When setting up VAT and Canadian GST, PTyyyy, RTyyyy, and
GTyyyy are the only valid values. For the A/P system, a second G/L Offset (PT_ _ _ _) is required when your tax setup involves VAT plus use
taxes (tax explanation code B). Use AAI PT_ _ _ _ to designate the use tax portion of the setup.
For sales taxes, the Accounts Payable and
Accounts Receivable systems ignore the values in this field. However, the Sales Order Management and Procurement systems require values in
this field. |
szGlClassByTaxArea2 | GL01 | char | OPT | NONE |
A code that indicates how to locate the tax account for general ledger entries. This field points to automatic accounting instructions (AAIs)
that, in turn, point to the tax account.
Examples are:
PTyyyy - for A/P (VAT only)
RTyyyy - for A/R (VAT only)
GTyyyy - for G/L (VAT
only)
4320 - for Sales Orders
4400 and 4410 - for Purchase Orders
When setting up VAT and Canadian GST, PTyyyy, RTyyyy, and
GTyyyy are the only valid values. For the A/P system, a second G/L Offset (PT_ _ _ _) is required when your tax setup involves VAT plus use
taxes (tax explanation code B). Use AAI PT_ _ _ _ to designate the use tax portion of the setup.
For sales taxes, the Accounts Payable and
Accounts Receivable systems ignore the values in this field. However, the Sales Order Management and Procurement systems require values in
this field. |
szGlClassByTaxArea3 | GL01 | char | OPT | NONE |
A code that indicates how to locate the tax account for general ledger entries. This field points to automatic accounting instructions (AAIs)
that, in turn, point to the tax account.
Examples are:
PTyyyy - for A/P (VAT only)
RTyyyy - for A/R (VAT only)
GTyyyy - for G/L (VAT
only)
4320 - for Sales Orders
4400 and 4410 - for Purchase Orders
When setting up VAT and Canadian GST, PTyyyy, RTyyyy, and
GTyyyy are the only valid values. For the A/P system, a second G/L Offset (PT_ _ _ _) is required when your tax setup involves VAT plus use
taxes (tax explanation code B). Use AAI PT_ _ _ _ to designate the use tax portion of the setup.
For sales taxes, the Accounts Payable and
Accounts Receivable systems ignore the values in this field. However, the Sales Order Management and Procurement systems require values in
this field. |
mnAmtTaxLine1 | STAM | MATH_NUMERIC | OPT | BOTH |
The amount assessed and payable to tax authorities. It is the total of the VAT, use, and sales taxes (PST). |
mnAmtTaxLine2 | STAM | MATH_NUMERIC | OPT | BOTH |
The amount assessed and payable to tax authorities. It is the total of the VAT, use, and sales taxes (PST). |
mnAmtTaxLine3 | STAM | MATH_NUMERIC | OPT | BOTH |
The amount assessed and payable to tax authorities. It is the total of the VAT, use, and sales taxes (PST). |