Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
szJobNumber | JOB | char | OPT | NONE |
Job Number |
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. |
mnItemNumberShortKit | KIT | MATH_NUMERIC | OPT | 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. |
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. |
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).
|
mnIdentifierShortItem | 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 |
szBranchComponent | 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) |
mnQtyRequiredStandard | QNTY | MATH_NUMERIC | OPT | NONE |
The number of units that the system applies to the transaction.
|
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. |
mnQuantityPrimary | MATH01 | MATH_NUMERIC | OPT | NONE |
- - - Good Performance Low Value.
|
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. |
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. |
mnFeaturePlannedPercent | FTRP | MATH_NUMERIC | OPT | NONE |
The percentage of demand for a specified feature based on projected production. For example, a company might produce 65% of their
lubricant with high viscosity, and 35% with low viscosity, based on customer demand.
The Material Planning system uses this percentage to
accurately plan for a process's co-products and by-products. Enter percentages as whole numbers, for example, enter 5% as 5.0. The default
value is 0%. |
mnStepScrapPercent | STPP | MATH_NUMERIC | OPT | NONE |
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. |
mnPercentOfScrap | SCRP | MATH_NUMERIC | OPT | NONE |
The percentage of unusable component material that is created during the manufacture of a particular parent item.
During DRP/MPS/MRP
generation, the system increases gross requirements for the component item to compensate for the loss.
Note: Shrink is the expected loss of
parent items (and hence, components) due to the manufacturing process. Shrink and scrap are compounded to figure the total loss in the
manufacture of a particular item. Accurate shrink and scrap factors can help to produce more accurate planning calculations.
Enter percentages
as whole numbers: 5 percent as 5.0
|
mnLeadtimeOffsetDays | LOVD | MATH_NUMERIC | OPT | NONE |
The number of days that a part is needed before or after the start date of a manufacturing work order. The system adds the leadtime offset
days for the part to the start date of the work order to determine the actual date that the part is required. To indicate that a part is needed prior
to the work order start date, enter the days as a negative number. To indicate how many days after the work order start date that the part is
required, enter a positive number. |
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. |
mnSubstituteItemSequenceNu | SBNT | MATH_NUMERIC | OPT | NONE |
A number that indicates the sequence for the substitute items for a component.
The system looks for substitute items by this sequence
number.
|
cCoproductsByproducts | COBY | char | OPT | 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 |
cStockingType | STKT | char | OPT | NONE |
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). |
cCacheActionCode | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
cCacheErrorCode | EV02 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
nNumberOfKeys | INT01 | integer | OPT | NONE |
Number of Days in Future to Query for Responses Due.
|
cSuppressErrorMessage | SUPPS | char | OPT | NONE |
A flag indicating whether or not runtime error messaging will occur when an error message is issued from a business function.
0 = allow
runtime error message handling.
1 = suppress runtime error message handling. |
szErrorMessageID | 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.
|
idCacheCursorPtr | GENLNG | ID | OPT | NONE |
General purpose ID variable. |
cSequentialFetch | EV03 | char | OPT | NONE |
A radio button that specifies the level at which trace/track result is to be displayed. Select the Detail to display all transactions except IB, IX,
and IZ types. Or, select Derivative Lots Only to display only those transactions that may have created new derivative lot.
|
szComponentPrimaryUM | UOM1 | char | OPT | NONE |
A user defined code (00/UM) that identifies the unit of measure that the system uses to express the quantity of an item, for example, EA
(each) or KG (kilogram). |
szComponentTFLA | TFLA | char | OPT | NONE |
Allows you to bypass the item-specific unit of measure and use the standard unit of measure. Valid values are:
blank Use the item-specific
unit of measure
1 Bypass the item-specific unit of measure and use the standard unit of measure |
mnComponentStandardPotency | STDP | MATH_NUMERIC | OPT | NONE |
The percentage of active ingredients normally found in an item. |
cComponentPotencyControl | OT1Y | char | OPT | NONE |
A code that indicates whether you control the item by potency. |
cCoponentRoundToWhole | SNS | char | OPT | NONE |
A code that determines whether the system performs rounding for planning purposes. Valid values are:
R Round either up or down to the
nearest whole number.
U Round up to the nearest whole number.
Blank Do not round.
Example of value R: If the calculated requirements for
an item are 4.6, the system rounds the quantity required to 5.0. If the calculated requirements are 4.4, the system rounds the quantity required
to 4.0.
Example of value U: If the calculated requirements for an item are greater than 4.0 and less than or equal to 5.0, the system rounds the
quantity required to 5.0. |
mnComponentNumber | 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.
|