Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
cCacheActionCode | EV01 | char | REQ | OUTPUT |
An option that specifies the type of processing for an event.
|
nIndexNumber | INT01 | integer | OPT | OUTPUT |
Number of Days in Future to Query for Responses Due.
|
nNumberOfKeys | INT01 | integer | REQ | OUTPUT |
Number of Days in Future to Query for Responses Due.
|
cReturnCursor | EV01 | char | OPT | OUTPUT |
An option that specifies the type of processing for an event.
|
idCursor | GENLNG | ID | OPT | BOTH |
General purpose ID variable. |
cCacheCodeError | EV01 | char | OPT | INPUT |
An option that specifies the type of processing for an event.
|
cSuppressErrorMessages | EV01 | char | OPT | OUTPUT |
An option that specifies the type of processing for an event.
|
szErrorMessageID | DTA1 | char | OPT | INPUT |
A 256 byte field used to hold miscellaneous data. |
mnJobnumber | JOBS | MATH_NUMERIC | REQ | OUTPUT |
The job number (work station ID) which executed the particular job. |
mnDocumentOrderInvoiceE | DOCO | MATH_NUMERIC | OPT | BOTH |
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 | BOTH |
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
|
mnUniqueKeyID | UKID | MATH_NUMERIC | OPT | BOTH |
This field is a unique number used to identify a record in a file. |
mnComponentItemNumber | ITM | MATH_NUMERIC | OPT | BOTH |
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 |
szComponent2ndItemNumber | LITM | char | OPT | BOTH |
A number that identifies the item. The system provides three separate item numbers plus an extensive cross-reference capability to
alternative item numbers. The three types of item numbers are:
Item Number (short)
An 8-digit, computer-assigned item number.
2nd Item Number
A
25-digit, user defined, alphanumeric item number.
3rd Item Number
Another 25-digit, user defined, alphanumeric item number.
In addition to
these three basic item numbers, the system provides an extensive cross-reference search capability. You can define numerous
cross-references to alternative part numbers. For example, you can define substitute item numbers, replacements, bar codes, customer numbers, or
supplier numbers.
|
szComponentBranchPlant | CMCU | char | OPT | BOTH |
A secondary or lower-level business unit. The system uses the value that you enter to indicate that a branch or plant contains several
subordinate departments or jobs. For example, assume that the component branch is named MMCU. The structure of MMCU might be as follows:
Branch/Plant - (MMCU)
Dept A - (MCU)
Dept B - (MCU)
Job 123 - (MCU) |
szComponentDescription | DSC1 | char | OPT | BOTH |
Brief information about an item; a remark or an explanation.
|
mnWorkOrderNumber | DOCO | MATH_NUMERIC | OPT | BOTH |
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. |
mnParentItemNumber | KIT | MATH_NUMERIC | OPT | BOTH |
The system provides for three separate item numbers.
1. Item Number (short) - An eight-digit, computer assigned, completely
non-significant item number.
2. 2nd Item Number - The 25-digit, free form, user defined alphanumeric item number.
3. 3rd Item Number - Another
25-digit, free form, user defined alphanumeric item number. |
szParentBranchPlant | MMCU | char | OPT | BOTH |
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. |
cStockingType | STKT | char | OPT | BOTH |
A user defined code (41/I) that indicates how you stock an item, for example, as finished goods or as raw materials. The following stocking
types are hard-coded and you should not change them:
0 Phantom item
B Bulk floor stock
C Configured item
E Emergency/corrective
maintenance
F Feature
K Kit parent item
N Nonstock
The first character of Description 2 in the user defined code table indicates if the item
is purchased (P) or manufactured (M). |
szLineType | LNTY | char | OPT | BOTH |
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 |
cInInterfaceFlgDistri | IVI | char | OPT | BOTH |
A code that identifies the type of interface to the Inventory Management system. Valid values are:
Y The dollar or unit value of any activity
containing this line type will be reflected in inventory. The system also edits the item that you enter to ensure that it is a valid item. Y is the
default.
A The system recognizes the number that you enter as a G/L account number. The system uses this code in purchasing only.
B The
system performs edits when using format 4 in purchase order entry.
The system retrieves price data from the inventory tables, but does not
update the quantity on the purchase order. This code is valid only when you have set the G/L Interface field to Y (yes). Budget checking is
fully functional when you use this interface code.
D The item in this line is an inventory item that will not affect availability or quantities.
N The
item is not an inventory item.
To verify whether the item exists in the Item Master file, use Inventory Interface N in conjunction with the flag, Edit
the Item Master for Non-Stock Items. |
cFixedOrVariableQty | FORQ | char | OPT | BOTH |
A code that indicates if the quantity per assembly for an item on the bill of material varies according to the quantity of the parent item
produced or is fixed regardless of the parent quantity. This value also determines if the component quantity is a percent of the parent quantity. Valid
values are:
F Fixed Quantity
V Variable Quantity (default)
% Quantities are expressed as a percentage and must total 100%For
fixed-quantity components, the Work Order and Material Requirements Planning systems do not extend the component's quantity per assembly
value by the order quantity. |
szUnitOfMeasureAsInput | UOM | char | OPT | BOTH |
A user defined code (00/UM) that indicates the quantity in which to express an inventory item, for example, CS (case) or BX (box).
|
jdDateRequestedJulian | DRQJ | JDEDATE | OPT | BOTH |
The date that an item is scheduled to arrive or that an action is scheduled for completion.
|
jdDateStart | STRT | JDEDATE | OPT | BOTH |
The start date for the order. You can enter this date manually, or have the system calculate it using a backscheduling routine. The routine
starts with the required date and offsets the total leadtime to calculate the appropriate start date.
|
mnBeginningHhMmSs | PBTM | MATH_NUMERIC | OPT | BOTH |
A field that is used to enter the beginning time of the operation sequence for the work center operation on the routing.
|
szItemType | GS3A | char | OPT | BOTH |
|
szLocation | LOCN | char | OPT | BOTH |
The storage location from which goods will be moved. |
szLot | LOTN | char | OPT | BOTH |
A number that identifies a lot or a serial number. A lot is a group of items with similar characteristics. |
mnStepScrapPercent | STPP | MATH_NUMERIC | OPT | BOTH |
A value that the system uses to increase or decrease the amount of materials to account for loss within the operation. The system updates
this value on Enter/Change Bill of Material when you run the Planned Yield Update program.
The system calculates this value by
compounding the yield percentages from the last operation to the first operation. Use a processing option in Enter/Change Routing to enable the
system to calculate the component scrap percent. |
szRelatedOrderNumber | RORN | char | OPT | BOTH |
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.
|
szRelatedCompanyKey | RKCO | char | OPT | BOTH |
The key company that is associated with the document number of the related order.
|
szRelatedOrderType | RCTO | char | OPT | BOTH |
A user defined code (system 00, type DT) that indicates the document type of the secondary or related order. For example, a purchase
order might be document type OP and might have been created to fill a related work order with document type WO. |
mnRelatedLineNumber | RLLN | MATH_NUMERIC | OPT | BOTH |
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. |
szComponentSequenceID | ATSQ | char | OPT | BOTH |
Reserved by J.D. Edwards
A string that is generated to uniquely identify and sequence items in a configuration.
|
szComponent3rdItemNumber | AITM | char | OPT | BOTH |
The system provides three separate item numbers plus an extensive cross-reference capability to alternate item numbers. These item
numbers are as follows:
1. Item Number (short) - An 8-digit, computer-assigned item number.
2. 2nd Item Number - The 25-digit, free-form, user
defined alphanumeric item number.
3. 3rd Item Number - Another 25-digit, free-form, user defined alphanumeric item number.
In addition to
these three basic item numbers, an extensive cross-reference search capability has been provided (see XRT). Numerous cross references to
alternate part numbers can be user defined, such as substitute item numbers, replacements, bar codes, customer numbers, or supplier
numbers. |
mnQuantityPer | QNTY | MATH_NUMERIC | OPT | BOTH |
The number of units that the system applies to the transaction.
|
mnQuantity | UORG | MATH_NUMERIC | OPT | BOTH |
The quantity of units affected by this transaction.
|
mnOperationSequenceNumber | OPSQ | MATH_NUMERIC | OPT | BOTH |
A number used to indicate an order of succession.
In routing instructions, a number that sequences the fabrication or assembly steps in the
manufacture of an item. You can track costs and charge time by operation.
In bills of material, a number that designates the routing step in the
fabrication or assembly process that requires a specified component part. You define the operation sequence after you create the routing
instructions for the item. The Shop Floor Management system uses this number in the backflush/preflush by operation process.
In engineering
change orders, a number that sequences the assembly steps for the engineering change.
For repetitive manufacturing, a number that
identifies the sequence in which an item is scheduled to be produced.
Skip To fields allow you to enter an operation sequence that you want to begin
the display of information.
You can use decimals to add steps between existing steps. For example, use 12.5 to add a step between steps
12 and 13. |
szWOStatus | SRST | char | OPT | BOTH |
A user defined code (00/SS) that describes the status of a work order, rate schedule, or engineering change order. Any status change from
90 through 99 triggers the system to automatically update the completion date.
|
nCacheRowNumber | INT01 | integer | OPT | NONE |
Number of Days in Future to Query for Responses Due.
|
cActionType | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
mnRecordCount | MATH01 | MATH_NUMERIC | OPT | NONE |
- - - Good Performance Low Value.
|
mnOrigOperationSequence | OPSQ | MATH_NUMERIC | OPT | NONE |
A number used to indicate an order of succession.
In routing instructions, a number that sequences the fabrication or assembly steps in the
manufacture of an item. You can track costs and charge time by operation.
In bills of material, a number that designates the routing step in the
fabrication or assembly process that requires a specified component part. You define the operation sequence after you create the routing
instructions for the item. The Shop Floor Management system uses this number in the backflush/preflush by operation process.
In engineering
change orders, a number that sequences the assembly steps for the engineering change.
For repetitive manufacturing, a number that
identifies the sequence in which an item is scheduled to be produced.
Skip To fields allow you to enter an operation sequence that you want to begin
the display of information.
You can use decimals to add steps between existing steps. For example, use 12.5 to add a step between steps
12 and 13. |
mnConfigurationID | CFGID | MATH_NUMERIC | OPT | NONE |
An identifier that represents a unique configuration. It is generated by a next number value and is the key to the configuration tables.
|
mnConfigComponentID | CFGCID | MATH_NUMERIC | OPT | NONE |
A number that represents a component in a configuration. This number, which is generated by next numbers, always restarts at 1 and
increments, based on the number of components in the configuration.
|