diff between bdc and bapi's

[Former Member]

diff between bdc and bapi's

[Former Member]

Naren,

Main differences are...

In case of bdc data transfer takes place from flat file into sap system ie the file existing in sap system to sap sytem

where is bapi's r remotly enabled function modules which are assigned to some business objects n used to transfer the data between different business partners who are using different systems other than sap.

not only that...

when you plan to upgrade your system version then bdc willnot support those upgradations where as bapi's will support.

I think i gave you some idea......

~~Guduri

[Former Member]

Hi,

BDC (Batch Data Communication) is a technology used for data transfer. it is meant for transferring data thru SAP transactions itself. when u use BDC for data transfer, the sequence of steps is the same as when u use standard sap transaction screens for data upload. the only difference is that u can use different options for foreground/background processing.

BDC:

Batch Data Communication (BDC) is the process of transferring data from one SAP System to another SAP system or from a non-SAP system to SAP System.

Features :

BDC is an automatic procedure.

This method is used to transfer large amount of data that is available in electronic medium.

BDC can be used primarily when installing the SAP system and when transferring data from a legacy system (external system).

BDC uses normal transaction codes to transfer data.

Types of BDC :

CLASSICAL BATCH INPUT (Session Method)

CALL TRANSACTION

BATCH INPUT METHOD:

This method is also called as ‘CLASSICAL METHOD’.

Features:

Asynchronous processing.

Synchronous Processing in database update.

Transfer data for more than one transaction.

Batch input processing log will be generated.

During processing, no transaction is started until the previous transaction has been written to the database.

CALL TRANSACTION METHOD :

This is another method to transfer data from the legacy system.

Features:

Synchronous processing. The system performs a database commit immediately before and after the CALL TRANSACTION USING statement.

Updating the database can be either synchronous or asynchronous. The program specifies the update type.

Transfer data for a single transaction.

Transfers data for a sequence of dialog screens.

No batch input processing log is generated.

For BDC:

http://myweb.dal.ca/hchinni/sap/bdc_home.htm

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&;

http://www.sap-img.com/abap/learning-bdc-programming.htm

http://www.sapdevelopment.co.uk/bdc/bdchome.htm

http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm

http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm

http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html

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.

check these links

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

Regards,

Priyanka.

[Former Member]

Hello Narendra,

Both the Bapis and bdcs are used for transfer/posting of data into the SAP system.

But Bapis are standard FMs which are provided the SAP for particular tranasactions whereas the bdcs are written by us as per the business requirements. Its always better to use BAPIs as these are standard and will be useful if any upgradation happens in the system. We go for bdcs generally if any Bapi doesn't satisfy all the reqirements we need. Also using the BAPI(like a FM) is very much simpler when compared to BDC.

Hope this is useful to you.

Reward if found useful.

Thanks & regards,

Prakash Ghantasala

[Former Member]

Hi,

let me explain BAPI first...

1) BAPI = Business Application Programming Interface.

From a programmer's perspective a BAPI is simply a

certain type of RFC-enabled function module.

Recommended and supported way for management of many SAP business objects like sales, customers, vendors stuff like that.

Business objects means business literally.

2) BDC = Batch Data Commands

a SAP standard transaction while recording it. This recording can be turned into an ABAP program or function module. You can modify these programs to change, e. g., the static data that you entered in the recording to dynamic data that is read from a file or something like that.

The diffrence is that BAPI is a kind of API, kind of library but BDC is not...

BDC is a kind of way to upload data. for example,

when you create customer using 'XD01', you don't know what records is inserted in which table. sometimes we need to take a repeated job. crateting lots of customers.

at that time, you can use BDC.

BAPI is RFC enable functional module. It does direct Database commit into SAP. It can be call from other system too.

BDC for any transaction goes through the screen sequence similar to someone is doing it online.

Since BDC goes through the screen sequence, it does all screen level validation and the custom validation ( if implemented ) created in transaction. On the other hand the BAPI for same functionality sometimes does not carryout some standard validation and custom validation.

pls reward if it helpful

thanks

Vana

[Former Member]

HI,

<b>BDC = Batch Data Commands</b>

Comparable to macros in, e. g., Word. You enter data in a SAP standard transaction while recording it. This recording can be turned into an ABAP program or function module. You can modify these programs to change, e. g., the static data that you enteren in the recording to dynamic data that is read from a file or something like that.

Works best with "simple" transactions, espacially the newer "Enjoy" transactions aren't easy to implement.

Not recommended by SAP any more, although it can be simple and effective to use sometimes.

Works with single or multiple transactions (hence "Batch").

<b>BAPI = Business Application Programming Interface</b>.

From an ABAP programmer's perspective a BAPI is simply a certain type of RFC-enabled function module that obeys certain rules such as: No explicit COMMIT WORK in the FM, return a BAPIRETxxx message, no user interaction, etc. See the documentation for details.

Recommended and supported way for management of many SAP business objects. Many different objects and methods available, although not everything a programmer needs.

Synchronous function modules, generally only one business object per call.

FEW MORE.

<b>Difference between BAPI and BDC</b>:BAPI is a higher end usage for tranfering the data from SAP to non-SAP and vice-versa. for ex: if we are using VB application,where in that we want to connect to SAP and retireve the data,and then change and update the data in SAP for that purpose we can use that.Apart from that, we can also use it for Uploading/Downloading the data from SAP to Non-SAP like BDC, provided we have an existing BAPI for that.BAPI function modules will also do all the checks required for data integrity like Transactions for BDC.There is one more advantage using BAPI instead of BDC. When we go for upgradation, there might be pozzibility to change the screen elements for transactions depending on the requirement. In that case,our BDC pgm may or may not work (depending on the screen changes they have made). Unless and until we prepare new BDC we cant use the old BDC pgm. But in BAPI, SAP promises that they are going to keep the old BAPI and for new functionality they will provide an upgraded BAPI. Until we write a new BAPI pgm, we can use the exisitng BAPI pgm.-Viplove

Reward if it helps you.

Thanks.

Message was edited by:

James Bond