Which movement type to use?

[Former Member]

Hi Experts,

For a particular material, there are 10 items in blocked status in SAP while the goods have already been removed in WMS around 5months back. Now I want to delete the 10 quantity in SAP to get the data in sync. Which movement type should be used here?

Regards,

AK

[joao_sousa2 · Accepted solution]

Now I want to delete the 10 quantity in SAP to get the data in sync.

You don't "delete" stock in SAP. To know what movement you need to use, you need to know the business context that made the 10 units "disappear", for example: internal consumption to cost center (201), scrapping (551), inventory (701/702), goods issue for customer (601), etc.

Without knowing what happened to the 10 units you can't know which movement to use. In order to determine the context, you need to do what Jurgen suggested, find the communication that failed.

[Former Member · Accepted solution]

Apologies as I meant to say that I want to remove the stock from the block stock and wrongly mentioned it as I want to delete the stock.

The materials were most probably scrapped due to wear and tear so maybe mvmt type 555 but let me double check with warehouse team about the details. Thanks for your help.

Cheers,

AK

[JL23]

if there is a real difference between MM and WM, then you can only clear it with LX23.

SAP assumes the WM figure is correct and makes MM equal

[Former Member]

Hi Jürgen L,

We use non SAP system for WMS and for this particular entry data didn't flow to SAP. Also as the items were in blocked state we didn't notice this before. Running LX23 shows "no data available for the plant and storage" (Message no. L1212) but MCHB table shows that 12 items in block stock which needs to be reduced to 2.

Regards,

AK

[JL23]

if you use a non-SAP system for WMS, then it is uselesss to make use of WM transactions in SAP (e.g. LX23)

You have to explain how the data is exchanged between those 2 systems. If you use for example IDOCs   then you need to check if you have a failed IDOC for the message type in BD87, then you need to check the error message and analyze the reason why it failed.

[Former Member]

I thought so too Jürgen about the tcode LX23.

Yes, the data is being triggered from the Warehouse to SAP using idocs. But this being a 5month old data, the idocs have been archived. Let me try to get the details from Warehouse system or may be check the feasibility of triggering the data to SAP once more. I will keep you posted on the details.

Thanks for your help

[JL23]

if it is too much effort to identify the missing documents, then do a physical inventory to correct the situation

[Former Member]

Finally we could trace the manifest for the cargo and the goods have been adjusted in SAP. Thanks everyone for their help

Best Regards,

AK