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

Using a FILE port

Former Member
0 Likes
2,265

Hi,

In our SAP system we have configured ALE settings so that we can receive IDOCs from External Non SAP system(WEBMETHODS).

Every thing is working fine.

SAP has recomended to use a File port for this .

Procedure

...

1. For the port definition (SAP menu: Tools ® Business Communication ® IDoc Basis ® Administration ® Port Definition) there are no limitations or notes that apply to the interface. For this type of IDoc implementation area, you can use the port type file, for example. Here the IDocs are stored in files; processing in the R/3 System is started with a synchronous RFC.

So my question is , what is the benefit by using a FILE port.?

if i use a FILE port like this , will the IDOCs be posted automatically or should I manually run a program which will access the file and posts the IDOCs(something like which we do in the case of Collect Idocs option) ?

Thanks Sruthi.

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
1,220

HI Sruthi,

As per your post, you are communicating with the Non-SAP system.

SAP recommends to go for FILE ports because, these Non-SAP sytems are mostly asynchornous. So, by using the FILE ports we can avoid the Data LOGs at the RFC communication and also the timelag.

IDocs post automaticaly, as we are having the setings in the FILE port. The FILE port will tell the location of the file to Operating system where the IDoc can be processed as file. The Operating system will trigger the startrfc program from where IDoc communicated as file to/from SAP.

Hope it is needful.

Thanks.

Ram.

Hi,

In our SAP system we have configured ALE settings so that we can receive IDOCs from External Non SAP system(WEBMETHODS).

Every thing is working fine.

SAP has recomended to use a File port for this .

Procedure

...

1. For the port definition (SAP menu: Tools ® Business Communication ® IDoc Basis ® Administration ® Port Definition) there are no limitations or notes that apply to the interface. For this type of IDoc implementation area, you can use the port type file, for example. Here the IDocs are stored in files; processing in the R/3 System is started with a synchronous RFC.

So my question is , what is the benefit by using a FILE port.?

if i use a FILE port like this , will the IDOCs be posted automatically or should I manually run a program which will access the file and posts the IDOCs(something like which we do in the case of Collect Idocs option) ?

Thanks Sruthi.

2 REPLIES 2
Read only

Former Member
0 Likes
1,220

Hi,

Check with the FM IDOC_INBOUND_FROM_FILE.

Thanks,

Asit Purbey.

Read only

Former Member
0 Likes
1,221

HI Sruthi,

As per your post, you are communicating with the Non-SAP system.

SAP recommends to go for FILE ports because, these Non-SAP sytems are mostly asynchornous. So, by using the FILE ports we can avoid the Data LOGs at the RFC communication and also the timelag.

IDocs post automaticaly, as we are having the setings in the FILE port. The FILE port will tell the location of the file to Operating system where the IDoc can be processed as file. The Operating system will trigger the startrfc program from where IDoc communicated as file to/from SAP.

Hope it is needful.

Thanks.

Ram.