Impact on shopping cart due to change in backend system

[Former Member]

Hi All,

Our client is changing the backend ECC5 system to ECC6 on new server (new logical sys) with FI restructring in ECC6.

We have SRM4.0 system ( with CCM on same client) with Extended classic scenario.

What will be impact on Shopping carts which are awaiting for approval or in Held status( used by client as template) .There is only product category and vendor and no material number in Shopping cart from catalog.

As the product categories and vendors are same in ECC6 also , during cutover can the shopping cart with held/open status be posted after changing backend system, Or we need to upload it.

Any thoughts on this please.

Best regards,

Avinash

[Former Member]

Hi Laurent/ Ganesh,

Thanks for your reply.

Yes, you are correct it is update of Open PO in SRM with new company code.

Can you give some information how the report can be build for this change and subsequent PO posting in backend ECC6.

can we consider Bapi for PO updation. Also the requirement is PO number should not be changed.

Regards,

Avinash

[Former Member]

Hi,

You are changing the Backend system only.

1 ) Shopping cart that are in held status will be in SRM server only it will not be transferred.

2) For the new backend system ECC6.0 please check the logical system configuration in ECC 6.0 since

based on this logical system config only for the approved shopping cart . P.o are created in the backend SAP R/3.

Please check the logical system configuation both in SRM SPRO & SAP R/3 SPRO setting.

3) Please check the Number range configuration in SAP R/3 -ECC 6.0 which is critical

Regards

G.Ganesh Kumar

[Former Member]

Hi Laurent,

Thanks for your reply.Does that mean we should not be able to upload Open SC or Open PO in SRM.

And only option is to close the open document.

Regards,

Avinash

[laurent_burtaire]

Hello Avinash,

What do you mean by 'upload' ?

Your SC or PO already exist in SRM...

Do you mean "update" ? If i am correct, you will have to create specific report in order to update Purchasing Documents in SRM and R/3 with new R/3 Company Code.

Regards.

Laurent.

[Former Member]

Hi All,

Has anybody came across such scenario,please suggest.

Regards,

Avinash

[Former Member]

Hi Laurent,

In ECC6 ,consolidation of many company codes to single company code will happen, whereas in SRM as there is only one backend purchasing org we need to map this with new backend purchasing org of ECC6.0(which is unique for SRM)

As per my understanding, as backend system change we need to replicate same product categories from ECC6 to SRM4.0 as SRM creates GUIDs for backend product categories and passes a sych GUID in ECC also.

Will the existing shopping carts in Held/open condition get processed which had been already created with old Product categories and vendor details (which are replicated from ECC5) when backend system changed to ECC6

Is this applicable for open purchase orders also as company code consolidates in ECC6. Do we need to close open PO or upload open with change data?

Please suggest.

Regards,

Avinash

[laurent_burtaire]

Hello Avinash,

Regarding your Company Codes consolidation in your ECC6, you will have some functional issues in SRM for Purchasing Documents created on Company Codes that do not exist any more in SRM, especially if those documents have not ended process flow (SC ->PO->CF).

Regards.

Laurent.

[laurent_burtaire]

Hello Avinash,

As for Vendors (see thread [Impact on Vendors in SRM when backend system replaced|;), by running BDLS transaction, it should be OK.

Regards.

Laurent.

Edited by: Laurent Burtaire on Feb 14, 2009 6:32 PM