| Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
|---|
| mnComponentShortItemNumber | ITM | MATH_NUMERIC | OPT | NONE |
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 |
| szComponentBranch | CMCU | char | OPT | NONE |
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) |
| jdAsOfDate | ASDE1 | JDEDATE | OPT | NONE |
The date used for effectivity checking. Enter a specific date to display documents (orders, bills of material, routings, as applicable) that are
effective on or after that date. The current system date is the default, but you can enter any future or past date. |
| szCostMethod | LEDG | char | OPT | NONE |
A user defined code (40/CM) that specifies the basis for calculating item costs. Cost methods 01 through 19 are reserved for J.D. Edwards
use.
|
| idCostRollupLinkedList | GENLNG | ID | OPT | NONE |
General purpose ID variable. |
| cSingleLevelBOM | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
| cProcessCoByProducts | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
| cMasterRoutingYN | MRYN | char | OPT | NONE |
An option that determines whether the system uses the master routing for an item or a routing defined for the parent item. Both routings are
retrieved from the Routing Master table (F3003).
If you choose to check for master routings, the Shop Floor Management system checks the
Item Cross Reference table (F4104), cross-reference type MR, for the parent item. If it finds a cross-reference, the program uses the master
routing from the Routing Master Table (F3003). If it does not find a cross-reference, the system uses the routing defined for the parent item. If
you do not choose to check for master routings, the program uses the parent item's routing from the Routing Master table.
For World:
Valid
values are:
Y Yes, use the master routing for an item, if one exists.
N No, do not check for a master routing for the item.
For OneWorld:
To specify
whether the system checks for cross-references and uses a master routing for the item, click the Master Routings option under the
BOM/Routing Options heading. |
| mnJobNumber | JOBS | MATH_NUMERIC | OPT | NONE |
The job number (work station ID) which executed the particular job. |
| szComputerID | CTID | char | OPT | NONE |
|
| szTypeBill | TBM | char | OPT | NONE |
A user defined code (40/TB) that designates the type of bill of material. You can define different types of bills of material for different uses.
For example:
M Standard manufacturing bill
RWK Rework bill
SPR Spare parts bill
The system enters bill type M in the work order
header when you create a work order, unless you specify another bill type. The system reads the bill type code on the work order header to
know which bill of material to use to create the work order parts list. MRP uses the bill type code to identify the bill of material to use when it
attaches MRP messages. Batch bills of material must be type M for shop floor management, product costing, and MRP processing. |