LT06 L3 009 Bulk storage type putaway is not respectingthe putaway strategy

Symptom

• Bulk storage types are used but during putaway, bins with available space are not chosen.
• No storage bin is found during putaway for a bulk managed storage type.
• Error L3 009 is issued stating that no bin is found even though there are available bins with space for putaway.
• "No destination storage bin to be found in storage type &" is issued when putting stock into a bulk managed storage bin even if bins are available.

Environment

• Logistics Execution (LE)
• SAP R/3
• SAP R/3 Enterprise 4.7
• SAP ERP Central Component
• SAP ERP
• SAP Enhancement package for SAP ERP
• SAP Enhancement package for SAP ERP, version for SAP HANA

Reproducing the Issue

1. Goto transaction LT01 to create a transfer order (TO) to move stock into a bulk managed storage bin.
2. Enter all relevant data on the initial screen (warehouse number, movement type, material, quantity, plant, storage location, batch value if relevant).
3. Press enter.
4. Select the source bin to pick the stock from.
5. Enter a bulk managed storage type and storage bin which has existing stock (for a different material / batch) in the destination data fields.
6. Press enter.
7. Error L3 009 is issued and the bin entered cannot be used.

Cause

If there is already material in the storage bins available but it's a different material than the one being putaway, the system will not force mixed storage. This is standard system behaviour. The user can manually enter the bin data and it will be accepted, but it will not be automatically determined.

The system will search for an existing bin with the same material (and batch if relevant) and will put the stock here if available. After this, the system will look for an empty bin. If nothing meets this criteria, the error message is shown.

The system behaviour is exactly as described in the documentation, i.e. the logic for putaway into bulk first checks for existing stock (when batch-specific totals are set this also means stock with the same batch number) and then searches for an empty bin if no existing stock exists. SAP note 88450 explains that mixed storage can only be produced by manual or userexit intervention and in those cases the customising is checked to verify whether mixed storage is indeed permitted.

Resolution

If it is a requirement to force mixed stock in these scenarios, it can be achieved via userexit coding. Please review enhancement MWMTO003 for this purpose.

首先按照物料+批次推荐仓位，如果没有，推荐空仓位。