is-u/crm integration: replication of technical objects - sap

IS-U/CRM Integration:Replication of Technical

Objects

SAP CRM 7 .0

AD

DO

N.N

DC

RM

_U

TIL

SAP Online Help 11.12.2008

IS-U/CRM Integration: Replication of Technical Objects 2008 2

Copyright

© Copyright 2008 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may bechanged without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietarysoftware components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of MicrosoftCorporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM,z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM,Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower,PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner,WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBMCorporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registeredtrademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin aretrademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, WorldWide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license fortechnology invented and implemented by Netscape.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessByDesign, and other SAP products and services mentioned herein as well as their respectivelogos are trademarks or registered trademarks of SAP AG in Germany and in several othercountries all over the world. All other product and service names mentioned are thetrademarks of their respective companies. Data contained in this document servesinformational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAPAG and its affiliated companies ("SAP Group") for informational purposes only, withoutrepresentation or warranty of any kind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The only warranties for SAP Group products andservices are those that are set forth in the express warranty statements accompanying suchproducts and services, if any. Nothing herein should be construed as constituting anadditional warranty.



Icons in Body Text

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types ofinformation at a glance. For more information, see Help on Help General InformationClasses and Information Classes for Business Information Warehouse on the first page of anyversion of SAP Library.

Typographic Conventions

Type Style Description

Example text Words or characters quoted from the screen. These include fieldnames, screen titles, pushbuttons labels, menu names, menu paths,and menu options.

Cross-references to other documentation.Example text Emphasized words or phrases in body text, graphic titles, and table

titles.

EXAMPLE TEXT Technical names of system objects. These include report names,program names, transaction codes, table names, and key concepts of aprogramming language when they are surrounded by body text, forexample, SELECT and INCLUDE.

Example text Output on the screen. This includes file and directory names and theirpaths, messages, names of variables and parameters, source text, andnames of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in thesystem exactly as they appear in the documentation.

<Example text> Variable user entry. Angle brackets indicate that you replace thesewords and characters with appropriate entries to make entries in thesystem.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.



IS-U/CRM Integration: Replication of Technical Objects.........................................................5

Integration – Data Model....................................................................................................6

Mapping IS-U Data in CRM................................................................................................7

Unicode ........................................................................................................................... 10

System Settings in SAP IS-U ........................................................................................... 11

Mass Changes and Migrations in SAP IS-U.................................................................. 12

System Settings in CRM .................................................................................................. 14

Administration Console................................................................................................. 15

Sites............................................................................................................................. 16

Subscriptions................................................................................................................ 17

Settings for Product...................................................................................................... 18

Download ........................................................................................................................ 19

Delta Download of Technical Objects............................................................................... 23

Upload of Technical IS-U Objects .................................................................................... 24

BDocs.............................................................................................................................. 27

Cust. Fields f. Tech. IS-U Obj. in SAP CRM 4.0 and SAP IS-U 4.71 ................................. 28

Excursus: Changing settypes and attributes..................................................................... 31

Automatic Enhancement of CI_POD ................................................................................ 34

Replication of Customer Enhancements........................................................................... 36

Utilities Industry Enhancements with CRM 2006s/2. ......................................................... 38



IS-U/CRM Integration: Replication of TechnicalObjectsThis section describes which settings you must make in both systems within the IS-U / CRMintegration in order to be able to replicate technical objects from one system to the other.

You will find information on the following themes:

Data Model Integration

Mapping IS-U Data in CRM System

Unicode

System Settings in IS-U

Mass Changes and Migrations in SAP IS-U

System Settings in CRM

Administration Console

Sites

Subscriptions

Settings for Product

Download

Delta Download of Technical Objects

Upload of Technical Objects

BDocs

Customer-Specific Fields for IS-U-Objects for SAP CRM 4.0 and SAP IS-U 4.71

Excursus: Changing Set Types and Attributes

Automatic Enhancement of CI_POD

Replication of Customer Enhancements

Utility Energy Enhancements with CRM 2006s/2



Integration – Data ModelThe following graphic explains the connection between objects in SAP IS-U and thecorresponding objects in SAP CRM. The integration solution ensures consistency betweenthe objects in both systems. In this way, for example, changes to an IS-U contract lead tochanges to the corresponding contract item in SAP CRM, and vice versa.

ConnectionobjectInstallation

Contract

Premise

Point ofDelivery

Contractaccount Bill

Billing

SAP IS-U SAP CRM

Businesspartner

Businesspartner

Businessagreement

Connectionobject(IBase)

Contractitem

PoD(IBase)



Mapping IS-U Data in CRM

Customer

Contractaccount

Installation

Contract

Premise

PoD

Connection

Connectionobject

Individualproduct

InstalledBase

1 : N Relationship1 : 1 Relationship



ConnectionObject

PoD

PoD

PoD

Walldorf, Hauptstraße 10

1st floor, divisionElectricity

1st floor, divisionelectricity

1st floor, divisionelectricity

IBase

Connection objects and points of delivery in CRM are stored as components in an IBase(Installed Base) of the category IU (technical objects for IS-U).

The following conditions apply for an IBase from the category IU.

The first component of an IBase is always a connection object.

An IBase only has one connection object.

0 .. n points of delivery can be allocated to a connection object.

Apart from the relationship between connection object point of delivery, there are noother relationships in the hierarchy. (Exception: Consumption profiles in scenario SalesManagement for Commercial & Industrial Customers)

These conditions mean that the IBase contains a maximum of two hierarchy levels. The firstlevel consists of a connection object, the second consists of 0 .. n points of delivery. IBaseswith a different structure are not valid IS-U IBases and cause errors during the upload.

IS-U IBase Maintenance

You cannot maintain IS-U IBases as default in the Easy Access menu (Create Installation andChange Installation) in CRM. The IBases are created or changed by an initial or deltadownload, or they can be changed in the relevant industry-specific interfaces.

Special features here are the connection objects and points of delivery, which can be createdin the CRM system. These objects can only be changed in CRM after they have beenreplicated successfully in IS-U. This ensures the consistency of the data.

An elementary principle of the IS-U / CRM integration is that an IBase component (point ofdelivery) in the object list is generally allocated to a CRM contract item (= contract in SAP IS-U). In this way, the link between business and technical objects is created in CRM. Technicalobjects in CRM are stored in the Installed Base (IBase) (transactions IB51-IB53). An IBaseusually consists of a connection object, to which any number of points of delivery can beallocated.

FilterYou can use the filter conditions to meet certain restrictions regarding the dataset during theinitial download and delta download. SAP predefines the fields HOUSE and REGIOGROUP,



from the IS-U table EHAUISU, for the connection object. The same fields are predefined forthe point of delivery, along with the field DIVISION from the IS-U table EANL.

Within the IS-U / CRM integration, you can also download certain data from the IS-U systeminto the CRM system (such as in the case of incorrect errors). You can, for example, onlydownload points of delivery that concern the column Division.

Use the Filter sync. (R/3) button in the IS-U table CRMFILTAB to define the filters, in orderto reconcile delta downloads with the set filter conditions.

After downloading certain data records, ensure, if necessary, that this table nolonger contains the unwanted filter that was set for the delta download.



UnicodeImplementation Considerations

Note

As of SAP CRM 5.0 (and partially as of CRM 4.0), the system supports all possiblecombination of CRM unicode/non-unicode and ERP unicode/non-unicode. If possible, werecommend that you run both systems in unicode mode. For more information, see SAP Note1022350.

End of the note.



System Settings in SAP IS-UUse the table ECRMCONTROL, which you can find in Customizing under Industry-SpecificSolutions Customer Service CRM Integration Define Basic Settings, to connect IS-Ucontracts and define the CRM reversal reason to be used during the move-in reversal.

Check table CRMSUBTAB, to determine whether the function module (MOD_NAME)IBSSI_POD_EXTRACT_VIACON is allocated to both entries for object (OBJNAME ) SI_POD.If this is not the case, see SAP note 605328.

For more information, see Maintenance of Master Data Templates [Extern].



Mass Changes and Migrations in SAP IS-U

You can use table ECRMCONTROL to control the replication of technical objects in IS-U. Thefollowing control parameters allow you do avoid problems resulting from mass processes(such as post-migration) and mass changes.

For migration after successful initial download or gradual migration, there are four differentvariants:

The parameter Y_CRM_REPL_OFF = Deactivate CRM Replication is included in themigration workbench.

In Customizing, you can again control the migration of individual technical objectsusing the following parameters:

o Download of Connection Object Currently Active

o Download of Point of Delivery Currently Active

These settings override the migration parameters (double security). You can usereport Report ECRM_ISU_CHECK_CONS_DL_OBJ (IS-U) and request loads as wellas the Data Integrity Manager (DIMa) (CRM-based data comparison) to comparemissing objects.

The system automatically transfers all objects that are not replicated in CRM during amigration or a mass change process to table ECRM_TEMP_OBJ. You can them load theminto CRM by request load with the filter settings for table ECRM_TEMP_OBJ and fieldXREPLCNTL = X.

CRMTech.Obj.

ActiveCO/PoDActive

MigrationCRM_REPL_OFF Effect

x x x No download- Entry in ECRM_TEMP_OBJ

x x Call download function

x x No download- Entry in ECRM_TEMP_OBJ

x No download- Entry in ECRM_TEMP_OBJ

x x No integration for technical objectsactive

x No integration for technical objectsactive

x No integration for technical objectsactive



System Settings in CRMCall the Change IS-U-Specific Parameters transaction (ECRM_ISU_PARAMS) and deselectthe UPL_VIA_CONTRACT checkbox (Upload of Technical IS-U Objects Using the Contract).You can also find the transaction in Customizing for Customer Relationship Managementunder Industry-Specific Solutions Utility Industries General Settings Define Client-Specific IS-U Parameters.

You can also replicate the technical objects with the contract in SAP IS-U. To do this, youmust select the relevant checkbox.

For more information about the CRM system settings, see the CRM Master Guide on SAPService Marketplace at http://service.sap.com/instguides underSAP Business Suite Applications SAP CRM SAP CRM *current release.



Administration Console

To download data from CRM to the ERP system, you must use the administration console inCRM to define sites and subscriptions. In the CRM system menu, choose Middleware

Administration Administration Console .



Sites

To upload data, you must specify a site as a replication target - in this case, an ERP system:In the administration console, use the input help for the Object Type field to select the Sitesobject type. Choose Create. Enter a name and description for the site, and use the input helpto select a type (in this case R/3). Use the Site Attribute pushbutton to allocate an RFCdestination.



Subscriptions

Once you have defined the sites, you must specify which data is to be sent to which site. Youuse subscriptions for this purpose. In the administration console, use the input help for theObject Type field to select the Subscriptions object type. Choose Create. You are taken to thesubscriptions assistant, which helps you to create a new subscription.



Settings for ProductProcedureÜberprüfen Sie die allgemeinen Produkteinstellungen im Customizing unter

Anwendungsübergreifende Komponenten SAP Produkt:

Basic Settings Define Output Format and Storage Format of Product IDs : Thelength of the ID is 40 characters (Transaction COMCPRFORMAT).

Product Without Customizing Transfer from Backend Systems Assign CategoryHierarchies to Applications

A hierarchy must exist here for the application product. The standard hierarchyR3PRODSTYP is often used here. If necessary you can also create a new hierarchyusing transaction COMM_HIERARCHY.

Settings for Product Type Number Assignment Number Ranges for ProductType Define Material

Create a number range group for your categories (see following section). Allocate thegroup to a number range.

Transaction SNUM Number range object ISU_TMPVST.

Also allocate this object to a number range.

Start report ECRM_ISU_CHANGE_CONNOBJATTR to prevent problems that oftenoccur when copying clients. The report replaces the existing error-prone set typeattribute entries for the connection object with the correct entries.

Transaction COMM_HIERARCHYCreate a main category for the individual object families 0101 and 0102 as a category of anexisting or a new hierarchy.

Assign category 0102 to set type ISU_POD and category 0101 to set type ISU_CONNOBJ.You can choose the names of the categories. You do not have to make any additional entriesin the other fields.

You can also allocate your customer set types here.

Caution

Make sure that you do not use product master set types (such as units of measure, productshort texts, basic data for material) for the categories of the technical objects.

End of the caution.



DownloadFeaturesRelevant Download Objects of CRM Integration

Regional Structure DNL_CUST_ADDR (Optional)Transaction R3AC3 – Customizing Adapter Objects

You can use this download object to load all Customizing settings of the regional structurefrom the ERP system to the CRM system. This allows you to prevent errors during theregional structure check when you change addresses or create new addresses.

Connection Objects SI_CONNOBJ (Mandatory)Transaction R3AC1 – Business Adapter Objects

The fields of the following DDIC structures are replicated in the standard:

IS-U CRM

BAPI_EHAU Master data for connection object

BAPI_EHAUADR Connection object address

BAPI_EHAUNOTE Meter reading note for connection object

BAPI_EHAUTXT Short texts for connection object

BAPI_EJEST Individual status for each object tab JEST

BAPI_EJSTO Status object information tab JSTO

Texts for the connection object are aslo replicated.

Points of Delivery SI_PODTransaction R3AC1 – Business Adapter Objects

Points of delivery cannot be replicated without the corresponding connection objects. Thefields of the following DDIC structures are replicated in the standard:

IS-U CRM

BAPI_EUI Master data for point of delivery

BAPI_EUIADR Premise address

BAPI_EUICATTXT Texts for premise types

BAPI_EUISERVICE Services for point of delivery

BAPI_EUISERVTXT Service texts

BAPI_EUITRANS Transformation of internal/external PoD number



IS-U CRM

BAPI_EUITXT Short text for point of delivery (for technical reasons, the grid data is alsotransported to this table if it is active).

During initial and request loads, points of delivery are only loaded via the higher-levelconnection object. This is because the point of delivery only has a unique GUID as a key.

Equipment EQUIPMENT (Optional)Transaction R3AC1 – Business Adapter Objects

You can use a standard adapter object to load equipment from the ERP system to the CRMsystem. To do this, you have to activate BADI implementation CRM_EQUI_LOAD_STDIMP.As od CRM 2007, there is a BOL relationship beween point of delivery and equipment(device, meter). You can use this relationship for the CRM service for simple serviceprocesses.

ActivitiesSettings for Connection Objects and Points of DeliveryBefore you start the initial download, make your settings in transaction R3AC1 with regard tothe block size of the selection (this also determines the number of data records in a Bdoc)and the filter conditions. Use the corresponding filter conditions to test the initial download, inwhich, for example, you only downloaded the first 100 connection objects in block sizes up to10 data records in the CRM system. This enables you to discover possible errors faster, andto eliminate them.

Notes on Performance With Regard To Technical ObjectsSee the following notes:

SAP Note 721844: Performance tips and tricks

SAP Note 721762: FAQ: Replication of technical objects

We recommend that you keep the block sizes small. A maximum of 50 connection objects or10-20 points of delivery is sufficient. With points of delivery you can define even smaller blocksize - for example, if units with a large number of premises/points ofm delivery exist in thesystem.

Working with BDoc FiltersYou can use the filter conditions to meet certain restrictions regarding the dataset during theinitial download and delta download. SAP predefines the fields HAUS and REGIOGROUP ,from the IS-U table EHAUISU, for the connection object. The same fields are predefined forthe point of delivery, along with the field SPARTE from the IS-U table EANL. Within the IS-U /CRM integration, you can also download certain data from the IS-U system into the CRMsystem (such as in the case of incorrect errors). You can, for example, only download pointsof delivery that concern the Electricity column. Use the Filter sync. (R/3) pushbutton in the IS-U table CRMFILTAB to define the filters, in order to reconcile delta downloads with the setfilter conditions.

Note

After downloading certain data records, ensure, if necessary, that this table no longercontains the unwanted filter that was set for the delta download.

End of the note.



Initial DownloadIt is not technically possible to delete master data in CRM (individual objects such asproducts, IBase components). For sandbox systems you have the limited possibility to useCOM_PRODUCT_DELETE_ALL to delete all individual objects and all products. In this case,the IBase entries remains empty. It is then possible to create new technical objects in CRM.

To start, choose transaction R3AS (Start Initial Download). Inn the Load Object field, enterSI_CONNOBJ or SI_POD and if necessary use the input help to select the sender orrecipient. In ERP, the initial download automatically generates a stop entry in the outboundqueue. As soon as the initial download has ended, the system removes it removedautomatically and triggers the delta download.

Note

For more information on data exchanges, see also the documentation under Help SAPLibrary Customer Relationship Management Data Exchange and Mobile Technology

CRM Integration Services Adapter and Site Categories Adapter Adapter Framework. If errors occur, see the outbound queue (transaction SMQ1) and the inbound queue

(transaction SMQ2) of the respective systems.

End of the note.

Transaction SMW01 (Display BDoc-Messages)When you have executed the transaction, exactly the same number of BDocs should havebeen created as the number of selected blocks. You can use various methods to control this.Some options are listed in the easy access menu of the CRM system, under Architectureand Technology Middleware Monitoring . You can gain a BDoc overview under themenu path Middleware Monitoring Message Flow Display BDoc Messages

(transaction SMW01). The BDoc category is SI_CONNOBJ or SI_POD.

You can recognize the queue names by the letter I, which means it is an initial download. Dstands for delta download and R stands for request load.

Caution

If an error occurs in a block, no data records from the block are created. You can manuallytransport blocks containing errors (for example, via the filter again) or transport them via deltadownloads. Errors that you do not correct for connection objects have a direct influence onthe point of delivery download.

End of the caution.

The connection of objects between the systems is as follows:

Object IS-U CRM

Connection object EHAUISU-CRM_GUID COMM_PRODUCT-PRODUCT_GUID

Point of delivery EUIHEAD-INT-UI COMM_PRODUCT-PRODUCT_GUID

During all loading process from SAP IS-U to the CRM system, the system checks whether therelevant GUID already exists in the CRM system. This determines whether the object waschanged or added. It also enables a new initial load or a request load.

You can choose the Extended Data pushbutton to display details on the loaded BDocs. Youcan then analyze the data structure of the BDocs. You can choose the ___ pushbutton todisplay error messages in the BDoc overview (transaction SMW01).

Typical errors that occur when loading objects are:



Missing or incorrect Customizing (occurs regularly for address)

Locked database – by transaction IB52, for example.

To solve this problem, end the transaction and restart the BDoc.

After you have eliminated the errors, you can use the ___ pushbutton with quick info textRetry Processing to retrigger BDocs.

Note

End of the note.

In the Data field of this overview, the characters behind the table name BAPI_EHAU areidentical to the connection object key in SAP IS-U (HAUS or TPLNR).

You can call existing IBase components (in this case connection objects) in the easy accessmenu of the CRM system, under Master Data Installation Display Installation

(transaction IB53). You do this by entering "COn" in the Object ID field (n stands for thetechnical location number for the connection object. It is identical to the number in SAP IS-U)and selecting IS-U Connection Objects in the Object Family field. Select Continue to go to theIBase overview. By selecting a node in the tree structure, and using the Component Detailsbutton, all detailed data for the technical object (connection object of point of delivery) isdisplayed.

Via Goto Address you can display the address of the technical object. The points ofdelivery belonging to the connection objects are also displayed in the tree structure, directlyafter the initial download. The objects are mainly stored in the CRM table COMM_PRODUCT.You can also use the fields Product ID and Object Family to find out, for example, how manyobjects have already been created.

Enhancements to Download of Points of DeliveryBefore you start the initial download of points of delivery, all connection objects, for whichpoints of delivery could already exist, should be created without errors.

The initial download process for points of delivery is much the same as the process forconnection objects. The object for points of delivery is SI_POD. The selection criteria listed inthe "Working with BDoc Filters" section are available for the filter. If filters already exist forconnection objects, these should be reproduced for the points of delivery.

During the download, the point of delivery "searches" for its corresponding connection object,via installations and premises, and automatically adds a further subnode to the IBasehierarchy for the connection object. You must undertake the following Customizing settings inthe CRM system, transaction COMCPRMSG, to download points of delivery: For messages009 and 011, specify that the system is not to issue a message in online mode.



Delta Download of Technical Objects

Delta Download of Connection Objects

The delta download of connection objects is generally triggered when the standardfunctionality is used to save a connection object. This means when a connection object iscreated, or an existing connection object is changed. Subsequent queue processing isidentical to that of the initial download.

During the initial download, a lock entry for delta downloads of the category ConnectionObject is set automatically in the outbound queue. Check the outbound queue of the IS-Usystem after a successful inital download and if necessary delete the entry manually.

For more information, see the documentation in the SAP Library.

Delta Download of Points of Delivery

The delta download of points of delivery runs the same way as for connection objects.



Upload of Technical IS-U Objects

As of CRM Release 4.0 you can replicate the technical IS-U objects connection object andpoint of delivery (PoD) as standalone objects from the CRM system into the IS-U backendsystem. Prerequisite is an SAP IS-U release as of SAP 4.71.

Note

For more detailed information on using customer-specific fields during replication see thesection Customer-Specific Fields for Technical IS-U Objects.

End of the note.

PrerequisitesSystem SettingsIn the CRM System

Call transaction Maintain IS-U CRM Parameters (ECRM_ISU_PARAMS) and set theUPL_VIA_CONTRACT indicator to SPACE. You can also find the transaction in Customizing.

Alternatively, you can replicate the technical objects with the contract in SAP IS-U. You onlyhave to select the indicator shown to do this.

In the IS-U System

Caution

See the notes on maintaining master data templates. The most common cause of errorsduring replication is incorrect master data templates.

End of the caution.

Upload Without Contract

In the IS-U backend system, you must create two master data templates for creating /changing technical objects. The master data template for connection objects must be from thecategory CRMCONNOBJ_ALONE. The master data template for points of delivery must befrom category CRM_POD_INST. The same rules apply for the naming of parameters as forthe general upload of technical objects with the contract. You can maintain the master datatemplates in Customizing, under SAP Utilities Customer Service CRM Integration

Allocate Master Data Template to Object Family for Uploading Technical Objects .

Caution

Naming Convention for Parameter Transfer

1. The parameter names are structured from the corresponding BAPI structuredescription with the field name, separated by _ .

2. The prefix BAPI_ is removed.

3. For repeat groups, such as the meter reading notes for the connection object, thefollowing applies: If the repeat groups only contain one line, the rules under 1.a nd 2.



apply. If there are more entries, the suffix _<Zeilennummer> is added as of thesecond entry.

End of the caution.

Example

1. Short text for connection object: EHAUTXT_SHTXT 2.

2. Language key for short text: EHAUTXT_LANGU_ISO

3. 1. Service for point of delivery: EUISERVICE_SERVICE

4. 2. Service for point of delivery: EUISERVICE_SERVICE_2

End of the example.

The definition means that a parameter never has the form <Structure>_<Field Name>.

You can use the BAPI structures listed below. Note that you should only use field values thatan agent in the Interaction Center can maintain for the technical objects:

BAPI Structure Description Repeat groups

BAPI_EHAU Connection object No

BAPI_EHAUNOTE Meter reading note for connection object Yes

BAPI_EHAUADR Connection object address No

BAPI_EHAUTXT Short text for connection object No

BAPI_EUI Point of delivery No

BAPI_EUITXT Short text for point of delivery No

BAPI_EUIADR Point of delivery address No

BAPI_EUISERVICE Services for point of delivery Yes

BAPI_EUISERVTXT Service texts Yes

Upload with Contract

It is also possible, in the CRM system, to create new technical objects, which are thenuploaded to the IS-U system via the contract object list, and are created as new, billabletechnical constructs (connection object, premise, installation, and point of delivery) using themaster data generator.

Master Data Template for Generation of Technical Objects

The master data generator works with a template from the category CRMTECHOBJ. Specifythe technical objects in this template, which the system is to create for a point of delivery andconnection object from SAP CRM in the ERP system.

Customizing Settings

Once you have created the master data template, in the ERP system link the productdescription from SAP CRM with the key for the master data template. Make these settings in



Customizing for SAP Utilities, under Customer Service CRM Integration Define MasterData for Generating Technical Objects for CRM Products .



BDocs

The same BDocs are used for uploads as for downloads. This refers to BDoc categoriesSI_CONNOBJ for connection objects and SI_POD for PoDs (points of delivery).

When you create or change a technical object in the CRM system, the system generates acorresponding BDoc. In the ERP Adapter, the technical object data is sent to the IS-Ubackend system. If the object can be successfully created, a response BDoc is generated. Inthe validation service, this response BDoc updates the ERP key for the technical object in theCRM system.

Queue Names

Because no R/3 key is known when the technical objects are created in the CRM system, it isalso not possible to form queue names from the connection object number. In the case ofuploads, the queue CSA_MASS_CONNOBJ is used for all new objects. The queue namesfrom R3AD_CONNOBJ<connection object number> are only available for downloads.

Error Processing

Serious errors, such as a missing master data template in the IS-U backend system, result inthe BDoc having an error status. Once you have corrected the system settings you can restartthe BDoc.

Caution

If errors occur when processing the master data templates, you must process these errors inthe IS-U backend system. You can do this using the new transaction IS-U Contract ErrorMonitor (ISU_ECRMREPLM). In this case, the BDoc is given the status "OK".

End of the caution.

Caution

For detailed information on this transaction, see document "Error Handling IS-U for UtilityContracts, Technical Objects from CRM". This is located in the SAP Service Marketplaceunder http://service.sap.com/utilities Product Information SAP CRM forUtilities Cookbooks & Guidelines .

End of the caution.



Cust. Fields f. Tech. IS-U Obj. in SAP CRM 4.0 andSAP IS-U 4.71PurposeAs of CRM Release 4.0, you can add customer-specific fields to the technical IS-U objects:Connection object and point of delivery. This section describes how you can do this:...

1. Define the customer-specific set categories in order to save your data in the CRMSystem.

2. Create the BAdIs for data exchange in the CRM system and the IS-U system (optional).

At the moment, the IS-U system supports customer-specific fields for connectionobjects and other master data, but not for points of delivery. If you have fields forthe point of delivery, you must ‘reroute’ these to other master data or store themin customer-specific tables.

Note

You can find further information on BAdIs in the SAP library under mySAPTechnology Components SAP Web Application Server ABAP Workbench

Changes for SAP Standards Business Add-Ins.

PrerequisitesIn order to use customer-specific fields in SAP CRM, the following prerequisites must be met:...

1. You must be using CRM release >= SAP CRM 4.0.

2. You must be using IS-U release >= SAP IS-U 4.71.

Technical objects are sent to the IS-U System independently as separate BDocs. There is aseparate system setting for this that you can check using the transactionECRM_ISU_PARAMS Maintain IS-U CRM parameters (indicator UPL_VIA_CONTRACT = ' ').

Transaction COMM_ATTRSETIn transaction COMM_ATTRRSET, you define the necessary attributes and allocate settypes. Read the documentation on this function. Do not use a lot of different set types, as thiscan have a negative effect on performance when processing products and individual objects.

Select the product category Material. Define the set type as Independent of Organization andallocate the corresponding object family (0101 = Connection Objects, 0102 = Points ofDelivery).

Multiple value attributes are not currently supported.

You can only allocate field names to attributes in the development system. The field namesare automatically generated in the customer system.

In the transaction COMM_HIERARCH or using the report mentioned below, allocate the newset type to your category for the object family.

For more information on categories and object families, see Customizing for CustomerRelationship Management under Master Data Installation Individual Objects / ObjectFamily.



Transport the set type. You can use this to guarantee that the fields of the newset type are included in the DDIC structureCOMT_PROD_MAT_MAINTAIN_API, which is the structure you need to updatethe data from individual objects during downloads.

You transport set types in transaction COMM_ATTRSET under Set Types /Attributes Transport Set Type. Set the Create API Append indicator.

Enhancement to the Connection Object in SAP CRMThe customer indlude CI_CON has been added to all relevant structures of the connectionobject in SAP CRM. The set type structures are also contained in this include. Werecommend that you use report ECRM_ISU_TO_DIV_SETUP_0101. This reportautomatically adds new set types in the correct product categories and deletes them again ifno objects exist for the category.

In the second section of the dialog, you can adjust the CI_CON customer includeautomatically. The report provides group names and automatically adds suffixes to thestructures. This prevents problems from occurring in the administration fields when multipleset types are used.

Once you have successfully created the include, you can use the new fields immediately –see transaction GENIL_BOL_BROWSER. For example, in the configuration of the connectionobject detail view, you can adjust the user interface, include the new fields directly in the view,and use them.

Enhancement to the Point of Delivery in SAP CRMThe functionality of the point of delivery is generally the same as the connection object. Thecustomer include CI_POD has been added to all structures relevant to the point of delivery inCRM. The main difference comes with release CRM 2006s/2 - as of this release, division-based enhancements of the point of delivery are also available.

You maintain the division-dependencies using the Customizing view clusterECRM_ISU_VC_DST. here, you can define the different divisions that you want to use for thepoints of delivery. The divisions are not the same as the divisions in the CRM or ERPsystems. They can be very flexible - for example, they can be utility divisions (such as 01 =Electricity, 02 = Gas) or, if necessary, the can be other services (such as IS = InsuranceServices, TS = Telecommunication Services).

Once you have defined your divisions for the points of delivery, you can allocate the set typesto the divisions. The set type ISU_POD is always available. This is the master set type thatcontains information on the division, for example. The EUI_EXT_UI and EUI_INT_UI fieldsare used for technical identification.

The last table is only relevant if you do not use an IC WebClient user interface. Here you canmake your own field settings – for example, for an e-commerce scenario (currently onlyavailable for telecommunications). To do this, use the configuration tool in the IC WebClient.

Customizing Report ECRM_ISU_TO_DIV_SETUPYou can use this report to make all the relevant settings for the enhancement of points ofdelivery in SAP CRM.

Transfer of Division-Dependent Set Types to PoD CategoryThe report reads all the set types defined in Customizing for the mentioned view cluster. Itautomatically detects which of the set types exist in the category of object family 0102 (basedon your Customizing settings for transaction COMM_HIERARCHY). If no set types areavailable, you can attach them to the category. If no point of delivery exists for this categoryor division, you can delete it.



Create or Change Customer Include CI_PODFor the product itself, it is necessary to generate or extend the customer include CI_POD (orCI_CON for the location) by the set type structures. You can select the available structures inthe ALV on the left hand side. Drag them to the middle, and execute the program step. Youcan then control the structure by choosing the Display pushbutton, for example.



Excursus: Changing settypes and attributesActivitiesAdding, changing or deleting attributes in existing settypes

At this point, you do not need to do anything else because the set type DDICstructure is directly included in the CI include; the fields are available on all levels

Caution: Changing attributes can cause problems, particularly if the set type tablescontain entries

Adding, Changing or Deleting Set Types

See note 1060547 for SAP CRM 2006s/1 and for SAP CRM 2006s/2 up to SP01

Add set types: Restart the report for generating the include CI_POD In addition, thenew set types are attached to the end of the structure with a new suffix; the otherincludes remain unchanged.

Changing: Do not change the set types manually.

Delete: Execute the report again. The include is deleted from the structure; the otherincludes remain unchanged. The suffix of the deleted set type can be used for a newset type.

Time periods for IObjects set types (since CRM 2006s/1 SP 4)As of support package four of CRM 2006s/1, it is possible to manage timeslices in the settypes of an individual object (service industry version). This means to make it possible tochange field values with a kind of “activation date”, in the future as well as in the past.

To activate the time dependency of a set type, choose the setup reportECRM_ISU_TO_DIV_SETUP and the choose the Execute button as shown in the followingfigure.

Note

Technical Background

If you mark a set type as time dependent and choose the Apply Changes button in the popup,the system replaces the generated SAVE function of the set type with a generic SAVEfunction. Accordingly, it is also possilbe to deselect the indicator and reactivate the genericfunction. However, in this case, changes will be lost in the future as the generated functionalways uses the current date as the start date and 31/12/9999 as the end date if the set typeis changed. The time dependency of the set types is independent from the service type;however, its use is only optional for every service type. To use the timeslices, use the viewconfiguration tool to set the ‘VALID_FROM’ and/or ‘VALID_TO’ fields to the technical datadetail view. These two fields are always generated when the set type is created. However,they are only valid for the fields of one set type.

EXAMPLE: Example: Set type ‘ZETC_T1’ used in service type ‘T1’ and ‘UG’:

Attribute ‘ZZ0010’ -> ZETC_OBU_ID

Set type structure ZETC_V1_MV includes fields ‘VALID_FROM’and ‘VALID_TO’

Set type name in structure CI_POD = ‘.INCLU-A2_’



Name of valid fields in the view configuration://SERVICEOBJECT/STRUCT.VALID_TOA2_ and//SERVICEOBJECT/STRUCT.VALID_FROM2_

Exception: Standard set type ISU_POD which is always allocated automatically. If you want tomake field EXT_UI, for example, time-dependet, use fields PD_VALID_FROM and/orPD_VALID_TO .

End of the note.

Detailed handling of the time periods - examplesChanges in the future (standard case)

Existing timeslice: 19.02.2004 14:10:42 - 31.12.9999 23:59:59

New value in the future

Entry from UI timestamp fields

PD_VALID_FROM COMT_VALID_FROM 21.12.2007

PD_VALID_TO COMT_VALID_TO empty

Leads to the following new timeslice in the tables:

ISU_PODH

19.02.2004 14:10:42 - 20.12.2007 23:59:59

ISU_POD 21.12.2007 00:00:00 - 31.12.9999 23:59:59


New timeslice insert

Entry from UI timestamp fields


PD_VALID_TO COMT_VALID_TO 23.12.2007


ISU_PODH

19.02.2004 14:10:42 - 20.12.2007 23:59:59

21.12.2007 00:00:00 - 22.12.2007 23:59:59

ISU_POD 23.12.2007 00:00:00 - 31.12.9999 23:59:59


New value in the past (mainly toll collection)

Entry from UI time stamp fields

PD_VALID_FROM COMT_VALID_FROM 30.06.2006 12:00

PD_VALID_TO COMT_VALID_TO




ISU_PODH

19.02.2004 14:10:42 - 30.06.2006 11:59:59

ISU_POD

30.06.2006 12:00:00 - 31.12.9999 23:59:59

ISU_PODH

19.02.2004 14:10:42 - 20.12.2007 23:59:59

21.12.2007 00:00:00 - 29.12.2007 23:59:59

ISU_POD

30.12.2007 00:00:00 - 31.12.9999 23:59:59

Changing an attribute with existing changes

Entry from UI time stamp fields


PD_VALID_TO COMT_VALID_TO

Insert not possible (check)

Cancellation of 30.12.2007 00:00:00 - 31.12.9999 23:59:59

Leads to the following new time slice in the tables:

ISU_PODH

19.02.2004 14:10:42 - 20.12.2007 23:59:59

21.12.2007 00:00:00 - 24.12.2007 23:59:59

ISU_POD

25.12.2007 00:00:00 - 31.12.9999 23:59:59



Automatic Enhancement of CI_PODActivities

Caution

The address enhancement is possible, but not recommended for utility customers.

With this support package it is possible to enlarge the technical object of type 0102 (= PoD)with an address or with warranties.

This development is mainly made for simplification. You can also use these extensionswithout defining additional settypes for different service type as mentioned above.

In the area of the CI_POD customer include you now have two additional options:

Option 1 Option 1: Automatic enhancement of the customer include structureCI_POD with the DDIC communication structure CRM_SI_WB_COMMSTRUC

Option 2 Option 1: Automatic enhancement of the customer include structureCI_POD with the DDIC communication structure CRM_SI_WB_WARRANTYSTRUC

Do not enhance the customer include manually, because the report also generates somenecessary additional information into the CI include.

You can use all of the fields list below directly in the views defined for the service typedependent service objects.

End of the caution.

Structure CRM_SI_WB_COMMSTRUCWith this structure you have different address structures for disposal:

1. Structure ADRS1: this structure is based on the SAP central address managementand includes the main address fields like street, postal code, city, etc.

2. 8 structures of type CRM_SI_WB_COMM_ADTEL: with this structure(s) you are ableto create up to eight telephone numbers with the main fields COUNTRY,TEL_NUMBER, TEL_EXTENS, REMARK, VALID_FROM and VALID_TO.

3. 8 structures of type CRM_SI_WB_COMM_ADSMTP: with this structure(s) you areable to create up to eight email addresses with the main fields SMTP_ADDR,REMARK, VALID_FROM and VALID_TO.

4. 4 structures of type CRM_SI_WB_COMM_ADFAX: with this structure(s) you are ableto create up to four fax numbers with the main fields COUNTRY, FAX_NUMBER,FAX_EXTENS, REMARK, VALID_FROM and VALID_TO.

5. 4 structures of type CRM_SI_WB_COMM_ADURI: with this structure(s) you are ableto create up to four URI addresses with the main fields URI_TYPE, URI_SCREEN,REMARK

Structure CRM_SI_WB_WARRANTYSTRUCWith this structure you have the option to add up to two warranties to the service object. Thefollowing fields exist for each of the warranties: WARRANTY_PROD, START_DATEWY,START_DATE_RULEWY, END_DATEWY, END_DATE_RULEWY,DETERMINE_DATESWY, DELETE_WYT.



The warranties themselves are based on the relationships between warranty products andindividual objects, as in the standard IBase. So can also display or edit warranties using theIBase transactions if necessary.



Replication of Customer Enhancements

Example

All BAdIs are delivered with example coding. You can display the coding in the transactionBAdI Builder – Definitions (SE18). Enter the name of the BAdI and select Display. In themenu, choose Goto Sample code Display . There are extensive comments for theBAdIs. The customer set type ISU_CUST01 is used as an example for the connection object,and the set type ISU_CUST02 is used as an example for the points of delivery. Both set typescontain the fields PARTNER, NAME_FIRST and NAME_LAST. The DDIC structures aregenerated automatically during creation of the set type. The data is attached to the BDocsSI_CONNOBJ or SI_POD as a new segment.

BAdIs to be Implemented

BAdIs to be implemented can be divided into two categories:

1. BAdIs for Data Exchange with the IS-U System

2. BAdIs for displaying data in the CRM system

BAdIs for data exchange with the IS-U System

List of BAdIs

IBSSI_SEND_TO_UPL (CRM)

This BAdI adds the customer-specific data to the BDoc for the technical objectsbefore upload.

IBSSI_RECEIVE_TO_UPL (IS-U)

This BAdI reads the customer-specific data from the BDoc for the technical objectsafter upload. The data is transferred to the master data generator.

IBSSI_SEND_TO_DWN (IS-U)

This BAdI adds the customer-specific data to the BDoc for the technical objectsbefore download.

IBSSI_RECEIVE_TO_DWN (CRM)

This BAdI reads the customer-specific data from the BDoc for the technical objectsafter download. You must maintain the set type of the individual object in the BAdI.

BDoc Enhancements

The BAdIs described above write and read the customer-specific data in the BDocsSI_CONNOBJ and SI_POD. You can display this data in the CRM system using the DisplayBDoc Messages transaction (SMW01). Select a BDoc and choose the Show BDoc. MessageExt. Data pushbutton. You can view your own data in the "normal" BAPI structures.

Overview screen

In the following figure, you can see the events for which each BAdI is called:



CustomerData

Bdoc for TO

IBSSI_SEND_TO_UPL

IBSSI_RECEIVE_TO_DWN

IBSSI_RECEIVE_TO_UPL

IBSSI_SEND_TO_DWN

In background: Callmaster data generator

Dialog: Create/change TO inIS-U transactions

In background: Create/changeind. objects in IBase

Dialog: Create/Change TO in ICWorkspace

IBSSI_DISPLAY_TO_CO

IBSSI_DISPLAY_TO_PODCRM IS-U

Upload

Download



Utilities Industry Enhancements with CRM 2006s/2.ActivitiesBlock 1-> Change address groups for connection objects and PoDsWith this action it is possible to set own addressgroups for connection objects and point ofdeliveries. This is particularly important for technical object address searches. Now it possibleto get better results- e.g. if somebody searches for CITY = ‘Examplevillage’, that the searchnow finds only connection objects OR(!) PoDs.

In former releases it finds connection objects AND PoDs. It is also possible to run or switchback to the old mode.

Execution of this block: recommended

Runtime of this block: medium.

Block 2-> Fill index table ECRM_ISU_TO_IDX for a better searchperformanceIndividual object, IBase components and their sets are stored in many different tables. Themain key of the object is defined in the new index table. This results in a better searchperformance for these obejcts.

Execution of this block: recommended

Runtime of this block: High

Block 3-> Deactivate index table ECRM_ISU_TO_IDX (for migration, forexample)Sometimes it makes sense to switch off the index, for example, during migration from IS-U, orwhen performance deteriorates during mass creation of technical objects.

We recommend execution of this block for mass processing of technical objects.

Runtime of this block: Very low

Block 4-> Fill field IN_GUID of table IBIN (only for migration from olderreleases)For a better selection of IBase data in the new searches, it is obligate to have the componentGUID in a RAW 16 format. This was not possible in older releases.

Execution of this block: obligatory if the fields are empty in table IBIN

Runtime of this block: Low

Block 5-> Create CRM GUIDs for premises (necessary for usingWebClient UI)

Note

This conversion is necessary to work with premises in the CRM WebClient UI.

Execution of this block: Obligatory

Runtime of this block: High



End of the note.

AppendixBADI ECRM_ISU_UTILITY_UIS was created primarily for the GUI interfaces. You can alsouse method CHECK_DATA_BEFORE_SAVE to make checks before saving.

is-u/crm integration: replication of technical objects - sap

Documents