impact on existing Shopping cart and PO - changes in backend system

[Former Member]

Hi All,

Our business Scenario self service proc (SRM4.0 with CCM 2.0 and backend system is ECC5)

& implementation scenario is extended classic. Now the backend system will be replaced by ECC6 with company code consolidation.

What will be effect on existing shopping carts and purchase orders which are open?

Some shopping carts are in approval process or in held condition.Now due to change in the company code ,these carts will be in error .

Similarly what will be impact on Purchase orders which are open.

Can the company code in purchase orders be changed and the same PO can be posted to new backend system ECC6 ?

Do any one know how to overcome this or did any one had the same situation?

Thanks & Regards,

Avinash

[Former Member]

Hi Kalyan,

Thanks for your reply.The implementation scenario is extended classic.

Regards,

Avinash

[Former Member]

Hi,

If the shopping carts are in awaiting approval/held status , then we can very change the company code.

Regarding the open purchase orders , I am not sure which scenario is being implemented - classic or extended classic ? In case of classic scenario , once the follow-on docs are created , the shopping cart cannot be changed which in turn means no changes can be made to the shopping cart. Now the follow-on document might have been created in the ECC5 backend system. Even if you upgrade the backend to ECC6 , the data would generally be available unless and until there are changes in the structures being used. If at all there are any changes in the structures we need to have some specific programs to take care of the change.

Hope this information helps.

Regards,

Kalyan