Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
cEdiTransactionAction | EDTC | char | OPT | NONE |
Code that identifies what the system should do with a transaction during final processing. Valid codes are:
A Add a new transaction
D
Delete an unprocessed transaction
This field controls what happens to an address in the F0101 file when you run the Batch Address Processing
program.
There are two action code fields on this screen. Note that the action code field under Transaction Information is different from the
action code under Batch Control. |
szEdiUserId | EDUS | char | OPT | NONE |
The source of the transaction. This can be a user ID, a workstation, the address of an external system, a node on a network, and so on. This
field helps identify both the transaction and its point of origin. |
szEdiBatchNumber | EDBT | char | OPT | NONE |
The number that the transmitter assigns to the batch. During batch processing, the system assigns a new batch number to the PeopleSoft
transactions for each control (user) batch number it finds.
|
szEdiTransactNumber | EDTN | char | OPT | NONE |
The number that an Electronic Data Interchange (EDI) transmitter assigns to a transaction. In a non-EDI environment, you can assign any
number that is meaningful to you to identify a transaction within a batch. It can be the same as a J.D. Edwards document number. |
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
|
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. |
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. |
cErrorF0411EditDoc | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|