‎2008 May 27 9:07 AM
Hiii
Plz tell me why BDC when we can do the same with Bapi...
plz list out the differences clearly
Thanks & Regards
krishna
‎2008 May 27 9:09 AM
some times some functionalities need to be handled explicitly which cannot be done with BAPI.
If BAPI is avaliable then its totally fine if its working exaclty as how u need it... else u need to go to BDC
‎2008 May 27 9:11 AM
I'm not gonna list differences between them, but I will let you know that I always prefer the BAPI way.
1. Good documenation in general.
2. Less problems with screen processing.
3. Remote enabled.
4. Good error logging, return messages.
‎2008 May 27 9:23 AM
If the same functionality can be achieved by BAPI then we generally go for BAPI instead of BDC. The main reason is that the screen no can change in the next version and in that case the BDC code will not work. But if no BAPI is available then we go for BDC.
Sometimes we need to handle a large amount of data in BDC/BAPI in which it is not preferable to use 'CALL TRANSACTION' command. If the corresponding BAPI internally use 'CALL TRANSACTION' command. Then instead of that BAPI we create a BDC with SESSION METHOD.
Ex: IDOC_INPUT_ORDERS internally use CALL TRANSACTION. So if we need to use a large amount of data we create a BDC with session method instead of using IDOC_INPUT_ORDERS.