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

problem with change version of the PO...Reply soon

Dear All,

I am facing the problem regarding the change version of the PO.

Purchase Order created and approved. Price amended and approved. User now needs to amend quantity, but when clicks on 'change' gets message <u><i><b>'Action not possible because change version exists'</b></i></u>.

i have checked the Workflow which is working fine.What might be the cause of this

Awaiting for your reply.

Add a comment
10|10000 characters needed characters exceeded

Related questions

5 Answers

  • Posted on Aug 01, 2007 at 04:26 AM

    > Dear All,

    >

    > I am facing the problem regarding the change version

    > of the PO.

    >

    > Purchase Order created and approved. Price amended

    > and approved. User now needs to amend quantity, but

    > when clicks on 'change' gets message

    > <u><i><b>'Action not possible because change version

    > exists'</b></i></u>.

    >

    > i have checked the Workflow which is working

    > fine.What might be the cause of this

    >

    > Awaiting for your reply.

    Hi,

    1. Please check that the changed PO is indeed in approved status (the status I1015 must in inactive in BBP_PD)

    2. If not, please check using the standard PO workflow if you are using a customized one.

    3. Please check that the PO output has been sent correctly.

    Regards.

    Yeu Sheng

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Dear Yen.

      Hope you are doing fine.

      The points 1 and 3 is working fine. We have used the z workflow copied from standard zero step approval workflow WS 14000075. This is working fine for rest of the PO's so not able to understand what will be the exact cause of the error.

      Please revert back if i need to check anything specific in workflow,

      also looking to hear the other approch for the above problem if there.

      thanks in advance.

  • author's profile photo Former Member
    Former Member
    Posted on Aug 07, 2007 at 01:09 AM

    Hi Rupesh,

    'Action not possible because change version exists'.

    Change version exists means whatever the changes in the PO are not replicated to SAP R/3 system. If the changes you made are there in SRM but not replicated to backend R/3 system than you need to first delete the change version.

    Once the change version is deleted changes can be done to the PO.

    Regards

    Hiten

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 07, 2007 at 11:09 AM

    Hi,

    Check with BBP_PD....is status approved and work item is in completed status in workflow item?

    If this is the case then it will work otherwise workflow itself is not in approval status so that till the completion of item you can change any thing......Check the save changes version WF ...wether the conditions are proper or not.....and one cause may be due to transfer process of document.....

    Navneet.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi

      <u>Seems like a SAP bug in the system...</u> Please raise a customer OSS message with SAP as well for faster processing of this issue.

      "I was a little bit surprised as well.

      But this is what a saw in the code of SRM 4.0 & 5.0.

      This control is linked to message BBP_PD 200 Purchase orders that have been ordered cannot be deleted.

      In term of process, you will have to "delete" all PO items and send this OrderChange to the supplier.

      There is also another control: to enable the "delete" button, the system simulate the cancellation action. So if the customizing of a system or user status prohibit the deletion action, then the simulation fails and the button is disabled."

      Related link->

      podelpossible-does-not-permit-to-delete-a-po---

      <b>Do update me as well.</b>

      Regards

      - Atul

  • author's profile photo Former Member
    Former Member
    Posted on Aug 20, 2007 at 08:44 AM

    Check for a flag in table BBP_PDHGP , Entry: CHANGE_LOCK = X

    The flag should be only removed, if no change version exists. IMPORTANT!!!

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 22, 2007 at 03:40 AM

    Hi,

    Whenever you change an ordered PO,SRM creates a change version of the PO till it gets approved.During approval stage you cannot change the active document of PO, as the change version is not approved.In your case it seems your change version is still in awaiting approval stage and you are trying to change the active document.

    Therefore first get the change version approved and then change the PO.

    Regards,

    Sanjeev

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi JR,

      This issue comes when the change version is locked. No further changes are allowed until and unless this lock is removed.

      Please check in BBP_PDHGP for the concerned P.O whether the Change_Version field is flagged "X" or not.

      In that case just ask your ABAP guy to write a simple program (which is executable in SE38) to remove the lock indicator (LS_LOCK) for the GUID of P.O. lock version (LV_GUID).

      This has resolved the issue in our case and further changes can be made to P.O.

      Regards,

      Teja

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.