SAP PO for Beginners Part – 16 – Brief Overview on XSLT Transformations in SAP PO with Examples
This blog will provide you with an overview on XSLT transformations in SAP PO with examples. It will help you learn and understand the use case of XSLT mapping in SAP PO. We will also explore several examples to illustrate how XSLT transformations work by creating an interface.
To put it plainly, underneath is the substance we will be intricate in this instructional exercise:
- Overview
- Creating XSLT Transformation in SAP NWDS
- Importing XSLT mapping in SAP PI
1. Overview on XSLT Transformations in SAP PO with Examples
This post makes sense of about utilizing XSLT planning in SAP Cycle Coordination for switching a basic contribution over completely to a somewhat complicated yield. It makes sense of the total course of setting up a .xsl document in SAP NWDS programming and afterward bringing in it to PI as a Compress record and test in Activity Planning.
XSLT represents EXtensible Template Language Change. At the point when it is beyond the realm of possibilities to expect to utilize message planning, normally when we really want to make an intricate design from a level message or where collection of hubs and so forth is required, we favor utilizing XSLT planning. XSLT portrays how a XML structure is changed into another XML structure. It is exceptionally easy to utilize a XSLT planning in PI. The XSLT is grown either through NWDS/Obscuration programming and afterward imported as a compress record into ESR.
The transformation of XSL code is managed by the XSLT processor. The XSLT processor takes one or more XML source documents along with the XSL file and processes them to produce a result document. For a comprehensive overview on XSLT Transformations in SAP PO with Examples, it’s important to note that the data/source document must be in XML format.
2. Creating XSLT transformation in SAP NWDS:
Make another Java Task in NWDS. Record – > New – > Java Task. Give a reasonable name and snap FINISH.
Inside it, we want to make source XML record. Right snap on Java Undertaking name – > New – > Other – > XML – > XML record and give a legitimate name to it.
Presently we want to make XSL record which will contain the change rationale.
Right snap on Java Undertaking name – > New – > Other – > XML – > XSL and give a legitimate name to it. Up to this point, we have made info and rationale document. Don’t bother making a result document, as the XSL processor which is worked inside NWDS will naturally change over the information record with rationale in XSL document and make a result XML document.
We can trial and check whether it’s getting made. Open the XML record and right snap on the work area region and pick – > Run As – > XSL Change.
There will be popup to choose XSLT record. Click on Add records to explore through project organizer structure.
On choosing the XSLT record, the XSLT processor actually looks at the XSL rationale and makes a result XML document.
Project folder structure:
We should take a basic model which will give a total thought regarding XSLT:
Leave the Source alone as displayed beneath:
<?xml version="1.0" encoding="UTF-8"?>
<Person>
<FirstName>Subin</FirstName>
<LastName>Sudhakaran</LastName>
<Gender>Male</Gender>
<Address>
<Street>Gandhi Street</Street>
<Houseno>Flat No. B1</Houseno>
<City>Chennai</City>
</Address>
</Person>
Let the desired target be as shown below:
<?xml version="1.0" encoding="UTF-8"?>
<Title>Male</Title>
<Name>Subin Sudhakaran</Name>
<Street>Flat No. B1 Gandhi Street</Street>
<City>Chennai</City>
Presently as we have the source and the objective with us, we can foster a XSLT planning between them in SAP NWDS.
XSL starter template:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/">
<!-- TODO: Auto-generated template -->
</xsl:template>
</xsl:stylesheet>
Presently how about we make sense of the above XSLT starter intricately. Since a XSL template is a XML archive itself, it generally starts with the XML statement: . The following component, , characterizes that this record is a XSLT template archive (alongside the variant number and XSLT namespace ascribes). The component characterizes a layout. The match=”/” trait partners it with the base of the XML source report. The substance inside component characterizes some HTML content to be composed as a result.
Presently how about we start the XSL rationale, where first field in the objective design is the TITLE which is planned to Orientation in source structure. Subsequently the rationale would be:
<Title>
<xsl:value-of select=”Person/Gender” />
</Title>
Esteem of selector will get the worth of the field from the source XML and the way of the field is given in the select property as a XPATH articulation.
Presently we should continue with next field NAME, where we want to link first name and last name in the source XML with in the middle between.
<Name>
<xsl:value-of select="concat(concat(Person/FirstName,' '), Person/LastName)"/>
</Name>
In the above XSL code, we are utilizing two connect administrators: First concat is for consolidating First Name with space close to it and next one is for joining First Name with space to last name.
Let’s do the same for rest of the fields: Street and City.
<Street>
<xsl:value-of select="concat(concat(Person/Address/Houseno, ' '), Person/Address/Street)"/>
</Street>
<City>
<xsl:value-of select="Person/Address/City"/>
</City>
Output:
Presently you would have a thought on how the XSLT change functions. We should get into different XSL labels accessible.
- <xsl:stylesheet> or <xsl:transform> :
or are the root components that proclaim the archive to be a XSL template. Both of the two components can be utilized as root components as they are interchangeable. We have utilized xsl:stylesheet in the above model. The xmlns:xsl=”http://www.w3.org/1999/XSL/Change” focuses to the authority W3C XSLT namespace. Assuming you utilize this namespace, you should likewise incorporate the characteristic version=”1.0″.
- <xsl:template> :
A XSL template comprises of at least one bunch of decides that are called layouts. A layout contains rules to apply when a predefined hub is coordinated. The worth of the match quality is a XPath articulation. In our model, match=”/” characterizes the entire report.
- <xsl:value-of> :
Esteem of component is utilized to remove the substance of the predetermined hub. The worth that should be brought ought to be given as XPATH articulation inside the select property.
- <xsl:for-each> :
JavaScript engineers would have speculated the usecase of this component. Its is utilized to circle through the hub. For instance, for our situation we have just a single individual hub, imagine a scenario where we have numerous individual hubs ?
We really want to show both individual hubs in the result, right ? With the ongoing rationale, on the off chance that you execute with different individual hubs, you will get just a single individual hub (initial one), as we are not circling through it. Thus, how about we circle through the individual hubs and show it in yield.
Input XML:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_XSLT_Source xmlns:ns0="http://XYZ.com/gen">
<Person>
<FirstName>Subin</FirstName>
<LastName>Sudhakaran</LastName>
<Gender>Male</Gender>
<Street>Gandhi Street</Street>
<Houseno>Flat No. B1</Houseno>
<City>Chennai</City>
</Person>
<Person>
<FirstName>Sudheesh</FirstName>
<LastName>Sudhakaran</LastName>
<Gender>Male</Gender>
<Street>Daniel Street</Street>
<Houseno>Flat No. B2</Houseno>
<City>Mysore</City>
</Person>
</ns0:MT_XSLT_Source>
XSL Logic:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet
version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:ns0="http://XYZ.com/gen"
xmlns:ns1="http://XYZ.com/Test">
<xsl:template match="/">
<ns1:MT_XSLT_Target>
<xsl:for-each select="ns0:MT_XSLT_Source/Person">
<Title>
<xsl:value-of select="Gender" />
</Title>
<Name>
<xsl:value-of select="concat(concat(FirstName,' '), LastName)" />
</Name>
<Street>
<xsl:value-of select="concat(concat(Houseno, ' '), Street)" />
</Street>
<City>
<xsl:value-of select="City" />
</City>
</xsl:for-each>
</ns1:MT_XSLT_Target>
</xsl:template>
</xsl:stylesheet>
Output:
We can likewise channel the result from the XML document by adding a basis to the select trait of component.
Eg: <xsl:for-each select="ns0:MT_XSLT_Source/Person[FirstName=’Subin’]">- <xsl:sort> :
Sort component will sort the result XML. We really want to indicate on what premise the arranging ought to occur.
<xsl:sort select=”FirstName”>- <xsl:if> :
The component is utilized to set a restrictive test against the substance of the XML document. The worth of the expected test trait contains the articulation to be assessed.
<xsl:if test=”expression”> </xsl:if>
<xsl:if test=”Gender =Male”>
We have investigated the fundamentals of XSLT change. Presently we should perceive how to utilize a XSLT planning in PI.
3. Importing XSLT mapping in SAP PI:
Steps engaged with sending a connection point or arrangement the planning program is:
Source Data Type:
Target Data Type:
I won’t show the screen captures for Message type, administration interfaces as those are fundamental and known. When message types and administration connection points are made, make IMPORTED Chronicles and import the XSL document in it.
For effective import of XSL document into imported chronicles, you want to change over it into Compress or Container record. It’s better and more straightforward to change over the XSL document to Compress record.
Operation Mapping:
That’s all there is to it. This is the methodology to create and deploy XSLT transformations in SAP PI. I hope you enjoyed this overview on XSLT Transformations in SAP PO with Examples. If you have any doubts, questions, or suggestions, please leave your comments below.
YOU MAY LIKE THIS
How to SPLIT Data in FOR LOOP Using Modern ABAP Syntax?