cancel
Showing results for 
Search instead for 
Did you mean: 

CRM 2007 - Replication Objects & developments

Former Member
0 Kudos

Dear all

We are on CRM 5.0 and in the process of migrating to CRM2007. Our business process is such that we have many replication objects (BPs from CRM to ECC6, Sales transactions from CRM to ECC, Material, pricing from ECC to CRM) that flow back and forth via middleware.

Now the question is during or after the upgrade, do we need to do something different to make sure this works seamlessly as it does for us now? Or do we need to do initial and delta loads again?

Also regarding JAVA and ABAB development items, I am assuming we can just update these components to CRM2007 via technical master guide.

In IC Win client, we have done a lot of enhancements including inbox searches, new EEWB fields. Would we need to develop these all over?

Please send your replies and thoughts.

Regards

Jai

Accepted Solutions (0)

Answers (1)

Answers (1)

stephenjohannes
Active Contributor
0 Kudos

Jai,

If your middleware is "vanilla" then you should not have to do anything except for the upgrade guide post-processing steps. Just make sure to "turn off" the middleware before the upgrade(clear out all open queues on ERP, deregister queues on ERP, clear out all queues in CRM, clean up middleware history) According to the upgrade guide you may need to regnerate your adapter objects.

Yes just follow the master/upgrade guides to upgrade those components as normal.

All your Winclient screen enhancements need to be migrated to the CRM webclient screens. However you won't need to recreate any of the fields on the underlying database. All the UI level enhancements will need to be reimplemented manually.

Take care,

Stephen

Former Member
0 Kudos

Hi Stephen

Thanks for your quick reply. This is very helpful.

Our middlware is not vanilla so assuming we will to do lot of fixing on this. Also when you refer upgrade guide are you referring to the master upgrade guide (technical upgrade- Upgrade Master Guide) or the migration guide (which has functional components - Migration to SAP CRM 2007 Version 1.0)? Or are you referring to some other guide? Please send the link if possible.

I have access to RKT docs, so once i know the document names, I will be able to search.

Regards

Jai

stephenjohannes
Active Contributor
0 Kudos

Jai,

I'm referring to the technical upgrade that your basis administrator uses to upgrade the system. There is a section in the guide that covers pre-upgrade and post-upgrade processing steps for the middleware. However this does not cover any of the reconcilation work that needs to be done. From CRM 50 to CRM 2007, I don't think there is a lot of major changes with the non-mobile middleware. Most of the pre and post processing steps involve the mobile middleware.

Since technically speaking CRM 2007 focused more on UI changes and less on backend changes, I would bet that your middleware impact should be minimal for non-mobile extensions. We don't use mobile here, so I can't tell you if the mobile middleware will cause you headaches.

Take care,

Stephen

Former Member
0 Kudos

Thanks very much again Stephen. I have one more question on your reply (last para below)

'All your Winclient screen enhancements need to be migrated to the CRM webclient screens. However you won't need to recreate any of the fields on the underlying database. All the UI level enhancements will need to be reimplemented manually.'

Are you meaning to say that all our Winclient screen enhancements (apart from new fields)will have to be manually reimplimented? Looks like we have lots of enhancments on Inbox and related searches so assuming this will have to be redone in CRM 2007 webclient.

Thanks

Jai

stephenjohannes
Active Contributor
0 Kudos

Jai,

Exactly you will need to migrate your screen enhancements from the SAP GUI to the new CRM webclient. However you won't need to create again the fields in the tables such like a business transaction extension on CRMD_CUSTOMER_H or if you added fields to BUT000.

It is very easy however to bring all the custom fields into the new user interface without much effort. Now custom logic that you may have implemented, will require more work due to the fact the UI application layer has changed.

Thank you,

Stephen