Using one Mvt type in MIGO for different stock types VS using different Mvt types

[Former Member]

Hi experts,

Can somebody, please, explain me what is the difference between using one movement type in MIGO and many in old MB* t-codes for different stock types?

For, example, in MIGO I can use 561 (for initial stock upload) and select necessary stock type from drop down list. But in MB1C I would have to use different movement types, 561 for unrestricted, 565 for block..

I see from testing that it produces the same result. But, for example, in MSEG the stock type field is updated only if posting done via MIGO. For example, for 565 done via MB1C the stock type field is empty, which corresponds to unrestricted stock type (although the quantity is posted to blocked stock - checked in MCHB)

Are there any other differences to know?
Which method is to be used best in practice?
This I believe is relevant not just comparing MIGO and MB*, but also comparing two methods inside MIGO, as we can use in MIGO one Mvt type with different stock types or use different Mvt types for each stock type.

Thank you!

[JL23]

When did your career with SAP begin?

Already beginning of the 21st century SAP decided to replace the old MB* Transactions with MIGO.

Almost 3 years ago the decommission was announced with OSS note 1804812 - MB transactions: Limited maintenance/decommissioning

with the ERP 6 came a system message M7 499 wich tells the user the transaction is obsolete.

So you should not need to think about or evaluate today whether to use MB transactions or MIGO. You should just assume MIGO is the transaction to use.

the movement types are the same, no matter whether you use MB transactions or MIGO. There exist no movement types that could only be used on one of both

[BijayKumarBarik]

If you want enjoy as and when material consumption to the project, and this is business process- better create valuated material and receive material with 101 movement type(MIGO) and supply those materials to project with 221 movement type with MB1A. Other related KPI along with restrictions - you need to manage from business side

[Former Member]

Yes, I've tried two options Mvt 561 + stock type "blocked" from drop-down and Mvt 565.
Both produced the same result (except that in MSEG the stock type field is updated only in first case).

So, I'm wondering if there is any difference between the two?

[JL23]

Already tried this "Mvt 561 + stock type "blocked" from drop-down."?

There are movements where this field makes sense and is really used like with the 101 receipt.

And there are movements which have for each stock type its extra movement type, like 561, 563 and 565.

This is SAP design and you won't change it.

[Former Member]

It is clear for me that MB* transactions are obsolete today and MIGO replaces them.
But my question was more about dealing with stock types

So thinhking only about MIGO, what is the difference between two ways, when posting to blocked stock?
1) Mvt 561 + stock type "blocked" from drop-down.
2) Mvt 565.