Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
mnOrderNumber | DOCO | MATH_NUMERIC | REQ | INPUT |
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 | REQ | INPUT |
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
|
szOrderCompany | KCOO | char | REQ | INPUT |
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 | REQ | INPUT |
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. |
mnOrderLineNumber | LNID | MATH_NUMERIC | REQ | INPUT |
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. |
mnReceiptLineNumber | NLIN | MATH_NUMERIC | REQ | INPUT |
A number representing the number of lines on either a purchase or sales order.
or The number of receivers recorded during the receipts
process. This field will be used in Voucher Matching. |
szLineType | LNTY | char | REQ | INPUT |
A code that controls how the system processes lines on a transaction. It controls the systems with which the transaction interfaces, such as
General Ledger, Job Cost, Accounts Payable, Accounts Receivable, and Inventory Management. It also specifies the conditions under
which a line prints on reports, and it is included in calculations. Codes include the following:
S
Stock item
J
Job cost
N
Nonstock item
F
Freight
T
Text information
M
Miscellaneous charges and credits
W
Work order |
mnDocNumber | DOC | MATH_NUMERIC | REQ | INPUT |
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 | REQ | INPUT |
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
|
szDocCompany | KCO | char | REQ | INPUT |
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. |
jdTransactionDate | TRDJ | JDEDATE | REQ | INPUT |
The date that an order was entered into the system. This date determines which effective level the system uses for inventory pricing. |
cSuppressErrorMessage | SUPPS | char | OPT | INPUT |
A flag indicating whether or not runtime error messaging will occur when an error message is issued from a business function.
0 = allow
runtime error message handling.
1 = suppress runtime error message handling. |
szErrorMessageId | DTAI | char | OPT | OUTPUT |
A code that identifies and defines a unit of information. It is an alphanumeric code up to 8 characters long that does not allow blanks or
special characters such as %, &, or +. You create new data items using system codes 55-59. You cannot change the alias.
|
cRolloverNotifyFlag | RNF | char | OPT | OUTPUT |
A code that indicates to the ERP system that the Encumbrance Rollover batch application should be re-run. Valid values are:
'1' - Re-run
the Encumbrance Rollover.
' ' - Do not need to re-run the Encumbrance Rollover.
|