whats the diff b/w RFC ,TRFC, IDOC?

[Former Member]

HI ,

1.ANY ONE CAN HELP ME WHATS THE DIFF B/W RFC,TRFC,IDOC?

2. WHATS THE FLOW IN ALE ?

THANKS IN ADVANCE.

[former_member187563 · Accepted solution]

hi,

You can easily get answers to these questions on help.sap and by searching on sdn.

these links are helpful:

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/03e6e790-0201-0010-9d98-ab810281...

http://help.sap.com/saphelp_nw04/helpdata/en/da/cca2ad1071144e9c4f3cf3421ecbce/frameset.htm

regards,

ujjwal kumar

[Former Member]

http://help.sap.com/saphelp_nw04/helpdata/en/da/cca2ad1071144e9c4f3cf3421ecbce/frameset.htm

chk it

SEARCH ON SDN U will FIND all ur ANSWER

[Former Member]

Hi,

Check these links I think you will get answers for ur Questions.

http://help.sap.com/saphelp_nw04/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/8b/ceea3b31aac554e10000000a114084/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/content.htm

http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/snippets/administration%2bof%2bale%2bfunctions

Regards,

Sharanya.

[Former Member]

Hi

Rfc:

SAP delivers the RFC Library for all current external platforms, in which RFC calls are contained for C programs. After installing the RFC Library on your external platform, you can use RFC client or RFC server programs with RFC calls.

The connection to the SAP R/3 System is made using the RFC call RfcOpen with the destination and logon data.

RfcCall calls an R/3 function module. RfcReceive receives the output of the function module. This enables you to use an asynchronous call. If you want to use a synchronous call, use RfcCallReceive instead of these two RFC calls.

To close the RFC connection to the SAP R/3 System, use call RfcClose.

The call RfcAccept accepts the incoming RFC connection.

All C routines for the RFC server program, that should be called remotely, must be registered as being remote-enabled using the call RfcInstallFunction.

The call RfcDispatch sends the incoming call to the corresponding C routine.

The call RfcGetData enables the C routine to receive the input sent from the calling program.

The call RfcSendData returns the result to the calling program.

The call RfcClose ends the RFC connection.

You can use the RFC Generator to create an RFC client in C for a remote-enabled R/3 function module. The corresponding remote call for the function module is already implemented in the collection of program files generated by the RFC Generator.

The RFC Generator also supports you when creating an external RFC server program in C. To do this, first define in the SAP System a remote-enabled dummy function module with empty coding and the interface that you want to use in the remote C routine you will be creating. The RFC generator generates an RFC server program in C with the required remote C routine, which is used for the function module. When you start the RFC Generator, select the option 'C Server' instead of 'C client'.

The RFC Generator also creates a text file which contains tips on using the generated program.

The programs generated by the RFC generator are sRFC client or sRFC server. You can also generate aRFC, tRFC, and qRFC for R/3-external connections. For more information, see the online documentation on RFC-API or the sample programs delivered with the RFC-SDK.

TRFC:

TRFC: (Transaction RFC) also originally known as asynchronous RFC, is an asynchronous communication method that executes the called function module in the RFC server only once. The remote system need not be available at the time when the RFC client program is executing a tRFC. The tRFC component stores the called RFC function, together with the corresponding data, in the SAP database under a unique transaction ID (TID).

Queued RFC (qRFC)

To guarantee that multiple LUWs (Logical unit of work)are processed in the order specified by the application, tRFC can be serialized using queues (inbound and outbound queues). This type of RFC is called queued RFC (qRFC).

qRFC is therefore an extension of tRFC. It transfers an LUW (transaction) only if it has no predecessors (in reference to the sequence defined in different application programs) in the participating queues.

Idoc :

IDOC: IDocs act as data containers in an ALE scenario. They are just a format of storing application data and then transferred using ALE

ALE:

Application Link Enabling - A means of creating and operating distributed applications; guarantees a distributed, but integrated, R/3 installation. This involves business-controlled message exchange using consistent data across loosely linked SAP applications. Applications are integrated using synchronous and asynchronous communication - not by using a central database.

ALE consists of the following layers:

Application services

Distribution services

Communication services

EDI (Electronic Data Interchange): Cross-company exchange of electronic data (for example business documents) between domestic and international business partners who use a variety of hardware, software, and communication services. The data involved is formatted according to predefined standards. In addition to this, SAP ALE technology is available for data exchange within a company.

Regards,

Suryanarayana

[Former Member]

HI

RFC:

Communication between applications of different systems in the SAP environment includes connections between SAP systems as well as between SAP systems and non-SAP systems. Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. The RFC calls a function to be executed in a remote system.

Transactional RFCu2014tRFC

Transactional RFC (tRFC, also originally known as asynchronous RFC) is an asynchronous communication method that executes the called function module in the RFC server only once.

Data can be transferred between two SAP systems reliably and safely using a transactional RFC (tRFC).The called function module is executed exactly once in the RFC server system. The remote system need not be available at the time when the RFC client program is executing a tRFC. The tRFC component stores the called RFC function together with the corresponding data in the database of the SAP system, including a unique transaction identifier.

IDOCS:

IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.

Idoc adapter resides on the ABAP engine and the Idoc is sent directly to the Integration Engine of XI from the R3 system hence no sender idoc adapter and no sender agreement for the idoc adapter. The IDOC Adapter is implemented in ABAP and reside directly on the Integration Server (ABAP Stack).Hence cannot define a sender IDOC channel in directory due to the fact that the IDOC adapter does not run in J2EE Adapter Framework but is an "built in" adapter same for the HTTP adapter also.

The IDOC Adapter is implemented in ABAP and reside directly on the Integration Server (ABAP Stack).You cannot define a sender IDOC channel in directory due to the fact that the IDOC adapter does not run in J2EE Adapter Framework but is a "built in" adapter.

Idoc adapter resides on the ABAP engine and the Idoc is sent directly to the Integration Engine of XI from the R3 system and so , no sender idoc adapter and no sender agreement for the idoc adapter.

cheers

Edited by: vemuganti naga phalguna on Jul 18, 2008 6:52 AM