My Oracle Support Banner

How To Map Custom Fields for the Order Item? (Doc ID 2015940.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Communications Order to Cash Integration Pack for Siebel CRM - Version 11.2 and later
Information in this document applies to any platform.


Customer want to extend a few elements under ListOfSWIOrderItem/SWIOrderItem element. However, it appears to be
that the template for extension is called at the wrong location in the code .

The file AIA_HOME/services/industry/Communications/Siebel/ProviderABCS/UpdateSalesOrde has, as follows:

<xsl:call-template name="SWIOrder_ext"/>
<xsl:variable name="AllOrderLines" select="."/>
<xsl:for-each select="/sordebo:UpdateSalesOrderEBM/sordebo:DataArea/sordebo:UpdateSalesOrder/sordebo:SalesOrderLine">
<xsl:call-template name="PopulateOrderItem">
<xsl:with-param name="currentNode" select="."/>
<xsl:with-param name="AllNodes" select="$AllOrderLines"/>
<xsl:call-template name="SWIOrderItem_ext">
<xsl:with-param name="currentNode" select="."/>

The template call to PopulateOrderItem creates theListOfSWIOrderItem/SWIOrderItem element. At the same level is the call to the template SWIOrderItem_ext. This is causing the extended elements appearing outside of SWIOrder structure instead being part of it.
How to correct this in the base code ? is there any existing patch available for the customer to take it ?


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.