Error while determining ref.mov.type for WM via Table 156S: 161/X/X/ /L/ /

[Former Member]

Hi all,

I'm facing this error while creating the Outbound Delivery starting by an MM-Stock Transfer Order via VL10B.

The system returns me this message: "Error while determining ref.mov.type for WM via Table 156S: 161/X/X/ /L/ /".

If I check the SPRO-Logistics Execution-Warehouse Management-Interfaces-Inventory Management-Define Movement Types-"Assign WM Movement Type References to IM Movement Types" I'm not able to see any row that respect the SAP suggestion: 161/X/X/ /L/ /

I imagine that "L" means "Goods movement for delivery note".

How can I resolve this problem? How can I make the correct row appear in the table?

As for my knowledge is not possibile, by standard, to add news rows directly in this table.

Help please,

Thanks,

Marco

[Former Member]

Hi All,

we have done a configuration in the customizing and now it is working.

thanks,

Vittoria

[MANIS]

Could you please share what was missing and what configuration you made so that other can get benefited who is facing the similar error.

[former_member550187]

Actually we need to update the quantity and value for the particular material type for the specific valuation area, for ex for packaging material we need to maintain it for material type VERP in t-code OMS2

[transcanada2003]

Hi guys, I know this is old. I am facing the same issue for 501 mvmt type while creating inbound del in vl31n. KBA 1733520 has been deleted from SAP knowledge database. Can anyone share this document with me if you have a copy? Or suggest a solution? I have tried to main the entry in OMLR but didn't help. Thanks a lot.

[Former Member]

there was an entry missing in the OMLR.

thanks,
Vittoria

[Former Member]

Hi Marco

Have you tried with a rule in "LE-WM Interface to Inventory Management" activity? (Tx OMLR) A setting similar to screen

Previously you should create/change Schedule line categories, according my understanding  from your post

Regards

Maelo

[MANIS]

Last logged in date of Marco Cariello is May 6, 2014 2:50 PM and the post is very old from Jan 2014 so i  doubt that u will get a prompt response from the Marco Cariello

[JL23]

The KBA 1733520 - Error L9029 (Error while determining ref.mov.type for WM via Table 156S: &) during deliver...  tells how to add entries

However, I actually think there might be something wrong from the process, as I do not have this entry either.

161 is a return, which is usually originating from a purchase order. It should have a B instead of the L in this sequence.

is it the first return order ever?

[Former Member]

Hi Jürgen L,

I have done customizing as like it is written in this document:

• http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c05e2251-91f0-2c10-4e91-e919468e4...

There are returns completed in the systems, but not from this process of Stock Tansfer Order.

I kindly ask you to give me more suggestions about process errors.

Thanks,

Regards,

Marco

[JL23]

This document just has the customizing steps for a STO, but your problem is a return to vendor. Right now I do not see the connection. Maybe I should have said this earlier.

An outbound delivery to a STO, should have a movement type 641 or 643 or 645 or 647.

a return will have a movement 161.

We have a few documents with detailed steps in MM.

Use the search term: STO return

then restrict on the left to MM

and further restrict on the left to Documents.

if you are looking for documents on returns to vendor

then just use the search term: vendor return

then restrict on the left to MM

and further restrict on the left to Documents.

[Former Member]

Hi Jurgen,

I kindly ask you to indicate where I can set the movement type 641, 643, 645, 647 in the customizing for the outbound delivery for STO.

Thank you for your availability,
Vittoria

[JL23]

The movement types are entered in IMG > SD > Sales documents > Schedule lines > Define Schedule line Categories

Honestly, I never needed to do this , we are working with the standard SAP given Schedule line categories, and they are just like they were when the system was implemented initially.

And when you create new categories, then just copy from the closest similar.