Search

Home
Trainings
Quiz
Tips
onials Advertise
Contact Us
SAP Virtual/Onsite Trainings

Tutorials

Functional

Cert Q's

Interview Q's

Document Categories:
ABAPTM
Adobe Forms
ABAP-HR
ALE & IDocs
ALV
BAPI
BASIS
BSP
Business Objects
Business Workflow
CRM NEW
LSMW
SAP Script/Smart Forms
BI/BW
eXchange Infrastructure (XI)
Enterprise Portals (EP)
eCATT
Object Oriented Programming
SAP Query
Userexits/BADIs
WebDynpro for Java/ABAPTM
Others
What's New?
ABAP Test Cockpit HOT
SAP ABAP Pragmas
Understanding SE32 (ABAP Text Element Maintenance)
Creating an IDoc File on SAP Application Server
Understanding Advance with dialog option of SAP Workflow
SAP Workflow Scenario: Maintenance Notification Approval
Enhancements to a standard class
Working with Floating Field in Adobe Forms
Inserting data from Internal Table into the step Send Mail
Display GL Account long text using enhancement framework
Differences between polymorphism in JAVA and ABAP
Passing multiline parameters from an ABAP Class event to a Workflow container
Concept of Re-evaluate agents for active work items in SAP Workflow
Dynamic creation of component usage in ABAP WebDynpro
Adobe Forms: Display symbols like copyright and others
Deactivate Hold functionality in Purchase order (ME21N)
Quiz on OOABAP
Add fields in FBL5N using BADIs
Tutorial on Wide casting
Defining a Range in Module Pool Program
Copy fields from one structure/table into another structure/table
Side Panel Usage in NWBC
Contribute?
Sample Specs

Jobs

What's Hot?
Web Dynpro for ABAP Tutorials
Join the Mailing List
Enter name and email address below:
Name:
Email:
Subscribe Unsubscribe GO
XSLT Mapping
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,
Message Mapping (Graphical Mapping using Mapping Editor in XI )
Java Mapping
ABAP Mapping
XSLT Mapping
The rest of the document gives you pre-requisites and steps that are necessary f
or making use of XSLT Mapping.
Pre-requisites
XSL

Extensible Stylesheet Language

XSLT XSL Transformations, the purpose of this is for transformation of XML docum
ents into other formats like XML, XHTML and etc. Here is the link to get corresp
onding tutorial http://www.w3schools.com/xsl/default.asp.
XPATH XSLT uses XPATH to find information in an XML document. XPATH is used to
navigate through elements and attributes in XML documents. Here is the link for
same http://www.w3schools.com/xpath/default.asp.
Steps required for developing XSLT Mapping
Create a source data type and a target data type
Create Message types for the source and target data types.
Create Message Interfaces includes Inbound Message interface and Outbound Messag
e interface.
XSLT Mapping does not require creation of Message mapping, so don t create any Mes
sage mapping.
Create an .XSL file which converts source data type into target data type.
Zip that .xsl file and import it into Integration Repository under Imported Arch
ives.
In Interface Mapping choose mapping program as XSL and specify this zip program.
(Through search help you will get XSL Mapping programs that you imported under
Imported Archives, select your corresponding XSL Program)
Test this mapping program by navigating to Test tab.
By having look at above steps you can easily find out that this mapping is no wh
ere 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 wou

ld be in ideal position to create an XSL Transformation (.xsl extension).

If you still find difficulties in generating XSL Transformation, then you can ma
ke use of a tool Altova MapForce which will create XSL file for you.
Steps for creating XSL file using this tool:
Open the Alto MapForce, import the source .xml and .xsd file in it
Similarly import the target .xml and .xsd in MapForce.
These two data files should match with source and target data types in Integrati
on Repository.
Complete the graphical mapping using extensive list of XSLT functions available
there.
Save the mapping file.
Click the XSLT tab. You will have the entire xslt logic there.
Copy that content and save it as .xsl file.
Zip above .xsl file and import the same into IR under Imported Archives.
Scenario demonstrating usage of XSLT Mapping
Take a business scenario where in business (Source System) sends an outbound del
ivery 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 sy
stem sends delivery information in an IDoc (which will be handled by message con
trol for delivery (VL01N/02N) and the target Logistics partner is not aware of t
hese IDoc structures, so in order to provide a communication between these two w
e need some interface mechanism which takes IDoc structure and converts it into
the format understandable by the target Logistics provider and vice versa.

Here 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 standard
s.
Important steps to make this scenario:

Import needed IDoc structure into IR, in our scenario import IDoc DESADV
.DELVRY03

Import corresponding XSD structure under External Definitions in IR. He

re the corresponding CIDX message is Load Tender Motor.

Import ZIP file corresponding to XSLT under Imported Archives in IR, whi
ch can transform source message to target structure.
Objects needed to be developed in IR
Inbound Message Interface: Create Inbound Message Interface resembling target CI
DX message.

Import XSL ZIP file

Provide path to corresponding zip file,

Save it

Interface Mapping: Provide source interface as DESADV.DELVRY03 and Target interf

ace as MI_IB_LoadTenderMotor

Now specify Mapping Program specific to XSL Type,

Choose corresponding Archive program from the search help provided under

Name .

Save it.
Now activate all the objects that are developed in IR.
Click here to continue...

Please send us your feedback/suggestions at webmaster@SAPTechnical.COM

Home Contribute
About Us Privacy
Terms Of Use
se on SAPTechnical.COM | Post Job Contact Us

Disclaimer

Safe

Companies: Advert

2006-2007 SAPTechnical.COM. All rights reserved.

All product names are trademarks of their respective companies. SAPTechnical.COM
is in no way affiliated with SAP AG.
SAP, SAP R/3, R/3 software, mySAP, ABAP, BAPI, xApps, SAP NetWeaver, and and any
other SAP trademarks are registered trademarks of SAP AG in Germany and in seve
ral other countries.
Every effort is made to ensure content integrity. Use information on this site a
t your own risk.
Graphic Design by Round the Bend Wizards
footer image

footer image