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

How to create an XML File Port in we21

Former Member
0 Kudos

Hi firends,

Can any one help me in creating the XML FILE PORT

Its Urgent




Former Member
0 Kudos

Hi Ganesh,

Award points if useful

This article details about the step by step in conversion of IDOCs to XML format for further use in XI or any other application. It is assumed that the reader of this article has some knowledge in ALE, IDOCs and Change Pointers.


Conversion of the Material IDOC (Message type: MATMAS) to XML format and store the same in the application server of SAP.


Change pointers are used for sending IDOCs for master data like Material Master. To work with Change pointers, following two steps have to be performed:

u2022 Turn on change pointer update generally

u2022 Providing the message types to be included for change pointer updation.

To do the above configurations:

TCode: SALE 􀃆 IDOC Interface / Application Link Enabling (SALE) 􀃆 Modeling and implementing Business Processes 􀃆 Master Data Distribution 􀃆 Replication of Master Data

ALE Configuration Steps:

1. Creation of logical system for the sender system.

2. Assignment of logical system to the client.

3. Create a logical system for the recipient

4. Creation of RFC destination (Connection type:TCP/IP)

5. Creation of Model View (TCode: BD64).

6. Save the Model View and Generate Partner Profiles.

7. There might be a problem with the automatic Port creation. Creation of the port has to be done manually.

8. Create an XML Port from the transaction WE21 (Port type: XML File).

Here directory is the path on the application server. The Function Module is used for file naming conventions. Any of the SAP provided function modules could be used for this (Use F4 help to check on this) or create any custom function module for any other naming conventions.

In the outbound trigger tab, mention the RFC destination created earlier.

9. Make an entry in the partner profile generated earlier for message type MATMAS.

10. A background job need to be scheduled, for a periodic run (interval as required) for the program RBDMIDOC with the message type MATMAS.

11. Depending on the settings in the partner profiles, it may be necessary to send IDocs directly by executing the program RSEOUT00 (if the setting is to u201CCollect IDocsu201D)

Test the above scenario by creating a material using MM01. An XML file would have been created in the directory specified in the XML port. The file could be downloaded onto the front-end system using the transaction CG3Y.

Edited by: ravee on Jun 4, 2008 10:06 PM

0 Kudos

Thanks Ravee,

Full ALE Configuration has to be done ?

In WE21 in the Directory we need to mention the Application File name ??

or any of the Directory say C:/<File name> ??

In the Outbound Trigger Tab,

Is it Cumpulsory to mention the RFC Destination ???

Kindly give your suggestions,

Thanks in Advance


0 Kudos

Hi Ganesh,


The file is uniquely identified via the directory ("path") and their names.

For IDoc files you may also use a "logical directory", which you assign in transaction FILE dependent on operating system "physical" directories.

Outbound file

There you can specify a fixed name for the file,