Enhancing Standard Components in Web Dynpro ABAP

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

2010 SAP AG 1

Middleware Replication: ISU

Installation Facts into CRM

Service Contract

Applies to:

SAP CRM and SAP IS-U. For more information, visit the Customer Relationship Management homepage.

Summary

This document is created to share the SAP CRM-ISU project experience. As per the standard SAP ISU-CRM

data model the installation facts are only maintained in the SAP ISU system and this data not gets replicated to SAP CRM system. This document explains the development which is required to take care of this simple requirement of replicating ISU Installation Facts data into the CRM Service Contract Custom field and can be

used as a reference for developing any future similar requirements.

I would like to thank Mr. Rajesh Elumalai for his contribution in the ABAP area.

Author: Suraj Jadhav SAP CRM-ISU Consultant

Company: Capgemini India Pvt. Ltd.

Created on: 14th December 2010

Author Bio

Suraj Jadhav is SAP Sales and Distribution Certified, CRM Leasing Trained Functional Consultant with Over 7 years of total experience and over 5 years of consulting experience in SAP CRM, ISU and Sales and

Distribution with leading IT consulting organizations.

Currently working as a Senior SAP CRM-ISU Consultant, in Capgemini India Pvt Ltd and providing innovative solutions to global clients.

Middleware Replication: ISU Installation Facts into CRM Service Contract


2010 SAP AG 2

Table of Contents

Introduction............................................................................................................................................. 3

Prerequisites ....................................................................................................................................... 3

ISU-CRM Replication Objects .................................................................................................................. 3

Middleware BAdI Development ................................................................................................................ 4

ECRM_CRM_DOWNLOAD .................................................................................................................. 4

ECRM_DOWNLOAD............................................................................................................................ 4

Test Results............................................................................................................................................ 5

ISU Installation Facts ........................................................................................................................... 5

ISU Contract ........................................................................................................................................ 5

CRM Service Contract in Web UI .......................................................................................................... 6

Sample Code .......................................................................................................................................... 6

Related Content ...................................................................................................................................... 7

Disclaimer and Liability Notice.................................................................................................................. 8



2010 SAP AG 3

Introduction

This document is prepared for sharing a development experience of one of the CRM-ISU implementation project. If there is any requirement of replicating any ISU installation facts data into the CRM Service

Contract Custom Fields, then this document will help SAP Consultants to speed up the development using the sample code. This document will also be very useful in future for something similar kind of replication requirements.

Prerequisites

SAP ISU and CRM business process knowledge.

Knowledge about SAP CRM middleware replication objects.

Middleware settings between the CRM and ISU systems

CRM Middleware BDoc (Business document) knowledge

SAP ABAP programming knowledge.

ISU-CRM Replication Objects

The data replication between the ISU and CRM system happens through the middleware and there are some objects for which data can be replicated into the CRM from ISU system.

Following diagram explains the details about the object relationship between the ISU and CRM systems in

terms of middleware replication:

Business Agreement

Service Contract

Connection Object

PoD & Premise

BP Relationship

Contract Account

Utility Contract

Connection Object

Business Activities

Business Partner Business Partner

ISU CRM

Installation

Premise

PoD CRM Installed Base

CRM Installed Base

BP Relationship

Business Contact

Business Contact Notes

M

I

D

D

L

E

W

A

r

E

R

E

P

L

I

C

A

T

I

O

N



2010 SAP AG 4

The CRM Replication can be done by two methods as below:

Initial Download

Delta Download and

Request Download

So as per the standard middleware settings, there is no object in CRM to which ISU installation facts data can be replicated.

For this SAP has provided us two BAdIs (Business Add-In) which we can use to replicate such type of data.

Middleware BAdI Development

As per the SAP CRM Middleware setup, the ISU installation facts data replication into CRM is not a standard practice. But if there are any business requirements to replicate some ISU data into CRM through

middleware then, this can be met using the middleware BAdIs.

SAP has provided following two different middleware related BAdIs, one in CRM system and other in ISU system

ECRM_CRM_DOWNLOAD (In ISU system)

ECRM_DOWNLOAD (In CRM system)

ECRM_CRM_DOWNLOAD

SAP has provided this BAdI in ISU system for downloading any ISU Contract related data into CRM BDoc

container, which is not supported in standard middleware objects.

So in our scenarios what we want is to send some custom facts data from ISU table into the CRM BDoc container.

For this we have to develop the method ecrm crm_download_fill_data_new, to fetch the ISU facts data from the table and then send it into the Bdoc container.

This BAdI then takes the ISU facts data from table ETTIFN and then sends this data to BDoc container.

Once this BAdI is developed and data is send to CRM container then the next BAdI will take care of the next steps.

ECRM_DOWNLOAD

SAP has provided this BAdI in CRM system for downloading any ISU data from CRM BDoc container into the CRM Service contract table structure, which is not supported in standard middleware objects.

For this we have to develop the method ecrm_download_fill_data, to fetch the data from the Bdoc container

and then send it to the relevant table-field.

This BAdI then downloads the ISU facts data which is sent by ISU BAdI and then replicated this to CRM table ORDERADM_i and field ZZ_METERTYPE

So as per our scenarios the installation facts data will then transferred into the custom field at the CRM service contract item level.

Note:

The sample code for the above two BAdIs are attached in the section Sample Code.



2010 SAP AG 5

Test Results

Below are the screen shots of the test results for successfully replicating the installation facts data into CRM

Service Contract custom field at the item level:

ISU Installation Facts

ISU Contract



2010 SAP AG 6

CRM Service Contract in Web UI

Sample Code

Below are the sample development codes related to the BAdIs mentioned above:

Note: This approach can also be valid if you migrate this type of data using the EMIGALL tool in SAP IS-U system. Using this approach we can easily replicate the ISU field data into CRM field through middleware.



2010 SAP AG 7

Related Content

SDN Middleware Forum

IS-Utilities SDN Forum

Customer Relationship Management homepage



2010 SAP AG 8

Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP off icial interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.

SAP w ill not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk.

SAP offers no guarantees and assumes no responsibility or liability of any type w ith respect to the content of this technical article or code sample, including any liability resulting from incompatibility betw een the content within this document and the materials and

services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable w ith respect to the content of this document.

Enhancing Standard Components in Web Dynpro ABAP

Documents

Transcript of Enhancing Standard Components in Web Dynpro ABAP