Usage decision stock posting issue

[jeffrey_pepito]

Dear All,

             In QA32, i did the results recording for the lot, saved it, then i made UD. So here after doing stock posting and when i click save,i get message UD saved.But when i refresh the same lot exists still. The status of lot is still INSP RREC SPRQ. I also checked in MMBE,the stock is still under Quality.

     For your notice:

Earlier i did force completion of results and when i make UD and save,i got the "Change long text message" and i couldn't save. So inorder to avoid it,i made complete result recording. So now i don't get that long text.But stock is not getting posted.

          Am a PP consultant and i have limited knowledge in QM,kindly get me through this.Thanks in advance.

[former_member185453 · Accepted solution]

Hi,

As per your system status the quantity is not yet posted to unrestricted (SPRQ- Stock posting required) though you have done UD. There is a " Insp. lot posting"  Tab in "Record Usage Decision" QA11, first you need to post the quantity before UD, but this is a manual function.

for the current lot, you change the UD in Transaction QA12 and do the posting manually to unrestricted and then save usage decision.

You need to do one IMG setting for auto goods posting during UD. in QS51 maintain the posting proposal in usage decision to unrestricted.

hope this will help to solve your issue.

Regards,

S Ahmed

[jeffrey_pepito · Accepted solution]

Hello Ahmed,

                      Thank you for your reply. I did according to what you said,but still i face it. It gets saved with status "Usage decision for lot xxxx yyyyyyy saved". But when i refresh, i get a pop up message, "Express document 'Update was terminated' received from Author 'xxxx'". And when i click continue,again the same lot appears with same old status. I think the problem is here. Am not sure. Kindly help me.

[busyaban7 · Accepted solution]

Hi Jeffery,

This may not be a standard issue, as after UD has been posted (which I believe was linked to posting proposal in config), stocks should have been moved to Unrestricted/Blocked stock. This is a separate process then result recording. But as you said, you did everything correctly, and even though your UD in QA11/QA12 is not working, there may be some custom enhancements/authorization impacting this process.

May I advice you to work with your ABAP colleague by replicating this scenario in Quality/Sandbox or Development system, and check what's going wrong here.

Thanks,

Arijit

[jeffrey_pepito · Accepted solution]

Hello Arjit,

                    Thanks for your reply and as you said, yeah even QA11 and QA12 are not working. And we're running this in development server only. You've mentioned "which I believe was linked to posting proposal in config" where to check this config whether i've linked. I mean which t-code. And as you said yeah i need to work with abaper.

[busyaban7 · Accepted solution]

You can try QS51 - Catalog type "3 - Usage Decision", your plant code, enter. Now check the selected set and go to Selected set code => Now against the UD code, go to the tab for posting proposal UD tab => check the one assigned for UD = A & R.

[jeffrey_pepito · Accepted solution]

Hello Arjit,

                    I haven't assigned anything for A and R. Only for "Accept with deviation" i.e A1, i've maintained "To unrestricted use".

[anand_rao3 · Accepted solution]

Hi Jeffrey,

I agree with Arijit here. This is not the standard system behavior. I am also reading in your one of the posts that you are getting message as update terminated. When you get such message it indicates that the database is not getting updated. You should analyse this with your basis consultant in SM13 transaction code. There you will get the exact reason behind this. Also try debug the program just before saving. By doing so you will get the conditions which are not meeting.

Anand

[busyaban7 · Accepted solution]

Hi Jeffrey,

Pls can you share the screenshot for all the codes form QS51 for your plant. If the posting proposal is not linked, then the stock posting will not happen in background and you need to do that manually in QA11. On top of that it seems there is some enhancement blocking you, which I believe you will take it up with developer.

Thanks,

Arijit

[jeffrey_pepito · Accepted solution]

Hello Arjit,

                   There were two lots in QA32 in which first lot had forced inspection result recording and second one was a normal inspection result recording it was not forced. Earlier in morning i deleted the three text ids(QALS,QAVE,QBST) from object "QPRUEFLOS" in tcode SE75. Then later now i added two text ids "QALS" and "QAVE". Then again i tried the second inspection lot in QA32. When i clicked save after UD,it took me to some text editor. I clicked back button(Only it was enabled) and came out. When i refreshed the lot was gone and stock posting happened.I checked in mmbe. But when i tried with first inspection lot,i get the same error "update terminated".And it remians there. I'm wondering how stock posting happened for second lot.

[jeffrey_pepito · Accepted solution]

Hello Anand,

          Thanks for your reply.Yeah i could understand its not standard behaviour. I consulted with basis team and they told its ABAP's job. I referred in net and found that sap note 196113 has to be implemented. So need to consult with ABAPers too.

[busyaban7 · Accepted solution]

HI Jeffrey,

I still do not have any clue on why you need to have this enhancement in place by deleting the text objects form object header - QPRUEFLOS. Are you trying for sending any quick emails, or something to any stakeholders? If so, there are always other ways to achieve it, like Follow-up actions, etc.

Please can you try adding the 3rd object QBST, as this seems to be related to stock update text object. May be after that you can try for a new case and suggest your observations.

Also please note that stock posting linked to UD code, if a separate function altogether and SAP gives this link through stock posting proposal. Else you can manually do through QA11, for stock relevant inspection types. This functionality is something separate then the one you seems to be trying to achieve. But as you know that SAP is quite integrated, there could be a chance that it could mess up with the system even for a small alteration like the one you have tried. I think that might have been the root cause for the issue you are experiencing now, but I am not too sure...

Thanks,

Arijit