BAPI

(Business Application Programming

Interface)
 Business Application Programming
Interfaces (BAPI's)
• BAPI – Scenario

• BAPI – Introduction and Definition

• SAP- Business Objects and Business Object Repository

(BOR)

• BAPI – Use and Advantages

• BAPI – Methods

• BAPI – Development Process Flow

1.Transaction Model for BAPI Implementation
● Defining and Implementing BAPI's
● Creating Individual Programming Objects
● Programming , Testing , Releasing , Documenting and Freezing
BAPI's

1. Peformance improvement and Enhancements for BAPI's

 BAPI SCENARIO
Allows External Applications to Communicate with
SAP- R/3.
Examples :
1) Distributed R/3 Scenario using Application Linking and
Enabling (ALE).

2) Visual Basic Programs as Front ends for SAP – R/3.

3) Work Flow Applicatons that Extend System Boundries

4) Connections to Non SAP Applications/ Legacy Systems

5) Connecting R/3 Systems to Internet using Interent

Application Components.

6) R/3 Satellite Systems

BAPI – Introduction and Definition

A Business Application Programming Interface(

BAPI) is a precisely defined Interface providing
access to processes and data in Business
application such as R/3.

BAPI is method of SAP – Business Object

Structure
BAPI in R/3 Implemented as Function Modules. Each function
module underlying a BAPI :
 Support RFC
 Must be Method of Business Object
 No Dialog Screen Involved
 SAP- Business Object
Repostiory
 Business Object Repository is the Object Oriented
repository in R/3 System , it contains among other objects.
SAP Business Object and Their Methods.
 In Business Object Repository BAPI is defined as the
method of Business Object which is remoted enabled.

KERNAL
(DATA)

INTEGRITY ( BIZ. RULES)

INTERFACE (BAPI)

ACCESS(COM, DCOM, JAVA)

SAP Business Object Architecture

SAP- BUSINESS OBJECTS
 BAPI – Use and Advantages
 Use
– To Use BAPI Method , just knowledge of how to call the
method
 Import Parameters

 Export Parameters

 Table Parameters

 Advantages
 Business Standard
 Standards Conformance
 Stability and Downward Compatibility
 Object Orientation
 Openness
 BAPI -Methods
 Read Only Method
– GetList
– GetDetail
– GetStatus
– ExistenceCheck
 Data Change Methods
– Create/CreateFromData
– Change
– Delete
 Replication Methods
– Replicate
– Clone/CloneMulitple
 BAPI – Development
Process
 Transaction Model for BAPI Implementation
– SAP -3.0 Implicit COMMIT WORK for Data Modifying
BAPI.
– SAP4.X Use of BAPI_TRANSACTION_COMMIT.
 BAPI Transactions - LUW and Statelessness
– Initial State Each Time BAPI Called
– No Functional Dependencies
– All or Nothing Principle
– No Exception Parameters, BAPI used RETURN
structure.
 SAP- Function Module
Implementation – Keys

 Constraint on Function Module as Method of Busines

Object
– Should be Remote Enabled.
– No COMMIT WORK Statement.
– No Changing Parameters, All parameters passed
by Value including Table Types.
– No Exception Parameters, BAPI used RETURN
structure.
 SAP – Implementation Details
 BAPI – Implementation Guidelines
– BAPI should return RETURN structure
– Parameters defined for BAPI method should be
declared as Dictionary Object
 Example

– COMPANYCODE BAPI1008-COMP-CODE
• 1008 – Function Group Name
– Business Object method naming convention
 Example

– BAPI_CREDITOR_GETDETAIL
– BAPI_SALESORDER_GETSTATUS
 BAPI- References

 http://www.sappoint.com/abap
 http://help.sap.com/saphelp_46c/helpda
ta/en/a5/3ec8534ac011d1894e0000e82
9fbbd/content.htm