Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
szPreviousCompanyKey | KCO | char | REQ | BOTH |
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. |
szNewCompanyKey | KCO | char | REQ | BOTH |
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. |
szPreviousDocumentType | DCT | char | REQ | BOTH |
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
|
szNewDocumentType | DCT | char | REQ | BOTH |
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
|
mnPreviousDocVoucherInvoiceE | DOC | MATH_NUMERIC | REQ | BOTH |
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. |
mnNewDocVoucherInvoiceE | DOC | MATH_NUMERIC | REQ | BOTH |
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. |
szVendorInvoiceNumber | VINV | char | REQ | BOTH |
The supplier's invoice number that is used for voucher entry. Voucher entry allows only one invoice per voucher number. If multiple invoice
numbers exist on a voucher, you must set them up as multiple vouchers or combine the invoices and enter them as one voucher. Depending
on how you have your accounts payable constants set, the system can do one of the following:
o Accept a duplicate invoice number
without warning or error
o Generate a warning message in which the duplicate invoice number can still be accepted
o Generate an error
message
Blank values are treated in the same manner as any other invoice number. Two blank invoice numbers are treated as duplicates.
To test
for duplicate invoice numbers that might have been entered in error, run the Suspected Duplicate Payments report (R04601).
Note: The
duplicate invoice number validation is not run for vouchers with document type NO. These vouchers are created by the Generate Reimbursements
program (R03B610).
|
jdDateInvoiceJ | DIVJ | JDEDATE | REQ | BOTH |
The date that either you or the system assigns to an invoice or voucher. This can be either the date of the supplier's invoice to you or the
date of your invoice to the customer. |
jdDateServiceCurrency | DSVJ | JDEDATE | REQ | BOTH |
A date that indicates when you purchased goods or services, or when you incurred a tax liability.
|
jdDateForGLandVoucherJULIA | DGJ | JDEDATE | REQ | BOTH |
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. |