Integration of SAP IS-U Two Contract Model with CRM 7.0 Contract Mgmt

[Former Member]

Hi,

We have 2-Contract model for all customers in SAP IS-U for distribution and supply services. We are also planning to implement CRM 7.0 Contract management and integrate with SAP IS-U. There is a talk in the air that CRM 7.0 Contract Management does not work with 2-Contract model in IS-U because of some POD replication issues in CRM and heard that some clients are currently facing this issue.

Our client is operating in Deregulated environment and we were planning to use Two contract model to separate the services.

Has anyone faced this issue in your projects or Is SAP working on this issue?

Please let me know if there are any workarounds where we can still use 2-contract model and integrate with CRM 7.0? Any help or inputs that can you can provide will be very helpful to us.

Thanks in advance.

Sachin

[william_eastman]

See also

[Former Member]

hello,

the company I work for is also in teh deregulated market. We have both a supply and distribution contract. We are currently working directly with teh IBU at SAp to come to a resolution for the companies that have the above mentioned model.

hopefully we wil come up with a solution that will satisfy all our needs.

Georgine

[oliviawalsh]

DearSachin,

As per Design it's only possible to have one contract at the same time per PoD.

If you in a deregulation market it's recommended you to use the IDE integration in CRM.

Unfortunatly your desired business scenario can be achieved on project base only. There are several ideas how to provide the data and the information. One would be to download only the most used contract category into the CRM system (eiher grid usage or supply) and have the other contract only in IS-U (no replication). With a customer enhancement it would be possible do retrieve the whole supply sceanario within the IC webclient.

Another idea would be to attach a new customer based field to the contract which indicates if the contract is a grid usage or supply contract and have the check for double contracts respect that data - this solution is quite tricky and should be considered only by very experienced consultants.

Or use 1 installation with 1 contract for simple supply scenario. The schema contains a rate for both, distribution and default supply. The default supply can be switched with an installation fact. In CRM, there is 1 contract with 1 product. If a customer switches to a 3rd party supplier, an inbound message from the supplier creates a second installation with a supply contract and switches off the default supply rate. This installation/contract is not visible in CRM, it is not replicated to CRM.

As you can see, there are some ideas how to solve your needs on project base, but unfortunatly SAP generally will not change the main architecture which allows several contracts per PoD.

I hope this information is helpful for you.

Regards

Olivia

[Former Member]

Thanks Olivia, this is helpful. Can you please explain the implications for move-in/move-out if we decide to go down the path of option 1 or option 2?