SAP Training, Tutorials, Certification and Jobs Materials
HOME TUTORIALS ARTICLES PROJECTS JOBS TOOLS REFERENCES CHAT FORUM GUESTS

Related 10 BAPITutorials
BAPI_AP_ACC_GETCURRENTBALANCE ( BAPI Function Module )
BAPI_VENDOR_DELETEPASSWORD ( BAPI Function Module )
BAPI_ACC_PURCHASE_ORDER_POST ( BAPI Function Module )
BAPI_CASHJOURNALDOC_CREATE ( BAPI function module )
BAPI_USER_CREATE | BAPI Function Module
BAPI_ECMORD_GET_LONGTEXT ( BAPI function Module )
BAPI_AP_ACC_GETOPENITEMS ( BAPI Function Module )
BAPI_BUSPARTNEREMPLOYE_GETLIST ( BAPI Function Module )
BAPI_ECMORD_SET_OBJADM ( BAPI Function Module )
BAPI_DOCUMENT_CREATENEWVERSION ( BAPI Function Module)

  BAPI Programming and Conventions

A D V E R T I S E M E N T
home--> Advanced ABAP --> BAPI
BAPI Programming and Conventions introduction tutorial
Programming a BAPI consists of two major tasks: 1. Defining BAPI Data structures in SE11 2. Program a RFC enabled BAPI function module for each method 3. Create a Business object for the BAPI in the BOR 4. Documentation the BAPI 5. Generate ALE interface for aynchronous BAPIs 6. Generate and release
Methods
Parameters
Standardized BAPIs
Standardized Parameters
Important things to remember..
BAPI/ALE Integration

Methods

  • If the BAPI to be implemented is a standardized BAPI, use the generic names, for example, GetList, GetDetail.
  • The method name must be in English (maximum 30 characters).
  • The individual components of a BAPI name are separated by the use of upper and lower case.Example: GetList
    Underscores ("_") are not allowed in BAPI names.
  • Each BAPI has a return parameter that is either an export parameter or an export table.
  • So that customers can enhance BAPIs, each BAPI must have an ExtensionIn and an ExtensionOut parameter.

Parameters

  • If standardized parameters are used, you have to use the names specified for standardized parameters.
  • BAPI parameter names should be as meaningful as possible. Poorly chosen names include abbreviations and technical names (e.g. "flag", table names, etc.).
    The parameter and field names must be in English with a maximum of 30 characters.
  • The components of a parameter name in the BOR are separated by upper and lower case letters to make them easier to read. Example: CompanyCodeDetail
  • Values that belong to each other semantically should be grouped together in one structured parameter, instead of using several scalar parameters.
  • For ISO-relevant fields (country, language, unit of measure, currency), additional fields for ISO codes are provided.
  • Unit of measure fields must accompany all quantity fields and currency identifiers must accompany currency amount fields.

 

Standardized BAPIs

Some BAPIs provide basic functions and can be used for most SAP business object types. These BAPIs should be implemented the same for all business object types. Standardized BAPIs are easier to use and prevent users having to deal with a number of different BAPIs. Whenever possible, a standardized BAPI must be used in preference to an individual BAPI.

The following standardized BAPIs are provided:

Reading instances of SAP business objects

GetList ( ) With the BAPI GetList you can select a range of object key values, for example, company codes and material numbers.
The BAPI GetList() is a class method.
GetDetail() With the BAPI GetDetail() the details of an instance of a business object type are retrieved and returned to the calling program. The instance is identified via its key. The BAPI GetDetail() is an instance method.

BAPIs that can create, change or delete instances of a business object type

The following BAPIs of the same object type have to be programmed so that they can be called several times within one transaction. For example, if, after sales order 1 has been created, a second sales order 2 is created in the same transaction, the second BAPI call must not affect the consistency of the sales order 2. After completing the transaction with a COMMIT WORK, both the orders are saved consistently in the database.

 

Create( ) and
CreateFromData( )
The BAPIs Create() and CreateFromData() create an instance of an SAP business object type, for example, a purchase order. These BAPIs are class methods.
Change( ) The BAPI Change() changes an existing instance of an SAP business object type, for example, a purchase order. The BAPI Change () is an instance method.
Delete( ) and Undelete( ) The BAPI Delete() deletes an instance of an SAP business object type from the database or sets a deletion flag.
The BAPI Undelete() removes a deletion flag. These BAPIs are instance methods.
Cancel ( ) Unlike the BAPI Delete(), the BAPI Cancel() cancels an instance of a business object type. The instance to be cancelled remains in the database and an additional instance is created and this is the one that is actually canceled. The Cancel() BAPI is an instance method.
Add ( ) and Remove ( ) The BAPI Add adds a subobject to an existing object instance and the BAPI and Remove removes a subobject from an object instance. These BAPIs are instance methods.

 

BAPIs for Mass Data Processing

The BAPIs listed above for creating and changing data can also be used for mass processing. For more information see BAPIs for Mass Data Transfer [Extern]

BAPIs for Replicating Business Object Instances

Replicate( ) and SaveReplica( ) The BAPIs Replicate() and SaveReplica() are implemented as methods of replicable business object types. They enable specific instances of an object type to be copied to one or more different systems. These BAPIs are used mainly to transfer data between distributed systems within the context of Application Link Enabling (ALE). These BAPIs are class methods.

Other Less Used Standardized BAPIs

  • Programming GetStatus() BAPIs [Extern]
  • Programming ExistenceCheck() BAPIs [Extern]

 

Standardized Parameters

There are some parameters that can be created for various BAPIs because they contain the same or the equivalent data in all BAPIs. They should be implemented the same in all BAPIs.

 

Address parameters Specific reference structures are defined for address parameters in BAPIs. You should copy these structures to use in your BAPI, especially if the underlying object type uses the central address management (CAM).
Change Parameters In BAPIs that cause database changes (for example, Change() and Create() BAPIs) you must be able to distinguish between parameter fields that contain modified values and parameter fields that have not been modified. This distinction is made through the use of standardized parameters.
Extension parameters The parameters ExtensionIn and ExtensionOut provides customers with a mechanism that enables BAPIs to be enhanced without modifications.
Return Parameters Each BAPI must have an export return parameter for returning messages to the calling application. To provide application programmers with a consistent error handling process for BAPI calls, all return parameters must be implemented in the same, standardized way.
Selection Parameters Standardized selection parameters are used in BAPIs that can be used to search for specific instances of a business object type (e.g. in GetList() ). These parameters enable the BAPI caller to specify the relevant selection criteria.
Test Run Parameters The parameter TestRun is used in write BAPIs (Create() and Change() ), to check the entries for the object instance in the database before actually creating the object instance. The creation of the object instance is only simulated and data is not updated.
Text Transfer Parameters To transfer BAPI documentation texts (e.g. the documentation of a business object type), you have to create standardized text transfer parameters.

 

Important things to remember..

It is important to follow the guidelines below when develop9ng BAPIs:

  • BAPIs must not contain CALL TRANSACTIO or SUBMIT REPORT
  • BAPIs must not invoke a COMMIT WORK. instead use the BAPI TransactionCommit to execute the commit after the BAPI has executed.
  • BAPI structures must not use includes.
  • There should be no functional dependecies between two BAPIs
  • BAPIs must perform there own authorization check
  • BAPIs should not use dialogs
  • BAPIs must not cause the program to abort or terminate. re4levant messages must be communicated through the return parameter.

BAPI/ALE Integration

When you use the BAPIs for asynchronous messagning, the application in the sendig systen calls the generated ALE IDoc interface isntead of the BAPI.

Asynchronous BAPIs use the ALE interface this way:

  • Creates an IDOC from the BAPI data
  • Sends the IDOC to the target system
  • Receives the IDOC in trhe target system, crreates the BAPI data from the IDoc and calls the BAPI

An ALE interface for a BAPi is created in transaction BDBG.


Email this Tutorial to my friend
Your Mail ID :
Friend mail ID:
Also send to me

Latest Added Tutorials

SAP PRE-SALE(very urgent requirement) - SAP JOBS INDIA
SAP PRE-SALE(very urgent requirement) - SAP JOBS INDIA
Experiense Required for this job: 6-9 years exp
Job Locations: Mumbai
Apply for this SAP Job in INDIA
SAP ABAP Professionals - SAP JOBS INDIA
SAP ABAP Professionals - SAP JOBS INDIA
Experiense Required for this job: 5 - 7 years exp
Job Locations: Bengaluru / Bangalore, Chennai, Others
Apply for this SAP Job in INDIA
Junior SAP Consultants - SAP JOBS INDIA
Junior SAP Consultants - SAP JOBS INDIA
Experiense Required for this job: 0-5 years exp
Job Locations: Bengaluru/Bangalore
Apply for this SAP Job in INDIA
SAP Plant Maintanence with ETM module - SAP JOBS INDIA
SAP Plant Maintanence with ETM module - SAP JOBS INDIA
Experiense Required for this job: 2-7 years exp
Job Locations: Pune
Apply for this SAP Job in INDIA
SAP Plant Maintainence /PM Consultant/Sr.consultant/TL - SAP JOBS INDIA
SAP Plant Maintainence /PM Consultant/Sr.consultant/TL - SAP JOBS INDIA
Experiense Required for this job: 3-8 years exp
Job Locations: Gurgaon, Kolkata
Apply for this SAP Job in INDIA
Immediate position for SAP ABAP Professionals. - SAP JOBS INDIA
Immediate position for SAP ABAP Professionals. - SAP JOBS INDIA
Experiense Required for this job: 5-9 years exp
Job Locations: Bengaluru/Bangalore, Chennai, Gurgaon
Apply for this SAP Job in INDIA
SAP - IS Retail (SRS) Consultant - SAP JOBS INDIA
SAP - IS Retail (SRS) Consultant - SAP JOBS INDIA
Experiense Required for this job: 5-8 years exp
Job Locations: Bengaluru/Bangalore
Apply for this SAP Job in INDIA
SAP BPC/EPM - SAP JOBS INDIA
SAP BPC/EPM - SAP JOBS INDIA
Experiense Required for this job: 4-9 years exp
Job Locations: Bengaluru/Bangalore, Hyderabad / Secunderabad, Pune
Apply for this SAP Job in INDIA
LOOKING FOR TECHNICAL AND FUNCTIONAL LEADS AND MANAGERS(SAP) - SAP JOBS INDIA
LOOKING FOR TECHNICAL AND FUNCTIONAL LEADS AND MANAGERS(SAP) - SAP JOBS INDIA
Experiense Required for this job: 3-8 years exp
Job Locations: Bengaluru/Bangalore, Chennai
Apply for this SAP Job in INDIA
SAP FICO Consultant - SAP JOBS INDIA
SAP FICO Consultant - SAP JOBS INDIA
Experiense Required for this job: 5-10 years exp
Job Locations: Hyderabad / Secunderabad
Apply for this SAP Job in INDIA

Most readed 5 Tutorials

List of SAP MM Transaction codes
This documentation covers the details of SAP MM Transaction codes
WRITE - Output to a list ( SAP ABAP Keyword)
WRITE ( Output to a list ) is a keyword used in SAP ABAP programming.This tutorial covers its introduction & syntax details.
FI Accounts Receivable and Accounts Payable | SAP FI PDF manual
The following topics are an introduction to the Accounts Receivable and Accounts Payable application components.
List of SAP HR TABLES and Infotypes tables
Detailed full list of tables and infotypes used in SAP HR module.
Report Programming in HR | SAP PDF study material )
This document is intended for all persons who would like to program their own reports in SAP HR or customize standard ones. The documentation is not intended to be an introduction to programming. It contains just the special features that form part of programming in SAP HR.A general knowledge of ABAP programming and HR applications is a prerequisite. This can be acquired by reading the relevant documentation and attending the courses.This document provides information which enables programmers to become acquainted with the special features of programming in HR.
  

CATEGORIES

  ABAP
  Advanced ABAP
  SAP JOBS
  SAP Functional Modules
  SAP R/3
  SAP NetWeaver
   
SAP Technical PDF Tutorials

ABAP
DICTIONARY
INTERNAL TABLES
ALV Reports
SAPSCRIPTS
SMARTFORMS
LSMW
BDC
ALE
IDOC
USER EXITS
TRANSPORTING
ITS


SAP Functional PDF  Tutorials

FI (Financial)
CO (Controlling)
HR (Human Resource)
LO (Logistics)
MM (Materials Management)
PP (Production Planning)
QM (Quality Management)
SD (Sales and Distribution)
TR (Treasury and cash)
WM (Warehouse Management)
PS (project Systems)
PM (plant Maintenance)
CA (Cross Application)


SAP References

transaction codes
System Fields
Function Modules
SAP TABLES
code optimization


TOOLS

SQL Trace tool
Runtime Analysis
LSMW
ABAP Query
CTS


SAP Emerging Technologies

SAP Advanced Planner and Optimizer (APO)
SAP Business Information Warehouse
(BW)

SAP Business Intelligence
(BI)

SAP Customer Relationship Management
(CRM)
SAP Enterprise Portal (EP)
SAP Exchange Infrastructure
(XI)

Human Resource Management Systems
(HRMS)
SAP Manufacturing
SAP Master Data Management
(MDM)

SAP Knowledge Warehouse
(KW)

SAP Product Lifecycle Management
(PLM)

SAP Service and Asset Management

SAP Strategic Enterprise Management
(SEM)

SAP Solutions for mobile business

SAP Solution Manager

SAP Training and Event Management
(TEM)
SAP Web Application Server
(Web AS)
SAP xApps



Jobs in Kerala

 
Custom Search
  site contact sapbrain.support@gmail.com All of the product names here are trademarks of their respective companies. The site www.sapbrainsonline.com no way affiliated with SAP AG. Use information on this site at your own risk. Information furnished in the site is collected from various sites and posts from users. This site does not host any files on its server. If any compliants about the posts please contact us at sapbrain.support@gmail.com, we are ready to move the posts.
Complete SAP Study materials | SAP JOBS | PDF Tutorials web counter