SAP CRM Data Exchange via XIF Adapter

SAP CRM Information Exchange by method of XIF Adapter has SOAP/XML or IDoc format utilizing external interfaces (abbreviation: XIF for exterior interfaces).

1. From the CRM System to external programs
2. From external system to the CRM System
3. The Data Objects may be loaded initially by approach of file transfer using the DX/LSMW Workbench as nicely as be dispatched completely to the CRM System.
4. The data objects can be loaded initially utilizing the CRM middle ware Adapter Framework in exterior methods, loaded in an information file or be sent permanently by CRM in external methods through acceptable application transactions.
5. CRM contains DX Workbench and mapping tool for file-based mostly preliminary data load
6. 15 Certified 3rd-Celebration ALE Message Handling Programs (BEA, IBM MQSeries, NEON, TIBCO,...) fifty eight Certified third-Party ALE Converters (CrossWorlds, Harbinger, Mercator, Oberon, Sterling, ...) fifty seven Licensed third-Social gathering EDI Subsystems (Actis, Harbinger, Premenos, Seeburger, Sterling,...), 14 Licensed third-Celebration migration interface partner instruments (Artuad. ETI*Extract, NSX, SOPRA,...)

The external interface adapter (XIF adapter) offers:

1. Services in the CRM Server Messaging Flow
2. Bulk-message capable IDoc and XML interfaces for exterior methods
3. More information about the XIF Adapter may be found in the SAPNet through the alias: crm-ci.

External Interface Adapter

In outbound transactions, for example, creating or changing a Data Object within an utility transaction, an mBDoc is created and transferred to the CRM middle ware. Attainable external receivers for the mBDoc are decided throughout the CRM middle ware and are transferred to the XIF adapter along with the mBDoc. The info within the mBDoc is transformed within the XIF adapter into an XML-like complicated Data Structure and an appropriate fundamental service (SOAP, ALE) is started that sends the Data Object to the external receiver; for instance, by means of a third-party middle ware Tool.In inbound transactions, incoming messages in XML- or IDoc format are acquired by the XIF adapter via the essential services (SOAP, ALE) and transformed into the constructions in the mBDoc. The CRM middle ware then begins, calling an applicable software validation service that updates the appliance after successful checks on the message.

Extra detailed overview of SOAP/XML Processing:

1. SOAP/XML messages may be dispatched to the SAP Trade Infrastructure the place the XML message can be mapped into different XML Schemata. The XML messages may be routed to other Business Systems.
2. SOAP/XML messages can be dispatched to XML Messaging systems that convert the XML into different XML schemata primarily based on mapping rules and ship these messages to different functions based on routing rules.
3. For CRM ¡ê Enterprise Connector communication, IDocs should be used: An IDoc switch is quicker in comparison to SOAP/XML as a result of the IDoc doc accommodates no metadata information (tags) not like an XML document, and due to this fact, the scale of doc sent down the line is considerably smaller in comparison.

Extra detailed overview of IDoc Processing

1. IDocs can be utilized to send messages to the SAP Alternate Infrastructure the place an IDoc XML doc will in all probability be established and mapped into different XML Schemata. The XML messages could be routed to other Business Systems.
2. IDocs can be utilized to ship messages to the Enterprise Connector where an IDoc XML doc will in all probability be established and mapped into other XML Schemata similar to Rosetta Net, xCBL or buyer‘s own schemata.
3. IDocs can be utilized to send messages to a flat file.
4. IDocs can be used to ship messages to an ALE converter, the place IDocs are mapped into standardized message formats (EDI communication).
5. IDocs can be utilized to send messages to an ALE Messaging System. In contrast to an ALE converter, the message handler will not carry out any conversion or mapping but instead receives IDocs and sends them to functions for processing.
6. IDocs can be used to ship messages to an EDI Sub-System. In distinction to an ALE converter, the EDISub System doesn't use direct program-to-program communication for transferring IDocs.

Related Posts
SAP CRM Technology Overview
CRM Data Exchange with SAP R/3
SAP CRM Organizational Model
ROLE OF INTERNAL TABLE IN ABAP DAY 22
ABAP SUB ROUTINES DAY 23
FUNCTION GROUPS AND FUNCTION MODULES IN ABAP DAY 24