Impact on Vendors in SRM when backend system replaced

[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. Can anyone explain what will be the impact to the SRM vendors ?

As vendors with same vendor code will be available in ECC6 can we use transaction BBP_update_mapping in SRM to map the same vendor.

Or we need to replicate from ECC6 itself. Will there any issue as vendor codes are same in both ECC5 and ECC6.0 .

Any thoughts on this please.

Best regards,

Avinash

[Former Member]

Hi Laurent,

Thanks. I will check this and will update.

Can you tell me the process to be followed for transaction BDLS as I understand this is done by Basis.

Regards,

Avinash

[Former Member]

Hi Muthu,

Thanks for your reply. Will raise OSS also and update.

Meanwhile any SRM experts who worked on such scenario, can guide us.

Regards,

Avinash

[former_member183819]

Hi Avinash,

In Define Backend Systems ,System type is ERP_2.0 for ECC 6.0 .

due to this settings lot of impacts on your system.

for one eg. depends upon this settings the standard driver classes are called when creating a new object.

so it makes lot of system performance also.

drivers available in srm system for different backend systems. so your question is very valid .not only vendor master.. everywhere you need to analyse the impact.

However raise a customer message to sap what are the impacts and update us also .

regards

Muthu

[Former Member]

Hi Sanjeev/Laurent,

Thanks for your immediate reply.

However still one point remain that we need to replicate product categories from New backend system(ECC6.0) as current product categories will be having GUID reference of with old backend system.

Can it be adjusted by running transaction BDLS.

For info, ECC6 is installed on new server for company code consolidation and current master data uploaded from ECC5 to ECC6.

Please suggest.

Regards,

Avinash

[laurent_burtaire]

Hello Avinash,

As written previously, all your "old" Product Categories (which means coming from your ECC5), if exist in your ECC6, will be correctly mapped with this new ECC6 backend by running BDLS.

GUID created for them will remain the same, but reference will be changed from ECC5 logical system to ECC6 logical system: you don't have to make a new replication for already existing Product Categories in SRM if they also exist in your ECC6.

You can also do some processes flow on a test environment to check if all is OK.

Regards.

Laurent.

[Former Member]

Hi Laurent,

As there will be Company code cosolidation in ECC6.Only one company code will be maintained.

Also we need to replicate same product categories from new backend system ECC6.0 which has different logical system name.

So please let me know whether running BDLS transaction will be the correct option.

Anybody has came across such scenario. Please suggest.

Regards,

Avinash

[former_member206968]

Hi

If your master data is going to remain same, then you don't need to replicate them again. Running BDLS should be able to set the correct mapping for your master data. However you may still need to do some basic settings manually like PPOMA_BBP attributes which are backend dependent.

Regards,

Sanjeev

[laurent_burtaire]

Hello Avinash,

I think running transaction BBP_UPDATE_MAPPING could be a solution.

Nevertheless, as your backend logical system will change (ECC5 to ECC6), BASIS team will have to run BDLS transaction in order to change backend logical system reference in Purchasing Documents created in SRM.

So, backend reference for your vendors should be correct in VENMAP table.

Regards.

Laurent.