Siebel CRM Integration to Oracle FLEXCUBE Universal Banking Implementation Guide > Customizing the Integration >

Updating Data Transformation Files

This topic describes how to update data transformation files when customizing the Integration.

This task is a step in Process of Customizing the Integration.

The EAI Extensible Stylesheet Language Transformation (XSLT) service is used to transform data from an external integration object structure to a Siebel integration object structure. XSL transformation (XSLT) files for each entity and operation used in the Integration are available in the SIEBSRVR\XSLT directory, where SIEBSRVR is the Siebel Server installation directory. These files are called at run-time by the Integration workflows to map data between Oracle FLEXCUBE Universal Banking and Siebel CRM. For information on the Integration workflows, see Siebel Finance Guide.

When customizing the Integration, verify that an XSLT file exists for the entity required for your customization, and that it supports the field data mapping required. If a file does not exist, or if it does not support the field mappings required, you must create a new XSLT file or amend an existing XSLT file for the new entities or fields being synchronized, as described in the following procedure.

To update the data transformation files

1. Verify whether or not an XSLT file already exists for the entity you are customizing:
   • If you have imported a new entity into Siebel Tools to use in the Integration, as described in Importing EBMs into Siebel Tools, you must create an XSLT file for the new entity. Proceed to step Step 2.
   • If the customization involves mapping additional fields for an entity that is already supported in the Integration, an XSLT file for the entity already exists in the SIEBSRVR\XSLT directory. Proceed to Step 3.
2. Create a new XSLT file for the entity and add it to the SIEBSRVR\XSLT directory.

   For an example of an XSLT file created for an entity imported into Siebel Tools for use in the Integration, see Example of an XSLT File Created For a New Entity.

3. Edit the appropriate XSLT file for the entity using an XML editor and add the new data mapping information.

Example of an XSLT File Created For a New Entity

This topic lists an example of an XSLT file created for an entity that has been imported into Siebel Tools for use in the Integration. It also lists the source and target XML files associated with the new XSLT file.

In this example, the CreateLoanAccountResponseEBM entity is imported into Siebel Tools, as described in Step 6; this provides the source XML file. The EAI XSD Wizard then generates the CreateLoanAccountResponseEBM integration object (the target XML file), as described in Step 8. In the XSLT file that must be created for the new entity, the value of the Name field in the source XML file is mapped to the Full Name field in the target XML file.

XSL Transformation File

The following shows the XSLT file created for the new entity to be used in the Integration, CreateLoanAccountResponseEBM.

NOTE:  The file in this topic is listed for example purposes only; it is not an actual representation of either an AIA EBM or a Siebel CRM XSD file.

<?xml version="1.0" encoding="ISO-8859-1"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml"/>

<xsl:template match="/">
<xsl:apply-templates select="CreateLoanAccountResponseEBM"/>
</xsl:template>

<xsl:template match="CreateLoanAccountResponseEBM">
<xsl:apply-templates select="EBMHeader"/>
</xsl:template>

<xsl:template match="EBMHeader">
<xsl:apply-templates select="Sender"/>
</xsl:template>

<xsl:template match="Sender">
<SiebelMessage>
<Account>
<AccountId>
<xsl:value-of select="Id"/>
</AccountId
<FullName>
<xsl:value-of select="Name"/> <!-- this step maps the value in the Name field (Aaron)in the source XML file to the FullName field in the Target xml file-->
</FullName>
</Account>
</SiebelMessage

</xsl:template>
</xsl:stylesheet>

XML Source File

The following shows an example of the CreateLoanAccountResponseEBM XML file imported into Siebel Tools.

<?xml version="1.0" encoding="UTF-8" ?>
<CreateLoanAccountResponseEBM languageCode="" versionID="">
<EBMHeader languageCode="">
<Sender>
<SenderMessageID schemeVersionID="" schemeID="" schemeAgencyID="">FC_88-2UU0</SenderMessageID>
<ID schemeVersionID="" schemeID="" schemeAgencyID="">FLEXCUBE</ID>
<Name>Aaron</Name> <!-- This is a new field. It is mapped to the Full Name Field in the Target.xml -->
</Sender>
<FaultNotification>
<FaultMessage>
<Code listID="" listVersionID="" listAgencyID="" />
<Text languageCode="" languageLocaleCode="" />
</FaultMessage>
</FaultNotification>
</EBMHeader>
</CreateLoanAccountResponseEBM

XML Target File

The following shows an example XML file generated for the CreateLoanAccountResponseEBM integration object in Siebel Tools.

<?xml version="1.0" encoding="UTF-8" ?>
<SiebelMessage>
<Account>
<AccountId/> <!-- this field maps to Id field in the source.xml -->
<FullName/> <!-- this field is mapped to Name field in source.xml -->
</Account>
</SiebelMessage>