Production orders also inherit the Produmex Manufacturing extension settings from their base Bill of Materials. For production orders other extensions are available, including ‘Milestone Groups’, ‘Due Time’, and ‘Allocation Strategy’.
A row in a BoM may be of type:
The sequence of materials and operations are important: materials required for an operation should come above (from top down) the operation, while produced products should come below. It is possible to define operations that do not require materials or do not create products.
The system differentiates purchased and own-manufactured materials. Materials that have their own BoM are regarded as own-manufactured. These materials are indicated with a factory icon on the ‘Row Image’ field. When clicking on the yellow arrow, for own-manufactured materials the BoM, while for purchased materials the Item Master Data will open.
The operation quantity indicates the time required for the process. The initial parameters of an operation are copied from the manufacturing operation, and these parameters may be customized for the BoM. The operation details form can be opened by clicking the row image icon. An operation can be defined as outsourced too. Fully outsourced operations are indicated with a different icon on the ‘Row Image’ field.
Indicates the row type.
![]() | raw material/subassembly material/supplier material |
![]() | operation/fully outsourced operation/operation cannot be allocated/finished |
![]() | unfinished product/unfinished material |
![]() | by-product |
![]() | phantom item |
![]() | cost |
To see the Operation Details form, click on the Row Image of the operation.
The two main function of milestones is to connect the operation lines with the belonging materials and to determine for what operations PDC information should be captured.
With the help of the milestones, during a PDC booking for the operation line the belonging materials or the product can also be booked. Milestones can be set for every BOM line where the row type is not ’Cost’. You can set the milestone type at a phantom line, but it makes no sense as the milestone settings from the BoM of the phantom item will be used in the production order.
The ‘Milestone type’ field can have five values:
We recommend to only use the ’Depends on End’ milestone type if the base quantity of the material is 1 and only ’Completed’ job bookings are used.
For the depending line the issue type must be ‘Manual’ while for operations it must be ‘Backflush’. Outsourced operations must be set to milestones and the issue method for an unfinished product must be set as ‘Backflush’. To set a milestone for the product, use the ‘Milestone type’ column on the BoM.
When you save the BoM, there is a validation for the milestones.
A warning will appear if there is no belonging operation for a material line with a ‘Depends on…’ milestone setting.
The saving will be blocked in the following cases:
Internal identification value.
Add the warehouse code where the rejected unfinished products or by-products will be stored to this field to the respective lines. For MultiBranch company databases the add-on validates if the rejected warehouse is in the same branch as the branch defined for the bill of materials row warehouse.
Production orders inherit the milestone type from the base BoM. An additional ‘Milestone Group’ field is added to the production orders which contains the code of the operation the line belongs to. This field is automatically set by the add-on based on the milestone settings and it cannot be changed manually.
Operations with allocations errors are indicated with an icon on the ‘Row Image’ field.
After the production order is added/updated, an advanced MRP runs in the background and calculates the due dates and times the operation must be finished/ the material must be available.
Defines whether this line is taken into account by the MRP logic or not.
On operation lines indicates whether there is an error with the allocation or not.
If the production order is a part of an MTO chain and its subassembly line has an MTO production order, the MTO scenario code is displayed on this field on the line of the subassembly.
In material lines it shows the BX ID of the linked operation. In operation lines it shows the BX ID of the next operation.
The planned outsourced quantity of an unfinished product.
The completed quantity of the unfinished product received from the subcontractor.
The quantity of an unfinished product that was booked as ‘Rejected’ by the quality inspector.
The completed quantity booked with PDC for an operation.
The quantity booked as ‘Rejected’ with PDC for an operation.
To set a milestone for the product, use the ‘Milestone type’ UDF on the BoM. As the product is never an operation, it makes no sense to set the milestone type as ‘Milestone’. When set as ‘Depends on…’ it is always connected to the last operation of the BoM.
The Calculation Base Quantity is an estimated quantity of a typical production order created from the BoM. This number is used when the setup and shutdown costs are calculated for a single unit of product. For more information please see: Cost calculation
Defines the warehouse used for rejected main products. For MultiBranch company databases the addon validates if the rejected warehouse is in the same branch as the branch defined for the bill of materials header warehouse. Keep in mind that SAP B1 does not validate branch consistency for BOMs; it validates for production orders but not for BOMs. This is why the add-on introduced a new Master Data Configuration Setting named “BOM Branch Validation Level”.
If set to ‘Yes’ the due date and time of an MTO child order is automatically aligned with the begin date and time of the parent production order. This setting is only taken into account if the ‘Auto Roll child MTOs’ option is enabled on the MTO tab of BX Core settings.
Internal identification value.
The operation granularity value impacts the allocation algorithm. The quantity produced in the operation during the allocation must be a multiple of this value. If the operation granularity value is set to zero, the allocation can be continuous.
On the ‘Custom Code’ field a generic BoM code can be added. This code can contain letters and numbers.
By default the production order created from the BoM only inherits the ‘Milestone type’ and ‘Rejected Warehouse’ UDFs. In order to copy other UDF settings to the production order, set the UDFs on the UDFCopyFromBoMToProdOrder table.
On the ‘Allocation Strategy UDF’ the scheduling logic for allocations can be defined. The default the allocation strategy depends on the ‘Default ProdOrd. Allocation Strategy’ set on the Production order tab of Produmex Manufacturing settings.
There are three possible values:
When using forward scheduling, the End Date/Time of the production might be later then the due date. In this case a warning will appear when creating/updating the production order.
Produmex Manufacturing extends the production order Due Date with a time component. With the Due Time production planning is detailed at the time of day level.
To recalculate the allocations for the production order, set the ‘Force Reallocation’ option to ‘Yes’ and click update. After the reallocation, the value will be set back to ‘No’.
Scheduling dates and times are displayed on UDFs that can be overviewed under the ‘Allocation’ category among the allocation message and state.
Under the ‘Outsourcing’ category outsourcing parameters of the production order can be seen.
Under the ‘Planning’ category key planning dates and times of the production order are displayed.
Under the ‘Technical’ category information about the parent order (if any) and other technical details can be overviewed.
Under the ‘General’ category production comments, missing capacity information and MTO details are indicated.
To see the list of allocation errors for the production order after the creation or an update, select the ‘Allocation status’ option from the right-click menu. On the opening ‘System Message’ form allocation errors will be listed.
To review the schedule/planning/allocations of a single production order, open the ‘Operations sequence diagram’ form. The form can be reached from the right-click menu of the production order.
On the form the operations of the production order are displayed in the required order with the work center allocations and the completion percentage.
When a production order is in ‘Planned’ status, no actual work center capacities have been allocated for its operations. Still, in this status an operation sequence diagram can be shown by right-clicking the production order form. In the operation sequence diagram for a planned production orders the work center allocations are only temporarily made; a kind of simulation.
After a production order has been created or updated, the Allocation/calculations results report can be opened from the right click menu to overview the allocations. The red cog indicates an allocation error where the system could not allocate enough capacity for the operation.
For more information please see: Requirements Report
For more information please see: Requirements Report
On the missing capacity report operations from the production order are listed if the total capacity needed for the operation is not available. Select a line and click on the ‘Job Scheduling Control Panel’ button to see the work center in question on the control panel.
For more information please see: Resource Allocations. Please note: As ‘Planned’ production orders do not have permanent allocations, the allocation report is not available for ‘Planned’ production orders.
For more information please see: Job Scheduling Control Panel
For more information please see: Cost calculation
For more information please see: Cost calculation
For more information please see: MTO Planning