|

![]() xTuple ERP 3.0 won the LinuxWorld product excellence award for best Business Application! Read more here!
|
Master Production Scheduling (MPS) is a planning system which serves several important purposes:
Typically, MPS is used to plan for Items having "independent" demand. Independent demand Items are defined as those Items which derive their demand directly from Customer requirements through Sales Orders. By contrast, "dependent" demand Items are normally purchased Items and subassemblies. The demand for dependent Items is derived indirectly—that is, based on the demand for their parent Items in a Bill of Materials. In this section, we will demonstrate xTuple ERP's MPS functionality, using a Production Plan called COLLECTORS-2007. We have linked a Planning Item, COLLECTORS-LINE, to this Production Plan. Both the Plan and the Planning Item are included in the data for the xTuple ERP Demo Database. NoteThe scenarios described in this section refer to Items and other data found in the xTuple ERP Demo Database. The Demo Database is available for download from the xTuple website. The Bill of Materials for the COLLECTORS-LINE Planning Item is composed of three MPS planned Items, each of which have the following quantities per:
Our Production Plan for the COLLECTORS-LINE Planning Item currently contains forecast periods for the first three months of 2007. In the example we will be using, we will actually adjust the dates and quantities for these periods to accommodate demand that is anticipated in late 2006, earlier than originally expected. To accommodate a current date that will be different from the date on which this section was written, you will be instructed to use date offsets of +28, +58, and +88 days. So, for example, if we forecast 1,000 units of the COLLECTORS-LINE Planning Item for November 2006, the planning system will create Orders for 500 BTRUCK1"s, 300 RTRUCK1's and 200 WTRUCK1"s. (See the quantity per values shown above for each Item in the COLLECTORS-LINE\qs Bill of Materials). The COLLECTORS-LINE itself is a logical construct, and, as such, no Planned Orders will be created for it. NoteIn our scenario, we will be forecasting using a Planning Item—a special type of Item used to defined families or lines of products. However, the system also allows you to place individual MPS Items on a Production Schedule. To begin the process of understanding how MPS works, we will first update and release our Production Plan (i.e., Forecast). To access the master list of Production Plans, follow these steps:
Now that we have opened the Production Plan for editing, we can drill down and modify the scheduled date and quantity for the COLLECTORS-LINE Planning Item. As you recall, COLLECTORS-LINE is the Planning Item whose Bill of Materials we discussed above. To begin, follow these steps:
![]() Production Plan Item Screen
Now that we have finished updating the Production Plan, we are ready to release it. Production Plans must be in a released state ("R") if they are to be considered when the MPS planning system is run. To release the Production Plan, follow these steps:
Because our Production Plan has been released, the MPS planning system will recognize it when MPS is run. The next step is to run MPS by Planner Code, as follows:
![]() Run MPS by Planner Code
NoteIn a production environment, you can select the SUBMIT button to send the MPS run to the Batch Manager for processing. Because the Batch Manager is not available for demonstration databases, please do not use this option. Once the MPS run is finished, we can go look at the Planned Orders generated by the run. To view the results of an MPS run, follow these steps:
![]() Planned Orders by Planner Code Display
The Planned Orders by Planner Code display shows us the top-down nature of the Forecast. Notice how the planned quantities match the quantity per ratio for each Planning Item component. Also notice how the Orders are grouped into three separate date buckets. We can understand how our new Planned Orders fit into a broader context by examining the MPS Detail display. To access the MPS Detail screen, follow these steps:
![]() MPS Detail Display
The example shows the MPS Detail for the selected Item based on the Calendar selected. In this case, the Calendar being used is a special absolute Calendar that shows the last three months of 2006 and the first two months of 2007. As you follow this scenario, you should select the Calendar appropriate for the current date—whatever the current date may be. If you need a 2008 Calendar, simply select it from the drop-down list and then click again on the Item whose MPS Detail information you want to display. Also, depending on the time of year, you may need to scroll to the right to see the Forecast and Planned Orders. Now that we have generated the planned MPS Orders, let's see the impact these will have on the plan for Material Requirements Planning (MRP) Items. To see how MRP will respond to the MPS Orders we created, it will be necessary to run MRP. To run MRP by Planner Code, follow these steps:
![]() Run MRP by Planner Code
Once the MRP run is finished, we can go look at the Planned Orders generated by the run. To view the results of an MRP run, follow these steps:
As you can see, the MRP run generated multiple Planned Orders which were not present after we ran MPS initially. The reason for this is simple: The extra Orders are MRP Orders generated to satisfy the demand created by the MPS Orders. Essentially, we forecasted demand and then discovered what materials would be needed to meet that demand—net existing Quantity on Hand, other demand, existing supplies, and expected receipts. If you want to filter out MRP or MPS Items, you may do so on the Planned Orders by Planner Code screen by following these steps:
![]() Planned Orders by Planner Code Display
If you want to continue further and act upon the advice provided by the MPS and MRP planning systems, you can proceed by right-clicking on a specific Planned Order and releasing it. For more information on releasing Planned Orders, see the Basic Business Process Flow chapter of the xTuple ERP Demo Guide. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||