idocs

[Former Member]

what is the difference beteween ALE and EDI?

what is the difference between TRFC and FILE ports?

are we use ALE for only for sap-to-sap?

[paruchuri_nagesh]

ALE and EDI stands for application link enabling and electronic data interchange

we can use ALE from sap to non-sap but it is expensive in this scenario ale uses memory to memory it is expensive in terms of memory so that incase of sap to non sap better to use edi .

trfc means transactional remote function call which ensures to deliver the document when we r using trfc if the target system is not available at the time of deliver .we can set time intervals in trfc. in these intervals system try to send the documents. it make sure to send the documents

in case of ALEs for sap to sap sub systems are not require but in case of EDI subsystems r require .

in EDI system uses file port to deliver the documents

[Former Member]

Hi

EDI refers to the global standard of interchange of data between two non homogeneous systems like internet and database, sap nd oracle etc..

ALE is the SAP specific standard for the same.

TRFC port sends data(read idocs) in the form of packets, multiple idocs sent in single packages.

File port sends idocs in the form of flat files.

please reward if useful

regards

swati

[Former Member]

TRFC port sends data(read idocs) in the form of segments,multiple idocs sent in single packages or segments.. and IDOC is secure means it is read only,& data available in records..Even superuser can't manupulate data in dis..

in case of flatfiles ,data can be manupulated by users so it can't secure.....

[Former Member]

Hi,

<b>what is the difference beteween ALE and EDI?</b>

1)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.

Refer

http://www.erpgenie.com/sapedi/index.htm

2) ALE

A means of creating and operating distributed applications.

Application Link Enabling (ALE) 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

Refer

http://www.sappoint.com/abap/ale.pdf

http://www.sappoint.com/abap/ale2.pdf

EDI - is a method of transferring electronic data between two systems( SAP or non SAP). for this there is some universally identified formats provided by the ANSI( Americian National Standards International) or EDIFACT ( EDI for Accounts Commence and Transfort)

ALE - is also a method of trenfering data between two systems, provided by the SAP.

Check this link

<b>what is the difference between TRFC and FILE ports?</b>

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.

refer

http://johnv.sapgenie.com/docs/RFC.pdf

http://zerone.samcheok.ac.kr/Asp_pr/Language/.%5Cuploadfile%5CJCo%20Tutorial-1.pdf

http://www.sapgenie.com/sapgenie/docs/SAP%20Connectors.doc

Regards,

Priyanka.