DeleteOperationResources
Delete Operation Resources
Major Business Rule
Object Name: B3000110
Parent DLL: CMFGBASE
Location: Client/Server
Language: C
1.Functional Description
1.1Purpose
Delete Co-Products, By-Products, Ingredients, and Intermediates from an Operation. (Mode: 1=All,
2=Co-Products, 3=By-Products, 4=Ingredients, 5=Intermediate)
1.2Setup Notes and Prerequisites
1.3Special Logic
2.Technical Specifications
2.4Processing
1.0. Delete Co-Products, By-Products, Ingredients, and Intermediates from the Operation.
1.1. If mode is equal to '1' or '2', delete Co-Products. Delete Co-Products from the Bill of
Material Table (F3002) using index CoByProduct, Item, +A where COBY='C', ITM=Parent Item, CMCU=Parent
Branch, TBM=Type of Bill, BQTY=Batch QuantityDisplay, UM=Unit of Measure, OPSQ=Operation Sequence.
1.2. If Mode is equal to '1' or '3', delete By-Products. Delete By-Products from the Bill of
Material Table (F3002) using index CoByProduct, Item, +A where COBY='B', ITM=Parent Item, CMCU=Parent
Branch, TBM=Type of Bill, BQTY=Batch QuantityDisplay, UM=Unit of Measure, OPSQ=Operation Sequence.
1.3. If Mode is equal to '1' or '4', delete Ingredients. Delete Ingredients from the Bill of
Material Table (F3002) using index CoByProduct, Parent Item, +A where COBY = blank, KIT=Parent Item,
MMCU=Parent Branch, TBM=Type of Bill, BQTY=Batch QuantityFile, and OPSQ=Operation Sequence.
1.4. If Mode is equal to '1' or '5', delete Intermediates. Delete Intermediates from the Bill of
Material Table (F3002) using index CoByProduct, Parent Item, +A where COBY = 'I', KIT=Parent Item,
MMCU=Parent Branch, TBM=Type of Bill, BQTY=Batch QuantityFile, and OPSQ=Operation Sequence.
^
Data Structure
D3000110 - Delete Operation Resources
Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
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. |
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. |
szTypeOfBill | TBM | char | NONE | 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. |
mnBatchQuantityFile | 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. |
szUnitOfMeasure | UM | char | NONE | 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. |
mnOperationSequence | 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. |
cMode | MODE | char | NONE | NONE |
The processing mode used in Purchase Order Consolidator to signify when specific orders are being processed. |
mnBatchQuantityDisplay | 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. |