Skip to Content
avatar image
Former Member

what is the difference between BAPI and RFC

Hi ALL,

I am new to ABAP can anybody tell me the difference between BAPI and RFC and in which situations those will be used.

Thanks in Advance

Regards

Ravikumar

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

6 Answers

  • avatar image
    Former Member
    Oct 10, 2007 at 10:22 AM

    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

    Regards

    Anji

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 10, 2007 at 10:25 AM

    Hi Ravi,

    BAPIs are RFC(Remote)-enabled function modules meaning that they provide users from external systems the ability to access to SAP systems and their functionality.

    To be clear, BAPIs are more than traditional RFC-enabled func modules. They actuallly work through SAP business objects (customers, sales orders).

    Remote Function Call:

    RFC is an SAP interface protocol.

    RFC is a fun module similar to other fun modulkes with special Parameter as DESTINATIOn and in the attributes you have to make it as RFC ebnables

    where as BAPI is the API of the BUSINESS OBJECT which you see in SWo1 Tcode

    Based on CPI-C, it considerably simplifies the programming of communication processes between systems.

    RFCs enable you to call and execute predefined functions in a remote system - or even in the same system.

    RFCs manage the communication process, parameter transfer and error handling.

    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).

    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.

    Reward for helpful.

    Regards,

    Harini.S

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 10, 2007 at 10:26 AM

    hi

    good

    BAPI stands for Business Application Programming Interface. It is a library of functions that are released to the public as an interface into an existing SAP system from an external system.

    RFC is the protocol used to call functions in an R/3 system by a caller external to R/3 or to call programs external to R/3 from an R/3 system.

    Functions can only be called via RFC, if they are tagged as RFC functions in the SAP development workbench. They are then called RFC function modules. BAPIs are complete sets of (BAPI) function modules that model a business application.

    When you are familiar with web developments: RFC can be compared to HTTP and BAPIs are CGI applications.

    In other words: A BAPI function is a function module that can be called remotely using the RFC technology.

    reward point if helpful.

    thanks

    mrutyun^

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 10, 2007 at 10:31 AM

    Hi,

    BAPI stands for Business Application Programming Interface. It is a library of functions that are released to the public as an interface into an existing SAP system from an external system.

    RFC is the protocol used to call functions in an R/3 system by a caller external to R/3 or to call programs external to R/3 from an R/3 system.

    Functions can only be called via RFC, if they are tagged as RFC functions in the SAP development workbench. They are then called RFC function modules. BAPIs are complete sets of (BAPI) function modules that model a business application.

    When you are familiar with web developments: RFC can be compared to HTTP and BAPIs are CGI applications.

    In other words: A BAPI function is a function module that can be called remotely using the RFC technology.

    Please check the links,

    BAPI and RFC

    RFC Vs BAPI

    <b>Rewad if usefull</b>

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 10, 2007 at 10:43 AM

    Note that Every BAPI is an RFC.

    But every RFC is not a BAPI.

    BAPI should have a structure in se11 starting with zbapi/ybapi.

    the RFC uses that strucuture for the logic.

    BAPI is for data trasfaer bertween nonsap to sap and also sap to sap.

    But every RFC need not do that.

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 10, 2007 at 10:50 AM

    Hi Ravi..

    <b>RFC </b>- Is the Proprietary communication protocol of SAP. It is used to call the Remote Function Modules in an SAP System From external (SAP or NON SAP) systems.

    <b>BAPI </b>- Is a Method of Business Object .

    Each BAPI will be assigned to a Remote function Module.

    So BAPI can also be called like an RFC from External systems.

    But : BAPI always runs in Background.

    BAPI cannot have EXCEPTIONS . RFC can have exceptions.

    Every BAPI must have a RETURN Parameter to return the Error messages.

    <b>reward if Helpful.</b>

    Add comment
    10|10000 characters needed characters exceeded