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

Ports

Former Member
0 Likes
748

what is the difference between file port and trfc port

5 REPLIES 5
Read only

Former Member
0 Likes
717

hello,

For ALE config we will use file port, for EDI we will use trfc port.

regards,

ram.

Read only

Former Member
0 Likes
717

hi guru thank for soving my query

Read only

Former Member
0 Likes
717

Hi,

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

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

<b>Reward points</b>

Regards

Read only

Former Member
0 Likes
717

Ports are a logical representation of the communication channels in SAP. R/3 defines four types of ports viz. tRFC (transactional Remote Function Calls), File, R/2, and Internet. ALE can use all port types to distribute Idocs.

You use the port maintenance in the IDoc adapter to establish an RFC connection to the system that contains the metadata that the IDoc adapter requires to convert IDocs (Intermediate Documents) that have been sent to it to IDoc XML format. This system is defined by the sender port and the client in the IDoc control record. It is either the sender SAP system or an SAP reference system.

You must maintain a port in the IDoc adapter for all clients in each SAP system that you want to connect to the Integration Server using IDocs.

This is also the case for receiver systems if they are subsystems (non-SAP systems). Systems of this kind are defined using the receiver port in the respective communication channel.

For more information, please check this link.

http://help.sap.com/saphelp_nw04/helpdata/en/3b/beb13b00ae793be10000000a11402f/content.htm

Read only

Former Member
0 Likes
717

Hi

thanks for all who responded to my query.

Regards

suresh