BIG PROBLEM / Negative stock altough not allowed in customizing
Hi all ;
We have a big problem related with negative stock even though disallowed in MM customizing.
The valuated stock of some materials are negative even though negative stocks are not allowed according to Customizing.
When we are making goods movement using bapi, system allowed negatice stock some materials. We check OSS note : “935755 - Negative stock even though it is not allowed in Customizing” . The negative stock was created due to a regular material document, so note solution is not efficient.
When you attempt to enter additional goods movements for this material, system chekcs storage location stocks and doesn’t allow negative stock.
SAP estimates the problem related with :
The duplicated posting entry has created a negative stock figure in
If two documents are posted with a very small time interval between
them, the second document can update the stock table before the first
document does and therefore the system doesnt post an error message.
There is no way to prevent this happening apart from allowing a sample
time between postings so that the database can be updated.
I would recommend you to follow the steps in the note 935755 to
fix this negative stock.
Sap respond like above info. Is there a recomendation about solution path...
Test data ******
Test data: ( Tcode: MB52-Material stock )
Storage location: *
Settings selection: Display Negative Stocks Only
Example material code;
Test data: ( Tcode: MB51-Material documents )
Material : PM100145
Plant : 1006
Storage Location : YSRF
Posting Date : 01.10.2013 - 16.11.2013
Mehmet Ozgur Unal replied
SAP SOLUTION :
Based on our initial problem description, I could read that the documents in question which created negative stock have been posted with the BAPI BAPI_GOODSMVT_CREATE.
To avoid any side effects in the BAPI call, kindly apply the calling pattern of SAP Note 369518 mentioned at the solution section to our custom call of the BAPI. This will ensure that each BAPI call will get anew LUW and such the issue should be solved.