| Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
|---|
| mnDocumentOrderInvoiceE | DOCO | MATH_NUMERIC | OPT | 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. |
| cDocumentType | TFLAG | char | OPT | NONE |
This is a hard coded UDC used to define whether a record in a table is a Case or a Work Order.
|
| mnSequenceNumber | CSEQN | MATH_NUMERIC | OPT | NONE |
A sequence number that indicates the number of associations for a case.
|
| cAssociationType | ASTYP | char | OPT | NONE |
Code indicates the type of association for a case.
|
| mnScriptInstanceId | SCRINSID | MATH_NUMERIC | OPT | NONE |
An ID that uniquely identifies a script instance.
|
| mnDocumentOrderInvoi | DOC1 | MATH_NUMERIC | OPT | NONE |
The document number associated with a given document type. |
| szOrderType | DCTO | char | OPT | 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 | OPT | 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. |
| mnLeadId | LEADID | MATH_NUMERIC | OPT | NONE |
A unique identifier for a lead (F90CB010).
|
| mnRelatedPoSoLineNo | RLLN | MATH_NUMERIC | OPT | NONE |
A number of the detail line on the related order for which the current order was created. For example, on a purchase order created to fill
open sales orders, this is the line number of the sales order on which the item you are ordering appears. |
| szCreatedByUser | CRTU | char | OPT | NONE |
The address book number of the user who created this record.
|
| szRelatedPoSoNumber | RORN | char | OPT | NONE |
A number that identifies a secondary purchase order, sales order, or work order that is associated with the original order. This number is for
informational purposes only.
|
| szProgramId | PID | char | OPT | NONE |
The number that identifies the batch or interactive program (batch or interactive object). For example, the number of the Sales Order Entry
interactive program is P4210, and the number of the Print Invoices batch process report is R42565.
The program ID is a variable length value.
It is assigned according to a structured syntax in the form TSSXXX, where:
T
The first character of the number is alphabetic and identifies the
type, such as P for Program, R for Report, and so on. For example, the value P in the number P4210 indicates that the object is a
program.
SS
The second and third characters of the number are numeric and identify the system code. For example, the value 42 in the number P4210
indicates that this program belongs to system 42, which is the Sales Order Processing system.
XXX
The remaining characters of the numer are
numeric and identify a unique program or report. For example, the value 10 in the number P4210 indicates that this is the Sales Order Entry
program.
|