Enterprise Resource Planning Blog Posts by SAP
Get insights and updates about cloud ERP and RISE with SAP, SAP S/4HANA and SAP S/4HANA Cloud, and more enterprise management capabilities with SAP blog posts.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

New Feature: MIGO Can Auto-Determine Warehouse Bin for Production Order/Reservation in 2502.2

ecco_liu
Product and Topic Expert
Product and Topic Expert
3 weeks ago
459

During the process of supporting ERP Public Cloud customers, we have received requests from several customers using Cloud WM on public cloud for a direct component issue to production orders through MIGO, with the functionality to determine Bin locations. Although MIGO allows for stock determination and batch determination when issuing components to production orders, previous system versions did not automatically suggest the physical Bin locations where the stock is stored. This limitation has inconvenienced users and hindered operational efficiency.

After receiving feedback from customers on these demands, the ERP Public Cloud WM product team assessed the reasonableness and priority of these requests. Following product development, starting from SAP S/4HANA Cloud Public Edition 2502.2, customers enabled with Cloud WM can now have Bin locations determined by the system directly in MIGO during component issue to production orders (MIGO, movement type 261, for goods issue to production orders or reservations). For detailed functionalities, please refer to the following test results.

First, create a production order in the internal system, with components issued from an WM-managed storage location, as shown below:

ecco_liu_0-1745653486493.png

 

Next, proceed to the MIGO transaction for component issue. Initially, the batch and bin location fields are empty. After clicking the "auto bin" button, the system will automatically find the appropriate bin location and batch based on predefined rules and populate these fields on the screen.

ecco_liu_1-1745653486497.png

 

ecco_liu_2-1745653486500.png

 

ecco_liu_3-1745653486503.png

 

 

ecco_liu_4-1745653486505.png

 

Click Post button and goods issue was posted successfully:

ecco_liu_5-1745653486510.png

 

Inspect the warehouse stock in the Warehouse Management Monitor application:

ecco_liu_6-1745653486515.png

 

Automatic warehouse determination and batch recommendation require comprehensive warehouse management configurations. You can also define outbound rules, such as FIFO (First-In-First-Out) or LIFO (Last-In-First-Out), where the system will find the appropriate stock based on the configured inventory search strategy.

ecco_liu_7-1745653486518.png

 

 

ecco_liu_8-1745653486520.png

 

ecco_liu_9-1745653486522.png

 

ecco_liu_10-1745653486524.png

If the BOM master data for finished product materials in a production order has a Production Supply Area specified for component materials, and the component materials also have a control cycle for WM (with the bin field maintained), then the default bin specified in the control cycle for WM will be displayed when issuing components for the production order using MIGO. For detailed information, refer to the internal system test screenshots below.

  • First, create the Production Supply Area:

ecco_liu_0-1745827795806.png

 

  • Next, maintain the control cycle for WM and link it to the bin location:

ecco_liu_1-1745827795827.png

 

  • The component materials in the BOM master data for the finished product need to be linked to the Production Supply Area created in the previous steps:

ecco_liu_2-1745827795840.png

 

  • Create a new production order:

ecco_liu_3-1745827795849.png

 

  • When issuing components using MIGO, the bin location field automatically populates with the default value from the control cycle.

ecco_liu_4-1745827795862.png

 

If the customer is not satisfied with the default bin location brought out by the control cycle for WM, they can use the auto bin functionality within MIGO. This allows the system to automatically determine and suggest a bin location based on the cloud WM stock removal strategy. If the recommended bin location is still not satisfactory, the customer can manually maintain a higher priority bin location for the final posting of component issuance. It is important to note that when manually specifying the bin location, the batch must also be updated accordingly.

 

The Cloud WM functionality in the public cloud system is currently quite robust. Whether it's shelf management for materials, warehouse inbound and outbound operations, handheld terminal scanning requirements, or system integration needs, there is comprehensive product support available. We recommend that customers with warehouse management needs prioritize using the free built-in warehouse management features (Cloud WM) in the ERP public cloud. If you have any product-related feedback during use, please feel free to contact us. Thank you.

 

For more detailed information and updates on the MIGO auto-bin functionality, you can refer to the SAP Help documentation: What's New in SAP S/4HANA Cloud Public Edition 2502.2: Automatic Bin Determination During Direct Goo....

Popular Blog Posts