The order type is stored in every manufacturing order. It includes information about how backflushing of material and operations should be made and what kind of shop floor document should be printed.
- Order type
- The code that identifies the manufacturing order type.
- Description
- The description of the manufacturing order type.
Backflushing material
- At delivery to stock
- Indicates if used material should be backflushed when the produced product is delivered to stock.
- Backflush at first reporting
- Indicates if total planned material quantity should be issued from stock when the first operation or reception reporting is done. Note: This field can only be set to YES if either the Backflushing material: At delivery to stock or Backflushing material: At operation report field is set to YES.
- At operation report
- Indicates if used material should be backflushed when an operation is reported with quantities. If this field is set to YES, connected material to the operation will be backflushed at operation reporting if approved quantity or rejected quantity has been entered at reporting.
- Backflush max as manufacturing order
- Indicates if backflushing is allowed if more material (higher quantity) than the manufacturing order has been planned to use. If this field is set to YES, the backflushing will be done up to the ordered quantity but not more even if the produced quantity is higher. If set to NO, the backflushing will be done according to the produced quantity.
- Location/batch item
- Indicates if items that are classified as serial, batch or warehouse management controlled should be backflushed. Note: The value in this field only takes effect when the Backflushing material: At delivery to stock or Backflushing material: At operation report field above is set to YES.
- Close not started oper at end
- Indicates if manufacturing order operations that not have been started should be backflushed. If this field is set to YES, the backflushing of time is done on the relation between ordered quantity and produced quantity.
- Reception at last operation
- Indicates if reception of produced item should be done when reporting on the last manufacturing order operation. The approved quantity is the value for making reception at the last operation.
- Actual cost for rec
- Indicates if the manufacturing order’s actual cost by unit should be used for calculating the reception amount (stock value) or if the pre-calculated cost by unit should be used. Note: Actual cost can only be used for the calculation if the cost type is average or FIFO. For standard cost the cost price on item or item/warehouse level is always used.
When the actual cost is used there are restrictions in the way manufacturing order reporting can be performed:
- It is not possible to use “Backflushing material at delivery to stock”, as the backflushing is based on the reception quantity and cost control value is not calculated at the time of performing the reception.
- It is not possible to use “Reception at last operation”, as material can be attached to the last operation and the previous operation(s) could be based on the reporting made on last operation (milestone reporting).
It is not possible to make a product reception when there are open reservations or open operations. In other words, operations must be reported and completed (status 60); material must be issued manually or backflushed at operation reporting and completed (status 60), and finally reception must be done manually from the issue/receive routine.
- Batch clearance
- Indicates if a created manufacturing order should go through an extra confirmation step before it is possible to start production. If this field is set to YES, a created manufacturing order will get order status 05 (not clearance) and must be accepted in the batch clearance function before the order status is 10 (ready).
- Included in WIP
- Indicates if manufacturing order with this order type should be printed on the Work in progress report.
- Order statistics
- Indicates if completed manufacturing orders should be stored in the Manufacturing order history file when manufacturing orders are reorganised.
- Create lower levels
- Indicates if manufacturing orders for the sub-assembly items should be created automatically when a manufacturing order is created for the parent item.
- Lower level order pl
- Mandatory entry if the Create lower levels field is set to YES. This field is used for determining how the lower level orders should be planned (i.e. if there should be one day between the requirement order (planned issue date) and the lower level order (completion date), or if the orders should be planned together (same day).
Indicates how the lower level orders should be planned.
Code Description 1 One day between the orders 2 Planned on same day
- Disp check lower lvl
- Indicates if disposal check for lower level manufacturing orders should be done. This field can only be set to YES if the Create lower levels field is set to YES.
- Batch no at creation
- Indicates if the batch number of the produced items should be generated at the creation of the manufacturing order. The generated batch number will be created from the batch mask that is defined for the item in the Item file, Inventory information panel. If this field is set to NO, a batch number must be manually entered when the manufacturing order is received. See Batch number for more information.
- Direct/delayed pur creation
- This mandatory field is only displayed when the Direct pur to m-order field is set to YES in the MFG control file. Indicates if the purchase order should be created directly after the manufacturing order has been created or delayed creation, that is, manually or through a batch function. Note: Fictitious component items and components defined with item class 2 and 4 will be included for direct purchase against the manufacturing order.
Code Description 1 Direct creation 2 Delayed creation 3 No purchase order
- Issue at pur receipt
- This mandatory field is only displayed when the Direct pur to m-order field is set to YES in the MFG control file. If this field is set to YES, it denotes that the material should be issued to the manufacturing order when the connected purchase order reception is made. If set to NO, it denotes that the issue should be made within the normal manufacturing order reporting routine.
- Purchase order type
- This field is only displayed when the Direct pur to m-order field is set to YES in the MFG control file. Displays a purchase order type that is used to create a purchase order for components defined with direct delivery. The purchase order type must be defined with update stock on-hand and transit delivery.
- Op reporting check
- This field controls the operation reporting in a more strict way. Indicates how validation should be made against a previous operation when reporting on an operation. If this field is set to 2, 3, 4 or 5, the Close not started operations at end field cannot be set to YES.
Code Description 1 No validation. It is possible to do reporting on any operation that is defined as reporting operation and not defined as sub-contract operation, without any validation on any previous operation. 2 Warning on status. If previous reporting operation is not closed (status 60) the user receives a warning message saying “Previous operation is not reported as complete”. In the event that the previous operation is not started (status 10, 20) the user receives an error message saying “Previous operation is not started”. 3 Stop on status. If previous reporting operation is not closed (status 60) the user receives an error message saying “Previous operation is not reported as complete”. 4 Warning on status and quantity. Same as status 2 but also validation on if previous reporting operation approved quantity is not equal to the total reported quantity (approved + scrapped) on reporting operation, the user receives a warning message saying “Total reported quantity not equal to previous operations approved quantity”. 5 Stop on status and quantity. Same as code 3 but also validation on if previous reporting operation approved quantity is not equal to the total reported quantity (approved + scrapped) on reporting operation, the user receives an error message saying “Total reported quantity not equal to previous operations approved quantity”.
- Cost model
- The code from the Cost model table indicates the cost model to be used for manufacturing orders of this order type. If this field is left blank, the cost model defined in the MFG control file will be used during manufacturing order creation.
- Allow rep without print shop floor
- Indicates if it is allowed to make reporting on a manufacturing order that has not been printed, that is, order status = 10 (ready).
- BtB order status
- The code indicates what status manufacturing orders should get that are created from BtB orders (= manufacturing order linked to sales or project order line).
Code Description 1 BtB manufacturing orders will get status 00 (preliminary). 2 BtB manufacturing orders will receive status 05 (batch clearance) if the Batch clearance field is set to YES in the Manufacturing order type table or if the Order allocation field is set to YES in the Item file on one or more components. In other cases, the status will be 10 (ready). 3 BtB manufacturing orders will get status 00 (preliminary) if the manufacturing order start date is within the production time of the item. If the manufacturing order start date is outside the production time of the item, the status will be set according to the same rules as code 2.