cancel
Showing results for 
Search instead for 
Did you mean: 

reg stock posting

Former Member
0 Kudos

Dear all,

we have done GR from production and while doing UD posting we are getting error at present the lot status is UD ICCO SPST

please give advice how to carryout stock posting

regards

venkat

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

UD ICCO SPST means Usage Decision is taken & stock posting is started,Means partially posted.

What you can do is go to QA32 >UD>click on stock posting screen->here check "to be posted" Qty-->post the Qty in appropriate slot & save.

Now check in MMBE is there any material lying in QI stock

Former Member
0 Kudos

Dear sujit,

Thanks for the immediate response,

Stock is lying in quality, when trying to post using QA12 we are seeing error as Stock posting can be done in QM only

regards

venkat

Former Member
0 Kudos

Dear all,

In addition to the above what we are seeing is we are getting status information that status is not allowing to do

regards

venkat

Former Member
0 Kudos

Hi

are you having any user status attached to the lot?

Former Member
0 Kudos

Hi,

Thanks for the responce we have not put any status profile ti insp lot moreover the lot status is as follows

UD: Usage Decision made

PASG: Plan specification assigned

CCTD: insp charcteristics created;

CALC:Sample calculated

STIC: Short-term inspection completed

ICCO:All inspectons completed

SPRQ:Quantity posting required

SPST: Stock posting started

PRTI: inspection instruction printed

Can you please advice why stock is still in quality

regards

venkat

former_member42743
Active Contributor
0 Kudos

The status SPST indicates that stock posting has been started.. I.e. some stock has already been posted. You could maybe reveiew the material documents for the material and batch (if applicable) and see what was posted and when.

You SHOULD be able to use QA12 (change Usage decision) and go to the stock posting screeen and see what is left to be posted. This can then be posted and the lot saved.

If you can't do this, than ther must be something else in play here. As other's have suggested, the most common is that a user status has been created and somehow interferring with the posting. The othe possibility is that some type of user exit is being hit upon and executing code that is causing the errors you see.

If you have the capability somewhere, I would try to run the QA12 transaction in debug with programmer and try to see exactly what is throwing the errors you are seeing.

FF

Answers (0)