Automatic Batch Determination Issue in EWM (S/4HANA Cloud 2502)

[JoseGuill]

Hi SAP Community,
We (on the customer’s side) are currently in an SAP S/4HANA Public Cloud implementation project, transitioning to the 2502 release. We've encountered a significant issue with automatic batch determination in our EWM-managed storage locations, and we are looking for insights from the community.

In the previous 2408 release, we observed that automatic batch determination was functioning correctly during outbound delivery creation. However, after upgrading to 2502, this functionality has ceased.
Our automatic batch determination is based on Condition Records. Specifically, we have configured condition records that define a minimum BBD (Best Before Date) for each customer and product combination. This ensures that customers receive products with an acceptable remaining shelf life.

The issue we are facing is that the system is no longer automatically selecting batches based on these condition records in the EWM warehouse during outbound delivery creation. We understand that with EWM managed storage locations, the final batch selection is done in EWM.
Given that this functionality was working in 2408, and is now failing in 2502, we suspect either a change in standard behavior or a potential misconfiguration on our end.

We have opened an SAP case regarding this issue. So far, SAP support has indicated that automatic batch determination is not possible in EWM-managed storage locations, and that only manual batch determination is available. However, we interpret note 3400017 as indicating that automatic batch determination can happen in EWM.

Our questions are:
1. Has anyone successfully configured automatic batch determination in EWM in version 2502, and if so, could you share your configuration approach?
2. Are there any known changes in the 2502 release that could affect automatic batch determination in EWM-managed storage locations?
3. Could anyone suggest specific configuration steps or checks we should perform to ensure our Condition Records are correctly being processed by EWM for batch determination?
Any help here would be really appreciated

Thanks a lot!

[erickgoulardt]

Dear Colleague, I hope you find yourself well! Thank you for joining the community. As soon as possible, a technical expert will contact you to clarify your question. I am adjusting the tags to redirect the issue to the right team. Best Regards, Erick Goulardt SAP Support

[GeovanaLettnin]

Hello @JoseGuill, We helped you to accept the answer, since there were no further updates under the topic. You can unaccept it anytime if the answer provided was not helpful enough and you have further questions. Best regards, Geovana

[Christian_Ries · Accepted solution]

Hi @JoseGuill ,

the batch determination in Warehouse Management is supported. It also considers the batch selection criteria if they are defined. In case this process does not work for you, I'd suggest to create an incident.

If you have already created an incident and received a negative response, please share the incident number with me and I can have a look.

Best regards,
Christian

[Peter237 · Accepted solution]

Hello Christian you mentioned batch determination in EWM is supported in SAP public cloud. Is batch determation also supported during backflush of components during confirmation? In other words if a batch search strategy has been defined with batch splits, this will be taken into account for backflushing of components?

[Christian_Ries · Accepted solution]

Yes, it also works during backflush. Just to be clear: The batch determination is then carried out in WM, based on the stock removal strategy. Please make sure to maintain the relevant stock removal strategy in the respective storage type (usually the storage type of the PSA).

[Peter_Kerkhof · Accepted solution]

Hello Christian We are on Cloud 2508. During production order creation and release the batch determination on expiration date is working for components. The batch splits are also visibile in the PMR. However, batch determination during confirmation is not working. We would expect again a batch split based on available batches on the PSA. We entered stock removal FEFO in the storage type Z105 (copy of S105). We created a case.