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.
|
szVoucherDocumentType | 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
|
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. |
szVoucherCompanyKey | 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. |
szVoucherSuffix | SFX | char | REQ | INPUT |
A number that identifies the pay item for a voucher or an invoice. The system assigns the pay item number. If the voucher or invoice has
multiple pay items, the numbers are sequential. |
szPaymentTermsCode01 | PTC | char | REQ | INPUT |
A code that specifies the terms of payment, including the percentage of discount available if the invoice is paid by the discount due date.
Use a blank code to indicate the most frequently-used payment term. You define each type of payment term on the Payment Terms Revisions
form. Examples of payment terms include:
Blank
Net 15
001
1/10 net 30
002
2/10 net 30
003
Due on the 10th day of every month
006
Due upon receipt
This code prints on customer invoices.
|
mnVendorNumber | AN8 | MATH_NUMERIC | REQ | INPUT |
A number that identifies an entry in the Address Book system, such as employee, applicant, participant, customer, supplier, tenant, or
location.
|
cPaymentInstrument | PYIN | char | REQ | INPUT |
A user defined code (00/PY) that determines the means by which a payment is issued to a supplier or received from the customer.
Examples of payment instruments include check, electronic funds transfer, lockbox, and EDI.
|
mnPaymentGroupControlNbr | HDC | MATH_NUMERIC | REQ | INPUT |
The Payment Control Group Number is used to group all payments and payment detail together in the A/P payments work files. This
number identifies a group of payments run for the same bank account, payment instrument, DREAM Writer version, Originator ID and currency. |
mnPaymentNumber | CKC | MATH_NUMERIC | REQ | INPUT |
The Check Control Number is used to group all A/P payment transactions for each individual check. |
cSuppressVoucherPayment | EV01 | char | OPT | BOTH |
An option that specifies the type of processing for an event.
|