Action not possible because change version exist

[Former Member]

Dear All,

We are at SRM5.0- Extended Classic scenario and facing issues for changing some of the PO documents.

When the buyers are trying to change the PO, error is getting populated as 'Action not possible because change version exist'. This error is not allowing us to change the PO.

These POs are changed in the past and all the relevant changes are reflected to backend system with no issues. In other words Change Versions do exists for these POs. Flags for Change Version completion is also set and all historical versions can be seen but without change history.

Additional information -

1. No approval workflows are implemented for PO.

2. No locks are active for these documents.

Appreciate your help!

Regards,

Sagar

[former_member94584]

This method works -

Please check the change version GUID in BBP_PD whether workitem should be available. If it is available then you can achieve

through SWO1 with methiod SETRELEASED. If work item is not available for change version then pleaes have a look on my 1st para.

Always change versions PO will have the status with Awaiting approval.

I hope the above information is clear and helpful to you.

[Former Member]

Hello All,

I am also finding same problem (Action not possible because change version exist) while canelling GR document.

I have seen this table "BBP_PDHGP" but could not able to locate which is the relavent GUID, so that I can delete or update the vesrion.

can anybody help me which the FM to be used to get away from this error.

Thanks in advance.

Regards

Sharan

[Former Member]

HI,

If you come across with change version issue, please put a X mark against the field DOC_CLOSED in the table BBP_PDHGP with change version of PO guid. Then change version is closed and PO status will be changed to Ordered. Please note that whatever changes you have done by changing PO or at a time of change version will be available. Again you have to do by changing the PO in the active version.

Or

Please check the change version GUID in BBP_PD whether workitem should be available. If it is available then you can achieve

through SWO1 with methiod SETRELEASED. If work item is not available for change version then pleaes have a look on my 1st para.

Always change versions PO will have the status with Awaiting approval.

I hope the above information is clear and helpful to you.

Thanks

Rajesh K

[Former Member]

HI,

If you come across with change version issue, please put a X mark against the field DOC_CLOSED in the table BBP_PDHGP with change version of PO guid. Then change version is closed and PO status will be changed to Ordered. Please note that whatever changes you have done by changing PO or at a time of change version will be available. Again you have to do by changing the PO in the active version.

Or

Please check the change version GUID in BBP_PD whether workitem should be available. If it is available then you can achieve

through SWO1 with methiod SETRELEASED. If work item is not available for change version then pleaes have a look on my 1st para.

Always change versions PO will have the status with Awaiting approval.

I hope the above information is clear and helpful to you.

Thanks

Rajesh K

[Former Member]

Hi Rakesh.

Thanks for your reply.

Let me explain you my issue again --> my client has done confirmation in SRM (GR 101) and posted invoice. Again he has cancelled confirmation (102 movement). Now again he wants to confirm (101 movement).

PO has 3 line items and for 2 line items he has done above said activities. with no issues. He is getting above error while he is confirming.

Now as per your advice I found Change version is updated in table "BBP_PDHGP" and field "CHANGE_LOCK".

Now to over come this error what I should do. Should I execute any FM to over come this issue? I have checked by executing FM "BBP_PDHGP_DB_DIRECT_UPDATE" but no luck. Since I have to do it in production client I am bit worried. hence your guidance is very much required.

Please help me.

Thanks in advance.

Regards

Sharan

[Former Member]

Dear All,

We have resolved this issue.

Issue was related with PO's Active Version was locked due to some reason. Lock entries found in table BBP_PDHGP, CHANGE_LOCK = X which are now removed by using standard function module - BBP_PDHGP_DB_DIRECT_UPDATE.

Posting above information in case any one experience such issue in future.

Regards,

Sagar

[matteo_montalto]

Hello Sagar,

since I'm experimenting same problems, can you please add some more details about your solution?

Hence I'm not interested in preserving the active, change version, my purpose was to overwrite it in an update procedure. But I was not able to do it for the same error you told in this thread. Now, I'm gonna investigating in two different directions:

1 - update directly the active change version (and here probably your solution could help), or...

2 - delete the change version, activate the previous one and then go on update creating a new version.

These two approaches are equivalent imho: I will get a new, active version in park state.

[Former Member]

Hello,

Just thinking from business perspective...

Is there any reason you are not interested for preserving active change version? I suggest you may want to keep all related/created versions as it is, as there might be a audit requirement about who made any changes to PO? Also this will be helpful for Procurement dept in case there is a conflict with vendor.

In case you are ok with the approach I have suggested then go ahead with it. This is approch is easy than the one you have mentioned in second point. You may also will not able to delete the active change version as the Lock is already exists.

Thanks & Regards,

Sagar

[matteo_montalto]

Hi Sagar and thanks for your response,

well, actually the active change version won't be preserved in any case. It would be overwritten in the first scenario, and deleted in the second one. The reason why I'd like to have this "brute force" method is to face an eventual human error. Suppose that a disalignment between R3 and SRM has been created; my report basically "alligns" the SRM version to the corresponding R3 one. And suppose also that the user made a mistake so that the program must be used a second time. I'd like to provide a way to "UNDO" the first execution of the program, that is to say: i'd like to provide a way to OVERWRITE the actual active, change version, or alternatively delete the change version that the report did create the first time it has been launched.

Hope it's a bit clearer now

Thanks for any hint/suggestion you can give me

EDIT: Oh, and please... can you provide me further information about your solution? I mean, use of that FM to unlock an active version of the PO and then the proper call to BBP_PD_PO_UPDATE specifying how you managed input params. Thanks a lot

Edited by: Matteo Montalto on Apr 9, 2009 11:43 AM

[Former Member]

The active version is locked because there is a change version. So to update it while there is a change version is not advisable. The way you could do it is to delete the change version with BBP_PD_PO_DELETE (that's what I think it is anyway - can't check) and give the change version guid. The active version will be unlocked then.

Regards,

Robin

[matteo_montalto]

Hi Robin, and thanks for your help....

Tried the solution you posted but without success; in the system I'm working on there no FM called BBP_PD_PO_DELETE. There's instead a BBP_PD_PO_DB_DELETE, tried it giving in input the change version's GUID but without any result.... probably that FM is not intended to do what I was hoping 😛

Please follow the discussion in my thread: . This one is closed and I can't give any point, and yep, I did a reply just to ask for info on a problem similar to mine

Thanks again,

Matteo