Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
mnShortItemNumber | ITM | MATH_NUMERIC | OPT | INPUT |
An inventory item number. The system provides three separate item numbers plus an extensive cross-reference capability to other item
numbers (see data item XRT) to accommodate substitute item numbers, replacements, bar codes, customer numbers, supplier numbers, and
so forth. The item numbers are as follows:
o Item Number (short) - An eight-digit, computer-assigned item number
o 2nd Item Number - The
25-digit, free-form, user defined alphanumeric item number
o 3rd Item Number - Another 25-digit, free-form, user defined alphanumeric item
number |
szDemandBranch | MCU | char | OPT | INPUT |
An alphanumeric code that identifies a separate entity within a business for which you want to track costs. For example, a business unit
might be a warehouse location, job, project, work center, branch, or plant.
You can assign a business unit to a document, entity, or person for
purposes of responsibility reporting. For example, the system provides reports of open accounts payable and accounts receivable by
business unit to track equipment by responsible department.
Business unit security might prevent you from viewing information about business units
for which you have no authority.
|
szSupplyBranch | MMCU | char | OPT | INPUT |
A code that represents a high-level business unit. Use this code to refer to a branch or plant that might have departments or jobs, which
represent lower-level business units, subordinate to it. For example:
o Branch/Plant (MMCU)
o Dept A (MCU)
o Dept B (MCU)
o Job 123
(MCU)
Business unit security is based on the higher-level business unit. |
cMessageType | MSGT | char | OPT | INPUT |
A code that distinguishes different messages generated in the Distribution Requirements Planning/Master Production Schedule/Material
Requirements Planning system. Valid codes are:
A Warning messages (user controlled)
B Order and expedite
C Cancel
D Defer
E
Expedite
F Frozen order (user controlled)
G Increase order quantity to (user controlled)
H Decrease rate quantity to
I Increase rate quantity to
L Decrease order quantity to (user controlled)
M Manual reminder
N Create rate
O Order
P Firm order
S FPO adjustment suggestion
T Past due order |
szOrderKeyCompany | KCOO | char | OPT | 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. |
mnDocumentNumber | DOCO | MATH_NUMERIC | OPT | 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. |
szDocumentType | DCTO | char | OPT | 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
|
cMessageTypeFlag | EV01 | char | OPT | INPUT |
An option that specifies the type of processing for an event.
|
mnLineID | LNID | MATH_NUMERIC | OPT | 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. |
szOrderSuffix | SFXO | char | OPT | 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. |
szDescription | DSC1 | char | OPT | INPUT |
Brief information about an item; a remark or an explanation.
|
mnTransactionQuantity | TRQT | MATH_NUMERIC | OPT | INPUT |
A value that represents the available quantity, which might consist of the on-hand balance minus commitments, reservations, and
backorders. You enter this value in the Branch/Plant Constants program (P41001).
|
mnSupplier | VEND | MATH_NUMERIC | OPT | INPUT |
The address book number of the preferred provider of this item. |
jdStartDate | RSTJ | JDEDATE | OPT | INPUT |
The recommended start date for an order. |
jdCompleteDate | RRQJ | JDEDATE | OPT | INPUT |
The completion date planned for this order. |
cErrorCode | EV01 | char | OPT | INPUT |
An option that specifies the type of processing for an event.
|
szErrorMessageID | DTAI | char | OPT | INPUT |
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.
|
cMode | EV01 | char | OPT | INPUT |
An option that specifies the type of processing for an event.
|
cOverrideStockingType | OSTT | char | OPT | INPUT |
|