Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
szVersion | VERS | char | NONE | NONE |
A user-defined set of specifications that control how applications and reports run. You use versions to group and save a set of user-defined
processing option values and data selection and sequencing options. Interactive versions are associated with applications (usually as a
menu selection). Batch versions are associated with batch jobs or reports. To run a batch process, you must choose a version. |
cPayStatusCode | PST | char | NONE | NONE |
A user defined code (00/PS) that indicates the current payment status for a voucher or an invoice. Examples of codes include:
A
Approved
for payment but not yet paid
H
Held pending approval
P
Paid
Note: Some of the payment status codes are hard coded; the system assigns
the code.
|
cPayStatusCode_2 | PST | char | NONE | NONE |
A user defined code (00/PS) that indicates the current payment status for a voucher or an invoice. Examples of codes include:
A
Approved
for payment but not yet paid
H
Held pending approval
P
Paid
Note: Some of the payment status codes are hard coded; the system assigns
the code.
|
szCompanyKey | KCO | char | NONE | NONE |
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. |
szDocumentType | DCT | char | NONE | 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
|
mnDocVoucherInvoiceE | DOC | MATH_NUMERIC | NONE | 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. |
szDocumentPayItem | SFX | char | NONE | NONE |
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. |
cEverestEventPoint01 | EV01 | char | NONE | NONE |
An option that specifies the type of processing for an event.
|
cEverestEventPoint02 | EV02 | char | NONE | NONE |
An option that specifies the type of processing for an event.
|