Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
cActionCode | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
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
|
szCompanyKey | KCO | char | OPT | 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. |
szDocumentPayItem | SFX | char | OPT | 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. |
mnPaymentID | PYID | MATH_NUMERIC | OPT | NONE |
A number that the system assigns from Next Numbers to identify and track payment records. |
mnFileLineIdentifier50 | RC5 | MATH_NUMERIC | OPT | NONE |
This field is used to create a unique key within a file and should be used with a next number approach. |
szDocTypeMatching | DCTM | char | OPT | NONE |
Within Auto Bank Statement process, a document type is needed for the following:
1) Document Type is needed for creating Variance
Journal Entries for payments, receipts, and journal entries when running the Auto Bank Statement Process (R09616). If Document Type on the
Payment Clear tab is left blank, it will default to PN. If Document Type on the Receipt Clear tab is left blank, it will default to RC. If Document
Type on the Journal Entry Reconcile tab is left blank, it will default to JE.
2) Document Type is needed for creating Journal Entries on the
Journal Entry Create tab, and the Draft Paid tab. For both of these, it will default to JE if left blank.
|
cReturnStatus | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
mnBatchNumber | ICU | MATH_NUMERIC | OPT | NONE |
A number that identifies a group of transactions that the system processes and balances as a unit. When you enter a batch, you can either
assign a batch number or let the system assign it using the Next Numbers program. |
szBatchType | ICUT | char | OPT | NONE |
A code that specifies the system and type of transactions entered in a batch. The system assigns the value when you enter a transaction.
Valid values are set up in user defined code table 98/IT. You cannot assign new values. All batch types are hard coded. |