Skip to end of metadata
Go to start of metadata

IDOC/ALE Data Exchange Set up.

Communication is the watch word for the world at this point of time. Right from people, countries, our day to day life, everything depends on communication in one form or the other which suits the target and the destination. Real time scenarios are one point reference from where all SAP products have evolved. Automatic Link Enabling (ALE) data exchange won't differ either from this path. For the data exchange between highly integrated SAP and non-SAP systems, ALE Distribution model came into existence. There are different aspects of ALE Distribution model, out of which Idoc is the core point of ALE.

There are lots of talks about Idocs and data exchange. Ever wondered what it takes to set it up in your system. I feel this document will certainly answer those questions.

To set up the communication with any other R/3 system or CRM system, a series of steps are required that you have to carry out in Customizing for ALE (Transaction SALE).

For details of ALE communication relationship maintenance, see under SAP Web Application Server ® IDoc Interface/ALE, in the SAP IMG in SPRO transaction:

There are few settings to be modeled before we use Idoc for Data Exchange:

  • Define the RFC Destinations.
  • Generate the Partner Profiles.
  • Site Subscription in Transaction smoeac.
Define RFC Connections:
  • Log on to SPRO transaction.
  • Browse to the following path :
  • SAP Web Application Server -> Application Server > IDOC Interface/ALE -> Communication.
  • In the above link click on Create RFC Connections.
  • There in the SAP Connections create a new RFC Connection for the preferred destination (In our case the example is Q8D Client 003.
  • Find the snap shots of the client destination which is registered.
    Click on Create RFC Connections. You will get this screen.
     Then click on the ABAP Connections and create a RFC Connection. If the RFC destination is already registered don't create it again. After filling up the data, then the screen looks like this with all the data. Target host and the system number have to be entered in this tab along with the description.
    In the next tab, you can enter the User name, if required new one or the current one which you are using. Password has to be set and saved.

The connection can be tested by clicking the button present in the tab. By clicking so the time taken for the RFC calls will be listed in the table.

Generate or maintain Partner Profiles:

After finishing the RFC destination registration, check the Partner profile in the transaction WE20. If there are partner profiles existing for the current client (For e.g. Q5C) that would have been listed there.

  • Go to Tx We20 and check whether the partner profile is existing for the current system in which you working on.
  • If there is a partner profile existing for the current system we are working it will be listed as in this snap shot.

             
Usually in the outbound parameters, if the message type (say for BP, it is CRMXIF_PARTNER_SAVE_M) is not maintained, click on the existing message type, you will get the following screen. 

There we need to register the Port, for which all the details will be picked up from the RFC Destination entry we have registered previously.

Click on the Receiver port, which will take you to the following screen.
 Here click on the create button and create the port with the RFC destination you have created previously. (For e.g. in our case it is Q8DCLNT003). Then this will take you to the RFC Destination screen.

  • After this is done click on the plus button in the Message type (either in inbound parameters or outbound parameters) depending upon our need, so that we can specify the message type and the receiver port which is the destination.
  • For outbound the registering will be like the following snap shot.

For Inbound the screen will be like the following snap shot.
Here the processing code will be APLI.

  • Similarly do these steps both in Host system and the target system.
  • If the scenario is one way, in CRM 5.0 register Inbound Parameter and in CRM 2007 register outbound parameter and vice versa.
Site Subscription in Transaction smoeac:

    After these registration are over, open Tx smoeac and do the site subscription as   follows.

  • Here we need to add the site and subscriptions.
  • Site is the destination to which the data is to be sent.
  • Subscription is to identify what are the data that have to be exchanged. (In Case of BP Data it will be All Business partner MESG)
  • After this done the entry has to be made in CRMXIF_C1 transaction where we enter the site type and accordingly the message type.
    Following is the snap shot of the CMRXIF_C1 transaction.

Following is the snap shot of transaction CRMXIF_C1.

In this transaction we need to finally register the Site name (Kind of Description), Site type (Is it going to be XIF Idoc or XIF XML), Bdoc Type and Interface name (Say for e.g. CRMXIF_PARTNER_SAVE for Business Partner exchange).