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. |
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. |
mnOriginalLineNumber | LNID | MATH_NUMERIC | OPT | 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. |
mnNewLineNumber | LNID | MATH_NUMERIC | OPT | 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. |
mnOverrideIncrementValue | LNID | MATH_NUMERIC | OPT | 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. |
cSuppressErrorMessage | SUPPS | char | OPT | NONE |
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 | NONE |
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.
|
mnConfigParentJobNumber | JOBS | MATH_NUMERIC | OPT | NONE |
The job number (work station ID) which executed the particular job. |
szComputerID | CTID | char | OPT | NONE |
|
cProcessingMode | PROM | char | OPT | NONE |
The processing mode used to enter a contract. Values are:
1 Line Item. An individual commitment line item is maintained for the base
contract and each change order. You enter progress payments, using the Progress Payments Entry screen, on a line item by line item basis for
the base contract and each change order.
3 Account Method - Incremental. The system summarizes all line item amounts for the base
contract and each change order by account.
However, when you enter a change order, you enter the actual amount of the change order.
The system adds that amount to the existing total of the correct amount. You must enter all change order amounts as incremental contract
amounts. For example, if your base contract amount is 1000 and you add a change order for 143, you enter the change order amount as 143. This
lets you enter progress payments against an account total for the base contract and each change order, not just individual items. The
processing mode for a contract is specified in the processing options of the Contract Entry and Commitment Revisions screens when the contract is
entered. |
mnLineNumberKitMaster | KTLN | MATH_NUMERIC | OPT | NONE |
This line number indicates the relative sequence in which a component is added to a kit or single level bill of materials. For example, the
system automatically assigns a whole number to the kit master line, for example,
1.0000. Each component line is assigned a consecutive
subset of that line number, for example, the first component has line 1.010, and the second component has 1.020. |
mnRelatedKitComponent | RKIT | MATH_NUMERIC | OPT | NONE |
In the Sales Order Processing System, when a kit component is defined in the Bill of Materials Master (F3002) as a second level or higher
item, it will be grouped and stored in the Sales Order Detail File (F4211) under a related kit component. This relationship is maintained so that
the system can perform kit balancing on the kit throughout the order processing cycle.
For example, if a kit has the following structure in the
Bill of Materials:
Level 0 - A
Level 1 - B, C, D
Level 2 - B1, B2, D1, D2, D3
Level 3 - B11, B12
Components B1, B2, B11, and
B12 will be grouped under Related Item B. |