Interface creation using BAPI
Skip to end of metadata
Created by Bharadwaj p, last modified on Nov 13, 2008 Go to start of metadata
1. Determining the SAP Business Object and Its Key Fields
2. Defining the Interface Structure of the BAPI
3. Identifying the name of the function group, or if a function group does not exist already, planning a name for one.
All BAPIs belonging to one SAP Business Object should be stored as function modules in one function group. Ascertain whether a function group has already been created for the BAPIs of the SAP Business Object in question. If a function group does not already exist, then plan a name for the one to be created.
To ascertain the technical name of the Business Object, open the Business Object in the Business Object Repository (BOR), as described in Determining the SAP Business Object and Its Key Fields. To display further details, for example, the object type, double click the name of the Business Object.
4. Assigning a name to the function module
Choose a name that gives an indication of what the BAPI is used for. The naming convention is: BAPI__. For information about naming a method refer to Naming the Method in the BOR.
For example, in the case of a BAPI which reads details for the object type Creditor, the name of the associated function module is BAPI_CREDITOR_GETDETAIL.
 Naming Parameters in the Function Module
 Defining the format for passing the values in the function module interface.
5.Parameters must not be converted before they are passed to and from the BAPI interface. This is because BAPIs are programming interfaces and not end user interfaces. Exceptions are currency codes, ISO codes and fields with an internal key.
 Specifying the Required Objects in ABAP Dictionary
 Naming the Method in the BOR
 Naming Parameters in the BOR 6. Generate the ALE interface from BDBG.

Interface Development using IDOC’s
Skip to end of metadata
Created by Ravi Kumar Gunda, last modified by Disha Jain on Sep 11, 2008 Go to start of metadata
Abstract
This document explains in detail of creating an interface to transfer data through Idoc’s between two SAP systems or between an SAP system and Non-SAP System and vice-versa.
Introduction
If there is a requirement of transferring data from SAP system to another system (SAP or Non-SAP) or vice-versa, there should be an interface which does the job for us. If there is no standard interface available then we have to create a customized interface, which can be achieved in two ways. One is through RFC calls and the other is through Idoc’s. There is one disadvantage in proceeding with RFC calls, that is we cannot keep track of the processed data and if an error occurs while transferring data we have to define an alternative way of transferring it again. But when we proceed with Idoc’s there is a track of all the data that we are sending and we can also know which data is processed and which data is not processed.

  1. Scenario between the XML and BAAN file format and Interfacing
    Managing Data between XML and BAAN text file format
  2. Mapping an IDOC Schema to an Industry Standard XML Schema
    Mapping an IDOC Schema to XML schema