whats difference between rfc and bapi?

[Former Member]

whats difference between rfc and bapi?

[Former Member]

Has been asked before...

Please check:

<a href="https://forums.sdn.sap.com/click.jspa?searchID=253866&messageID=2558225">https://forums.sdn.sap.com/click.jspa?searchID=253866&messageID=2558225</a>

BR

Niklas

[Former Member]

both are FMs. Both are REMOTE Enabled FMs.only BAPI is based upon Object,

which is registred in BOR, thats all

[anversha_s]

hi,

<b>Remote Function Call:</b>

RFC is an SAP interface protocol. 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.

http://help.sap.com/saphelp_47x200/helpdata/en/22/042860488911d189490000e829fbbd/frameset.htm.

<b> BAPI</b>

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. <b>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.</b> 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.

rgds

Anver

[Former Member]

Hi,

).

5. Make changes to the RFC connection.

To delete an RFC user, first delete the user, and then the RFC connection to the system.

You should use one user for all RFC connections.

6. To delete RFC connections to the satellite system, choose the RFC connection by double-click. You go to the transaction Edit RFC Destination (SM59) in the satellite system.

Change RFC Destination Assignment

You can assign existing RFC destinations to a client with the Assign and Check RFC Destinations pushbutton.

Delete RFC destinations

Delete Row only deletes the selected row in the Clients tab, it does not delete the RFC connection to a system.

To delete existing RFC connections, choose the RFC connections by double-click in the Clients tab, or select them and choose Clean-Up RFC Destinations.

For further information about deleting RFC connections, see Edit RFC Destinations in the SAP Library.

RFC generation error handling

· The generation of the RFC connection can fail because the user specified in the Generate RFC Destinations dialog box already exists in the target system, and cannot be created again. You can solve the problem as follows:

¡ If this user is not otherwise used, you can delete it in the target system, and regenerate the RFC destination.

¡ Change the user to be created, in the Generate RFC Destinations dialog box, and regenerate the RFC destination.

¡ If you know the password, or can change it, delete the RFC destination, and regenerate it with the user option Use Existing User, Specify Password.

· The Support Package status in the component systems must be sufficient. The error log long text tells you the required Support Package status.

· The generated user may not have all necessary authorization in the target system. The generation log indicates this. Assign the required authorization to the generated user in the target system, manually.

Result

The system shows the RFC connections generated, on the Clients tab.

Give the users which RFC connections to the component systems want to use, the appropriate authorization in the component systems and in the Solution Manager system. Recreate the authorization profile, if necessary. For further information about the authorization objects and profiles required, see:

· the SAP Solution Manager configuration guide

· System Settings for Customizing Distribution and Scout, for Customizing Synchronization.

BAPI ,

Then Standard BDC

Then Specifc BDC!

BAPI are made in order to work correctly even after a SAP realease change. Moreover, a bapi includes the same rules as the Txn.

If you have possibility to use bapi then its better to go for bapi rather than bdc the main difference between these two is

If any upgradations are made in the system then bdc programs willnot work properly where as bapi's will support the upgradations

if you don't have standard bapi better to go with bdc

if you find it useful mark the points

If there is one then defenitly BAPI.

Also many times you might not have all the data which is required by the BAPI to successfully run.

A BDC is conv when u have less fields or when there's no BAPI existing.

A BDC cannot be called form some other language as an object but BAPI is an object and has methods which can be called.

BAPI is better one than BDC....When u have internal table, using BAPI directly loads data to sap but where as for BDC u have to write hughe code etc....

Check below links which will give u better idea...

/message/2272598#2272598

1. Which is better to use BAPI or BDC?

BAPI is always better.

2. a) Very easy to use (Just like FM)

b) In future, if screen sequence changes, then we have to change BDC,

whereas sap guarantees the corresponding compatibilty/change

in BAPI.

c) Recording/screen sequence/programname/screen fieldname,

--- all these things are not required to be explored & recorded.

BAPI vs BDC

SAP usually upgrade their Version, so each and every time they will change the screens .so you have to change your BDC programs accordingly ,tis is not the case with BAPI .

CHK THIS LINKS:

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

http://sappoint.com/abap/

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

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

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.

</b>

Thanks

Manju

[Former Member]

Hi,

If you want to access a SAP business object you should always go for the BAPI and not use any apparently similar RFC function module. Only the BAPI will ensure that all incoming data are validated and that the business object is after any CREATE or CHANGE is in a consistent state when you use it in a dialog transaction.

Regards,

Karthik

[Ulrich_Schmidt1]

Actually, the question is wrong...

The correct question should be: "what is the difference between an RFM and a BAPI?". Anversha S in his reply from 2006 already summed it up pretty well. Let me try to clarify it with an example:

• RFC ("remote function call") is the name of a network communication protocol -- like for example "HTTP"
• RFM ("remote-enabled function module") is the name for the "things" that can be called/executed via this protocol -- In the HTTP-world this would for example correspond to a "Web-Service".
• BAPI ("business application programming interface") is a special kind of RFM corresponding to a "business object", guaranteeing data-consistency across mulitple tables, stability across different R/3 releases, etc. everything that has already been mentioned further up in this discussion.

So similarly as one cannot say "a Web-Service is an HTTP", one cannot say "a BAPI is an RFC"... Both would be like saying "a car is a street"... Correct would be "a car travels on a street" and similarly "a Web-Service is exeuted via HTTP" and "a BAPI or RFM is executed via RFC".

Regards, Ulrich