XSLT call Value Mapping
Maintain the value mapping using the option available in the Integration directory. The following values should be entered for maintaining the value mapping. In the XSLT Mapping use the Java function “Valuemappingaccessor” to read the values from the table.
Class ValueMappingAccessor
This class is used read the Value mapping stored in the Integration server (Java Cache). Class has a method getValueMapping. The Class is imported into the SWC Eyyy_xxxx under namespace “http://xxx.ash.com/COMMON/Common”
Method public static String getValueMapping(String srcContext, String dstContext, String srcAgency, String srcSchema, String dstAgency, String dstSchema, String key, Map inputParam, String throwException)
Paramters Description
srcContext Source context in the Integration server (Java Cache) under which, the value is stored.
For example, if the source values are stored using standard Value mapping table in the ID, then use source context as http://sap.com/xi/XI
dstContext Destination context in the Integration server (Java Cache) under which the value is stored
For example, if the source values are stored using standard Value mapping table in the ID, then Target context as http://sap.com/xi/XI
srcAgency Source Agency, a unique identifying value, value to be used is not yet decided.
srcSchema Source Schema, For example this can be source field name
key Source field value, that is required to determine the target, In the figure 1 shown below, We need to send ‘IN’ to get ‘India’
dstAgency Destination Agency, a unique identifying value, value to be used is not yet decided
dstSchema Destination Schema, For example this can be target field name
inputParam Mapping transformation constants, to write the trace into the header of the message
throwException An indicator to throw an exception, if the value is not found in the cache. If the parameter is set to “true” or “TRUE”, an exception is raised & message fails in the mapping step of the Pipe line.
Returns the value, that is stored in the Value mapping context for the given parameters
If the value mapping is maintained using Integration Directory value mapping, then we need to call the value mapping function as follows
If it has to be called using XSLT Mapping., then the sample code shows how to use the java class the java class “ValueMappingAccessor”.
<?xml version="1.0"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:ns0="http://www.ashok.com/idoctofile/employee" xmlns:ValueMap="java:com.xxx.yyy.ValueMappingAccessor">
<xsl:param name="CountryCode">
<xsl:value-of select="ns0:MT_EMPDETAILS/Country"/>
</xsl:param>
<xsl:param name="inputparam"/>
<xsl:template match="/">
<ns0:MT_EMPADDRESS xmlns:ns0="http://www.ashok.com/idoctofile/employee">
<EmployeeNo>
<xsl:value-of select="ns0:MT_EMPDETAILS/EmployeeNo"/>
</EmployeeNo>
<FirstName>
<xsl:value-of select="ns0:MT_EMPDETAILS/FirstName"/>
</FirstName>
<LastName>
<xsl:value-of select="ns0:MT_EMPDETAILS/LastName"/>
</LastName>
<Address1>
<xsl:value-of select="ns0:MT_EMPDETAILS/AddressLine1"/>
</Address1>
<Address2>
<xsl:value-of select="ns0:MT_EMPDETAILS/AddressLine2"/>
</Address2>
<City>
<xsl:value-of select="ns0:MT_EMPDETAILS/City"/>
</City>
<State>
<xsl:value-of select="ns0:MT_EMPDETAILS/State"/>
</State>
<Country>
<xsl:if test="function-available('ValueMap:getValueMapping')">
<xsl:value-of select="ValueMap:getValueMapping('http://sap.com/XI/xi', 'http://sap.com/XI/xi', 'Canonical','Country', 'KCRS', 'Country', $CountryCode, $inputparam, 'TRUE')"/>
</xsl:if>
</Country>
<ZipCode>
<xsl:value-of select="ns0:MT_EMPDETAILS/Zipcode"/>
</ZipCode>
</ns0:MT_EMPADDRESS>
</xsl:template>
</xsl:stylesheet>
If the values are maintained using Value mapping replication technique
Edited by: Ashok Reddy Thatigutla on Feb 15, 2008 9:43 AM
Edited by: Ashok Reddy Thatigutla on Feb 15, 2008 9:44 AM
Edited by: Ashok Reddy Thatigutla on Feb 15, 2008 10:06 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.