| Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
|---|
| szItemNoUnknownFormat | UITM | char | OPT | NONE |
A number that the system assigns to an item. It can be in short, long, or third item number format. |
| szDescription001 | DL01 | char | OPT | NONE |
A user defined name or remark. |
| szCostCenterAlt | MMCU | char | OPT | 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. |
| mnUnitsBatchQuantity | BQTY | MATH_NUMERIC | OPT | 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. |
| 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. |
| jdEffectiveFromDate | EFFF | JDEDATE | OPT | 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. |
| jdEffectiveThruDate | EFFT | JDEDATE | OPT | 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. |
| szUnitOfMeasureAsInput | UOM | char | OPT | 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).
|
| szUnitOfMeasure | UM | char | OPT | 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. |
| cIssueTypeCode | ITC | char | OPT | NONE |
A code that indicates how the system issues each component in the bill of material from stock. In Shop Floor Management, it indicates how
the system issues a part to a work order. Valid values are:
I Manual issue
F Floor stock (there is no issue)
B Backflush (when the part is
reported as complete)
P Preflush (when the parts list is generated)
U Super backflush (at the pay-point operation)
S Sub-contract item (send
to supplier)
Blank Shippable end item
You can issue a component in more than one way within a specific branch/plant by using different
codes on the bill of material and the work order parts list. The bill of material code overrides the branch/plant value. |
| mnQtyRequiredStandard | QNTY | MATH_NUMERIC | OPT | NONE |
The number of units that the system applies to the transaction.
|
| mnSequenceNoOperations | 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. |
| cFixedOrVariableQty | FORQ | char | OPT | NONE |
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. |
| szErrorMessage | 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.
|
| cSuppressErrorMessages | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
| mnJobnumber | JOBS | MATH_NUMERIC | OPT | NONE |
The job number (work station ID) which executed the particular job. |
| idLastAddedPointer | GENLNG | ID | OPT | NONE |
General purpose ID variable. |
| cModeAddRetreive | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
| idHeaderElementPointer | GENLNG | ID | OPT | NONE |
General purpose ID variable. |
| 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.
|