Skip to Content
author's profile photo Former Member
Former Member

Suppress PO output in case a PO is updated by a purchase order response

Experts,

we are in SRM 5.0. We are trying to suppress any PO output when a PO is updated by purchase order response. We are experimenting with PO output start conditions (Customizing). No succes until now. We tried to check whether the object status table has status 'Variance in PO response' (I1352). No effect.

Does anybody have a clue or even better, an example, how to achieve this without the use of BADI's or defining any customer fields?

Apparantly when a purchase order is updated via the purchase order response the BBP_DOC_CHANGE_BADI is not triggered, or at least we were not able to debug it, so it looks like this is no option either.

Any suggestions?

Thanks for your help, Maurice de Feijter

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on May 11, 2011 at 11:44 AM

    Try this note:

    Note 1462576 - Unwanted output generated for PO

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on May 12, 2011 at 01:03 PM

    Hello Jay, thanks for your suggestion. We are currently implementing SP 14 to 17 in which the note you mentioned is included. Unfortunately PO output is still not suppressed automatically when a PO response is accepted and copied to the PO, even if no content is changed (price, quantity, delivery date ....) .

    That is the reason why we were looking for the possibility to use start conditions in customizing. The main problem there it that we do not know how to recognize that a PO change is triggered by the PO response, and how to configure that in a condition. SAP docu does not give any clue.

    So, any other suggestion is welcome

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      That is the reason why we were looking for the possibility to use start conditions in customizing....

      I wouldn't start looking for workarounds at this point. Instead I would create an OSS message for SAP because this should work (PCO should not cause new PO output/version) as standard.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.