Explore topic-wise InterviewSolutions in .

Stage1: CREATING a STRUCTURE in SE11

Stage2: Creating the function module in SE37

Stage 3: Creating the BUSINESS OBJECT in SWO1

Stage 4: Viewing the created BAPI in BAPI Explorer

Stage1: Creating a structure in SE11

Stage2: Creating the function module in SE37

Stage 3: Creating the business object in SWO1

Stage 4: Viewing the created BAPI in BAPI Explorer

BAPI:

• BAPI is faster than BDC.
• BAPI directly UPDATES database.
• BAPI would generally used for small data uploads.
• For PROCESSING errors, the Return PARAMETERS for BAPI should be used.This parameter returns exception messages or success messages to the calling program.

BDC:

• BDC goes through all the screens as a normal user would do and hence it is slower.
• Background and Foreground processing options are available for BDC.
• BDCS would be preferred for large volumes of data upload since background processing OPTION is available.
• Errors can be processed in SM35 for session method and in the batch input program for Call Transaction method.

BAPI:

BDC:

BAPI :

• BAPI is a library of function modules released by SAP to the PUBLIC so that they can interface with SAP.
• There is a Business Object Associated with a BAPI. So a BAPI has an Interface, Key Field, Attributes, Methods, and Events.
• Outside world (JAVA, VB, .Net or any Non SAP system) can connect to SAP using a BAPI.
• ERROR or Success messages are returned in a RETURN table.

RFC:

• RFC is nothing but a remote enabled function module. So if there is a Function Module in SAP system 1 on server X , it can be called from a SAP system 2 residing on server Y.
• No Business Object is associated with a RFC.
• Non–SAP world cannot connect to SAP using RFC.
• RFC does not have a return table.

BAPI :

RFC:

• The Business Object Repository (BOR) is the central access point for the SAP business object types and their BAPIs. The BOR contains all the RELEVANT information on the SAP business object types, their key fields, and their BAPI methods that are needed to integrate the correct object type definitions and BAPI calls in an application program. This makes the integration of middleware (such as the DCOM Connector, ActiveX Controls, CORBA Gateway, and so on) possible.
• Creates instances of SAP business OBJECTS. The RUNTIME environment of the BOR receives requests to create runtime objects from CLIENT applications and creates the APPROPRIATE object instances.

• A TRANSACTION is COMPLETED either using a COMMIT WORK command or a ROLLBACK command. A BAPI transaction must be ended by calling the BAPIs BapiService.TransactionCommit() or BapiService.TransactionRollback().
• The CALL of a BAPI must not trigger further LUWs that are independent of the BAPI.

For this reason BAPIs must not contain the following COMMANDS:

• CALL TRANSACTION
• SUBMIT REPORT
• SUBMIT REPORT AND RETURN

For this reason BAPIs must not contain the following commands:

BAPIs are defined as API methods of SAP BUSINESS Object TYPES. These object types are used within the Business FRAMEWORK to enable object-based communication between components. Business objects and their BAPIs enable object ORIENTATION to be used in central information processing in companies.

BAPIs are defined as API methods of SAP Business Object Types. These object types are used within the Business Framework to enable object-based communication between components. Business objects and their BAPIs enable object orientation to be used in central information processing in companies.

• A business object type, which represents of a business entity in the SAP R/3 System, encompasses both the functionality (in the form of methods) and the data (in the form of attributes) of this entity. The implementation details of the business object type are hidden from the user. The business object type is accessed through defined functions (methods). This is REFERRED to as encapsulation.
• Business object types form the point of entry to the data and the functionality of the SAP R/3 System. At the business object type level, both non-SAP systems and the various SAP business components can communicate with each other.
• The business object type Sales Order represents a customer’s request to the COMPANY to supply a PARTICULAR quantity of MATERIAL at a certain point in time or to perform services at a certain point in time. A specific sales order is identified by a sales document number. The business object type contains all the necessary information for a sales order: sold-to party, sales organization, document date, net value of the order, and currency of the sales and distribution document.

• Business Components:SAP Business Components provide autonomous business functions and consist of business objects. For example, the business objects Employee and Applicant are assigned to the Business COMPONENT Human Resources. Business processes are either implemented within a Business Component or across several Components (DISTRIBUTED business processes).
• Business Objects:The object-oriented structure of the R/3 System is based on Business Objects. They encapsulate business data and functionality and define the functional scope and boundaries of a Business Component.
• Business Application Programming INTERFACES (BAPI):BAPIs are interfaces for Business Objects. Together with the Business Objects, BAPIs define and document the interface standard at the business level.
• Integration Service, Application Link Enabling (ALE):The ALE Integration Service enables the integration of business processes that are carried out in different R/3 and non-SAP systems. This service is based on the system-wide distribution of Business Objects using the ALE distribution model.
• COMMUNICATION SERVICES:These are the communication technologies, for example, Distributed Component Object Model (DCOM) and Remote Function Call (RFC) that use the Business Framework to access BAPIs.

The return parameter RETURN CONTAINS success or error MESSAGES for the BAPI, and depending on the SAP R/3 Release has the DICTIONARY STRUCTURE BAPIRETURN, BAPIRETURN1, BAPIRET1, BAPIRET2.

The return parameter RETURN contains success or error messages for the BAPI, and depending on the SAP R/3 Release has the dictionary structure BAPIRETURN, BAPIRETURN1, BAPIRET1, BAPIRET2.

• Allows an OBJECT-oriented view of all data and processes in an SAP System.
• Arranging the various business object types ACCORDING to the component hierarchy.
• It ensures BAPI interface stability.
• It manages BAPIs in release updates.
• It CREATES instances of SAP business objects.

The Business Object Repository (BOR) is root access POINT for the SAP business object TYPES and their BAPIs. The BOR was DEVELOPED for SAP Business Workflow.

The Business Object Repository (BOR) is root access point for the SAP business object types and their BAPIs. The BOR was developed for SAP Business Workflow.

We can reduce the COMPLEXITY of SYSTEMS STRUCTURE by dividing the complex structures into smaller UNITS.

We can reduce the complexity of Systems structure by dividing the complex structures into smaller units.

A business object type is the representation of a business object, like an human work force or a INVOICE, in an SAP SYSTEM. It encompasses both the functions and the DATA into single object.

A business object type is the representation of a business object, like an human work force or a Invoice, in an SAP System. It encompasses both the functions and the data into single object.

• SUPPORT of SYNCHRONOUS and asynchronous communication.
• Support of machine-to-machine and human-to-machine communication.
• Communication support for COMPONENTS that are narrowly linked and coupled through the INTERNET.

• Converting all parameter data to the representation needed in the remote system
• CALLING the communication routines needed to talk to the remote system.
• Handling communications errors, and notifying the CALLER, if desired ( using EXCEPTIONS parameter of the CALL FUNCTION).
• Convert the data into the FORMAT understandable by the remote (target) system.
• Call up certain routines which are necessary to start communication with the remote system.
• HANDLE errors that might occur in the process of communication.
• RFC can handle errors itself.
• every BAPI is a RFc whereas every RFC is not a BAPI.
• RFC's are not registered in the BOR.

CALL FUNCTION...DESTINATION statement. The DESTINATION parameter tells the SAP SYSTEM that the called function RUNS in a system other than the callers.

CALL FUNCTION...DESTINATION statement. The DESTINATION parameter tells the SAP System that the called function runs in a system other than the callers.

• A CALLING INTERFACE for ABAP PROGRAMS
• A calling interface for Non-SAP programs.

• SYNCHRONOUS RFC
• TRANSACTIONAL RFC (TRFC)
• QUEUED RFC (qRFC)

BAPI:

BAPI is a RFC enabled function module and we CREATE business objects and registered in the BOR (Business Object Repository) which can be accessed outside the SAP system by using other applications (Non-SAP) LANGUAGES such as VB or JAVA. That time we only define the business object and its methods from external system.

RFC:

COMMUNICATION between applications of different systems in the SAP environment INCLUDING connections between SAP systems as well as between SAP systems and non-SAP systems. Remote Function Call (RFC) is the STANDARD SAP interface for communication between SAP systems. The RFC calls a function to be executed in a remote system.

BAPI:

BAPI is a RFC enabled function module and we create business objects and registered in the BOR (Business Object Repository) which can be accessed outside the SAP system by using other applications (Non-SAP) Languages such as VB or JAVA. That time we only define the business object and its methods from external system.

RFC:

Communication between applications of different systems in the SAP environment including connections between SAP systems as well as between SAP systems and non-SAP systems. Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. The RFC calls a function to be executed in a remote system.

USING BAPI,we can connect :

• NEW R/3 components.
• Non-SAP software.
• Legacy systems.
• ISOLATING components within the R/3 SYSTEM .
• Connecting R/3 Systems to the Internet.
• PC programs.
• Workflow applications.

Using BAPI,we can connect :

1. Creating a structure in SE11
2. Creating the FUNCTION MODULE in SE37
3. Creating the BUSINESS object in SWO1
4. Viewing the CREATED BAPI in BAPI Explorer
5. Test the BAPI.(BAPI tcode)

BAPI is a Business Application Programming which provides ACCESS to processes and data in business application systems such as R/3. BAPIs are defined as API methods of SAP business OBJECT TYPES. Business object types and their BAPIs are DESCRIBED and stored in the Business Object Repository (BOR). A BAPI is implemented as a function module, that is stored and described in the Function Builder.

BAPI is a Business Application Programming which provides access to processes and data in business application systems such as R/3. BAPIs are defined as API methods of SAP business object types. Business object types and their BAPIs are described and stored in the Business Object Repository (BOR). A BAPI is implemented as a function module, that is stored and described in the Function Builder.