| Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
|---|
| szWorkCenter | MCU | char | OPT | NONE |
An alphanumeric code that identifies a separate entity within a business for which you want to track costs. For example, a business unit
might be a warehouse location, job, project, work center, branch, or plant.
You can assign a business unit to a document, entity, or person for
purposes of responsibility reporting. For example, the system provides reports of open accounts payable and accounts receivable by
business unit to track equipment by responsible department.
Business unit security might prevent you from viewing information about business units
for which you have no authority.
|
| mnShortItemNumber | 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 |
| mnOperationSequence | 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. |
| szBranch | 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| mnOrderNumber | DOCO | MATH_NUMERIC | OPT | NONE |
A number that identifies an original document. This document can be a voucher, a sales order, an invoice, unapplied cash, a journal entry,
and so on. |
| cMode | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
| 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.
|
| 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. |