In SAP project practice, according to business needs, the SAP system allows business personnel to modify the destination storage bin on the TO document when confirming the TO. After all, when the TO is created, the system automatically suggests the destination storage bin code according to certain rules. When the business personnel go to the shelf, it is possible that the inventory of other materials has been stored on the shelf. Therefore, at this time, the business personnel need to modify the destination storage bin in TO document when he do TO confirmation.
The premise of realizing this function is to set the value of 'Dst bin ch.during confirm' field in the corresponding storage type to 1. As shown in the following figure:
Does it mean that the destination storage bin be modified as long as it is set here when user confirmed the TO? The answer is No.
I encountered a similar phenomenon in my current project. The configuration of destination storage type on the TO has clearly set this field to 1. When user execute LT12 confirms the TO, SAP system still does not allow the business personnel to change the destination storage bin. Why？
It took me a lot of time to find the root cause, I found that the values of " destination storage type " and "destination storage bin" were set in related WM movement type.
This will prevent the user from modifying the destination storage bin when the TO confirmation.
See the F1 help document for the field of "Destination Storage Bin ",
Focus on the last sentence of help document, which means that once the destination storage type and storage bin are specified here, the set values here will be copied to the destination storage type and storage bin fields after the TO is generated, and cannot be modified.
SAP WM module, system allow user to change the destination storage bin when TO confirmation. But if we specify the destination storage bin in related WM movement type, then user cannot change the destination storage bin any longer.
- SAP Managed Tags:
