Scribd
Upload
660 views

Conversion of IDOC's To XML Format

This document details the steps to convert IDOCs to XML format for use in XI or other applications. It outlines configuring ALE and creating logical systems, model views, ports, and partner profiles to enable IDOC exchange between systems. A background job then periodically runs the program to collect IDOCs of a specified message type and generate corresponding XML files in a designated application server directory.

Uploaded by

Rakesh Rai
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
660 views

Conversion of IDOC's To XML Format

This document details the steps to convert IDOCs to XML format for use in XI or other applications. It outlines configuring ALE and creating logical systems, model views, ports, and partner profiles to enable IDOC exchange between systems. A background job then periodically runs the program to collect IDOCs of a specified message type and generate corresponding XML files in a designated application server directory.

Uploaded by

Rakesh Rai
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 3

This Tutorial 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 Tutorial has some knowlede in !L"#
IDOCs and Chane $ointers.
Scenario% Conversion of the Material IDOC &Messae type% M!TM!'( to XML format and store the
same in the application server of '!$).
Approach
Chane pointers are used for sendin IDOCs for master data like Material Master. To work with
Chane pointers# followin two steps have to be performed%
Turn on chane pointer update enerally
$rovidin the messae types to be included for chane pointer updation.
To do the above confiurations%
TCode% '!L" **+ IDOC Interface , !pplication Link "nablin &'!L"( **+ Modelin and implementin
-usiness $rocesses **+ Master Data Distribution **+ .eplication of Master Data
ALE Configuration Steps%
/. Creation of loical system for the sender system.
0. !ssinment of loical system to the client.
1. Create a loical system for the recipient
2. Creation of .3C destination &Connection type%TC$,I$(

4. Creation of Model 5iew &TCode% -D62(.
6. 'ave the Model 5iew and 7enerate $artner $rofiles.
8. There miht be a problem with the automatic $ort creation. Creation of the port has to be
done manually.
9. Create an XML $ort from the transaction :"0/ &$ort type% XML 3ile(.
;ere directory is the path on the application server. The 3unction Module is used for file namin
conventions. !ny of the '!$) provided function modules could be used for this &<se 32 help to check
on this( or create any custom function module for any other namin conventions.
In the outbound trier tab# mention the .3C destination created earlier.

=. Make an entry in the partner profile enerated earlier for messae type M!TM!'.
/>. ! backround ?ob need to be scheduled# for a periodic run &interval as re@uired( for the
proram .-DMIDOC with the messae type M!TM!'.
//. Dependin on the settins in the partner profiles# it may be necessary to send IDocs directly
by eAecutin the proram .'"O<T>> &if the settin is to BCollect IDocsC(
Test the above scenario by creatin a material usin MM>/. !n XML file would have been created in
the directory specified in the XML port. The file could be downloaded onto the front*end system usin
the transaction C71D.

You might also like