S/4HANA Subcontracting with MRP Area: material reservation not reduced

[Giovanni_Borsar]

Hello experts,

I'm seeking your support to understand the correct procedure for sending components to a subcontractor within a Subcontracting flow with MRP Areas in an S/4Hana environment.

According to the configuration, sinse I don't have any stock in the MRP Area, MRP Live MD01N creates transfer requirements from the plant to the MRP Area in order to supply the MRP Area.

The issue is that when I send the materials to the subcontractor using the standard transactions (ME2O, ME2ON or ADSUBCON), the quantities of the transfer requirements are not reduced accordingly.

Those TrnRes quantities aren't updated from my mov. 541 perfomed by ME2ON, but only at the next run of the MRP LIVE.

This creates problems in both the stock Overview (MD04) of the sending plant and the MRP Area, until the next run of the MRP Live.

Do I have the wrong expectations or is there something wrong with the process?"

Let me know if you need some other details.

@Caetano I hope for your answer.

Thanks in advance

[ChristelFl]

Dear Giovanni,

[ChristelFl]

Dear Giovanni, we are facing the same issue currently. Have you found any solution for this or do you have a workaround?

[ChristelFl]

Dear Giovanni, we are facing the same issue currently. Have you found any solution for this or do you have a workaround? Best regards Florian

[Giovanni_Borsar]

Hello ChristelFl, no solutions yet. A possible workaround is to perform the godd issue (541) using the Transfer Requirement instead the ME2O/ME2ON.

[MOHAMMED_BASER]

Hi Giovanni,
As you explain its correct everyone will expect immediate updates to transfer requirements, but SAP S/4HANA's subcontracting flow with MRP Areas has a known limitation, movement 541 does not automatically reduce transfer requirements until the next MRP Live run.

To mitigate this issue, you can follow below mention best practices.
1. Schedule MRP Live (MD01N) more frequently, especially after major subcontracting movements.
2. Consider using BAdIs or custom logic to trigger MRP Live or refresh MD04 views post-541 movement.
3. Use transaction MDAB (Regenerative Planning) or MDRE (Reorganization of Planning File Entries) if you want to force updates outside of MD01N.
4. Explore SAP Notes or OSS messages for enhancements or patches that may address this behavior.

It’s a standard behavior in S/4HANA with MRP Areas. SAP has not yet provided a native solution to auto-update transfer requirements post-541

https://community.sap.com/t5/enterprise-resource-planning-blog-posts-by-members/s-4hana-subcontracti...