|Home • Trainings •Quiz • Tips • Tutorials • Functional • Cert Q's • Interview Q's • Jobs • Testimonials • Advertise • Contact Us|
By Vijay Kumar Thirumareddi, YASH PI Competency Core Team, Yash Technologies
This document gives you clear understanding of XSLT Mapping,
which shall convert source structure to specific target structure.
Below are different ways of achieving this conversion in XI,
The rest of the document gives you pre-requisites and steps
that are necessary for making use of XSLT Mapping.
Steps required for developing XSLT Mapping
By having look at above steps you can easily find out that
this mapping is no where different from other mapping programs, here the
challenging lies in creating an XSLT file. If you spend couple of minutes in
studying XPATH tutorial you would be in ideal position to create an XSL
Transformation (.xsl extension).
If you still find difficulties in generating XSL
Transformation, then you can make use of a tool “Altova MapForce” which will
create XSL file for you.
Steps for creating XSL file using this tool:
Scenario demonstrating usage of XSLT Mapping
a business scenario where in business (Source System) sends an outbound delivery
to their Logistics partner for transporting the same. But here the source
business is running on SAP R/3 and corresponding Logistics partner is not on
SAP, hence the interpretation of data/communication is different. Because source
system sends delivery information in an IDoc (which will be handled by message
control for delivery (VL01N/02N) and the target Logistics partner is not aware
of these IDoc structures, so in order to provide a communication between these
two we need some interface mechanism which takes IDoc structure and converts it
into the format understandable by the target Logistics provider and vice versa.
the target system expects the xml files in CIDX format, so XI system takes IDoc
as an input and converts it to an XML file adhering to CIDX naming standards.
steps to make this scenario:
IDoc structure into IR, in our scenario import IDoc DESADV.DELVRY03
corresponding XSD structure under External Definitions in IR.
Here the corresponding CIDX message is
Load Tender Motor.
Import ZIP file
corresponding to XSLT under Imported Archives in IR, which can transform source
message to target structure.
Objects needed to be developed in IR
Inbound Message Interface: Create Inbound Message Interface resembling target CIDX
Import XSL ZIP file
path to corresponding zip file,
Interface Mapping: Provide source interface as DESADV.DELVRY03 and Target interface as
specify Mapping Program specific to XSL Type,
corresponding Archive program from the search help provided under “Name”.
Please send us your feedback/suggestions at webmaster@SAPTechnical.COM
©2006-2007 SAPTechnical.COM. All rights reserved.
product names are trademarks of their respective companies. SAPTechnical.COM
is in no way affiliated with SAP AG.
Graphic Design by Round the Bend Wizards