Change the Destination storage type for Putaway during palletization

[Former Member]

Hi,

we have 2 storage types. One is used for bulk storage (001) and another one is used for active (002), where all the stock will be picked from.

We have a scenario where the customer wants to do the palletization during the Transfer order for a Material document posted. User wants to change the system proposed storage unit breakdown by the  actual storage unit quantity received. Vendors will not always send the storage unit as per the agreed quantities. So the user will have to change the storage unit quantities based on the actual quantity received which will be different from the SUT quantities maintained in material master.

Now, once the palletization criteria entered and during putaway, we need to change the destination storage type based on the available stock in the active storage type (002). We do this to keep the stock at maximum bin stock so that the picking will not be affected. So, only the actual stock required in the Active storage type (002) will be moved to Active Storage type and the remaining stock will be moved to the bulk storage type (001).

I am using the enhancement MWMTO007 for this purpose and EXIT_SAPML03T_002.

The system is working fine if we allow the system to create the SUs based on the SUT quantity in Material master. But if we change the quantities for SUs it is not changing the destination storage types and is going directly to the bulk storage type (001). Please help me out if we can change the destination storage types after the palletization data modified and once we click on the Putaway (foreground / background). Should we use any other enhancements?

Configs:

Our Storage type search is defined as : Bulk (001), Active (002)

Bulk Storage type is maintained with "User Exit Active" and the putaway strategy is "Blank"

Active Storage Type is maintained with Fixed bin Putaway strategy and "user Exit" is not  checked.

Regards,

Vijay

[mihailo_sundic · Accepted solution]

Since this is a custom development in a user-exit, the best advice I can give you is to debug the code, put a breakpoint in the user-exit, and try it out in both cases and see why it works in one case and not in the other.

There must be some point at which the process goes in different directions, you need to find that and see what's the cause, by debugging.