GetF3003NextOperationSequence
Get F3003 Next Operation Sequence
Major Business Rule
Object Name: B3000140
Parent DLL: CMFGBASE
Location: Client/Server
Language: C
1.Functional Description
1.1Purpose
Determine the next Operation Sequence Number for the Routing
2.4Processing
1.0. Retrieve from the Routing Master Table (F3003) by the Index "Parent Branch, Parent Item, +A" to
determine the Last Operation Sequence used by the Parent Branch, Parent Item, Type, and Batch
Quantity. If the Routing does not exist, set Last Operation Sequence Number to zero.
2.0. Determine the Increment Amount for the Operation Sequence.
2.1. Move 1 to the Increment Amount.
2.1. Retreive from the Data Dictionary the number of decimal positions for the Dictionary Item
'OPSQ'.
2.2. For each decimal position multiply the Increment Amount by 10.
3.0. Add the Increment Amount to the Last Operation Sequence Number.
Data Structure
D3000140 - Get F3003 Next Operation Sequence
| Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
|---|
| 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. |
| szTypeOfRouting | TRT | char | NONE | 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 | 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. |
| mnNextOperationsSequence | 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. |