Google+ SAP CRM Adapter Overview - SAP ABAP

SAP CRM Adapter Overview

The SAP CRM Adapter receives knowledge from the Circulation and sends this knowledge to the CRM online components.It receives the info contained in BDocs from the Stream Control and writes the content material of the BDoc information segments into the corresponding tables of the CRM on-line database. This database can additionally be accessed through the CRM online components.If a enterprise object is modified through an online element, the CRM on-line database is up to date accordingly. On the similar time the CRM on-line element additionally generates a new BDocs, which contains the changed tables, and initiates a model new Circulate via inserting those BDocs into the queue of the Inbound Adapter.

Both the CRM service and the CRM On-line elements entry the CRM Online database utilizing the same application programming interface (API).Every business item that's uploaded to the web parts has a person CRM carrier,which is implemented in separate operate module. The names of these capabilities modules might be bought from the corresponding flow definition.If data is changed in one of many CRM Online elements, these adjustments are written to the CRM On-line database and at the similar time a BDoc is generated that contains the changed data. This BDoc is placed into the queue of the Inbound Adapter and thus initiates a brand new Circulation within the Movement Control.

R/3 Adapter Customizing

The initial obtain is precipitated by the R/3 Adapter on the CRM system. The downloaded objects are mapped to BAPI buildings at the CRM server and written to the consolidated database (CDB) for being processed by means of the move control.Solely sure enterprise gadgets may be uploaded from the CRM Machine to the OLTP R/3 Gadget,while many business gadgets can integrated right into a delta download from the OLTP R/3 System to the CRM System.

Key Completion

A key completion/technology is finished by way of the R/3 key area relations.Worth for field CITY1 for Customer 255 has been changed within the OLTP R/3 System.The delta obtain always transfers the modified fields plus the R/3 key (KUNNR = ‘255’). The Key Era Carrier (KeyGen) checks if KUNNR has already received an SFA key earlier than through wanting into an inside KeyGen table (SMO9_KYTBL) and into table SMOKNA1 in the CDB.The Key Technology Service first completes/generates keys for the root segment after which for the segments of the subsequent lower hierarchy level.Aside from the basis phase, at all times a primary key (SFAKEY) and a foreign key (SFAKEY of the mother or father segment) are given. This info is kept within the BDoc segments (table SMOG_SEGM).

The first key of a each segment and the foreign key of the parent segment is at all times fetched automatically.There could be keys which have no hierarchical meaning (references) or can't be fetched by way of this logic.

Example: SFAKNA1 in SALESDOCUMENT cannot be fetched since SMOKNA1 shouldn't be part of the BDoc; in this case a fetch mechanism for non-key fields uses table SMO9_XFTCH to search for the obligatory keys.


Possible data exchanges

New download items has new table now not belonging to current business item:

1.The table will be to start with downloaded (many instances or on regular foundation) by integration into the Customizing Download (download for customizing tables) that is a straightforward manner of enhancement,except for mapping.

2. New desk in current obtain object:The table is downloaded (initial/delta) by method of an enhancement of the “Send_to_Server” operate module via user exits.

3.New upload objects has Business gadgets Buyer, Touch and Sales Doc can be superior and uploaded.New fields will be added to all of them and new tables might be introduced to the Customer and Touch items only.

New or Modified Objects

If the information fields within the OLTP R/3 and CDB tables have equivalent names and knowledge elements, the process of extending the preliminary download with a model new or changed customizing object may be very simple.Only preliminary and synchronization download might be supported using this technique.If an append structure to an existing desk is used, the append structure must be introduced to the CDB table and the appropriate BDoc kind needs to be changed as defined in unit BDoc Modeling.If a model new table is used, either an present BDoc needs to be prolonged or a new BDoc must be created.The table is then brought to the checklist of obtain tables within the R/3 Adapter customizing entries present in the item management menu path.In the above cases, table fields are mapped automatically. If area names or data sorts do not agree,the mapping needs to be programmed in a buyer exit.If key fields are completely different or R/3 key family members should be supported, further entries should be made in table SMO9_XFTCH to support the vital thing generation process throughout the download.

Prevalent customizing obtain objects are created by way of specifying a obtain item name and description, the GUID of the BDoc sort (is acquired from SMOGTRANS), and the number of objects to be downloaded in a single BAPI call.This quantity should not be too small to keep away from too many calls and thus time-consuming processing,nor ought to it be too giant to avoid timeouts.

The tables to be mapped should be specified by entering the corresponding table names of the source table in the OLTP R/3 System and the vacation spot table on the CRM Middle ware.Desk fields with identical names and knowledge varieties will then be mapped automatically.Filter settings can be specified for certain fields to solely obtain and map sure values of these fields.


Related Posts

SAP CRM Organizational Model

CRM Middle ware System Architecture
CRM Middle ware Enhancement
CRM Middle ware Data Flow 
CRM Middle ware Modelling
SAP journey from R/3 towards MySAP.com
MySAP technology RFC,BAPI,ALE and IDOC overview

No comments :

Post a Comment