Skip to Content
avatar image
Former Member

Purchase Requisition Release strategy for Account Assignment F

Hi , I have configured system according to the client requirement for overall release of Purchase requisition . 1. Created Classification CT04 : For Account assignment F , G/L account , Document Type and Plant ( for other Release strategy without Account assignment ) 2. Created Class CL02 and assigned all the classification . 3. Created Group and assigned Class 4 . Created Codes 5. Created Indicators 6. Created Release strategy 7 Activated the overall release for document type 8 Checked OMGQCk everything is green except for itemwise release which is not configured . 9 . Maintained CL20N and visible in CL30n Currently my Purchase requisition is triggering for one Release strategy which doesnt have Account assignment and maintained for a specific plant . But its not triggering for account assignment category F . Cannot find the user exit( M06B0002 ) for the PR release strategy as mentioned in many threads while debugging . Can you please help me in finding a solution.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Jan 22 at 12:09 PM

    Do you what is important for a header level strategy when you use item level information?

    Add comment
    10|10000 characters needed characters exceeded

    • No external can analyze your problem if you do not show what classification is used for your release strategy, and not how the values are in your PO,hence you have to do the analysis yourself. Currently we know as much as the last picture in this blog: Purchasing Release Strategy - an expanded explanation and a GPS through SCN and SAP notes

      A PO does not get by itself a release strategy if you remove a characteristic from the classification, you still need to create a new PO to verify that. Sorry this is not clear from your reply if you did that. And if you did that and the release strategy did not kick in , then it must have to do with another characteristic that does not match.

      Kindly read the blog, it points to various documents and OSS notes that help to trouble shoot the situation if it is not already clear from the blog itself.