SAP for Utilities Discussions
Connect with fellow SAP users to share best practices, troubleshoot challenges, and collaborate on building a sustainable energy future. Join the discussion.
cancel
Showing results for 
Search instead for 
Did you mean: 

Replicating ISU Installation Facts into CRM Service Contract

Former Member
0 Kudos

Hi All,

Is the Replicating ISU Installation Facts into CRM Service Contract is standard way of working or we need to use some other approach?

Cheers,

Suraj

14 REPLIES 14

friedrich_keller
Contributor
0 Kudos

Suraj,

Installation facts are only known in IS-U. Installations facts and further rate info finally translate to a product in CRM.

Kind regards,

Fritz

0 Kudos

Thanks Fritz.

So can I assume that this is not the standard replication and we need to develop some LSMW or program to load the installation facts in CRM service contract if there is any specific requirement in CRM system.

Cheers,

Suraj

0 Kudos

Hi Suraj,

You should be able to store installation facts as CRM Service Contract attributes. We are actually replicating CRM attributes to ISU as installation fact. You will have to explore options if you can actually replicate them back up.

Regards,

Raj.

0 Kudos

Suraj,

In the standard (this was your question) facts are not replicated to CRM. However, you may choose to replicate them to a CRM contract with an own implementation resp. replicate them to IS-U and change/create the facts on an installation either with the master data generator or again an own implementation.

Kind regards,

Fritz

0 Kudos

Hi,

Thanks for your quick answers.

I think we have to explore this back replication of installation Facts from ISU to CRM using some implementation.

Is there any documentation available to understand how we can do this?

Cheers,

Suraj

0 Kudos

Suraj,

You may choose to implement the BAdis ECRM_UPLOAD/ECRM_DOWNLOAD on the CRM system and the BAdi ECRM_CRM_UPLOAD/ECRM_CRM_DOWNLOAD on the IS-U system.

Kind regards,

Fritz

0 Kudos

Thanks Fritz.

Let me test these 2 BAdis.

I will update this thread once tested.

Cheers,

Suraj

0 Kudos

Have you tried PME concept in CRM. This is pretty standard but uni-directional.

Ramana

0 Kudos

Thanks Ramana.

I think it will work from CRM to ISU, but what I am looking for is from ISU custom installation facts to CRM..

Cheers,

Suraj

0 Kudos

Hi Fritz,

We have implemented the BAdI's in ISU as well as CRM.

After doing a coding, in both the BAdI's, we are able to transfer the facts data from ISU to the CRM BDoc for SI_CONTRACT.

But here we are not able to update this value in CRM table.

Any idea about this.

Can we get some sample coding for this?

Cheers,

Suraj

0 Kudos

Its working fine now.

We have just fine tuned our ABAP code.

cheers,

suraj

0 Kudos

Suraj,

You mind revealing you coding as a generic coding of the two BAdis?

Cheers,

Fritz

Former Member
0 Kudos

Hello,

I would like to use these BADIs to replicate installation facts from IS-U to CRM contract configuration.

But I would like to use the Delta Load. However, if I change datas on my IS-U installation, there is no BDocs executed.

I guess it is working fine if we want to download contracts by request or initial load... But I don't make any changes on table EVERH, so there is no BDoc generated.

Any idea ?

Nick

0 Kudos

Nick:

Installation Facts change in ISU does not correspond to any replication object in CRM. It is a task performed in a standalone environment. If you are talking about an integrated CR&B environment, there are several factors that one should consider while changing installation facts. For example, your client has to decide on which system to be the system of record for Contracts. If you consider CRM as the s-o-r for Contracts, may be you should advise them to initiate the corresponding CRM process to change installation facts from within CRM. We consider the configurable attribute on a product in CR&B as corresponding parameter of installation fact. Hence, you have to recommend a Contract Change which in turn will let you change the configurable attributes on a proudct for a given Contract. When this changed contract triggers the middleware and MDT, you can handle the installation facts. It is also worth advising your client the new features released by SAP in EhP1 of CRM around building rules on product configuration using BRR+ (in case you are using CRM 7.0 EhP1).

Ramana