BAPIs are functions?

Former Member · ‎2007 Aug 07

What are BAPIs?

CALL FUNCTION 'BAPI_BATCH_CREATE'

EXPORTING

MATERIAL = itab-matnr

BATCH = itab-charg

PLANT = itab-werks

BATCHATTRIBUTES = attr

BATCHCONTROLFIELDS = contr

BATCHSTORAGELOCATION = itab-lgort

INTERNALNUMBERCOM =
EXTENSION1 =
IMPORTING
BATCH =
BATCHATTRIBUTES =

TABLES

RETURN = ret2.

For example what does the above code do?

I do not know anything on this topic.

Former Member · ‎2007 Aug 07

Hi

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.

BAPI-step by step

http://www.sapgenie.com/abap/bapi/example.htm

just refer to the link below

http://www.sapmaterial.com/?gclid=CN322K28t4sCFQ-WbgodSGbK2g

list of all bapis

http://www.planetsap.com/LIST_ALL_BAPIs.htm

for BAPI's

http://www.sappoint.com/abap/bapiintro.pdf

http://www.sappoint.com/abap/bapiprg.pdf

http://www.sappoint.com/abap/bapiactx.pdf

http://www.sappoint.com/abap/bapilst.pdf

http://www.sappoint.com/abap/bapiexer.pdf

http://service.sap.com/ale

http://service.sap.com/bapi

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf

http://www.planetsap.com/Bapi_main_page.htm

http://www.topxml.com/sap/sap_idoc_xml.asp

http://www.sapdevelopment.co.uk/

http://www.sapdevelopment.co.uk/java/jco/bapi_jco.pdf

Also refer to the following links..

www.sap-img.com/bapi.htm

www.sap-img.com/abap/bapi-conventions.htm

www.planetsap.com/Bapi_main_page.htm

www.sapgenie.com/abap/bapi/index.htm

Checkout !!

http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html

http://techrepublic.com.com/5100-6329-1051160.html#

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.

LOGIC_SWITCH-COND_HANDL = 'X'.

order_header_inx-updateflag = 'U'.

conditions

clear conditions_in[].

clear conditions_inx[].

clear: step_nr,

item_nr,

cond_count,

cond_type.

step_nr = '710'.

item_nr = '000000'.

cond_count = '01'.

cond_type = 'ZCP2'.

CONDITIONS_IN-ITM_NUMBER = item_nr.

conditions_in-cond_st_no = step_nr.

CONDITIONS_IN-COND_COUNT = cond_count.

CONDITIONS_IN-COND_TYPE = cond_type.

CONDITIONS_IN-COND_VALUE = 666.

CONDITIONS_IN-CURRENCY = 'EUR'.

append conditions_in.

CONDITIONS_INX-ITM_NUMBER = item_nr.

conditions_inx-cond_st_no = step_nr.

CONDITIONS_INX-COND_COUNT = cond_count.

CONDITIONS_INX-COND_TYPE = cond_type.

CONDITIONS_INX-UPDATEFLAG = 'U'.

CONDITIONS_INX-COND_VALUE = 'X'.

CONDITIONS_INX-CURRENCY = 'X'.

append conditions_inx.

CALL FUNCTION 'BAPI_SALESORDER_CHANGE'

EXPORTING

SALESDOCUMENT = salesdocument

ORDER_HEADER_IN = order_header_in

ORDER_HEADER_INX = order_header_inx

LOGIC_SWITCH = logic_switch

TABLES

RETURN = return

CONDITIONS_IN = conditions_in

CONDITIONS_INX = conditions_inx

.

if return-type ne 'E'.

commit work and wait.

endif.

ENDFORM. " saveTransactionJOCR

Bdc to Bapi

The steps to be followed are :

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

[for VA01 use BAPI_SALESORDER_CREATEFROMDAT2]

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

Possible UPDATEFLAGS:

U = change

D = delete

I = add

Example

1. Delete the whole order

2. Delete order items

3. Change the order

4. Change the configuration

Notes

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 Files\SAPpc\sapgui\RFCSDK\com4abap.

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'

exporting

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

importing

worker_dest = worker_dest

exceptions

connect_to_dcom_service_failed = 1

connect_to_dcom_worker_failed = 2

others = 3.

call function 'create_com_instance' destination worker_dest

exporting

clsid = g_c_clsid

typelib = g_c_typelib

importing

instid = g_f_oid

exceptions

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

exporting

%instid = g_f_oid

%method = 'UpdatePDF'

sntemp = g_v_const_filent

snsysid = sy-sysid

snflag = 'N'

tables

rssaptable = g_t_pdfdetail1

%return = g_t_pdfdetail1 "t_test

exceptions

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

FM END_COM_SESSION

BAPI

http://help.sap.com/saphelp_nw2004s/helpdata/en/7e/5e114a4a1611d1894c0000e829fbbd/frameset.htm

http://www.sapgenie.com/abap/bapi/example.htm

http://help.sap.com/saphelp_46c/helpdata/en/9b/417f07ee2211d1ad14080009b0fb56/frameset.htm

http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html

http://techrepublic.com.com/5100-6329-1051160.html#

http://www.sap-img.com/bapi.htm

http://www.sap-img.com/abap/bapi-conventions.htm

http://www.sappoint.com/abap/bapiintro.pdf

http://www.sapgenie.com/abap/bapi/example.htm

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf

Reward points for useful Answers

Regards

Anji

Former Member · ‎2007 Aug 07

Here is a sample code for the use of this BAPI. Check if this helps -

----

Report ZTESTBAPI *
This is a dummy program designed to show how to create a batch and *
then apply/change characteristics via BAPI control. *

----

REPORT ztestbapi.

TABLES: klah, ksml, cabn.

holds data for charcateristics with type NUM

DATA: BEGIN OF numtab OCCURS 0.

INCLUDE STRUCTURE bapi1003_alloc_values_num.

DATA: END OF numtab.

holds data for charcateristics with type CHAR/DATE

DATA: BEGIN OF chatab OCCURS 0.

INCLUDE STRUCTURE bapi1003_alloc_values_char.

DATA: END OF chatab.

holds data for charcateristics with type CURR

DATA: BEGIN OF curtab OCCURS 0.

INCLUDE STRUCTURE bapi1003_alloc_values_curr.

DATA: END OF curtab.

Error return table

DATA: BEGIN OF rettab OCCURS 0.

INCLUDE STRUCTURE bapiret2.

DATA: END OF rettab.

DATA: BEGIN OF it_ksml OCCURS 0.

INCLUDE STRUCTURE ksml.

DATA: END OF it_ksml.

characteristic names

DATA: BEGIN OF it_cabn OCCURS 0,

atinn LIKE cabn-atinn,

atnam LIKE cabn-atnam,

atfor LIKE cabn-atfor,

END OF it_cabn.

DATA: BEGIN OF it_object OCCURS 0.

INCLUDE STRUCTURE bapi1003_object_keys.

DATA: END OF it_object.

example of an object key 00000000000730000007505847897897

DATA: w_object LIKE bapi1003_key-object.

Change these defaults to suit your system

PARAMETERS: p_matnr LIKE mara-matnr OBLIGATORY DEFAULT '7300000',

p_werks LIKE t001w-werks OBLIGATORY DEFAULT '0750',

p_charg LIKE mcha-charg OBLIGATORY DEFAULT '5847897898',

p_lgort LIKE dfbatch-lgort OBLIGATORY DEFAULT '1000',

p_klart LIKE klah-klart OBLIGATORY DEFAULT '022',

p_class LIKE klah-class OBLIGATORY DEFAULT 'RETREAD'.

INITIALIZATION.

PERFORM get_characteristics.

START-OF-SELECTION.

PERFORM create_batch.

PERFORM bapi_commit.

PERFORM build_object_key.

PERFORM extract_original_batch.

END-OF-SELECTION.

PERFORM update_original_batch.

PERFORM bapi_commit.

----

FORM get_characteristics *

----

FORM get_characteristics.

extract the characteristic names for KLART/CLASS

CLEAR: klah, ksml, it_cabn.

REFRESH it_cabn.

SELECT SINGLE clint FROM klah

INTO CORRESPONDING FIELDS OF klah

WHERE klart = p_klart

AND class = p_class.

IF syst-subrc = 0.

SELECT * FROM ksml

INTO CORRESPONDING FIELDS OF ksml

WHERE clint = klah-clint.

SELECT SINGLE * FROM cabn

INTO CORRESPONDING FIELDS OF cabn

WHERE atinn = ksml-imerk.

IF syst-subrc = 0.

it_cabn-atinn = cabn-atinn.

it_cabn-atnam = cabn-atnam.

it_cabn-atfor = cabn-atfor.

APPEND it_cabn.

ENDIF.

ENDSELECT.

ENDIF.

ENDFORM.

----

FORM create_batch *

----

FORM create_batch.

CLEAR: rettab.

REFRESH: rettab.

create the batch using screen values, you will most likely have to
determine the next batch number from the number range.

CALL FUNCTION 'BAPI_BATCH_CREATE'

EXPORTING

material = p_matnr

batch = p_charg

plant = p_werks

batchstoragelocation = p_lgort

TABLES

return = rettab.

ENDFORM.

----

FORM build_object_key *

----

FORM build_object_key.

build the object key

CLEAR: it_object, rettab.

REFRESH: it_object, rettab.

it_object-key_field = 'MATNR'.

it_object-value_int = p_matnr.

APPEND it_object.

it_object-key_field = 'WERKS'.

it_object-value_int = p_werks.

APPEND it_object.

it_object-key_field = 'CHARG'.

it_object-value_int = p_charg.

APPEND it_object.

CALL FUNCTION 'BAPI_OBJCL_CONCATENATEKEY'

EXPORTING

objecttable = 'MCHA'

IMPORTING

objectkey_conc = w_object

TABLES

objectkeytable = it_object

return = rettab.

ENDFORM.

----

FORM extract_original_batch *

----

FORM extract_original_batch.

extract the original characteristic data if exists

CLEAR: numtab, chatab, curtab, rettab.

REFRESH: numtab, chatab, curtab, rettab.

CALL FUNCTION 'BAPI_OBJCL_GETDETAIL'

EXPORTING

objectkey = w_object

objecttable = 'MCHA'

classnum = p_class

classtype = p_klart

TABLES

allocvaluesnum = numtab

allocvalueschar = chatab

allocvaluescurr = curtab

return = rettab.

ENDFORM.

----

FORM update_original_batch *

----

FORM update_original_batch.

Below are some examples of characteristics to update, obviously you
would change these to match the ones in your system
ATNAM is the characteristic name.

find characteristic format in it_cabn and call update routine

READ TABLE it_cabn WITH KEY atnam = 'TREAD'.

PERFORM update_table USING it_cabn-atfor it_cabn-atnam 'HW203'.

READ TABLE it_cabn WITH KEY atnam = 'ORRETREAD'.

PERFORM update_table USING it_cabn-atfor it_cabn-atnam '11225HW203C'.

READ TABLE it_cabn WITH KEY atnam = 'CASINGCODE'.

PERFORM update_table USING it_cabn-atfor it_cabn-atnam '7100044'.

READ TABLE it_cabn WITH KEY atnam = 'CASINGSTATUS'.

PERFORM update_table USING it_cabn-atfor it_cabn-atnam 'CUSTOMER'.

READ TABLE it_cabn WITH KEY atnam = 'CASEVAL'.

PERFORM update_table USING it_cabn-atfor it_cabn-atnam '0'.

READ TABLE it_cabn WITH KEY atnam = 'CUSTOMER'.

PERFORM update_table USING it_cabn-atfor it_cabn-atnam '0276933500'.

READ TABLE it_cabn WITH KEY atnam = 'FROMLOC'.

PERFORM update_table USING it_cabn-atfor it_cabn-atnam '0584'.

READ TABLE it_cabn WITH KEY atnam = 'BRAND'.

PERFORM update_table USING it_cabn-atfor it_cabn-atnam 'BRI'.

READ TABLE it_cabn WITH KEY atnam = 'NOCAPS'.

PERFORM update_table USING it_cabn-atfor it_cabn-atnam '1'.

READ TABLE it_cabn WITH KEY atnam = 'RETURNLOC'.

PERFORM update_table USING it_cabn-atfor it_cabn-atnam '0584'.

READ TABLE it_cabn WITH KEY atnam = 'RECDATE'.

PERFORM update_table USING it_cabn-atfor it_cabn-atnam '26.07.2004'.

READ TABLE it_cabn WITH KEY atnam = 'SENTDATE'.

PERFORM update_table USING it_cabn-atfor it_cabn-atnam '26.07.2004'.

READ TABLE it_cabn WITH KEY atnam = 'FLOC'.

PERFORM update_table USING it_cabn-atfor it_cabn-atnam '0750'.

READ TABLE it_cabn WITH KEY atnam = 'AUTOCLAVE'.

PERFORM update_table USING it_cabn-atfor it_cabn-atnam '4'.

READ TABLE it_cabn WITH KEY atnam = 'REPAIRCODE'.

PERFORM update_table USING it_cabn-atfor it_cabn-atnam 'MINOR'.

perform the update

PERFORM bapi_change.

ENDFORM.

----

FORM update_table *

----

FORM update_table USING atfor atnam value.

depending on data format, start building the characteristics table
ready for update

CASE atfor.

WHEN 'NUM'.

READ TABLE numtab WITH KEY charact = atnam.

IF syst-subrc = 0.

numtab-value_from = value.

MODIFY numtab INDEX syst-tabix.

ELSE.

numtab-charact = atnam.

numtab-value_from = value.

APPEND numtab.

ENDIF.

WHEN 'CURR'.

WHEN 'CHAR' OR 'DATE'.

READ TABLE chatab WITH KEY charact = atnam.

IF syst-subrc = 0.

chatab-value_neutral = value.

MODIFY chatab INDEX syst-tabix.

ELSE.

chatab-charact = atnam.

chatab-value_neutral = value.

APPEND chatab.

ENDIF.

ENDCASE.

ENDFORM.

----

FORM bapi_change *

----

FORM bapi_change.

Apply the characteristics to the batch.

CALL FUNCTION 'BAPI_OBJCL_CHANGE'

EXPORTING

objectkey = w_object

objecttable = 'MCHA'

classnum = p_class

classtype = p_klart

TABLES

allocvaluesnumnew = numtab

allocvaluescharnew = chatab

allocvaluescurrnew = curtab

return = rettab.

ENDFORM.

----

FORM bapi_commit *

----

FORM bapi_commit.

commit the changes

CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.

ENDFORM.

varma_narayana · ‎2007 Aug 07

Hi..

BAPIs are internally Remote Enabled Function modules.

But these BAPIs are created as Methods of the Business objects in Business object builder Tcode SWO1.

So we can call a BAPI from an External system (SAP or NON SAP)

and We can call a BAPI internally like a Function module.

Reward if Helpful.

Former Member · ‎2007 Aug 07

Hi,

BAPI is kind of normal Function module wher the data represents in business oriented unlike in normal function module where we use the login understand with in SAP.

http://www.erpgenie.com/abap/bapi/example.htm

Regards

Sudheer

Former Member · ‎2007 Aug 07

Hi !

You can try the very good transaction BAPI to exlore BAPIs and see what

they do.

Regards

rainer

Some points would be nice if that helped a bit.

Former Member · ‎2007 Aug 07

The Business Application Programming Interfaces (BAPI) allow object-oriented access to the SAP system through methods for the business object types. Together with the business object types, BAPIs define and document the interface standard at the business level.

BAPIs (Business Application Programming Interfaces) are the standard SAP interfaces. They play an important role in the technical integration and in the exchange of business data between SAP components, and between SAP and non-SAP components. BAPIs enable you to integrate these components and are therefore an important part of developing integration scenarios where multiple components are connected to each other, either on a local network or on the Internet.

BAPIs allow integration at the business level, not the technical level. This provides for greater stability of the linkage and independence from the underlying communication technology.

Object-oriented technologies have become standard for communication between different software products. For this reason SAP has introduced business object types that structure the data and processes according to business criteria. Business object types are used to break the SAP system down into smaller, disjunctive units, improving its structure and reducing its complexity.

BAPIs are defined as methods for the business object types. As a result, both the object-oriented structures in SAP Systems and the opportunity for object-oriented access are offered. These object-oriented interfaces allow other components to directly access the application layer of an SAP system without having to know the specific implementation details.

The introduction of business object types and their BAPIs enable object orientation to be used in central information processing in companies. For example, you can reuse existing functions and data, achieve trouble-free technical interoperability, and implement non-SAP components.

When implementing BAPIs, you should pursue the goal of avoiding the disadvantages of the "postcard effect" associated with conventional interfaces: No separation between contents and transport. In the case of a postcard, the text is written on a card that also serves as the information medium. If the information medium changes, then the receiver has to read the text in a different way. As a result, changes to the interface affect the type of access.

BAPIs, in contrast, clearly separate the business contents from the underlying communication technology. This procedure can be compared to a letter in an envelope: It is easy to put a letter in a new envelope, just like it is easy to apply new and/or different communication technologies like COM/DCOM, the CORBA standard, or new Internet standards. The envelope itself is irrelevant to understanding the contents of the letter. In this example, the BAPIs correspond to the letter, meaning they are independent of the programming language and communication mechanisms used.

Using BAPIs results in the following benefits:

BAPIs represent well-defined, internally consistent units that always represent business facts and leave a consistent database state behind.

The business contents can be standardized, since BAPIs not only allow the integration of the SAP system and other software components at a technical level, but also at the business level.

BAPIs have become a communication standard between business systems. Access is possible through object-oriented interface technologies (such as COM/DCOM from Microsoft). The SAP business objects conform to the guidelines of the OAG (Object Application Group), and meet the CORBA standard from the OMG (Object Management Group).

Stability and compatibility

Once SAP has released a BAPI, its interface definitions and parameters will remain stable in the long term, which means application programs will not be affected by changes to the underlying SAP software or data. If upward-compatible enhancements are made to the BAPIs, the stability of the existing applications is not affected.

Openness

BAPIs can be accessed from any widespread development platform.

Please go through the link for further information:

http://help.sap.com/saphelp_nw04/helpdata/en/5c/f3f0371bc15d73e10000009b38f8cf/frameset.htm

BAPI with example:

http://www.erpgenie.com/sap/abap/bapi/example.htm

Please reward the helpful entries.

Regards,

Raman.

By Category

Related Content

Activity Groups

Industry Groups

Influence and Feedback Groups

Interest Groups

Location Groups

Customer Only Groups

Forums

Related Resources

Products

Learning and Support

About

My SAP Profile

My SAP Profile

BAPIs are functions?