Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
cMatchType | MATC | char | NONE | NONE |
A code, attached to each purchase-order detail record or receipt record, that indicates whether a voucher exists and whether the voucher
or receipt record has been reversed. Valid values are:
1
No voucher exists.
2
A voucher exists.
3
The voucher has been reversed.
4
The receipt
record has been reversed.
Note: Record types 3 and 4 are audit records only; you cannot access these record types for the Voucher Match
program (P4314) or the PO Receipts program (P4312).
|
mnDocumentOrderInvoiceE | DOCO | MATH_NUMERIC | NONE | NONE |
A number that identifies an original document. This document can be a voucher, a sales order, an invoice, unapplied cash, a journal entry,
and so on. |
szOrderType | DCTO | char | NONE | NONE |
A user defined code (00/DT) that identifies the type of document. This code also indicates the origin of the transaction. J.D. Edwards has
reserved document type codes for vouchers, invoices, receipts, and time sheets, which create automatic offset entries during the post
program. (These entries are not self-balancing when you originally enter them.)
The following document types are defined by J.D. Edwards and
should not be changed:
P
Accounts Payable documents
R
Accounts Receivable documents
T
Payroll documents
I
Inventory documents
O
Purchase Order Processing documents
J
General Accounting/Joint Interest Billing documents
S
Sales Order Processing documents
|
szCompanyKeyOrderNo | KCOO | char | NONE | NONE |
A number that, along with order number and order type, uniquely identifies an order document (such as a purchase order, a contract, a
sales order, and so on).
If you use the Next Numbers by Company/Fiscal Year facility, the Automatic Next Numbers program (X0010) uses the
order company to retrieve the correct next number for that company. If two or more order documents have the same order number and order
type, the order company lets you locate the desired document.
If you use the regular Next Numbers facility, the order company is not used to
assign a next number. In this case, you probably would not use the order company to locate the document. |
szOrderSuffix | SFXO | char | NONE | NONE |
In the A/R and A/P systems, a code that corresponds to the pay item. In the Sales Order and Procurement systems, this code identifies
multiple transactions for an original order.
For purchase orders, the code is always 000.
For sales orders with multiple partial receipts against an
order, the first receiver used to record receipt has a suffix of 000, the next has a suffix of 001, the next 002, and so on. |
mnLineNumber | LNID | MATH_NUMERIC | NONE | NONE |
A number that identifies multiple occurrences, such as line numbers on a purchase order or other document. Generally, the system assigns
this number,but in some cases you can override it. |
jdDateForGLandVoucherJULIA | DGJ | JDEDATE | NONE | NONE |
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. |
szCurrencyCodeFrom | CRCD | char | NONE | NONE |
A code that identifies the currency of a transaction.
|
mnBatchNumber | ICU | MATH_NUMERIC | NONE | 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. |
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. |