Skip to Content
avatar image
Former Member

Clear stock from IM storage location that is WM-managed

We have an IM storage location that is WM-managed. However, we found that there are remaining stocks in IM (MMBE) but there are no more stocks in WM (LS24). The plant has confirmed that there is no longer any physical stocks as these have been disposed of some time back. How do we clear out the stock from the IM location without changing the WM stock?

In our test environment, we have already performed the following transactions but have been unsuccessful in clearing out the IM stock:

1. Clear inventory difference between WM and IM

- Since there was no longer any stock in WM, received "dummy" stock into WM just to have a bin to clear

- Created inventory record (LI01N), posted inventory count (LI11N) and cleared difference in WM (LI20), then cleared difference between IM and WM (LI21F) by entering an inflated value for WM stock to be cleared

- Result was that IM stock was cleared (no stock remained), but WM storage location 999 (for inventory difference) became negative

2. LX23 - We get an error that there is a deficit of BA stock ("Deficit of BA Blocked 8 CAS: <Material> <Plant> <SLoc> <Batch>

3. MB11, movement type 741 - We get error "Check table T156SY: entry Z01 X X does not exist"

Given these, is this our only option now: Remove the link of the IM storage location to WM so that we could proceed to clear the inventory in IM?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    Aug 12, 2010 at 01:23 PM

    Hello,

    you can use transaction LX23 - Stock Comparison. According documentation:

    3. "Clear differences"

    If you mark this field, the system will generate a batch input session. By starting the batch input session, the differences to be cleared are removed in the IM system. Negative WM stock figures and stock differences in returns will not be cleared.

    If you want to have a batch input file generated for the purpose of clearing the differences, it is important, for consistency reasons, that the materials in the respective warehouse are blocked in order that postings affecting stock figures can be prevented.

    CAREFUL: If you generate this session, all the material stocks belonging to the respective warehouse number are blocked completely, that is, for the duration of the program, no postings affecting the stock in the warehouse will be possible!

    Andrzej

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 13, 2010 at 09:30 AM

    Hi, Andrej.

    We've already tried LX23 but get the error: Deficit of BA Blocked 8 CAS : 161883 0370 WDON 0001457123

    We're looking at removing the WM link of the storage location, but want to get inputs if there are other transactions that could clear out the remaining stock from the IM location without having to change any config.

    Luan

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Please post stock to the batch , change the parameters of the batch as unrestricted in batch master.You may use BMBC (batch infformation cockpit ) or msc1n and change it. You will have to use warehouse movement type 712 , this will also add to inventory. Then do a physical inventory in the ware house and writeoff all the warehouse stock, this will not clear the differences with inventory management , mark the batch for deletion, . Then run LX23 to post differences in inventory management (batch input ) as you did earlier.

  • avatar image
    Former Member
    Sep 20, 2010 at 09:04 AM

    Hi

    I think that you have answered your own question that is remove the Warehouse link from the storage location and then remove the stock from IM and reinstate the link.

    You could try transaction LX23 which compares the stock levels in IM amd WM and if you select 'clear differences' it may remove the stock for you

    Try it in test first

    I hope that this helps

    Frenchy

    Add comment
    10|10000 characters needed characters exceeded