PO Change in Extended Classic Scenario

[Former Member]

Hi SRM Experts,

Our client is using ECC 5 and SRM 3 (BBPCRM 4.0) and using classing scenario successfully.

Now we have started using extended classic scenario for limited suppliers.

Now the client requirement is to change the PO after approval.As you know that in ECC the PO can be displayed only.

And the PO already directly submitted to the supplier.

Is it possible to change the PO after submitting to supplier ?

They are looking for some changes in text/shipping address etc.

Appreciate all your suggestions.

Thanks and Regards,

Pradeep

[Former Member]

Thanks Masa..

[masa_139]

Hi,

You can activate Change Version PO.

SRM -> SRM Server -> Cross-Application Basic Settings -> Switch On Version Control for Purchasing Document.

You can also customize BBPD_COMP_FIELDS table entries. For example, when you just change internal information like internal note, system does not need to send change version PO to supplier.

Regards,

Masa

[Former Member]

Thanks Masa for your quick reply.

Could you please tell me that,we are using work flow for SC approval and when the Shopping Cart created the WF also starts and finally the SC get final approval the PO will push to supplier directly and the same will be replicated in ECC (display only).

So after activating the version control will it still allow the user to change the SC/PO after completing the approval ?

If so do we need to make any changes in our WF ?

Thanks and Regards,

Pradeep

[masa_139]

Hi,

It is same process for Change version PO.

You can customize workflow start condition in SWB_COND transaction. For PO, you see event SAVED and CHANGEVERSIONSAVED.

What are business reasons you have switched from Classic to Extended Classic ?

I would keep Classic mode.

Regards,

Masa

[Former Member]

Hi Masa,

One of the rhe reason behind the changes to Xtened classic is the supplier.The supplier accept orders only online.

Other reason is the supplier required the order in XML format.

Thanks,

Pradeep