| Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
|---|
| 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.
|
| szSessionID | CFGSID | char | OPT | NONE |
An identifier that represents a unique configuration. It is generated from an encryption algorithm. Regardless of the number of segments or
levels in the configured item, the system always converts the information into a 32-character digest. The digest is always a full 32 characters
in length, consists of numbers and characters, and does not contain any blanks. You cannot determine the initial value from the digest, and it
has no significant meaning.
|
| mnParentItemNumber | 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. |
| szTypeRouting | TRT | char | OPT | NONE |
A user defined code (40/TR) that indicates the type of routing. You can define different types of routing instructions for different uses.
For
example:
M Standard Manufacturing Routing
RWK Rework Routing
RSH Rush Routing You define the routing type on the work order
header. The system then uses the specific type of routing that you define in the work order routing.
Product Costing and Capacity Planning systems
use only M type routings. |
| mnComponentItemNumber | 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 |
| szBranchPlant | 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. |
| mnBatchQuantity | 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. |
| szParentUnitOfMeasure | 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).
|
| mnRoutingRevisionNumber | RRVN | MATH_NUMERIC | OPT | NONE |
A unique number that determines the Revision Number for Routing.
|
| mnLevelofBOM | LBOM | MATH_NUMERIC | OPT | NONE |
A component level within the BOM.
|
| 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. |
| mnAssmblyBatchQty | BQTE1 | MATH_NUMERIC | OPT | NONE |
The quantity of finished units that you expect this bill of material or routing to produce. This field allows you to 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. |
| mnJobnumberA | JOBS | MATH_NUMERIC | OPT | NONE |
The job number (work station ID) which executed the particular job. |
| 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. |
| mnLeanQuantityPer | LQNTY | MATH_NUMERIC | OPT | NONE |
The number of Units required PER finished unit.
|
| 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. |
| 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). |
| szDFMLineIdentifier | DFMLINE | char | OPT | NONE |
This is used to identify the DFM line.
|
| idPPATPointer | GENLNG | ID | OPT | NONE |
General purpose ID variable. |