cancel
Showing results for 
Search instead for 
Did you mean: 

No SU suggestion for LT11 bulk storage pick

former_member214692
Participant
0 Kudos

When confirming a bulk storage pick in LT24, system is failing to accepts the SU in the TO line...taking me to LT11 where I am forced to manually enter the SU. System issues message L3295 " Stock removals from block stor.with SU management require entry of SU"

Does anybody know how I can get past this?

Vlad

Accepted Solutions (0)

Answers (2)

Answers (2)

sushant_wanjari
Contributor
0 Kudos

Hi Vlad,

For stock removal from SU managed bulk storage, system does not propose a SU by itself. The user needs to enter the SU when confirming the transfer order. This is standard SAP.

LT24 - list of TO's per material. You can't use this transaction to confirm TO's in single step as the TO's don't have the required SU.

On the RF as well, the user needs to enter/scan SU and then confirm the TO.

-Sushant

MANIS
Active Contributor
0 Kudos

LT24 is a transaction which displays the list of Transfer order based on Material.

LT11 is to confirm the transfer order -single item

So using LT24 you cannot confirm the transfer order, Using LS11 you can confirm line by line however if your Block storage is SU managed then you need to enter the SU manually / Scan during confirmation as for Bulk system propose only Bin number. Quant and SU number gets updated (based on the scan / entry) at the time of confirmation.

former_member214692
Participant
0 Kudos

According to SAP Help (steps 4 and 5), LM07 should suggest the SU. Is that only for an RF mobile transaction system guided, and you are confirming that LT11 does not behave the same?

Picking from Bulk - Mobile Data Entry (LE-MOB) - SAP Library

JL23
Active Contributor
0 Kudos

the step 5 in your link already explains the action: Enter the SU/HU number in the Verify SU field using the scanner or keyboard.

Just imagine the cases where you have bulk storage like here:

each of these pallets has its own SU number. SAP does not know where exactly the SU number 123 is in this bulk storage. Now imagine SAP would propose the SU number. Your warehouse worker would need to climb between the pallet staples to find this SU. Then they would need a forklift to pull aside all pallets in front of this staple to get to the right SU (marked in blue).

Would you really consider this as a best practice process?

former_member214692
Participant
0 Kudos

Jurgen,

Step 4 in Help is not clear, because if you do LM07 for non-bulk, the system displays the SU on the RF screen. So the term 'verify' truly means that you are confirming the SU pick suggestion. With Bulk, the SU is not displayed, yet step 4 states that the SU should be displayed!

The source screen appears, displaying:

  • Source information, including source bin and source SU/HU
  • Material information, including material number and name, quantity and UoM

In any event, putting the SAP help aside, I get your point but it's unfortunate that SAP doesn't at least give the option of us choosing to have the SU suggested. First, there may be a very legitimate FIFO situation where despite the handling involved, you want to issue out the pallet that is considerably older than the one stacked on top or front. Second, as in my situation, our bulk is an 'aisle' X pallets long but no pallets stacked on top. So picking any one pallet is no problem.


My main point of this thread was to confirm standard system behavior which, judging by all the posters, contradicts the SAP Help quoted above. I can close thread shortly.

MANIS
Active Contributor
0 Kudos

in addition to your observation FIFO principle doesn't apply for Bulk storage

former_member214692
Participant
0 Kudos

To add another observation (gripe): I have internal Classic Kanban replenishment in place. For non-bulk, I can issue Full signal and that will automatically confirm the pick TO. But because of bulk, I can't use the Full signal. I am forced to confirm the TO (as it requires SU), and that in turn will do the Full signal