How to correct the UD stock posting issues

[kalyanaramachandran_krish]

Dear,

UD has been posted to an inspection lot but stock has not been updated to UNRES stock.

What could be the reason and how to correct this...

[busyaban7]

Hi KK,

Please provide some more inputs -

i) What is the process followed and what is the inspection type created?

ii) Do you have posting proposal added with the UD code?

iii) What is the system status for your inspection lot created? Does it has the status 'SPRQ' or 'SPST'?

If you see your inspection lot material is still under 'Quality' Stock in MMBE, though the UD has been applied correctly, please try the SAP note 48815. It should post the material document with MvT 321 and post the stock form "Quality' Stock to "Unrestricted Stock'.

Thanks,

Arijit

[kalyanaramachandran_krish]

Inspection type 01, the process is When the UD processed the quantity of the Lot will be automatically posted to un-restricted stock type.

But in the recent time we have been facing couple of instances in which though UD completed, stock not updated ( checked at selected set it is set correctly for UD followup action) The status is sometime SPST and some time SPRQ.

What we are doing now is using sap notes program we reset UD to open qa11 and re run ud which post stock corrctly to UNRES.

Also, one more help is required to implement a preventive method to stop re-occurence of this UD posting issues.

What we have to do for this.

[busyaban7]

So it means that the proposed SAP note 48815 is the quick fix which is working fine for you, right?

Well, I guess there may not be any specific single reason as to why materials behave like that during UD. Could be varrious system & process related performance issues or material blocking, or may be some other issues involved.

You may raise a message with SAP for further checking, on this performance related issue.

[kalyanaramachandran_krish]

Do you mean that we cannot take any preventive measure to stop re-occurrence of this in future?

[busyaban7]

To my understanding, there may not be any such full proof system in place in SAP (...forget it that is specific to any module or not..) where performance issues will never occur. Based on the amount of custom stuffs existing, transaction load on system, logical queries / enhancements working to support business process, etc performance is bound to differ form client to client, system to system. That's why the recommendation is always to stick to standard SAP provided ways of working as far as possible to minimize/eliminate such performance issues.

For better response, let other experts also pitch in in this thread and share their views/experience on such topics. And my recommendation would be to open a thread with SAP for any specific performance related issue and get their thoughts on it.