Skip to Content
author's profile photo Former Member
Former Member

bapis vs rfcs

tell me the difference between bapis and rfcs

Add a comment
10|10000 characters needed characters exceeded

Related questions

5 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Oct 13, 2006 at 04:48 AM

    same thread

    bapi-vs-rfc

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 13, 2006 at 04:50 AM

    Hi,

    Here is the difference

    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.

    Regrads,

    Ruthra

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 13, 2006 at 04:55 AM

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

    The difference between RFc and BAPI is related to business objects. You create business objects and those are then registered in 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.

    A BAPI function is an RFC function whereas an RFC function is not always a BAPI.

    Best Regards,

    Vibha

    *Please mark all the helpful answers

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Oct 14, 2006 at 06:08 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.

    regards

    pavan

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Oct 14, 2006 at 06:55 AM

    hi pavan,

    Th advantages of BAPI

    1. Simple to use (its just an FM)

    2. Not cumbersome like bdc

    where we have to record each and every screen

    sequence.

    3. SAP guarantees the consistency

    of bapi in future releases.

    One of the big plusses for BAPIs is that the interface and function are not supposed to change. This is a big plus when you do upgrades or hot packs because the transaction can change (format, required inputs etc) which means you then need to update the call transaction.

    Some of the BAPIs are better documented and easier to use than others.

    You usually need to perform the BAPI that actually does the COMMIT after you call your BAPI.

    The Program coding for calling a BAPI is usually cleaner than setting up the screen flow etc for the Call Transaction.

    You don't need to worry about special data circumstances interrupting the normal data flow of the screens and causing errors because of that.

    BAPIs probably have better performance since they don't do the screen flow processing.

    In general if the BAPI exists for the transaction you want to perform and you can figure out how to use it the BAPI is probably the best way to go.

    This is just from my experience working with both BAPI and Call Transaction. I have had some very good successes with BAPIs, but very occasionally found that I could not get the BAPI to perform the update I needed.

    Refer the transaction BAPI for detail information.

    You can also refer to below links:

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

    Basic learning guide:

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

    BAPI intro:

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

    Overview:

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

    Also have a look at the following link :

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

    Go through the following Document

    Bapi to create customer master

    -


    BAPI_CUSTOMER_CREATEFROMDATA

    BAPI_CUSTOMER_CREATEFROMDATA1

    Or you can use FM SD_CUSTOMER_MAINTAIN_ALL

    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.

    Check these Links out

    http://searchsap.techtarget.com/ateQuestionNResponse/0,289625,sid21_cid558752_tax293481,00.html

    http://www.sap-img.com/abap/interview-question-on-bapi-rfc-abap-objects-tables.htm

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

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

    Please check out this thread..

    bapi

    Also refer to the following links..

    www.sappoint.com/abap/bapiintro.pdf

    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#

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

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

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

    Java Connector(JCO) can call not only BAPI's but also the function modules which are remotely enabled..

    BAPI's as i said earlier are remotely enabled function modules..

    Hence, JCO can call also BAPI's(n not only BAPI's as u mentioned).

    Check the following BDC over 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.

    ***pls assign the points if info is useful**

    anver

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.