How to Configure SAP R/3 for IDoc and BAPI/RFM Connectivity

Document created by akhil_khandelwal Employee on Apr 18, 2016Last modified by Adam Arrowsmith on Dec 14, 2016
Version 9Show Document
  • View in full screen mode

This article covers the basic configuration steps for SAP connectivity, both for IDoc and BAPI/Remote Enabled Function Module calls.

 

 

Introduction

Integration with SAP R/3 is typically performed via one of two methods:

  • IDoc - IDocs (Intermediate Document) are a popular data structure by SAP primarily used to exchange business/transaction data between SAP and external systems electronically. Official Documentation:  IDoc Interface/ALE - SAP Library.
  • BAPI/Remote Enabled Function Module - BAPIs are programmatic interfaces developed within SAP that can be invoked synchronously from a external system or with in SAP. Official Documentation: SAP Library , RFC Interface - Connectivity - SAP Library.

 

The Dell Boomi SAP Connector enables you to connect to your SAP NetWeaver-based application and get or send data via BAPIs, Remote Function Modules (RFMs) and asynchronously via IDocs. You can browse the list of available BAPI/RFMs and IDocs available in your SAP system and auto-generate the request and response profiles to use in Dell Boomi AtomSphere processes and maps. Official documentation: SAP Connector.

 

The SAP Connector supports three actions:

  • GET - Used for BAPI/Remote Function Module (RFC type communication)
  • SEND - Used for Inbound IDoc processing
  • LISTEN - Used for Outbound IDoc processing or receiving IDoc

 

The environmental and SAP configurations described below will vary based on the integration method.

 

Atom Configuration

A local Atom installed within your network is typically required to be able to integrate with the SAP application.

 

The SAP Connector uses the SAP Library for Java Connectivity (JCO) for BAPI/RFM and SAP Java IDOC Class Library for IDoc. You will need to download corresponding jars and .dll from SAP Service Market Place Portal (SMP). The jars are OS/Kernel dependent so be sure to download the compatible version for your environment.

 

  1. Download the files from the SAP Service Market Place Portal:
  2. Unzip and add the files to ../<atom_root>/userlib/sapjco (create the directories as needed):
  3. Restart Atom Service.

 

SAP Configuration for BAPI Integration

There is no additional configuration required for standard BAPI integration other than ensuring the SAP user configured within the SAP Connector has sufficient roles/privileges for accessing and invoking the desired BAPIs.

 

If the standard functions do not meet your integration requirements, you will need to enlist an SAP ABAP developer to design and implement a custom function according to your needs. Function design is beyond the scope of this article but remember to activate/release the function for it to be visible to the SAP Connector's import wizard.

 

SAP Configuration for IDoc Integration

The following configurations are required in SAP to send or receive IDocs. These steps should be performed by a SAP Admin/BASIS professional.

 

Setup Logical System, Distribution Model, and Generate Partner Profile. For more information see SAP Help: Implementation - IDoc Interface/ALE - SAP Library and SCN Welcome | SCN.

 

  1. Add Logical System using transaction code SALE:
  2. Create/Change Distribution Model using transaction code SALE or BD64:
  3. You may either create new model view or edit an existing one. Then add sender/receiver (Logical System) and message types:
  4. Generate Partner Profiles. Use the method as provided in screenshot or transaction code we20:

 

Additional SAP Configuration for Outbound IDoc Integration

The following configurations are required in SAP to send outbound IDocs to the Atom. These steps should be performed by a SAP Admin/BASIS professional.

 

  1. Configure Gateway:
    1. Register external Program in SAP gateway by editing reginfo. Gateway Security Files secinfo and reginfo - Security Settings in the Gateway - SAP L
    2. Import reginfo in Gateway using transaction code SMGW:
    3. Create RFC Destination of Type = 'T' (TCP/IP) - SAP JCo Server Programming - Components of SAP Communication Technology - SAP Library:
    4. Restart the Atom and check gateway monitor to ensure that the connection is registered correctly:
  2. Create a Port using transaction code WE21:

 

Local TID Database Configuration (Outbound IDoc Only)

When listening for outbound IDocs sent from SAP, the SAP Connector requires a local database to track the TIDs for the IDocs received and processed successfully. The local Atom must be able to access the database.

 

The connectivity database information will be configured in the SAP Connector connection component > Listener Settings tab. If the database is not supported by default, you will need to obtain the appropriate JDBC driver and add it to the Atom. See Database Connector.

 

 The example below uses a MySQL database.

 

Create a new database. The database name is arbitrary. The SAP Connector will automatically create the tables during first IDoc interaction.

 

CREATE {DATABASE | SCHEMA} [IF NOT EXISTS] db_name

 

 

Additional TID Database Details

The following is provided for informational purposes.

Table NameTID_MGMT
ColumnsTID varchar(255)
PROG_ID varchar(255)
STATUS varchar(255)
Primary KeyTID, PROG_ID
STATUS Values

CHECKED - Initial receipt of IDoc message

CONFIRMED - After all RFC functions have been completed successfully

COMMITED - Successfully handled by the SAP Connector

 

Conclusion

The article covers basic configuration steps required to establish connectivity between SAP R/3 System and a Local Atom. An enterprise system like SAP provides multiple ways to doing certain things, so some steps may vary.

10 people found this helpful

Attachments

    Outcomes