Automatic Batch Copying in MIGO
When transferring stocks with transaction MB1B, such as movement types 311 or 313, the SAP S/4HANA automatic batch copying feature conveniently transfers the issuing batch information to the receiving batch automatically. However, this automatic batch processing is not available when using transaction MIGO, which requires users to manually input the receiving batch details.
Business & Productivity Software
This blog post examines the operational differences between MB1B and MIGO, the customization steps needed to resolve these discrepancies, and user-specific solutions for improving SAP operational efficiency.
Table of Contents
What is Automatic Batch Copying?
Understanding the Issue
Configuring MIGO
New Batch Creation in MIGO
Implementation of Custom Logic
Receiving Valuation Type (UMBAR)
Final Thoughts
What is Automatic Batch Copying?
Automatic batch copying in SAP S/4HANA is the process where the system automatically assigns the batch number of the issuing material to the receiving material during a stock transfer. This feature eliminates the need for users to manually input the batch number for the receiving material, ensuring consistency and reducing error potential.
Computers & Electronics
Consider transferring 100 units of a chemical substance from storage location A to B. The batch number at location A is “BATCH123.” With automatic batch copying enabled, when you perform the transfer in SAP (using transactions like MB1B or MIGO), the system automatically assigns “BATCH123” to the substance at location B, without needing manual batch number entry.
Key Points:
Batch Number: A unique identifier for a specific quantity of material produced under the same conditions, aiding in inventory tracking and management, especially for closely monitored materials like pharmaceuticals or food products.
Issuing Batch: The batch number linked to the material being transferred from one location to another.
Receiving Batch: The batch number assigned to the material upon receipt at the destination.
Understanding the Issue
To reproduce and understand the issue, follow these steps:
1. Customizing Path Configuration:
Navigate through “IMG SPRO → Logistics General → Batch Management → Creation of New Batches → Define Batch Creation for Goods Movements“.
Ensure movement type 311 is set to ‘Automatic / Manual without Check’.
2. Perform Stock Transfer Using MIGO:
Access Transaction MIGO.
Select “Transfer posting”, choose “Other”, and specify the Movement Type.
Enter the Batch Number in the Issuing Storage Location, leaving the Receiving Storage Location Batch Number blank.
Select “Document OK” and press Enter.
Note that the Issuing Batch number is not copied to the Receiving Batch Number.
The reason is the deactivation of automatic batch number creation under customizing settings for movement type 311. This discrepancy can lead to inefficiencies and confusion among users accustomed to the simpler MB1B process.
This issue also occurs with other movement types like 301 and 309.
Configuring MIGO
MIGO's behavior depends on custom settings. For movement type 311 in MIGO, the field UMCHA is set to “required,” necessitating manual entry by users. Understanding this customization helps create a tailored solution to streamline stock transfer processes.
To align MIGO’s behavior with MB1B, customization settings within the system need adjustment. Customizing the field UMCHA (receiving batch) is crucial for movement type 311.
Navigate to: SPRO -> Material Management -> Inventory Management and Physical Inventory -> Settings for Goods Movements (MIGO) -> Field Selection per Movement Type.
Here are the three configuration options for handling the UMCHA field:
1. Set as Required Entry: If the UMCHA field is marked as required, users must manually enter the receiving batch number.
2. Set as Optional Entry: If the UMCHA field is set to optional, the system will automatically copy the issuing batch number to the receiving batch field, though users can manually overwrite it if needed.
3. Field Deletion from Customizing: If the UMCHA field entry is removed from customization, the issuing batch number will be copied to the receiving batch field, but the field will be locked for modifications, preventing manual changes.
New Batch Creation in MIGO
If you want to create a new batch in the Receiving Storage Location in Transfer Postings in MIGO, select one of the options explained above. Refer to SAP Note#2544546 for more details.
Set as Optional Entry
Set as Required Entry.
Implementation of Custom Logic
If pre-defined system behaviors don’t meet operational needs, custom logic can be implemented. SAP provides enhancement/user exits like SAPLV01Z, EXIT_SAPLV01Z_001, and EXIT_SAPLV01Z_002 to customize the batch management process.
Receiving Valuation Type (UMBAR)
The resolution methods discussed also apply to UMBAR, the field controlling receiving valuation type, using similar customization.
Final Thoughts
In SAP, effective stock transfer management is essential for streamlined inventory operations and data accuracy. The discrepancy between MB1B and MIGO regarding automatic batch number copying can be resolved with the right customization settings and enhancements.
By understanding and configuring the UMCHA field settings, aligning MIGO behaviors with MB1B’s automated convenience is achievable. Implementing these resolutions ensures stock transfer processes are more intuitive, less prone to manual errors, and standardized across different transaction methods, driving operational efficiency and user satisfaction.
For more tailored solutions, leveraging user exits for advanced custom logic is a critical strategy, providing the flexibility needed to optimize system performance specific to organizational needs.
You want to see it yourself ? there is not better learning than doing.
Get in touch with the Real SAP System, check our SAP Access.
Don't miss the opportunity.
