‎2007 Apr 04 5:44 AM
Hi All ,
We can use both BAPI as well as BDC to create a sales order . then why don't we use BDC rather then BAPI ...
And which one is better among then ....
OR in other words
when we move from non sap system to sap system we have some sap provided
BDC program to load the data into the system ,
why don't we use the BAPI and send all the data in Internal tables and use them in BAPI ...
Regards
Saurabh Garg
‎2007 Apr 04 5:47 AM
1.BDC will have Screen Flow , but not in BAPI, this makes huge diff.
2.Error Log , only External Commit
3.BAPI can be accessed by any other toools like VB etc
we have a lot of advantages .
Regards
Prabhu
‎2007 Apr 04 9:20 AM
Hi,
In sales order generally we can fill minimum 15 mandatory fields in different tabs,
Again it is bdc table control.If you want to do with bdc the recording program will be too big and there is lot of change of errors.In the case of BAPI simply you have to pass the fields to the appropriate fields in the funciton module.
In bapi after sales order created you will get all the message in to bapireturn table.
But in the case of bdc you have to handle the errors
In the bapi there is option that for test run there is no test run option in bdc.Test run means if we want to create a sales order with the given data is there any errors or success.
Thanks and regards,
shyla
‎2007 Apr 04 9:54 AM
Hi Saurabh,
Hope this helps you.
<b>
BAPI stands for Business API(Application Program Interface).</b>
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.
List of all BAPIs
http://www.planetsap.com/LIST_ALL_BAPIs.htm
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.
<b>BDC:</b>
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.
<b>Features :</b>
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.
BAPI Step-by-Step
http://help.sap.com/saphelp_nw04s/helpdata/en/87/f3ae74e68111d1b3ff006094b944c8/content.htm
http://www.sap-img.com/sap-data-migration.htm
http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc
http://allsaplinks.com/lsmw.html
http://myweb.dal.ca/hchinni/sap/lsmw_home.htm
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
<b>*** Reward Points if Useful.</b>
Regards
Gokul