Picking lower-level Handling Units via RF Transactions

[Former Member]

Hi experts

How can I randomly pick Handling Units to my transfer orders using the SAP RF transactions?

I am trying to go into my warehouse and randomly pick boxes which are nested into a top level pallet HU which is the Storage Unit in the Storage Bin.

Pallet = Top Level HU = Storage Unit

Box = Lower level 'nested' HU

I know this is possible when confirming a Transfer Order using LM12 to remove lower level handling units from a Storage Unit. This can be done using the 'pick handling unit' functionality.

I have not been able to see how this can be done using the RF LMxx transactions.

Ideally I would like to scan the lower level HU's and pick them onto my Transfer Order using my handheld device and SAP LMxx transactions.

Please advise

Edd

[former_member536836 · Accepted solution]

Whenever you do picking you scan Higher level HU in case of nested HU. You can not scan lower level Hu. If you want to scan lower level HU then I guess you can do empty higher level Hu & then scan lower level Hu.

Please check.

Regards,

Prashant

[former_member536836]

Sorry ,I missed out you have to repack the lower level HU & then scan the same.

regards,

prashant

[Former Member]

Hi,

From a proces point of view, the following. In case you receive nested HU's and you dont break them up into the lower HU's, you expect to deliver the nested HU to customers. I.e. you;re only interested in the highest level HU. If this is not the case, you should unpack or repack before performing GR on the inbound delivery.

If accidentely you want to pick lower level HU's, you need to repack. The problem is that WM only created an SU number for the highest HU level and not for the lower.

MZ

[Former Member]

Hi

I have a follow up question for this:

Assuming the full nested HU has been GR'd and posted to the Warehouse as a Storage Unit, how do I 'split' my nested HU into lower level HU's in the warehouse? Will this 'split' them into Storage Units?

I wish to keep the information related to the nested Handling Units as these contain HU's contain the materials batch and serial number information. Therefore, I do not want to simply empty the entire HU and start again

My requirement is to randomly scan lower level HU's to pick for an Outbound Delivery

Kind Regards

Edd

[Former Member]

Hi Edd,

In my opinion the even if you unpack the higher level HU the information regarding the material batch and serial no will not be lost. The information contained in the lower level HU was there and will be there. you simply unpack the higher level HU and since it is SU managed as well the lower level HU no will become the SU no.

Regards,

Vijay

[Former Member]

Thanks Vijay!

What standard transaction would I use to unpack the Handling Unit? And is there an available RF transaction?

Also, would this need to be done in either an Interim or Special Storage Type such as a pick point? Or can it be unpacked in any Storage Type

Warm Regards

Edd

[Former Member]

Hi,

pl check the storage type 923 and bin pack.bin or some other bin maintained for packing n unpacking. there u can use the Tcode HU02 to pack or unpack it. other T codes could be HUPAST if you have maintained the packing station in customizing.

The correspondoing RF transaction for packing and unpacking HU is LM19 and LM22 respectively.

Regards,

Vijay

Edited by: vijay kumar on Jul 13, 2009 12:31 PM

[Former Member]

Hi thr,

I have similar scenario....Would like to seek your inputs...

We have WM managed SLoc, with HUM.

1. FG is packed into 1st HU (Tray) and then into 2nd HU (Container).

2. Container is received as GR against Process Order.

3. Then it is transferred to Warehouse via a TO.

Reqmt is : TO use RF device at both packing stations and to automate the whole process.

Request for your inputs.

Regards

Yatin Dhruva

[Former Member]

Hi Gurus

Here is my solution.

Storage units are only available at the top HU level (as Storage Units), and we are using RF transaction LM06 to do our picking for an outbound delivery. This transaction does not allow picking HU's underneath the top-level HU because these are not available in the warehouse as SU's.

Further, the transactions such as LM45, LM46, LM47 for picking lower level HU's were quite unwieldy and required us to copy these transactions and custom develop them. We ruled this out

Therefore, we decided to stick with LM06 to do our picking.

If we need to pick lower-level HU's we have developed our own custom 'unpacking' RF transaction which can rapidly unpack a HU to the next level down. This transaction moves the HU to the '923' interim storage type, and then unpacks it 1 level, before moving all the lower level HU/SU's back to the storage type you need them in

Would like to hear how anyone else has gone about this problem of picking 'nested' HU's underneath the top level HU/SU

Cheers

Ed

[Former Member]

Hello Ed,

Thanks for your feedback concerning LM06 tcode.

I'm struggling against a similar problem, may be you can help.

- there are nested HUs in the warehouse (the stock was packed for some customers who require a full packing description)

- so there is a higher-level HU (the pallet) packing lower-level HUs (the boxes on the pallet). The boxes contain many different products (ie many different quants)

- the Picking TO (with movement type 601) is created to the destination ST 916. The source HU is the higher-level HU. There is 1 TO item per product on the pallet. The destination HU is not determined yet.

- Since there are many TO items, the system requires a pick-HU

- using tcode LT12, WM displays a pop-up window and asks for the lower-level HUs

- using the LM06, WM displays an error message that says that there is not enough stock on the higher-level HU.

Do you know if it is possible to configure the LM06 to get the same kind of function as the LT12 ? Or is the LT47 a better choice ?

Thanks for your feedback.

Cyril

[former_member373709]

were you able to resolve this issue ?