In SAP APO, Production Planning/Detailed Scheduling (PP/DS) is used to generate procurement proposals to meet the production requirements. This component is also used for defining resource plan and order details. You can also plan for critical products to reduce the lead time and to improve time delivery performance.
PP/DS can be used to create executable plans and to achieve the following −
Transaction and master data from the OLAP system is moved to APO and after order processing planning, results are moved to APO system.
Integration of PP/DS with SAP APO applications
Let us now discuss integration of PP/DS with SAP APO applications.
Integration with Demand Planning
Demand planning is used to meet the market demand for critical products after considering different factors and the result of demand planning is a demand plan. Demand plan is moved to PP/DS to raise procurement proposals for both external system and internal procurement process.
Using Demand Plan, demand planning is executed for customers and planned independent requirement results are transferred from DP to PP/DS to cover PIR by creating procurement proposals.
Following is the Process Flow −
Supply Network Planning (SNP) ensures that product quantities are available at the right time, right place without overloading of resources in production and transportation process. SNP defines the quantities in which products should be procured, produced, or transported. PP/DS defines lot sizes of products to be procured, and sequences of planning order.
Both the methods are integrated and planning is performed for different task distribution.
Supply Network Planning and PP/DS Planning Tasks
SNP and PP/DS are defined for different phases - SNP planning is used for medium-term objectives and short-term planning is for PP/DS. The horizon for SNP planning and PP/DS planning are same and the planning area doesn't overlap.
When the same planning version is used for SNP and PP/DS, it is also possible to convert SNP orders into PP/DS orders.
PP/DS Alert Monitoring
You can monitor alerts raised in PP/DS planning using the Alert monitor. You need to define an alert profile relevant for to your planning. Different alert types are created in PP/DS.
Alerts Related to Relationship between Orders or Operations
The system compares the shelf life planning with the actual shelf life of receipt during planning.
When shelf life requirements are met, pegging relationships are created.
When procurement planning heuristic is run, different PP/DS alerts can be raised w.r.t Planning. Following are the common alert types −
Procurement Planning Exceptions
In PP/DS alerts related to procurement planning are generated when you define setting in customizing. Navigate to Application logs for PP/DS, and define and maintain exception groups.
To check exception message, you can use the context menu of alert. Each of the message belongs to different alert classes.
Example − An alert can have different class that shows different status messages.
Class 1 − Termination Messages
Class 2 − Error Messages
Class 3 − Warning Messages
Class 4 − Success Messages
Order Related PP/DS Alerts
Following PP/DS alerts are raised w.r.t orders raised −
In PP/DS, you can have alerts raised related to resources in planning.
Following PP/DS alerts can be raised related to campaign planning. When planning with production campaign is performed, the system can issue following alerts −
PP/DS can be used to create executable plans and to achieve the following −
- Improve the on-time delivery performance for critical products
- Reduce lead times
- Improve coordination between resources and better procurement process
- Reduce the stock cost
Transaction and master data from the OLAP system is moved to APO and after order processing planning, results are moved to APO system.
Integration of PP/DS with SAP APO applications
Let us now discuss integration of PP/DS with SAP APO applications.
Integration with Demand Planning
Demand planning is used to meet the market demand for critical products after considering different factors and the result of demand planning is a demand plan. Demand plan is moved to PP/DS to raise procurement proposals for both external system and internal procurement process.
Using Demand Plan, demand planning is executed for customers and planned independent requirement results are transferred from DP to PP/DS to cover PIR by creating procurement proposals.
Following is the Process Flow −
- Step 1 − First step is to start with the release of demand plan to Supply Network Planning. Demand plan can be released as mass processing or online.
- Step 2 − Consider the release period same on PP/DS horizon and Supply Network Planning horizon.
- Step 3 − Copy requirements to target planning version, resulting in a demand plan to Supply Network Planning, which in turn triggers an event in PP/DS for products.
- Step 4 − Action takes place as per Planning Procedure for mentioned products.
- Step 5 − Execution of PP/DS Planning.
Supply Network Planning (SNP) ensures that product quantities are available at the right time, right place without overloading of resources in production and transportation process. SNP defines the quantities in which products should be procured, produced, or transported. PP/DS defines lot sizes of products to be procured, and sequences of planning order.
Both the methods are integrated and planning is performed for different task distribution.
Supply Network Planning and PP/DS Planning Tasks
SNP and PP/DS are defined for different phases - SNP planning is used for medium-term objectives and short-term planning is for PP/DS. The horizon for SNP planning and PP/DS planning are same and the planning area doesn't overlap.
When the same planning version is used for SNP and PP/DS, it is also possible to convert SNP orders into PP/DS orders.
PP/DS Alert Monitoring
You can monitor alerts raised in PP/DS planning using the Alert monitor. You need to define an alert profile relevant for to your planning. Different alert types are created in PP/DS.
Alerts Related to Relationship between Orders or Operations
- Dynamic pegging with date/time alerts
- Fixed pegging alerts
- Quantity alerts for pegging
- Shelf life
The system compares the shelf life planning with the actual shelf life of receipt during planning.
When shelf life requirements are met, pegging relationships are created.
- Relationship between Operations
When procurement planning heuristic is run, different PP/DS alerts can be raised w.r.t Planning. Following are the common alert types −
Procurement Planning Exceptions
In PP/DS alerts related to procurement planning are generated when you define setting in customizing. Navigate to Application logs for PP/DS, and define and maintain exception groups.
To check exception message, you can use the context menu of alert. Each of the message belongs to different alert classes.
Example − An alert can have different class that shows different status messages.
Class 1 − Termination Messages
Class 2 − Error Messages
Class 3 − Warning Messages
Class 4 − Success Messages
Order Related PP/DS Alerts
Following PP/DS alerts are raised w.r.t orders raised −
- Alerts for the orders with status deallocated
- Alerts for orders with date time in the past
- Quantity falls short/exceeds desired quantity
- Order with validity period expired
In PP/DS, you can have alerts raised related to resources in planning.
- Alerts related to resource utilization above/beyond threshold value
- Capacity overload for bucket resource
- Resource overload in case of single/multi-activity resource
- Alerts related to container resources planning
Following PP/DS alerts can be raised related to campaign planning. When planning with production campaign is performed, the system can issue following alerts −
- Alerts related to cleanout order in a campaign
- Alerts related to interrupted campaign