SAP continuously evolving its technology to meet global business needs. A key transition is the big shift from Advanced Planning and Optimization (APO) Production Planning/Detailed Scheduling (PPDS) to the more advanced SAP S/4HANA Production Planning and Detailed Scheduling (S/4 PP/DS) – formerly known as ePP/DS.
This meaningful transition marks a leap from a somewhat isolated planning tool within the broader APO suite to a fully integrated component of the S/4HANA landscape now-a days. S/4 PP/DS embeds detailed scheduling and planning capabilities directly into the digital core of S/4HANA, leveraging the power of HANA’s in-memory technology to enhance performance and real-time data processing.
A typical high level process flow diagram for SBC for Make to order scenario (MTO) is depicted in below image. A sales order is created for a MTO product which calls for ATP (Availability-to-promise) check in aATP and finds no available stock, hence it goes to embedded PP-DS (now called as Advanced planning in S/4HANA) for ‘Capacity & Scheduling simulation). Subsequently, a Delivery proposal is created in S/HANA core and a Planned orders are created in PP-DS on saving of Sales order for the finished good as well as for components.
Business Scenario: In MTO scenario customer’s order doesn’t have inventory to fulfil the order. And by leveraging the SBC functionality Order confirmation should happen and subsequent Planned order should be available, we will use Capacity Product Allocation check and confirm the Sales order accordingly.
Process flow:
Quick Notes to set-up SBC:
As I observed the most of the settings are already covered as per the SAP Standard settings from both PP/DS and SD ATP side, you may check the blogs mentioned in the reference section for the details. Still, please take a note of the followings:
First displayed is the sales order creation in the Fiori app Create Sales Order.
Once the sales order has been created, the aATP run has been triggered and the Supply Creation-Based Confirmation has been initiated, the user can see an overview of the check executed in the intermediate results view.
As long as the sales order has not been saved, the user can check the temporary requirements in the product view to see the proposed results of the ATP check.
Product Allocation (PAL) with SBC :
I will not go into details about Product Allocation, as it is a blog for itself. You can read about how to use and setup PAL in different blog posts or please refer to SAP Help document as mentioned in the reference section.
For my use case, as I described above, I have a straightforward PAL setup, with: monthly buckets for the capacity allocations.
The reason for not using Sales PAL here is within an MTO scenario including sales PAL will not update the PAL time bucket after the data in the planning order will change. This may cause a high discrepancy between the date of the PAL consumption and the delivery date. Please refer to the SAP FAQ document: 2691783 - FAQ: Product Allocation Check (PAL) with aATP - SAP for Me ( Point : 37)
Conclusion: This is a nice feature if you have a MTO scenario and you can leverage SBC with Capacity PAL to get the more accurate results.
Reference:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |