Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

differences between rfc and ale/idoc.

Former Member
0 Likes
3,108

hi ..

will u please send the differences between rfc and ale/idoc's.

hi ..

will u please send the differences between rfc and ale/idoc's.

3 REPLIES 3
Read only

matt
Active Contributor
0 Likes
1,548

RFC and ALE/IDOC are as different from one another as, for example, a carburettor and a car.

ALE/IDOC might use RFC, but to talk about the differences makes no sense.

Read only

Former Member
0 Likes
1,548

Hi Karthik,

Please try to search in the forums and if you could not find anything related, then post. There are lot of threads on this subject and you will learn/know more if you search.

Good Luck.

Hope this helps.

Thanks,

Srinivasa

Read only

Former Member
0 Likes
1,548

Hi,

Please reward with points if helpful................

ALE is SAP proprietary technology that enables data communications between two or more SAP R/3 systems and/or R/3 and external systems. There are three layers in ALE system: application services, distribution services, and communication services.

For communication services, ALE performs a Remote Function Call (RFC) using the port definition and RFC destination specified by the customer model. RFC is used to communicate 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.

*************************************************************

Means of creating and operating distributed applications.

The purpose of Application Line Enabling is to guarantee a distributed, but integrated, R/3 installation. This involves business-controlled message exchange with consistent data across loosely linked SAP applications.

Application integration is achieved not via a central database, but via synchronous and asynchronous communication.

Application Link Enabling comprises the following three layers:

application services

distribution services

communication services

Two Development Models

Distribution using BAPIs

Distribution using Message type

The programming model "Distribution using message types" contains the definitions of message types and IDoc types and the ABAP code for processing inbound and outbound IDocs.

Defining message types and IDoc types:

If you want to create message type enhancements for master data distribution, you also have to create a new message type for each enhancement.

The ALE interface does not allow you to create different segment data for different IDoc types for the same message type.

Writing ABAP code:

Outbound Processing

Inbound Processing

You can find information on other ALE functions under:

Master Data Distribution

Communicating with Non-R/3 Systems

********************************************************************************

1. The Remote Function Call facility allows you to call an R/3 Function module on a “remote” machine.

2. To communicate between two R/3 Systems and also with an External System. External Application program also can call these function module for integration.

3. RFC or sRFC - Synchronous RFC

aRFC - Asynchronous RFC

tRFC - Transactional RFC

qRFC - Queued RFC (I.e. Serialization of tRFC)

Types of RFC Call

Synchronous

CALL FUNCTION Func Destination Dest

CALL FUNCTION func DESTINATION 'NONE' ...

CALL FUNCTION func DESTINATION ’BACK' ...

Asynchronous

CALL FUNCTION func … STARTING NEW TASK taskname

PERFORMING form ON END OF TASK

RECEIVE RESULTS FROM FUNCTION func

********************************************************************************

Thanks

sivaparvathi