Ansicht
Dokumentation
Functional Enhancements in MIGO (Changed) ( RELNMM_IM_470_MIGO )
BAL Application Log Documentation Fill RESBD Structure from EBP Component StructureThis documentation is copyright by SAP AG.
Short text
Functional Enhancements in MIGO (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the transaction for goods movements MIGO has the following new functions:
- Transfer Postings and Stock Transfers
- You can now also set MIGO for transfer postings and stock transfers. To do this, choose the actions Transfer posting, Remove from storage or Place in storage from the list box for the business transaction (Action Can Be Carried Out in the MIGO Transaction).
- Subsequent Adjustment
- It is now also possible to use MIGO for subsequent adjustment in subcontracting. To do this, choose the action Subsequent adjustment in the list box for business transaction (Action Can Be Carried Out in the MIGO Transaction) .
- New Business Add-Ins for MIGO
-
There are new Business Add-Ins available for MIGO.
See release info Business Add-Ins in Inventory Management.
- Change Default Values
- It is now possible to change the default values for the movement type and special stock indicator directly, without calling the dialog box for the default values. Enter the desired movement type and the special stock indicator in MIGO, in the first line on the top right and choose Execute (Enter).
- Manual Entry of Number of GR Slips to Print
-
It is now possible to enter manually the number of GR slips to be printed when posting a goods movement.
The Number of GR Slips field is only visible, if the field in Customizing for MIGO field selection for each movement type has been included. In Inventory Management Customizing, choose Settings for Enjoy Transactions -> Settings for Goods Movements (MIGO) -> Field Selection per Movement Type.
- Manual Selection for the Version of GR/GI Slips
- It is now possible to enter manally enter the version for the GR/GI slip (individual slip, individual slip with check text, collective slip). Until now, the system determined the version from the settings in Customizing (Maintain Conditions).
- The system now behaves in the following way:
- In the header data on the General tab page, the version appears as a list box. When the material document is displayed, the Print button does not appear if the material document has not yet been printed. To create messages during the display, you must now select the checkbox to the right of the printer symbol. Both the checkbox for printing and the version are ready for input, if messages have not yet been created for the material document.
- Version proposal:
If the user manually changes the proposed version, this version is held for the current transaction as the user default and is then proposed during creation of the next document of this transaction type. If the user does not yet have a user default for the transaction type, the default version is determined from Customizing (default version per transaction).
- In the display of the material document, the version saved in the material document is proposed. The user can change the version in the header data and then start message determination from the checkbox. The message determination is executed with the manually changed version. However, the version in the material document is not changed, as this is the version when the material document is created.
Effects on Existing Data
Effects on Data Transfer
Effects on System Administration
Effects on Customizing
Further Information
Release info Replacing the MB* Transactions with the Transaction MIGO
BAL Application Log Documentation ABAP Short Reference
This documentation is copyright by SAP AG.
Length: 5197 Date: 20240520 Time: 200614 sap01-206 ( 86 ms )