Download

Features

Relevant 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 structure from the ERP system to the CRM system. This allows you to prevent errors during the regional 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_POD

Transaction R3AC1 – Business Adapter Objects

Points of delivery cannot be replicated without the corresponding connection objects. The fields 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
BAPI_EUITXT	Short text for point of delivery (for technical reasons, the grid data is also transported to this table if it is active).

During initial and request loads, points of delivery are only loaded via the higher-level connection 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 CRM system. 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 service processes.

Activities

Settings for Connection Objects and Points of Delivery

Before you start the initial download, make your settings in transaction R3AC1 with regard to the 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, in which, for example, you only downloaded the first 100 connection objects in block sizes up to 10 data records in the CRM system. This enables you to discover possible errors faster, and to eliminate them.

Notes on Performance With Regard To Technical Objects

See 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 or 10-20 points of delivery is sufficient. With points of delivery you can define even smaller block size - for example, if units with a large number of premises/points ofm delivery exist in the system.

Working with BDoc Filters

You can use the filter conditions to meet certain restrictions regarding the dataset during the initial 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 for the 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 CRM system (such as in the case of incorrect errors). You can, for example, only download points of 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 set filter conditions.

Note Note

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

End of the note.

Initial Download

It is not technically possible to delete master data in CRM (individual objects such as products, IBase components). For sandbox systems you have the limited possibility to use COM_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, enter SI_CONNOBJ or SI_POD and if necessary use the input help to select the sender or recipient. In ERP, the initial download automatically generates a stop entry in the outbound queue. As soon as the initial download has ended, the system removes it removed automatically and triggers the delta download.

Note Note

For more information on data exchanges, see also the documentation under Help SAP Library 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 have been 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 Architecture and Technology Middleware Monitoring . You can gain a BDoc overview under the menu 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. D stands for delta download and R stands for request load.

Caution Caution

If an error occurs in a block, no data records from the block are created. You can manually transport blocks containing errors (for example, via the filter again) or transport them via delta downloads. Errors that you do not correct for connection objects have a direct influence on the 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 the relevant GUID already exists in the CRM system. This determines whether the object was changed 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. You can then analyze the data structure of the BDocs. You can choose the ___ pushbutton to display 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 text Retry Processing to retrigger BDocs.

Note Note

End of the note.

In the Data field of this overview, the characters behind the table name BAPI_EHAU are identical 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 access menu 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 the technical 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 the IBase overview. By selecting a node in the tree structure, and using the Component Details button, all detailed data for the technical object (connection object of point of delivery) is displayed.

Via Goto Address you can display the address of the technical object. The points of delivery belonging to the connection objects are also displayed in the tree structure, directly after 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 many objects have already been created.

Enhancements to Download of Points of Delivery

Before you start the initial download of points of delivery, all connection objects, for which points 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 for connection objects. The object for points of delivery is SI_POD. The selection criteria listed in the "Working with BDoc Filters" section are available for the filter. If filters already exist for connection 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 IBase hierarchy for the connection object. You must undertake the following Customizing settings in the CRM system, transaction COMCPRMSG, to download points of delivery: For messages 009 and 011, specify that the system is not to issue a message in online mode.