| Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
|---|
| idHRequest | GENLNG | ID | NONE | NONE |
General purpose ID variable. |
| szParentBranch | MMCU | char | NONE | NONE |
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. |
| mnParentItem | KIT | MATH_NUMERIC | NONE | NONE |
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. |
| szTypeBill | TBM | char | NONE | 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. |
| mnBatchQuantity | BQTY | MATH_NUMERIC | NONE | NONE |
The quantity of finished units that you expect this bill of material or routing to produce. You can specify varying quantities of components
based on the amount of finished goods produced. For example, 1 ounce of solvent is required per unit up to 100 units of finished product.
However, if 200 units of finished product is produced, 2 ounces of solvent are required per finished unit. In this example, you would set up batch
quantities for 100 and 200 units of finished product, specifying the proper amount of solvent per unit. |
| szBatchQuantityUOM | UOM | char | NONE | NONE |
A user defined code (00/UM) that indicates the quantity in which to express an inventory item, for example, CS (case) or BX (box).
|
| szLevel | INDL | char | NONE | NONE |
A number indicating the level of a child in the relationship to its parent in a hierarchy. |
| szComponentBranch | CMCU | char | NONE | 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) |
| mnComponentItem | KIT | MATH_NUMERIC | NONE | NONE |
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. |
| mnQuantityRequired | QNTY | MATH_NUMERIC | NONE | NONE |
The number of units that the system applies to the transaction.
|
| szUnitOfMeasure | UM | char | NONE | NONE |
A user defined code (00/UM) that identifies the unit of measurement for an amount or quantity. For example, it can represent a barrel, box,
cubic meter, liter, hour, and so on. |
| mnOperationsSequenceNo | OPSQ | MATH_NUMERIC | NONE | 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. |
| szLineType | LNTY | char | NONE | NONE |
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 |
| jdEffectiveFrom | EFFF | JDEDATE | NONE | NONE |
A date that indicates one of the following:
o When a component part goes into effect on a bill of material
o When a routing step goes into
effect as a sequence on the routing for an item
o When a rate schedule is in effect The default is the current system date. You can enter
future effective dates so that the system plans for upcoming changes. Items that are no longer effective in the future can still be recorded and
recognized in Product Costing, Shop Floor Management, and Capacity Requirements Planning. The Material Requirements Planning system
determines valid components by effectivity dates, not by the bill of material revision level. Some forms display data based on the effectivity
dates you enter. |
| jdEffectiveThru | EFFT | JDEDATE | NONE | NONE |
A date that indicates one of the following:
o When a component part is no longer in effect on a bill of material
o When a routing step is no
longer in effect as a sequence on the routing for an item
o When a rate schedule is no longer active The default is December 31 of the
default year defined in the Data Dictionary for Century Change Year. You can enter future effective dates so that the system plans for upcoming
changes. Items that are no longer effective in the future can still be recorded and recognized in Product Costing, Shop Floor Management,
and Capacity Requirements Planning. The Material Requirements Planning system determines valid components by effectivity dates, not by
the bill of material revision level. Some forms display data based on the effectivity dates you enter. |
| jdAsOfDate | ASDE1 | JDEDATE | NONE | 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. |
| szSecondItemNumber | LITM | char | NONE | NONE |
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.
|
| szThirdItemNumber | AITM | char | NONE | NONE |
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. |
| cCoByProducts | COBY | char | NONE | NONE |
A code that distinguishes standard components or ingredients from co-products,by-products, and intermediates. Co-products are
(concurrent) end items as the result of a process. By-products are items that can be produced at any step of a process, but were not planned.
Intermediate products are items defined as a result of a step but are automatically consumed in the following step.
Generally, intermediates are
nonstock items and are only defined steps with a pay-point for reporting purposes. Standard components (Discrete Manufacturing)
or ingredients
(Process Manufacturing) are consumed during the production process. Valid values are:
C Co-products
B By-products
I Intermediate
products
Blank Standard components or ingredients |
| cTextYN | TXYN | char | NONE | NONE |
A code that indicates whether the information with this order line type contains only text information.
In World software, valid values are:
Y
This line contains only text information.
N This line contains more than text information.
In OneWorld, a checkmark indicates that the
information with this order line type contains only text information. |
| cInventoryInterfaceYN | IVI | char | NONE | NONE |
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. |
| cRecordFound | EV01 | char | NONE | NONE |
An option that specifies the type of processing for an event.
|
| mnComponentLineNumber | CPNB | MATH_NUMERIC | OPT | NONE |
A number that specifies how the system displays the sequence of components on a single-level bill of material. This number initially
indicates the sequence in which a component was added to the bill of material. You can modify this number to change the sequence in which the
components appear.
|