Splitting quantities across bins

[JackN11]

Hi,

We’ve implemented the BADI /SCWM/EX_CORE_PTS_NBIN_NRM to allow mixed storage of the same material with different batch numbers, as our process does not involve receiving via handling units.

Before the implementation, the system would automatically split quantities across bins when the bin capacity was exceeded provided that the storage type allowed splitting. However, after activating the BADI, this automatic bin splitting no longer occurs.

Has anyone experienced this behaviour or found a solution to restore the standard bin splitting logic while keeping the BADI active?

Thanks in advance for your support.

Jack

[beata_d]

Hello Chris, Hello Jack, I am facing a similar issue and I have been wondering if using BAdI /SCWM/EX_CORE_PTS_MIX BAdI instead of /SCWM/EX_CORE_PTS_NBIN_NRM would be a better option here (for mixed storage)? With this BAdI there could be an additional check for allowing mixed storage (based on stock attributes): MIX_ALLOWED (allow mixed storage despite Customizing) MIX_CHECK (forbid mixed storage; Customizing allowed)? Thank You. Kind regards, Beata

[beata_d]

Hello Chris, Hello Jack,

I am facing a similar issue and I have been wondering if using BAdI /SCWM/EX_CORE_PTS_MIX instead of /SCWM/EX_CORE_PTS_NBIN_NRM would be a better option here (for mixed storage)? With this BAdI there could be (theoretically) an additional check for allowing mixed storage (based on stock attributes): MIX_ALLOWED (allow mixed storage despite Customizing) MIX_CHECK (forbid mixed storage; Customizing allowed)?

Thank You.

Kind regards,

Beata

[Chris1973]

Hi @JackN11 

Thank you for your question.

The reason it happens is because your custom logic overrides the standard bin determination that performs capacity check. You can fix this and keep the enhancement you introduced by:

• In your BAdI implementation, ensure to call the standard bin determination logic, this will ensure that the system still executes the automatic split routine.
• Ensure you verify if your BAdI filter values are limited to the relevant storage types only.

The following reference will provide some details:

https://community.sap.com/t5/supply-chain-management-q-a/regarding-badi-scwm-ex-core-pts-nbin-nrm-fo...

https://community.sap.com/t5/supply-chain-management-q-a/regarding-to-badi-scwm-ex-core-pts-nbin-nrm...

Best regards

Chris

[beata_d]

Hello Chris,

[beata_d]

Hello Chris, I am facing a similar issue and I have been wondering if using BAdI /SCWM/EX_CORE_PTS_MIX BAdI instead of /SCWM/EX_CORE_PTS_NBIN_NRM would be a better option here (for mixed storage). With this BAdI there could be an additional check for allowing mixed storage (based on stock attributes): MIX_ALLOWED (allow mixed storage despite Customizing) MIX_CHECK (forbid mixed storage; Customizing allowed)? Thank You. Kind regards, Beata

[beata_d]

Hello Chris, I am facing a similar issue and I have been wondering if using BAdI /SCWM/EX_CORE_PTS_MIX BAdI instead of /SCWM/EX_CORE_PTS_NBIN_NRM would be a better option here (for mixed storage). With this BAdI there could be an additional check for allowing mixed storage (based on stock attributes): MIX_ALLOWED (allow mixed storage despite Customizing) MIX_CHECK (forbid mixed storage; Customizing allowed)? Thank You. Kind regards, Beata

[Chris1973]

Hi @beata_d 

It depends on what your goal is; if your goal is to allow mixed storage for the same material with different batches and you still want to keep the standard bin-splitting behaviour, then yes /SCWM/EX_CORE_PTS_MIX is a better fit in your case.

The BAdI lets you control your mixed storage dynamically through the flags MIX_ALLOWED and MIX_CHECK without it overriding the standard logic. Make sure you only use /SCWM/EX_CORE_PTS_NBIN_NRM if you truly need custom bin search logic, else stick with the aforementioned.

Best regards

Chris