Show TOC
Enjoy
Transaction for Posting Goods Movements (MIGO)
Use
Prior to Release 4.6C, you could only use the
transaction MIGO to post goods receipts from external procurement.
As of Release 4.6C, you can also use the MIGO
transaction to post the following goods movements:
- Goods receipts for an order
MIGO also supports the following
functions:
- Automatic creation of transfer
requirements
- Entry of an external sales value
In the standard
system, the field for entering an
external sales value is hidden for all movement types. If you
require this field (for example, when entering a goods receipt), you have to
switch it on in the activity Field Selection per Movement
Type in Customizing for Inventory Management.
- Entry of pallet data for the Warehouse
Management System
The new functions in this transaction replace
the following old transactions:
- Goods receipt for order (transaction code
MB31)
- 'Other' goods receipts (transaction code
MB1C)
- Goods issue (transaction code
MB1A)
- Cancel material document for goods issues
(transaction code MBST)
- Change material document for goods issues
(transaction code MB02)
- Display material document for goods issues
(transaction code MB03)
The MIGO transaction is still subject to the
following restrictions:
- Subsequent adjustment of stocks of material
provided to vendor is not yet possible
- Generic article processing is not yet possible
(SAP Retail)
- You cannot carry out goods movements using
structured material (SAP Retail)
- Merchandise distribution is not yet possible
(SAP Retail)
- Supplementary Logistics Service is not yet
possible (SAP Retail)
The old transactions will remain fully
functional until the restrictions of the MIGO transaction are resolved in a
future release.
Effects on
Customizing
In Customizing for Inventory Management, you
can make the following new settings via Settings for Enjoy
Transactions -> Settings for Goods Movements (MIGO):
Here you can define
which fields are visible in the header and detail data. You can hide
pushbuttons you do not require.
You can define
individually for each movement type whether fields are required entry fields
or optional entry fields (for example, Reason for movement,
goods recipient , or sales
value).
In this step, you
can restrict the number of chooseable transactions and reference documents.
For example, if you never work with subsequent deliveries or goods receipt
blocked stock, you can hide these transactions in the list of possible
entries. If you never reference transport documents or delivery documents in
Shipping, you can also hide these document types.
See
also
For more information, refer to the
documentation on the MIGO transaction. To call up the
documentation, choose Help in the application
toolbar in MIGO.