Configuration Guide
Initial configuration
The initial selection of a plant will determine the key to which all preceding configuration relating to storage locations, bins and stock will be associated to.
Storage Location Activation
This process will configure the storage locations that will be active for IM Multi Bin Management, against the plant selected in the previous step.
The user double clicks ‘Activate Plant/Sloc’ to view the current ‘active’ storage locations on the right hand of the screen. Storage locations that are flagged as ‘active’ will be relevant for the IM Multi Bin Management processes (e.g., Picking / Physical Inventory / General Postings / Goods Receipt).

Existing values can be activated and deactivated by selecting and deselecting the ‘Active’ flag.
To enter a new value, the user selects the ‘Display / Change’ icon () and then selects the ‘New Entries’ option. When all required values have been updated, they select ‘Save’.
Maintain Bins
The physical storage bins must be created in the bin table, in advance of stock usage. The maintenance of bins can be accessed either as part of this main cluster transaction /TCTM/IMB_CFG or directly via transaction /TCTM/IMB_LAGP.
Bins can also created as part of the inventory load - see the User Guides section.
Bins can be flagged for putaway or removal blocks to prevent them being considered for certain processes.
Verification fields and sort sequences can be used for optimization of workflow.

This configuration replicates some WM storage bin functionality:
Removal block (RB)
Placement block (PB)
Dynamic bin (DB)
System bin
Document type (Doc Type)
In addition to maintaining physical IM storage bins, dynamic (or temporary) bins for outbound deliveries and purchase order numbers are generated automatically and will appear as the result of a material document receipt posting or a pick from an IM bin.
The document type is only relevant for dynamic bins and indicates whether the bin was created from the processing of a material document or the picking of an outbound delivery.
In addition, two "system" bins will be created automatically when the IMMB functionality starts to be used:
‘TRANSFERS’ for postings that are not a purchase order goods receipt, used for stock pending putaway, or when a movement is made in an active storage location where a bin is not specified.
‘LOST&FOUND’ for when a user executes a bin-to-bin transaction for stock that needs further investigation.
Maintain Stock
This allows access to the bin level view of materials and their stock levels. There are several other ways to display and edit the bin stock, including an upload transaction, and these are explained in the User Guides section.
BAdi Movement Types
Movement type configuration can be accessed either as part of the main cluster transaction /TCTM/IMB_CFG, or via transaction /TCTM/IMB_BWART.
Movement types must be activated for the BAdi processing so that if posting are made in MIGO and not PreBilt then an appropriate stock change is registered in the IM Multi Bin tables via the system bins. This allows subsequent investigation and processing to correct any stock movements.
Processes using PreBilt applications that are relevant to support IM Multi Bin Management functionality are:
General material movements and postings
Inbound goods receipt
Outbound picking
Any SAP IM movement type can be activated to ensure that a MIGO posting will make an IM Multi Bin entry but only the following have specifically been coded to support using dynamic bins or designated IMMB bins with special logic:
101 GR goods receipt
311 TF Transfer within plant
312 TR transfer in plant
321 TF quality to unrest
322 TR quality to unrestricted
323 TF quality in plant
324 TR quality in plant
325 TF blocked in plant
326 TR blocked in plant
343 TF blocked to unrestricted
344 TR blocked to unrestricted
349 TF blocked to QI
350 TR blocked to QI
501 Receipt w/o PO
561 Initial stock entry
601 GD goods issue: delivery
Any other movement types will just default to using the 'TRANSFERS' bin when posting from MIGO.
Only the following movement types have been coded to update the Goods Receipt Date in the IMMB tables:
101 Goods Receipt for PO
501 Receipt w/o PO
561 Initial load
Last updated
Was this helpful?
