cancel
Showing results for 
Search instead for 
Did you mean: 

Unpacking HU assigned to Delivery with RF (LM25)

Former Member
0 Kudos

Dear,

I am experiencing problems once I try to unpack picked Materials (Transfer Order is confirmed) from a Handling Unit assigned to an Outbound Delivery by means of RF.

What I actually want to do is repack (1. unpack Materials from picked HU, 2. pack Materials into new HU with other Packaging Material).

Note that Handling Unit Management is active and Goods Issue is not yet posted for the Outbound Delivery of course.

In VL02N I can easily do this from the Packing screen (select picked HU, Empty, enter Packaging Material/create new HU, select new HU + Material, Pack).

Now when I try to unpack with LM25 (I saw on this forum this is the transaction for Unpack HU by Delivery), by entering the HU concerned, the system tells me:

Wrong object ID

for HU 1000001010

What am I doing wrong here and how can I make it work?

Thanks a lot in advance for any clues!

Kind regards,

Bart

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi

I'm not sure if this is all related to your issues, but it might be useful info. We got an external specialist to assist with my issue and he showed me how to unpack using LM61. As some of the posts suggest, you cannot use e.g. LM25 or LM22 directly as those screens first require important input from LM61. RF Steps to Unpack:

a.) LM61->Scan Delivery and F4 Nxt

b.) F2 More

c.) F11 Unpack

d.) Scan HU

e.) F4 ByMt (Unpack Materials from HU)

f.) Scan Material in first input enabled field

g.) Type Quantity (to unpack) in second input enabled field and ENTER

(Notice that there are 2 entries for the same material/qty - the one has the checkbox selected and the other doesn't. See it like a positive and a negative)

h.) Now if you save, you'll get a success message that 'Handling unit was unpacked'

The other issue I had was to Unpack a HU child from HU parent. It is very similar to the above. The only difference is that you must scan the child HU to unpack in the last screen and enter/save. I think the idea from SAP is so as you take the HU out of the Parent HU, you scan it, enter and save after you're done unpacking. But just one important note. We have an important requirement that you cannot unpack a Loaded HU or even if the Parent HU is loaded. SAP allows this unpacking with LM61 and we had to build in those validations. Also another nice-to-know is that you can set a breakpoint at SE37 WS_DELIVERY_UPDATE_2 if you'd like to see how SAP unloads using this function.

Best regards,

Adrian Bruwer

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi Bart

Since the TO is confirmed, I suggest to move the pallet from 916 back to its original storage type from where it was picked. You may have to do this using PC/Laptop...or if you have developed custom RF Transaction for bin to bin movement you can use the same

Now please try to use LM25.

Regards

Jayaram


Former Member
0 Kudos

Did one of you find a solution? Please reply if you did. We have the same issue.

0 Kudos


Hello,

I'm not sure if this is still a valid issue as it has been marked as answered, but just to give some background on this behavior.

The transactions LM24 and LM25 should not be called directly in this way (to pack or unpack).  This

is because there is no verification of the delivery or any other data. These transactions are called by LM61 when accessing the packing functionality from there. Can you check if the same error can be seen there?

With regards to Barts original error message, the coding details below where it is raised due to having no delivery reference in LM25 to check the HU assignment against


RLMOBI01

        IF WA_HEADERS-VPOBJ <> CON_OUTB_HU OR SY-TCODE <> CON_LM24

           OR ASSIGN_GI_HU_2_DEL <> 'ON'.

*...Wrong object id &1 for HU &2

        MESSAGE_NUMBER = '325'.

        MESSAGE_VAR2 = PARENT_HU_ID.

        MESSAGE_VAR1 = HU_OBJECT_ID.

        PERFORM ERROR_MESSAGE.

        ERROR_CODE = 9.

        ENDIF.                                          "^_n_795668

      ENDIF.

Regards

Stephen

Former Member
0 Kudos

Hello Stephen,

Issue is still open/valid.

Thanks for your comments.

I tried to use transaction LM61 (note I don't find it in any SAP menu (with SEARCH_SAP_MENU), but once I try, the system tells me: failed to determine screen number..

Kind regards,

Bart

0 Kudos

Hi Bart,

Can you check this when using the standard menus/variants in the RF customizing? (Note, none of the RF transactions appear in the desktop SAP menu and as such can't be found with SEARCH_SAP_MENU).

In the standard ("MAIN") menu path, LM61 can be found through the following:

2. Outbound Process > 1. Goods Issue > 1. GI by Delivery.

Regards

Stephen

Former Member
0 Kudos

Hello Bart,

you got any solution for this? We are having same issue in our system.

Cheers,

Nag