cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

How to handle Inventory records with Sales order number on Sap DM?

MaxRogl
Discoverer
0 Likes
204

Dear Community,

We are facing an issue regarding floor stocks with Sales order number on SAP DM.

MaxRogl_1-1749040168640.png

Our goal is to have clean stock, after the last production step is finished the product will be sold to the customer, the stock no longer exists on SAP DM (as on S4 side as well).

In general, we talk about process industries with process orders. Stock is created via goods receipt as this regular should be used. After the stock occurs on DM, this stock is also transferred to S4. In both system we can identify the same postings 1:1, the stock represents a similar picture.

Now we are facing the issue, when the produced quantity was delivered with a regular sales order to the customer, the stock on S4 is reduced (as our assumption was) but  the stock on SAP DM is still available and we start thinking about, how to clean up this stock.

For this case we tried to hand over before the delivery takes place this stock to S4. Via app” manage floor stocks” we assume to transfer stock from a production storage location to the central storage location using the Reason code “RTN-INV_CHANGE – floor stock return to ERP”, what is simply for records with Sales order number not possible.

We tried to achieve our goal (to eliminate the floor stock on DM side) also starting the procedure on S4 side, using a regular transfer posting via MIGO, movement type 311/E from the production storage location to the central storage location.
The result on DM side is an additional created inventory record, the stock is on DM side two times available (once on production storage location and once on central storage location created via movement 311/E).

May I do not understand the procedure fully, but how are these stocks consumed? From my understanding this finally created stocks never will be reduced in SAP DM, these inventory records stay there for a not known reason.

 

Accepted Solutions (0)

Answers (0)