Skip to Content
Author's profile photo Former Member

Palletization data from transaction MIGO is not given over into the WM Transfer Requirement

In this example I do a Goods Receipt (GR) for a Purchase Order (PO) into a Storage Location where Warehouse Management is activated.

Please note, that old MM transactions (like MB01, MB1A, MB1C, MB11 and so on) do not offer the same functionality.

In transaction MIGO optionally you can enter the palettization data for WM.

Or it will be filled out automatically from the tab “Warehouse Mgmt 2” in material master, in case you have already entered this data for the Storage Type, like this:

2014-09-18- 14-42-12.png

If this is not done in advance, you still can enter the data in MIGO. Sometimes the default (or the calculated result using the default – see “Qty per SU” fields on below picture) from the Material Master is not good for you. In this case you can delete this quickly – see the red marking on the picture below – and you can enter the data you need.

2014-09-18- 14-58-05.png

But even if you enter the palettization data for every GR, the system still checks the flag T321-WENUM, and the data is only stored when this flag is ‘1’. If it is not set up, this data is not stored in the Material document, therefore it will not be given over to the Transfer Requirement, too.

You can set this in SPRO (IMG -> Logistics Execution -> Warehouse Management -> Interfaces -> Inventory Management -> Define Movement Types -> LE-WM inventory management  -> column ‘Add. data’ = ‘1’.

(In the old MM transactions you only got popup window – instead of the WM palletization tab – during GR to enter palletization data when you have customized table T321 to contain the following value: T321-WENUM = ‘1’.)

So if no palletization data is in the TR after MIGO, then please check the relevant movement type if T321-WENUM is set to 1.

Debugging hints:

If you don’t know by heart which line you have to edit in table T321, then place a breakpoint on the last line of from T321_LESEN (within include LLCMBF3F), and when program stops and debugger opens, you can check entries in table T321.

From this you can identify which line of table T321 is found.

By the way, the same form is called in the following cases, too:

1. at TR creation for material document (but not called in LT04 during TO creation)

2. at inbound delivery creation in VL31N, e.g. for PO

2.1. at TO creation for inbound delivery in LT03

3. at outbound delivery creation in VL01N, e.g. for SO

3.2. at TO creation for outbound delivery in LT03

4. at posting change notice creation from material document (e.g. posting change into blocked stock using IM movement 344). But not called in LT05 during TO creation.

Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.