SAP configuration and requirements

This app relates to SAP standard transaction MIGO – Goods Movement, which allows actions to be carried out in Inventory Management, resulting in a material document being generated. These postings will result in posting change notices in Warehouse Management if the issuing storage location is relevant for WM.

IMG setup

Standard SAP IMG configuration that this app considers is as follows:

Cost centres

All relevant configuration relating to cost centres:

Controlling > Cost Center Accounting > Master Data > Cost Centers

MIGO

All relevant configuration relating to MIGO:

Materials Management > Inventory Management and Physical Inventory > Field Selection for Goods Movements Initial/Header Screens

Materials Management > Inventory Management and Physical Inventory > Settings for Enjoy Transactions

Materials Management > Inventory Management and Physical Inventory > Goods Issue / Transfer Postings

Materials Management > Inventory Management and Physical Inventory > Goods Receipt

Materials Management > Inventory Management and Physical Inventory > Movement Types

Integration with warehouse management

If required, SAP IMG configuration and PreBilt App Master Data can be setup to enable the source or destination storage type and storage bin to be entered in the General Postings app and then passed through to the Stock Movements app to create the transfer orders from the transfer requirement and then confirm out of or into the entered bin. This requires that automatic transfer order creation is not activated in SAP as PreBilt will control the transfer order creation.

Alternatively, the app can be used just to jump the transfer orders that are created automatically in the background from the transfer requirements but then the source or destination bin is irrelevant in the General Postings app.

Output determination

All relevant configuration relating to output determination:

Materials Management > Inventory Management and Physical Inventory > Print Control > General Settings > Print Version – determine default setting for transactions:

• MIGO_GI

• MIGO_TR

VLMOVE

The configuration for VLMOVE allowable movement types based on specific processes as defined in:

Logistics - General > Handling Unit Management > Basics > Define Movement Types for Inventory Adjustment Postings

Where SAP has constraints in VLMOVE those same constraints will be manifest in the PreBilt transactions. Examples of this include the following:

• Plant to Plant transfers of Handling Units that contain materials in Quality or Blocked status. OSS note 496992 explains that the goods issue from blocked stock and quality inspection stock is not supported and that SAP does not have a solution.

• Serial number capture is not triggered in the transfers and movement of handling units since they are already linked to the handling unit.

Master data requirements

Output determination

Setup of condition records for relevant output type and transaction/event type in transaction code MN21-MN22.

If an output is required, the user’s parameter ID ‘NDR’ (Print via output control in MM - Inventory management) should be maintained in transaction code SU3. This is used in the posting of the material documents and can be changed dynamically in the app.