BDC and RFC

dear all, may I know what is the different between BDC and RFC?

Hi,

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.sap-img.com/abap/learning-bdc-
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html

RFC
Remote Function Call:
RFCs are requests that an SAP component sends to invoke functions on remote systems, or calls that remote systems initiate to invoke functions on an SAP component.A process that can accept RFCs from SAP components. This allows SAP components to access functions in external systems. In SAP BC terminology, the process is called a Listener. Listeners are one or more threads on SAP Business Connector that wait for incoming requests from SAP components. Listeners are named and register with an SAP gateway to indicate that they are ready to accept requests. Listeners can accept RFC or tRFC requests.
Transactional RFC (tRFC) and Queued RFC (qRFC). tRFC is used mainly to transfer ALE Intermediate Documents (IDocs).
Transactional RFC:
If an error occurs during a synchronous remote function call, the system cannot tell at what point the error occurred (most crucially, whether the function module was actually processed in R/3 before the operation failed). Restarting a failed call is therefore a dangerous thing to do, since you risk duplicating a completed function call.
To alleviate this problem, you can use transactional RFC, which guarantees that each function call you issue will only be executed once, even if you submit it repeatedly to the R/3 System. The system implements this safeguard by assigning a unique transaction ID (TID) to each transaction that you submit. When you attempt to process the transaction, the system checks whether that TID has already been processed. If it has, the transaction is ignored.
Queued RFC:
When you use transactional RFC, you cannot guarantee the order in which the function calls will be processed in the system (it is quite possible that one call might overtake another). For cases where you need to specify a particular processing order, you can use queued RFC, which is an extension of transactional RFC. In qRFC, you place each function call in a logical queue. A function call cannot be executed until all of its predecessors in the queue have been processed. Queued RFC calls are processed asynchronously.
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.
Have a look at this link.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE2/BCFESDE2.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/22/042860488911d189490000e829fbbd/frameset.htm.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f078394a-4469-2910-c4bf-853c75674694
Please go through the following link. You will get good info on RFC & its types.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f078394a-4469-2910-c4bf-853c75674694
Regards,
Priyanka.

Similar Messages

Difference betrween BAPI and RFC

Hi All
Can anyone tell me the difference between BAPI and RFC.
I am unable to find it out ,except one,ie BAPI is based on object oriented concept .
please justify your answers with real scenerios.

Remote Function Call:
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.
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.
Difference Between BAPI and RFC
What is the main difference between BAPI and RFC and difference between BAPI and BDC?
BAPI is used only when it is available for the particular transaction like Delivery Sales order. but BDC can be used for any
transaction which have screen and fields.
BAPI is directly updated the database instead BDC run through the screen flow.
So BAPI can't handle all the flow logic checking and enhancement put by programmer to faciliate the user requirement.
Difference between BAPI and BDC:
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.
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 you 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. It is not possible to connect SAP to Non-SAP systems to retrieve data using RFC alone. RFC can acces the SAP from outside only through BAPI and same is for vice versa access.
RFC is the protocol used by SAP for remote communication, that is, for communications between remote (independent) systems. RFC is used for communications between two independent SAP systems, or for communications between an SAP system and a non-SAP system, such as an external application. It can also be used for communications between modules on the same system. Using the RFC interfaces you can extend the functionality of R/3 applications from an external program.
BAPI-step by step
http://www.sapgenie.com/abap/bapi/example.htm
list of all bapis
http://www.planetsap.com/LIST_ALL_BAPIs.htm
for BAPI's
http://www.sappoint.com/abap/bapiintro.pdf
http://www.sappoint.com/abap/bapiprg.pdf
http://www.sappoint.com/abap/bapiactx.pdf
http://www.sappoint.com/abap/bapilst.pdf
http://www.sappoint.com/abap/bapiexer.pdf
http://service.sap.com/ale
http://service.sap.com/bapi
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf
http://www.planetsap.com/Bapi_main_page.htm
http://www.topxml.com/sap/sap_idoc_xml.asp
http://www.sapdevelopment.co.uk/
http://www.sapdevelopment.co.uk/java/jco/bapi_jco.pdf
also refer these threads
What is the difference between RFC and BAPI?.
whats difference between rfc and bapi?
difference between rfc & bapi
difference between RFC and BAPi
Difference between BAPI and RFC?
also chk this
http://www.sap-img.com/abap/interview-question-on-bapi-rfc-abap-objects-tables.htm
regards,
srinivas
*reward for useful answers*

Logical system and rfc destination

hello all,
what is the difference between logical system and RFC destination?
thanks for ur help in advance.
regards,
vikas

Hi,
In any ALE scenario u need one sender and one receiver system.
Logical systems are just logical representation of these systems but in case of RFC destination u specify technical parameters for those systems like IP address and username and password to connect to that system.
Thus when u create port i.e.we21 u specify actual RFC destination for the system to which u want to connect and when u create partner profile for that logical system u specify this port so when u want to send data to this logical system i.e receiver system port will be used which in turn has RFC destination which will be used to connect to that system.
In simple terms logical systems are logical representation of any system and RFC destinations are physical/techinical systems.
Regards

Logical system and rfc destination related Query?

Hi Dudes
Do we need to define logical system and RFC destination if they are in different clients in same server
Regards
Raj Kumar

Hi
Both are client independent setting, so even if you define in one client, it would be available in other clients also.
Regards,
Sanjeev

Logical systems for modeldata and RFC metadata

Hi All,
I want to know how I can display the my own created logical system names under the drop-down menu when i have to select the logical system names for modeldata and rfc metadata. I don't want to them to be written instead i want them to be one of the options in the drop down menu, as we have them in the FLIGHT_LIST_INIT example found in the sample applications and examples.
Thanks in advance
Srikant

Hi,
While creating SLD for your R/3 systems give the desired name of wht u want instead of logical name.
For configuring the same refer the link below :-
http://help.sap.com/saphelp_erp2004/helpdata/en/29/e0b75c2b7d40c5bfbda82e905b701c/frameset.htm
Regards,
guru

What is the diffrence between BAPI and RFC and business object

Hi Experts,
Can anybody tel me what is the diffrence between RFC and BAPI , and also what is ther relation with business object?
Thanx in advance.
Nilesh Hiwale

Hi,
BAPI's are associated with Business Objects and also they are RFC enabled.
But RFC's are the FM's which can be called from external systems, those FM's can be used in many places based on the applications..
Check these Links
whats the difference between BAPI and RFC??
Diff. Between BAPI and RFC
Regards
Kiran

Difference between BAPI and RFC?

Difference between BAPI and RFC?
also where to use BAPI and where to use RFC?

Hi,
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.
Regards,
Prakash

Diff b/w BDC and LSMW

hi
i want know what is the difference between BDC and LSMW and which is best also tell me BDC and LSMW using for which type data (like master or transactional data)
thanka in advance
deepak

Hi deepak,
LSMW and BDC are vastly different.
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.
LSMW on the other hand is a tool that helps migrate data from a legacy system (non-sap system ) to SAP system. it offers u various options to use either batch input, direct input, BAPIs or idocs. it involves a series of some 17-18 steps to migrate data.
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
LSMW:
The LSM Workbench is an R/3-based tool that supports You when transferring data from non-SAP systems ("Legacy Systems") to R/3 once or periodically.
The tool supports conversion of data of the legacy system in a convenient way. The data can then be imported into the R/3 system via batch input, direct input, BAPIs or IDocs.
Furthermore, the LSM Workbench provides a recording function that allows to generate a "data migration object" in an entry or change transaction.
The main advantages of the LSM Workbench:
Part of R/3 and thus independent of individual platforms
A variety of technical possibilities of data conversion:
Data consistency due to standard import techniques:
Batch input
Direct input
BAPIs (Business Application Programming Interfaces)
IDocs (Intermediate Documents)
The import technique to be used in an individual case depends on the business object.
Generation of the conversion program on the basis of defined rules
Clear interactive process guide
Interface for data in spreadsheet format
Creation of data migration objects on the basis of recorded transactions
Charge-free for SAP customers and SAP partners
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

DIFFERENCE B/W IDOC AND RFC   ADAPTERS

HI FRIENDS,
WHAT IS THE DIFFERENCE B/W   IDOC AND RFC   ADAPTERS..? AND WHICH ONE IS
PREFERABLE TO USE    IN TRANSFERING DATA FROM THIRD-PARTY SYSTEM TO SAP.?
REGARDS,
RAMAKRISHNA.

Hi
These links will help you to understand :
http://help.sap.com/saphelp_nw04/helpdata/en/11/028417f9f8b24cbe1b0b398e1cb76a/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/ab/bdb13b00ae793be10000000a11402f/frameset.htm
Please dont forget to reward with points.
Edited by: Dheeraj Kumar on Mar 3, 2008 2:59 PM

Help with RFC sender, Program And RFC Destination

Hi!!
my scenary is asynchronous
 RFC Sender -> SAP-XI -> Oracle reciever
I have a problem with abap, especially rfc, program and rfc destination. The connection with SAP-XI exist and SAP-XI receive the message but the message is empty.
1. In my program on the line
 CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
 catch an error system_failure = 2 and it dont execute the rfc ZBAPI_SD_PED_ORD_SERVIC
2. I rewrite my program, that line to
 CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' STARTING NEW TASK 'NEW' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
 catch an error communication_failure = 1 but the rfc ZBAPI_SD_PED_ORD_SERVIC is executed but no send to SAP-XI
3. I rewrite my program, that line to
 CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' IN BACKGROUND TASK DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
 No error but it dont execute the rfc ZBAPI_SD_PED_ORD_SERVIC and the message in SAP-XI is empty, display the tables but not the row. i check the table PED_ORDEN and RETURN but the controls fields dont are afected.
What is my Error?
Where am i making a mistake?
RFC
FUNCTION zbapi_sd_ped_ord_servic.
*"Interfase local
*" TABLES
*" PED_ORDEN STRUCTURE ZSD_RFC_T04
*" RETURN STRUCTURE ZSD_RFC_R06
TABLES: zsd_ped_orden, zsd_rfc_r01.
DATA: tb_ped_orden LIKE zsd_ped_orden OCCURS 0 WITH HEADER LINE,
 tb_rfc_orden_error LIKE zsd_rfc_r01 OCCURS 0 WITH HEADER LINE.
*Get Pedido by Ordenes
SELECT * INTO CORRESPONDING FIELDS OF TABLE tb_ped_orden
 FROM zsd_ped_orden
 WHERE estatus EQ space.
LOOP AT tb_ped_orden.
 MOVE-CORRESPONDING tb_ped_orden TO ped_orden.
 APPEND ped_orden.
 tb_ped_orden-estatus = 'X'.
 tb_ped_orden-fecha_actualiz = sy-datum.
 tb_ped_orden-hora_actualiz = sy-uzeit.
 MODIFY tb_ped_orden.
ENDLOOP.
MODIFY zsd_ped_orden FROM TABLE tb_ped_orden.
COMMIT WORK.
*Errors in Ordenes
SELECT * INTO CORRESPONDING FIELDS OF TABLE tb_rfc_orden_error
 FROM zsd_rfc_r01
 WHERE estatus EQ space.
LOOP AT tb_rfc_orden_error.
 MOVE-CORRESPONDING tb_rfc_orden_error TO return.
 APPEND return.
 tb_rfc_orden_error-estatus = 'X'.
 tb_rfc_orden_error-fecha_actualiz = sy-datum.
 tb_rfc_orden_error-hora_actualiz = sy-uzeit.
 MODIFY tb_rfc_orden_error.
ENDLOOP.
MODIFY zsd_rfc_r01 FROM TABLE tb_rfc_orden_error.
COMMIT WORK.
ENDFUNCTION.
PROGRAM
REPORT ZBAPI_SD_PED_ORD_SERVIC.
DATA: ped_orden LIKE ZSD_RFC_T04 OCCURS 0 WITH HEADER LINE,
 return LIKE ZSD_RFC_R06 OCCURS 0 WITH HEADER LINE.
CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
 TABLES
 ped_orden = ped_orden
 return = return
EXCEPTIONS
 communication_failure = 1
 system_failure = 2
 OTHERS = 3.
IF sy-subrc <> 0.
MESSAGE 'error' type 'I'.
ENDIF.
COMMIT WORK.
RFC DESTINATION
RFC Destination: ZXI_ENVIAR_PED_ORD_SERVIC
Connection TYpe: TCP/IP Connection
Register Server Program: ZBAPI_SD_PED_ORD_SERVIC
Gateway host: host00
Gateway service: sapgw00

hi
For rfc sender adapter we hv to do some settings .Please chk whether this settings are well configured or not.
a) RFC destination
b) RFC channel in the XI directory
This weblog is a response to a few question about the basic configuration of the RFC sender adapter
that were posted on the XI forum (and also on my e-mail)
So here we go, basically we have to configure 2 things:
a) RFC destination
b) RFC channel in the XI directory
RFC destination:
1. To create the RFC go to TCODE: SM59
2. Create new destination of type T (TCP/IP)
3. Make sure you select Registered Server Program option before writing your program ID
4. Write you program ID (remember it's case-sensitive)
5. In the gateway host and gateway service write the values of your "Application system" - business system (not the XI server)
7. No configuration in the J2EE administrator nessecary
Now we can proceed to RFC channel configuration:
1. Enter your Application Server
2. Your Application Server Service
3. Enter your Program ID from the RFC destination
And we're done:)
Now you can test the RFC destination in SM59 to see if it works.
Please chk this following link.
1. RFC Processing with the RFC Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/25/76cd3bae738826e10000000a11402f/content.htm
2. Configuring the Sender RFC Adapter -
http://help.sap.com/saphelp_nw04/helpdata/en/67/6d0540ba5ee569e10000000a155106/content.htm
3. /people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
regards
Manas

Difference Between BAPI And RFC in ABAP

Hi,
i want to know difference between BAPI and RFC in SAP,
can we call SAP GUI screen from NON SAP System Using BAPI.
Reg,
Hariharan

Hi Ravishankar,
The difference is not importat while you understand the concept.
I think, RFC is the protocol for calling functions from external systems in R/3.
I understand like BAPI a series of complet functions that SAP offers you for use and model a business use.
But if I need program a function that can be called for external system i would call it RFC_NAME, because is a unique function that makes a single task.
In other words, the difference i think is about work idea more than another thing.
RFC
A remote function call is a call to a function module running in a system different from the caller's. The remote function can also be called from within the same system (as a remote call).
RFC consists of two interfaces : A calling interface for ABAP Programs and a calling interface for Non-SAP programs.
The RFC Interface takes care of :-
- Converting all parameter data to the representation needed in the remote system
Calling the communication routines needed to talk to the remote system.
Handling communications errors, and notifying the caller, if desired ( using EXCEPTIONS paramater of the CALL FUNCTION).
BAPI
BAPIs are standardized programming interfaces (methods) enabling external applications to access business processes and data in the R/3 System.
BAPIs provide stable and standardized methods to achieve seamless integration between the R/3 System and external applications, legacy systems and add-ons.
BAPIs are defined in the BOR(Business object repository) as methods of SAP business object types that carry out specific business functions.
BAPIs are implemented as RFC-enabled function modules and are created in the Function Builder of the ABAP Workbench.
The most critical difference btwn BAPI and FM is that BAPI can be wrapped in Business objects whereas RFC cant.
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
Refer following SDN threads:
Diff. Between BAPI and RFC
Re: BAPI and RFC
Hope this resolves your query.
Reward all the helpful answers.
Regards

ALE/IDOC and RFC/BAPI Integration Scenarios with SAP DS for ESA v3

Hi,
we are planning two PoCs of Integration Plattforms. One of our major requirement set is SAP Integration into our existing SOA.
Because we also have R/3 4.7 Systems in production, we are planning to test ALE/IDOC and RFC/BAPI Integration scenarios with these Integration Plattforms.
My question is:
We are looking for are smart solution to get a SAP Test Environment, where we can test ALE/IDOC und RFC/BAPI Integration scenarios.
It is possible to do this with SAP DS for ESA v3 or shall we better use IDES for that purpose?
Best regards,
Steven

Hi Abhishek,
This is our scenario. We are doing an integration of SAP HR r/3 system with the CRM system. We need housing information details of the employees which we have in custom infotype 9310 in SAP HR system and we need those details in the CRM system. So am planning out for an ALE/IDOC approach for the integration and gonna maintain the 9310 details in a custom table. In the CRM system, we gonna build a BOL layer for accessing the 9310 details. Also i'm preparing a HLD for this process. I wanna read and go through few same HLD's before i submit my proposal to my client. Please suggest me and help me out.
Thanks in advance.
Regards,
Arunmozhi.

RFC Sender problem between 46D and RFC adapter

Hi,
I have this simple integration scenario where I want to send data to a archiving system;
SAP -> (tRFC) -> XI -> (MQ) -> BizTalk -> (MQ) Arch.syst.
SAP side ***
A Z-program using a Z func. like;
 CALL FUNCTION 'ZSD_DCF_SEND_TAG'
 IN BACKGROUND TASK
 DESTINATION 'XISYSTEM_TRFC_DCF'
 EXPORTING
 pt_filing_info = gt_filing.
 COMMIT WORK AND WAIT.
XI side ***
Both IR and ID is configured correctly, in the development environment everything works just great. I have created a test program where I can define how many calls I will do, looping over the func. call with a commit inside the loop - 500 or more msgs are ok.
The integration scenario is transported to quality enviroment using CMS, and the RFC sender comm.ch. is configured accordingly.
The problem in quality ***
When sending just 1 msg, everything is just fine, message received and delivered to MQ.
When sending >= 2 msgs, the 1 msg is always ok, BUT all others fails due to the following from Adapter monitor;
RFC_HISTORY
- Error: 2006-01-19 10:55:18 CET: com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel 'RFCSender_XI0002' (02d4d30de3593874942ed0659add0827, party '', schema 'TechnicalSystem', identifier 'Q93#120')
- OK: 2006-01-19 10:55:17 CET: Message processed for interface ZSD_DCF_SEND_TAG
My sending system is Q93 CLI 505 so I can understand the error, BUT I cannot understand why the RFC adapter is saying the TechnicalSystem is Q93#120 - it should be Q93#505. My Q XI has client 120...
It seems to me that the RFC adapter is kind of confused about the sender..
I have created a OSS message and SAP has looged on and looked into it with both a XI expert and RFC expert without being able to answer - all is configured correctly.
- The SLD config. for bus.system Q93 is ok -
- The bus.system in ID is showing correct vaues for
Adapter Specific Identifiers (SID Q93, client 505)
- Both Dev. and Qual. environment are running on XI 3.0 SP 14 latest patch, RFC component version on the SAP side is identical between dev. and qual. SAP systems
- It doesn't matter which gw I use (Q93 gw or XI gw), the error is persistent
- It doesn't matter if I increase initial conn, max conn.
I have also tried to use qRFC instead, but with the same result.
Anyone using tRFC for asynch. communication from SAP to XI seeing something similar?
Meanwhile, I will do RFC trace on GW and RFC Adapter on AE....
Please, do not say SP15, oss msg for FAQ RFC adapter or links to RFCAdapter config....
best regards
Torstein

Hi,
SAP Note 730870 FAQ: XI 3.0 RfcAdapter Q.no 15
Q 15: Whats wrong when the error message "lookup of alternativeServiceIdentifier via CPA-cache failed" shows up while sending a RFC call to the RfcAdapter?
A: A RFC sender channel is located beneath a service within the Integration Directory. Within this service choose "Service" -> "Adapter-Specific Identifiers". The values in the fields "R/3 System ID" and "Client" has to be maintained with the correct values of the system, that sends the RFC call to the RfcAdapter. It normaly only makes sense to have these values filled for services of type "Business System". If maintained in SLD, this fields will be filled automaticaly for services of type "Business System" and can be updated with the button "Compare with System Landscape Directory".
- Give correct appserver and gateway service details in XI.
- Open the service holding the RFC adapter you are trying to use. On the top menu, goto Service -> Adapter Specific Identifiers..
Regards,
Prateek

Load balancing and rfc metadata repository in reciever rfc communication ch

hi.
i want to know the purpose of load balancing and rfc meta data repository in RFC communication channel.
and can u send me any examples on this load balancing.
waiting for your response.
bye.
regards.
seeta ram.

Hi Seeta Ram,
Load distribution is handled by the message server (there is one message server in an SAP System). When a user logs on, the message server assigns him or her to the application server that currently has the smallest load.
Well now you can understand that we use load balancing for better performance by distributing the work to different processes to balance or maintain the work load in SAP system.
For more information refer to this link
http://help.sap.com/saphelp_nw04/helpdata/en/28/75153a1a5b4c2de10000000a114084/content.htm
Regards
Sumit Bhutani

How can we use TABLE CONTROL in BDC and WORK FLOW of ABAP.

how can we use TABLE CONTROL in BDC and WORK FLOW of ABAP.?
please explain the important questions.

How to deal with table control / step loop in BDC
Steploop and table contol is inevitable in certain transactions. When we run BDC for such transactions, we will face the situation: how many visible lines of steploop/tablecontrol are on the screen? Although we can always find certain method to deal with it, such as function code 'NP', 'POPO', considering some extreme situation: there is only one line visible one the screen, our BDC program should display an error message. (See transaction 'ME21', we you resize your screen to let only one row visible, you can not enter mutiple lines on this screen even you use 'NP')
Now with the help of Poonam on sapfans.com developement forum, I find a method with which we can determine the number of visible lines on Transaction Screen from our Calling BDC program. Maybe it is useless to you, but I think it will give your some idea.
Demo ABAP code has two purposes:
1. how to determine number of visible lines and how to calculte page number;
(the 'calpage' routine has been modify to meet general purpose usage)
2. using field symbol in BDC program, please pay special attention to the difference in Static ASSIGN and Dynamic ASSIGN.
Now I begin to describe the step to implement my method:
(I use transaction 'ME21', screen 121 for sample,
the method using is Call Transation Using..)
Step1: go to screen painter to display the screen 121, then we can count the fixed line on this screen, there is 7 lines above the steploop and 2 lines below the steploop, so there are total 9 fixed lines on this screen. This means except these 9 lines, all the other line is for step loop. Then have a look at steploop itselp, one entry of it will occupy two lines.
(Be careful, for table control, the head and the bottom scroll bar will possess another two fixed lines, and there is a maximum number for table line)
Now we have : FixedLine = 9
 LoopLine = 2(for table control, LoopLine is always equal to 1)
Step2: go to transaction itself(ME21) to see how it roll page, in ME21, the first line of new page is always occupied by the last line of last page, so it begin with index '02', but in some other case, fisrt line is empty and ready for input.
Now we have: FirstLine = 0
 or FirstLine = 1 ( in our case, FirstLine is 1 because the first line of new page is fulfilled)
Step3: write a subroutine calcalculating number of pages
(here, the name of actual parameter is the same as formal parameter)
global data: FixedLine type i, " number of fixed line on a certain screen
 LoopLine type i, " the number of lines occupied by one steploop item
 FirstLine type i, " possbile value 0 or 1, 0 stand for the first line of new " scrolling screen is empty, otherwise is 1
 Dataline type i, " number of items you will use in BDC, using DESCRIBE to get
 pageno type i, " you need to scroll screen how many times.
 line type i, " number of lines appears on the screen.
 index(2) type N, " the screen index for certain item
 begin type i, " from parameter of loop
 end type i. " to parameter of loop
*in code sample, the DataTable-linindex stands for the table index number of this line
form calpage using FixedLine type i (see step 1)
 LoopLine type i (see step 1)
 FirstLine type i (see step 2)
 DataLine type i ( this is the item number you will enter in transaction)
 changing pageno type i (return the number of page, depends on run-time visible line in table control/ Step Loop)
 changing line type i.(visible lines one the screen)
data: midd type i,
 vline type i, "visible lines
if DataLine eq 0.
 Message eXXX.
endif.
vline = ( sy-srows - FixedLine ) div LoopLine.
*for table control, you should compare vline with maximum line of
*table control, then take the small one that is min(vline, maximum)
*here only illustrate step loop
if FirstLine eq 0.
 pageno = DataLine div vline.
 if pageno eq 0.
 pageno = pageno + 1.
 endif.
elseif FirstLine eq 1.
 pageno = ( DataLine - 1 ) div ( vline - 1 ) + 1.
 midd = ( DataLine - 1 ) mod ( vline - 1).
 if midd = 0 and DataLine gt 1.
 pageno = pageno - 1.
 endif.
endif.
line = vline.
endform.
Step4 write a subroutine to calculate the line index for each item.
form calindex using Line type i (visible lines on the screen)
 FirstLine type i(see step 2)
 LineIndex type i(item index)
 changing Index type n. (index on the screen)
if FirstLine = 0.
 index = LineIndex mod Line.
 if index = '00'.
 index = Line.
 endif.
elseif FirstLine = 1.
 index = LineIndex mod ( Line - 1 ).
 if ( index between 1 and 0 ) and LineIndex gt 1.
 index = index + Line - 1.
 endif.
 if Line = 2.
 index = index + Line - 1.
 endif.
endif.
endform.
Step5 write a subroutine to calculate the loop range.
form calrange using Line type i ( visible lines on the screen)
 DataLine type i
 FirstLine type i
 loopindex like sy-index
 changing begin type i
 end type i.
If FirstLine = 0.
 if loopindex = 1.
 begin = 1.
 if DataLine <= Line.
 end = DataLine.
 else.
 end = Line.
 endif.
 elseif loopindex gt 1.
 begin = Line * ( loopindex - 1 ) + 1.
 end = Line * loopindex.
 if end gt DataLine.
 end = DataLine.
 endif.
 endif.
elseif FirstLine = 1.
if loopindex = 1.
 begin = 1.
 if DataLine <= Line.
 end = DataLine.
 else.
 end = Line.
 endif.
elseif loop index gt 1.
 begin = ( Line - 1 ) * ( loopindex - 1 ) + 2.
 end = ( Line - 1 ) * ( loopindex - 1 ) + Line.
 if end gt DataLine.
 end = DataLine.
 endif.
endif.
endif.
endform.
Step6 using field sysbol in your BDC, for example: in ME21, but you should calculate each item will correponding to which index in steploop/Table Control
form creat_bdc.
field-symbols: <material>, <quan>, <indicator>.
data: name1(14) value 'EKPO-EMATN(XX)',
 name2(14) value 'EKPO-MENGE(XX)',
 name3(15) value 'RM06E-SELKZ(XX)'.
assign: name1 to <material>,
 name2 to <quan>,
 name3 to <indicator>.
do pageno times.
if sy-index gt 1
*insert scroll page ok_code"
endif.
 perform calrange using Line DataLine FirstLine sy-index
 changing begin end.
loop at DataTable from begin to end.
 perform calindex using Line FirstLine DataTable-LineIndex changing Index.
 name1+11(2) = Index.
 name2+11(2) = Index.
 name3+12(2) = Index.
 perform bdcfield using <material> DataTable-matnr.
 perform bdcfield using <quan> DataTable-menge.
 perform bdcfield using <indicator> DataTable-indicator.
endloop.
enddo.
An example abap program of handling Table Control during bdc programming.
REPORT zmm_bdcp_purchaseorderkb02
 NO STANDARD PAGE HEADING LINE-SIZE 255.
 Declaring internal tables *
*-----Declaring line structure
DATA : BEGIN OF it_dummy OCCURS 0,
 dummy(255) TYPE c,
 END OF it_dummy.
*-----Internal table for line items
DATA : BEGIN OF it_idata OCCURS 0,
 ematn(18), "Material Number.
 menge(13), "Qyantity.
 netpr(11), "Net Price.
 werks(4), "Plant.
 ebelp(5), "Item Number.
 END OF it_idata.
*-----Deep structure for header data and line items
DATA : BEGIN OF it_me21 OCCURS 0,
 lifnr(10), "Vendor A/c No.
 bsart(4), "A/c Type.
 bedat(8), "Date of creation of PO.
 ekorg(4), "Purchasing Organisation.
 ekgrp(3), "Purchasing Group.
 x_data LIKE TABLE OF it_idata,
 END OF it_me21.
DATA : x_idata LIKE LINE OF it_idata.
DATA : v_delimit VALUE ','.
DATA : v_indx(3) TYPE n.
DATA : v_fnam(30) TYPE c.
DATA : v_count TYPE n.
DATA : v_ne TYPE i.
DATA : v_ns TYPE i.
*include bdcrecx1.
INCLUDE zmm_incl_purchaseorderkb01.
 Search help for file *
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
CALL FUNCTION 'F4_FILENAME'
 EXPORTING
 program_name = syst-cprog
 dynpro_number = syst-dynnr
 IMPORTING
 file_name = p_file.
START-OF-SELECTION.
 To upload the data into line structure *
CALL FUNCTION 'WS_UPLOAD'
 EXPORTING
 filename = p_file
 filetype = 'DAT'
 TABLES
 data_tab = it_dummy.
 Processing the data from line structure to internal tables *
REFRESH:it_me21.
CLEAR :it_me21.
LOOP AT it_dummy.
 IF it_dummy-dummy+0(01) = 'H'.
 v_indx = v_indx + 1.
 CLEAR it_idata.
 REFRESH it_idata.
 CLEAR it_me21-x_data.
 REFRESH it_me21-x_data.
 SHIFT it_dummy.
 SPLIT it_dummy AT v_delimit INTO it_me21-lifnr
 it_me21-bsart
 it_me21-bedat
 it_me21-ekorg
 it_me21-ekgrp.
 APPEND it_me21.
 ELSEIF it_dummy-dummy+0(01) = 'L'.
 SHIFT it_dummy.
 SPLIT it_dummy AT v_delimit INTO it_idata-ematn
 it_idata-menge
 it_idata-netpr
 it_idata-werks
 it_idata-ebelp.
 APPEND it_idata TO it_me21-x_data.
 MODIFY it_me21 INDEX v_indx.
 ENDIF.
ENDLOOP.
 To open the group *
PERFORM open_group.
 To populate the bdcdata table for header data *
LOOP AT it_me21.
 v_count = v_count + 1.
 REFRESH it_bdcdata.
 PERFORM subr_bdc_table USING: 'X' 'SAPMM06E' '0100',
 ' ' 'BDC_CURSOR' 'EKKO-LIFNR',
 ' ' 'BDC_OKCODE' '/00',
 ' ' 'EKKO-LIFNR' it_me21-lifnr,
 ' ' 'RM06E-BSART' it_me21-bsart,
 ' ' 'RM06E-BEDAT' it_me21-bedat,
 ' ' 'EKKO-EKORG' it_me21-ekorg,
 ' ' 'EKKO-EKGRP' it_me21-ekgrp,
 ' ' 'RM06E-LPEIN' 'T'.
 PERFORM subr_bdc_table USING: 'X' 'SAPMM06E' '0120',
 ' ' 'BDC_CURSOR' 'RM06E-EBELP',
 ' ' 'BDC_OKCODE' '/00'.
 MOVE 1 TO v_indx.
*-----To populate the bdcdata table for line item data
 LOOP AT it_me21-x_data INTO x_idata.
 CONCATENATE 'EKPO-EMATN(' v_indx ')' INTO v_fnam.
 PERFORM subr_bdc_table USING ' ' v_fnam x_idata-ematn.
 CONCATENATE 'EKPO-MENGE(' v_indx ')' INTO v_fnam.
 PERFORM subr_bdc_table USING ' ' v_fnam x_idata-menge.
 CONCATENATE 'EKPO-NETPR(' v_indx ')' INTO v_fnam.
 PERFORM subr_bdc_table USING ' ' v_fnam x_idata-netpr.
 CONCATENATE 'EKPO-WERKS(' v_indx ')' INTO v_fnam.
 PERFORM subr_bdc_table USING ' ' v_fnam x_idata-werks.
 v_indx = v_indx + 1.
 PERFORM subr_bdc_table USING: 'X' 'SAPMM06E' '0120',
 ' ' 'BDC_CURSOR' 'RM06E-EBELP',
 ' ' 'BDC_OKCODE' '/00'.
 ENDLOOP.
 PERFORM subr_bdc_table USING: 'X' 'SAPMM06E' '0120',
 ' ' 'BDC_CURSOR' 'RM06E-EBELP',
 ' ' 'BDC_OKCODE' '=BU'.
 PERFORM bdc_transaction USING 'ME21'.
ENDLOOP.
PERFORM close_group.
 End of selection event *
END-OF-SELECTION.
IF session NE 'X'.
*-----To display the successful records
 WRITE :/10 text-001. "Sucess records
 WRITE :/10 SY-ULINE(20).
 SKIP.
 IF it_sucess IS INITIAL.
 WRITE :/ text-002.
 ELSE.
 WRITE :/ text-008, "Total number of Succesful records
 35 v_ns.
 SKIP.
 WRITE:/ text-003, "Vendor Number
 17 text-004, "Record number
 30 text-005. "Message
 ENDIF.
 LOOP AT it_sucess.
 WRITE:/4 it_sucess-lifnr,
 17 it_sucess-tabix CENTERED,
 30 it_sucess-sucess_rec.
 ENDLOOP.
 SKIP.
*-----To display the erroneous records
 WRITE:/10 text-006. "Error Records
 WRITE:/10 SY-ULINE(17).
 SKIP.
 IF it_error IS INITIAL.
 WRITE:/ text-007. "No error records
 ELSE.
 WRITE:/ text-009, "Total number of erroneous records
 35 v_ne.
 SKIP.
 WRITE:/ text-003, "Vendor Number
 17 text-004, "Record number
 30 text-005. "Message
 ENDIF.
 LOOP AT it_error.
 WRITE:/4 it_error-lifnr,
 17 it_error-tabix CENTERED,
 30 it_error-error_rec.
 ENDLOOP.
 REFRESH it_sucess.
 REFRESH it_error.
ENDIF.
CODE IN INCLUDE.
Include ZMM_INCL_PURCHASEORDERKB01
DATA: it_BDCDATA LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
DATA: it_MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
DATA: E_GROUP_OPENED.
*-----Internal table to store sucess records
DATA:BEGIN OF it_sucess OCCURS 0,
 msgtyp(1) TYPE c,
 lifnr LIKE ekko-lifnr,
 tabix LIKE sy-tabix,
 sucess_rec(125),
 END OF it_sucess.
DATA: g_mess(125) type c.
*-----Internal table to store error records
DATA:BEGIN OF it_error OCCURS 0,
 msgtyp(1) TYPE c,
 lifnr LIKE ekko-lifnr,
 tabix LIKE sy-tabix,
 error_rec(125),
 END OF it_error.
 Selection screen
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS session RADIOBUTTON GROUP ctu. "create session
SELECTION-SCREEN COMMENT 3(20) text-s07 FOR FIELD session.
SELECTION-SCREEN POSITION 45.
PARAMETERS ctu RADIOBUTTON GROUP ctu. "call transaction
SELECTION-SCREEN COMMENT 48(20) text-s08 FOR FIELD ctu.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(20) text-s01 FOR FIELD group.
SELECTION-SCREEN POSITION 25.
PARAMETERS group(12). "group name of session
SELECTION-SCREEN COMMENT 48(20) text-s05 FOR FIELD ctumode.
SELECTION-SCREEN POSITION 70.
PARAMETERS ctumode LIKE ctu_params-dismode DEFAULT 'N'.
"A: show all dynpros
"E: show dynpro on error only
"N: do not display dynpro
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 48(20) text-s06 FOR FIELD cupdate.
SELECTION-SCREEN POSITION 70.
PARAMETERS cupdate LIKE ctu_params-updmode DEFAULT 'L'.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(20) text-s03 FOR FIELD keep.
SELECTION-SCREEN POSITION 25.
PARAMETERS: keep AS CHECKBOX. "' ' = delete session if finished
"'X' = keep session if finished
SELECTION-SCREEN COMMENT 48(20) text-s09 FOR FIELD e_group.
SELECTION-SCREEN POSITION 70.
PARAMETERS e_group(12). "group name of error-session
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 51(17) text-s03 FOR FIELD e_keep.
SELECTION-SCREEN POSITION 70.
PARAMETERS: e_keep AS CHECKBOX. "' ' = delete session if finished
"'X' = keep session if finished
SELECTION-SCREEN END OF LINE.
PARAMETERS:p_file LIKE rlgrap-filename.
at selection screen *
AT SELECTION-SCREEN.
group and user must be filled for create session
IF SESSION = 'X' AND
 GROUP = SPACE. "OR USER = SPACE.
 MESSAGE E613(MS).
ENDIF.
create batchinput session *
FORM OPEN_GROUP.
IF SESSION = 'X'.
 SKIP.
 WRITE: /(20) 'Create group'(I01), GROUP.
 SKIP.
*----open batchinput group
 CALL FUNCTION 'BDC_OPEN_GROUP'
 EXPORTING
 CLIENT = SY-MANDT
 GROUP = GROUP
 USER = sy-uname.
 WRITE:/(30) 'BDC_OPEN_GROUP'(I02),
 (12) 'returncode:'(I05),
 SY-SUBRC.
ENDIF.
ENDFORM. "OPEN_GROUP
end batchinput session *
FORM CLOSE_GROUP.
IF SESSION = 'X'.
*------close batchinput group
 CALL FUNCTION 'BDC_CLOSE_GROUP'.
 WRITE: /(30) 'BDC_CLOSE_GROUP'(I04),
 (12) 'returncode:'(I05),
 SY-SUBRC.
ELSE.
 IF E_GROUP_OPENED = 'X'.
 CALL FUNCTION 'BDC_CLOSE_GROUP'.
 WRITE: /.
 WRITE: /(30) 'Fehlermappe wurde erzeugt'(I06).
 ENDIF.
ENDIF.
ENDFORM. "CLOSE_GROUP
 Start new transaction according to parameters *
FORM BDC_TRANSACTION USING TCODE TYPE ANY.
DATA: L_SUBRC LIKE SY-SUBRC.
*------batch input session
IF SESSION = 'X'.
 CALL FUNCTION 'BDC_INSERT'
 EXPORTING
 TCODE = TCODE
 TABLES
 DYNPROTAB = it_BDCDATA.
 WRITE: / 'BDC_INSERT'(I03),
 TCODE,
 'returncode:'(I05),
 SY-SUBRC,
 'RECORD:',
 SY-INDEX.
ELSE.
 REFRESH it_MESSTAB.
 CALL TRANSACTION TCODE USING it_BDCDATA
 MODE CTUMODE
 UPDATE CUPDATE
 MESSAGES INTO it_MESSTAB.
 L_SUBRC = SY-SUBRC.
 WRITE: / 'CALL_TRANSACTION',
 TCODE,
 'returncode:'(I05),
 L_SUBRC,
 'RECORD:',
 SY-INDEX.
ENDIF.
Message handling for Call Transaction *
perform subr_mess_hand using g_mess.
*-----Erzeugen fehlermappe
IF L_SUBRC <> 0 AND E_GROUP <> SPACE.
 IF E_GROUP_OPENED = ' '.
 CALL FUNCTION 'BDC_OPEN_GROUP'
 EXPORTING
 CLIENT = SY-MANDT
 GROUP = E_GROUP
 USER = sy-uname
 KEEP = E_KEEP.
 E_GROUP_OPENED = 'X'.
 ENDIF.
 CALL FUNCTION 'BDC_INSERT'
 EXPORTING
 TCODE = TCODE
 TABLES
 DYNPROTAB = it_BDCDATA.
ENDIF.
REFRESH it_BDCDATA.
ENDFORM. "BDC_TRANSACTION
 Form subr_bdc_table *
 text
 -->P_0220 text *
 -->P_0221 text *
 -->P_0222 text *
FORM subr_bdc_table USING VALUE(P_0220) TYPE ANY
 VALUE(P_0221) TYPE ANY
 VALUE(P_0222) TYPE ANY.
CLEAR it_bdcdata.
IF P_0220 = ' '.
 CLEAR it_bdcdata.
 it_bdcdata-fnam = P_0221.
 it_bdcdata-fval = P_0222.
 APPEND it_bdcdata.
ELSE.
 it_bdcdata-dynbegin = P_0220.
 it_bdcdata-program = P_0221.
 it_bdcdata-dynpro = P_0222.
 APPEND it_bdcdata.
ENDIF.
ENDFORM. " subr_bdc_table
 Form subr_mess_hand *
 text *
 -->P_G_MESS text *
FORM subr_mess_hand USING P_G_MESS TYPE ANY.
LOOP AT IT_MESSTAB.
 CALL FUNCTION 'FORMAT_MESSAGE'
 EXPORTING
 ID = it_messtab-msgid
 LANG = it_messtab-msgspra
 NO = it_messtab-msgnr
 v1 = it_messtab-msgv1
 v2 = it_messtab-msgv2
 IMPORTING
 MSG = P_G_MESS
 EXCEPTIONS
 OTHERS = 0.
 CASE it_messtab-msgtyp.
 when 'E'.
 it_error-error_rec = P_G_MESS.
 it_error-lifnr = it_me21-lifnr.
 it_error-tabix = v_count.
 APPEND IT_ERROR.
 when 'S'.
 it_sucess-sucess_rec = P_G_MESS.
 it_sucess-lifnr = it_me21-lifnr.
 it_sucess-tabix = v_count.
 APPEND IT_SUCESS.
 endcase.
ENDLOOP.
Describe table it_sucess lines v_ns.
Describe table it_error lines v_ne.
ENDFORM. " subr_mess_hand
Also refer
http://sap.ittoolbox.com/groups/technical-functional/sap-dev/bdc-table-control-668404
and
http://www.sap-img.com/abap/bdc-example-using-table-control-in-bdc.htm
Regards,
srinivas
*reward for useful answers*

BDC and RFC

Similar Messages

Maybe you are looking for