Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
Showing results for 
Search instead for 
Did you mean: 

BAPI implementation

Former Member
0 Kudos


How to implement a BAPI in our own development?

Thanks & Regards



Former Member
0 Kudos


In BAPI explorer, Customer BAPI, cannot be viewed directly.

To display all BAPIs, including your own BAPIs starting with Y or Z, change the settings by choosing Goto -> Set release filter.

Use transaction BAPI, and then Click F5 Key and Select All Radio button.

BAPI-step by step

list of all bapis

for BAPI's

Also refer to the following links..

Checkout !!,289142,sid21_gci948835,00.html


u can check the below the material also

what is BAPI?

BAPI stands for Business API(Application Program Interface).

A BAPI is remotely enabled function module ie it can be invoked from remote programs like standalone JAVA

programs, web interface etc..

You can make your function module remotely enabled in attributes of Function module but

A BAPI are standard SAP function modules provided by SAP for remote access. Also they are part of Businees

Objest Repository(BOR).

BAPI are RFC enabled function modules. the difference between RFc and BAPI are business objects. You create

business objects and those are then registered in your BOR (Business Object Repository) which can be accessed

outside the SAP system by using some other applications (Non-SAP) such as VB or JAVA. in this case u only

specify the business object and its method from external system in BAPI there is no direct system call. while RFC

are direct system call 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<subobject> ( ) and Remove<subobject> ( ) The BAPI Add<subobject> adds a subobject to an existing object

inst! ance and the BAPI and Remove<subobject> removes a subobject from an object instance. These BAPIs are

instance methods.

Example Code

U need to give the step_nr, item_nr, cond_count and cond_type so the correct conditon will be updated. If no

condition exists for the given parameters, a new condition will be created.

U can find these parameters for a particular condition type in table KONV.


*& Form saveTransactionJOCR


  • text


  • --> p1 text

  • <-- p2 text


FORM saveTransactionJOCR .

data: salesdocument like BAPIVBELN-VBELN,

order_header_inx like bapisdh1x,

order_header_in like bapisdh1,

return type standard table of bapiret2 with header line,

conditions_in type standard table of bapicond with header line,

conditions_inx type standard table of bapicondx with header line,

logic_switch like BAPISDLS,

step_nr like conditions_in-cond_st_no,

item_nr like conditions_in-itm_number,

cond_count like conditions_in-cond_count,

cond_type like conditions_in-cond_type.

salesdocument = wa_order_information-VBELN.


order_header_inx-updateflag = 'U'.

  • conditions

clear conditions_in[].

clear conditions_inx[].

clear: step_nr,




step_nr = '710'.

item_nr = '000000'.

cond_count = '01'.

cond_type = 'ZCP2'.


conditions_in-cond_st_no = step_nr.





append conditions_in.


conditions_inx-cond_st_no = step_nr.






append conditions_inx.



SALESDOCUMENT = salesdocument

ORDER_HEADER_IN = order_header_in

ORDER_HEADER_INX = order_header_inx

LOGIC_SWITCH = logic_switch


RETURN = return

CONDITIONS_IN = conditions_in

CONDITIONS_INX = conditions_inx


if return-type ne 'E'.

commit work and wait.


ENDFORM. " saveTransactionJOCR

Bdc to Bapi

The steps to be followed are :

1. Find out the relevant BAPI (BAPI_SALESORDER_CHANGE for VA02).


2. Create a Z program and call the BAPi (same as a Funtion module call).

2. Now, if you see this BAPi, it has

-> Importing structures.

eg: SALESDOCUMENT: this will take the Sales order header data as input.

-> Tables parameters:

eg: ORDER_ITEM_IN: this will take the line item data as input.

Note :

Only specify fields that should be changed

Select these fields by entering an X in the checkboxes

Enter a U in the UPDATEFLAG field

Always specify key fields when changing the data, including in the checkboxes

The configuration is an exception here. If this needs to be changed, you need to complete it again fully.

Maintain quantities and dates in the schedule line data


U = change

D = delete

I = add


1. Delete the whole order

2. Delete order items

3. Change the order

4. Change the configuration


1. Minimum entry:

You must enter the order number in the SALESDOCUMENT structure.

You must always enter key fields for changes.

You must always specify the update indicator in the ORDER_HEADER_INX.

2. Commit control:

The BAPI does not run a database Commit, which means that the application must trigger the Commit so that the

changes are read to the database. To do this, use the BAPI_TRANSACTION_COMMIT BAPI.

For further details... refer to the Function Module documentation for the BAPi.

Bapi to VB(Visual Basic)

Long back I had used the following flow structure to acheive the same.

Report -> SM59 RFC destination -> COM4ABAP -> VB.exe

my report uses the rfc destination to create a COM session with com4abap. com4abap calls the vb.exe and

manages the flow of data between sap and vb exe.

You need to have com4abap.exe

If com4abap is installed you will find it in sapgui installatin directory , C:\Program


else refer OSS note 419822 for installation of com4abap

after making the settings in com4abap to point to the vb program and setting up rfc destination in sm59 to point to

com4abap session , you can use the following function modules to call the vb code.

for setting up com4abap and rfc destination please refer to the documentation for com4abap.

  • Invoke NEW DCOM session

call function 'BEGIN_COM_SESSION'


service_dest = service_dest "(this will be a RFC destination created in SM59)


worker_dest = worker_dest


connect_to_dcom_service_failed = 1

connect_to_dcom_worker_failed = 2

others = 3.

call function 'create_com_instance' destination worker_dest


clsid = g_c_clsid

typelib = g_c_typelib


instid = g_f_oid


communication_failure = 1 message g_f_msg

system_failure = 2 message g_f_msg

invalid_instance_id = 3

others = 4.

call function 'com_invoke' destination worker_dest


%instid = g_f_oid

%method = 'UpdatePDF'

sntemp = g_v_const_filent

snsysid = sy-sysid

snflag = 'N'


rssaptable = g_t_pdfdetail1

%return = g_t_pdfdetail1 "t_test


communication_failure = 1 message g_f_msg

system_failure = 2 message g_f_msg

invalid_instance_id = 3

others = 4.

then close the com session , using

FM delete_com_instance




Former Member
0 Kudos


It is as good as implementing Function Module.

Go to SE38 , Create a report, Click on Pattern, write BAPI name there, say e.g:

BAPI_MATERIAL_DISPLAY To display material like MM03.

Give appropriate parameters to BAPI and Execute the program.

Reward if useful!

Former Member
0 Kudos

Determining Details of BAPIs


To use a BAPI, you have to determine the information you have to forward to call the BAPI or function in your application program.


You can find this information in the BAPI Explorer or in the BAPI Browser.

The BAPI Explorer is available as of Release 4.6A and replaces the BAPI Browser used in earlier releases. The BAPI Explorer uses up-to-date HTML control technology which requires SAPgui version 4.6A.

If you are using a SAPgui from an earlier release, the BAPI Browser is displayed instead of the BAPI Explorer.

Details of BAPIs of Business Object Types

The following information is required to use BAPIs of SAP business object types:

The import, export and import/export parameters of the BAPI

Standardized parameters supply the same or equivalent data and can therefore be used in different BAPIs. These parameters have the same name in all BAPIs and are implemented using the same guidelines. For further information see Standardized Parameters.

They key fields of the SAP business object type

The key fields of SAP business object types specify the identification structure with which client programs can uniquely access a specific instance of the object type. The key fields are required if the BAPI is using specific instances of an object type. BAPIs are divided into these categories:

- Instance-dependent BAPIs

Instance-dependent BAPIs use specific instances of an object type which the client application must specify in the key fields of the business object. An example of an instance-dependent BAPI is CompanyCode.GetDetail() and when used the client application must specify the company code ID, for example, GetSAPObject("CompanyCode","0001").

- Instance-independent BAPIs

Instance-independent BAPIs do not use specific instances of an object type. They usually return a list of object type instances in tables to the calling program. Instance-independent BAPIs are also called class methods. The BAPI CompanyCode.GetList(), which returns a list of company codes, is an example of an instance-independent BAPI.

Some instance-independent BAPIs generate object instances and report back information on the generated object instance to the calling application. An example of this type of BAPI is SalesOrder.CreateFromData(), which creates a customer order and reports back information to the calling program.

· The documentation on the business object type, the key fields, the BAPI and its parameters.

· The name of the function module, if the RFC calls are sent to the function module underlying the BAPI.

Once you have retrieved all the required information, you can use the BAPI in your application program.

Details of BAPIs of Interface Types

The following information is required to use BAPIs of SAP business object types:

The import, export and import/export parameters of the BAPI

The name of the function module that is to implement the interface

The documentation on the BAPI and its parameters.

Once you have retrieved all the necessary information, you can implement the interface and use the BAPI in your application program.

Process Flow

From the initial R/3 screen, choose Tools ® Business Framework ® BAPI Explorer or enter the transaction code BAPI in the SAPgui command field.

If you are using a SAPgui of Release 4.6A or later, the BAPI Explorer will be displayed. For more information about using the BAPI Explorer see BAPI Explorer.

If you are using a SAPgui in a release earlier than 4.6A, the BAPI Browser appears instead of the BAPI Explorer. For further information see BAPI Browser.

rewrads point if helpful...


Former Member
0 Kudos

Hi Santhosh,

<b> There are 5 different steps in BAPI.</b> - Create BAPI Structure

- <b>Create BAPI Function Module or API Method.</b>

- <b>Create BAPI object</b> -

-<b> Release BAPI Function Module</b>.

- <b>Release BAPI object.</b>

Step1. Creating BAPI Structure:

- Go to <SE11>.

- Select Data Type & Enter a name.

- Click on Create.

- Note: Always BAPI should be in a development class with request number (Not Local Object).

- Select Structure & hit ENTER.

- Enter the fields from your database. Make sure that the first field is the Primary Key Field.


Step 2. Creating BAPI module:

- Enter TR.CODE <SE37>.

- Before entering any thing, from the present screen that you are in, select the menu

Goto -> Function Groups -> Create Group.

Enter a name (Note: This name Must start with ZBAPI)

Let this screen be as it is and open another window and there, enter TR.CODE <SE80).

Click on the Third ICON that says Inactive Objects.

Select the group that you just created and click on Activate.

Notice that the group you created will disappear from the list of inactive objects.

- Go back to ><SE37> screen and enter a name and hit <ENTER>. Then enter the group name that you just created and activated.

NOTE: When you release a function module the respective group will be attached to that particular application. It cannot be used for any other application. NEVER include an already existing group that is attached to another module.

Now click on the first Tab that says [ATTRIBUTES] and select the radio button that says remote-enabled module since we will be accessing this from any external system.

Then click on the second tab that says [IMPORT].

Enter a PARAMETER NAME, TYPE and the structure you created in the first step. Also select the check box ‘Pa’. All remotely enabled functional modules MUST be Pa enabled, where Pa means ‘Passed by Value’ and if you don’t select ‘Pa’, then that means it will be passed by reference..

Then click on tab that says [EXPORT].

Enter the following as is in the first three fields

RETURN TYPE BAPIRETURN (These 3 field values are always same)

Here also select ‘Pa’ meaning Pass by value.

Note: BAPIRETURN contains structure with message fields.


Step 3. Creating BAPI object:

- Enter Tr.Code <SWO1> (Note. It is letter ‘O’ and not Zero).

- Enter a name and then click on create. Enter details.

NOTE: Make sure that that Object Type and Program name are SAME.

- Enter Application ‘M’, if you are using standard table Mara. If you are using your own database then select ‘Z’ at the bottom.

- Then hit <ENTER>.

- Now we have to add ‘Methods’. High light METHODS and then select the following from the menu:

Goto Utilities -> API Methods -> Add Methods.

- Enter function Module name and hit <ENTER>.

- Select the second FORWARD ARROW button (>)to go to next step.

- Check if every thing looks ok and again click on FORWARD ARROW button (>).

- Then select ‘YES’ and click on <SAVE>.

- Now on a different screen goto TR.CODE <SE37>. Enter Function Module name and select from the top menu Function Module -> Release -> Release.

- Goback to TR.CODE <SWO1>.

Here select the menu combination shown below in the same order.

- Edit -> Change Release Status -> Object Type Component -> To Implemented.

- Edit -> Change Release Status -> Object Type Component -> To Released.

- Edit -> Change Release Status -> Object Type -> To Implemented.

- Edit -> Change Release Status -> Object Type -> To Released.

- Then click on <SAVE>.

- Then click on Generate Button (4th button from left hand side looks like spinning wheel).

- Then Click on the button that says ‘PROGRAM’ to see the source code.

To check if this is present in work flow goto TR.CODE <BAPI>.

Here it shows business object repository.

- First click on the middle button and then select “ALL” and hit ENTER.

- Goto tab [ALPHABETICAL] and look for the object that you created. This shows that the BAPI object has been created successfully

<b>Reward pts if found usefull :)</b>