Technical Articles
Advanced ATP Release for Delivery in SAP S/4HANA
Introduction
This blog is for SD consultants. I used SAP S/4HANA OP2020 FPS1 version. However, it also works with SAP S/4HANA 2021 and 2022 onwards, and SAP S/4HANA Cloud, private edition.
What is Release for Delivery
It is manual back order process.
After advanced ATP BOP you can also modify the results manually just before creating delivery documents.
You have to create delivery documents through Release for delivery, if you modify confirmed quantity by using it.
Customize
Tr-cd:spro
IMG >Cross-Application Components >Advanced Available-to-Promise(aATP) >Product Availability Check(PAC) >Define Availability Check Group
Product Master:
Tr-cd: mm02
Configure Order Fulfillment Responsibilities
Fiori App ID F2246
Click “Create” button.
”*” is a mandatory field.
In this case Product number are set for the selection criteria.
Click “Crate” button.
Input a user ID and click “Apply” button.
Click “Apply” button.
Click “Create” button.
Configuration end
Execute Release for delivery
Fiori App ID F1786
Click “>” button.
Push Sort button.
Select criteria and push ok button.
Reduce lower delivery priority sales order conformation quantity manually.
Then, impact bar shows available quantity.
Increase higher priority sales order quantity manually.
Then, push publish and back button.
Click prepared.
And select item then push release for delivery button.
Delivery documents are created immediately.
Conclusion
You understand how Release for delivery works.
Appendix
BAdIs
BAdI for customize the Release for Delivery Impact Bar
–BADI_ATP_R4D_MATERIAL_IMPACT (influences impact on material level = multiple lines)
–BADI_ATP_R4D_REQUIREMNT_IMPACT(influences impact on line item level)
Help:
SAP Note:
2667162 – FAQ: Release for Delivery (R4D)
2632900 – Release for Delivery: additional information.
3066116 – Release for Delivery: additional information
Related SAP Blog:
Thank you so much for your document, and appreciating you for your dedication.
Thank you for this - In the context of aATP and Preparing/releasing sales order material line items without availability issues for delivery function in the "Release for Delivery" App. Does this mean that aATP introduces the option to block delivery creation for ALL SO/STO deliveries until released? Is this the same for both S/4HANA 2020 FPS02 and S/4HANA CLOUD ES 2105?
Hi Morne/ Kazuhisa -
From my experience with this, there isn't really a block that prevents you from creating the delivery if you don't release it through the R4D app. If you had a background Delivery Due List job running, and the same Sales Order is picked up in Delivery Due List with no availability issues, then the Delivery can get created without being released on R4D. One might also proceed to manually create the delivery.
So I would pay extra attention to what is included in the Delivery Due List scope (if you have this running as a background job) vs the Order Fulfillment Responsibility scope to be aware of any overlaps.
Yiin
Hello Morne,
Yes, if you don't release the SO STO, then the delivery documents for them will not be created. It is like delivery block.
Best regards,
Kaz
Hello,
My question is for Configure Order Responsibility App.
Is there any way to add new selection criteria for this app like Product Allocation or Back Order Processing?
Hello,
Only defined criteria is available.
Best regards,
Kaz
Hi Kazuhisa San,
First of all, thanks for the wonderful document.
We have implemented Backorder processing in aATP . The BOP sorting was done on Sold to Party which means we want to prioritize specific customer orders. The scenario worked fine until we activated PAL functionality.
Now, the Sales order confirmation is not happening based on customer base. We have the below mentioned scenario:
Sales Order 1 is created for Customer A which has no. 2 priority in BOP sorting and the confirmation is done at the time of SO creation only.
Sales Order 2 is created for customer 2 which has no.1 priority in BOP sorting and the partial confirmation is done for the remaining stock material.
When we run the BOP, system should be able to confirm SO2 for the whole quantity and SO1 should be partially confirmed.
But this is not happening. Please guide if we are missing something.
BR,
Biswaranjan
Hello Biswaranjan,
Please check Confirmation Strategies. For example: "Redistribute" Assigned requirements can get a better, equal, or worse confirmation.
https://help.sap.com/viewer/f132c385e0234fe68ae9ff35b2da178c/2021.000/en-US/1ba3a457ef816b10e10000000a441470.html
Hi Kazuhisa,
We have implemented Backorder processing in aATP . The BOP sorting was done on Sold to Party which means we want to prioritize specific customer orders. The scenario worked fine until we activated PAL functionality.
Now, the Sales order confirmation is not happening based on customer base. We have the below mentioned scenario:
Sales Order 1 is created for Customer A which has no. 2 priority in BOP sorting and the confirmation is done at the time of SO creation only.
Sales Order 2 is created for customer 2 which has no.1 priority in BOP sorting and the partial confirmation is done for the remaining stock material.
When we run the BOP, system should be able to confirm SO2 for the whole quantity and SO1 should be partially confirmed.
But this is not happening. Please guide if we are missing something.
BR,
Biswa
Hi Kazuhia,
Thank you for the very informative blog. We are testing Release for Delivery app and are finding that if we remove quantity from one order and try to confirm it against another order that has a partial delivery completed it is not confirming a second schedule line for the remaining quantity. For example Order 1234 has 20 confirmed. We change the 20 to 16. Order 5678 has 6 confirmed and delivered out of 10. We change the confirmed quantity to 4, which is the open backorder. All appears fine until we try to release for delivery. We get a message " 6 have been delivered previously. 4 cannot currently be confirmed. We have validated that the order is not on credit hold or any other block and is complete.
Any thought on how to resolve this?
Thank you in advance for your guidance,
Gina
Hello Gina,
I think that it is a program bug. Please post an incindent and send it to SAP.
Best Regards,
Kaz