My Oracle Support Banner

Entity References Not Handled For Lookup Data Elements (Doc ID 785068.1)

Last updated on AUGUST 13, 2013

Applies to:

Oracle Communications Order and Service Management - Version: 6.3.1 and later   [Release: 6.3 and later ]
Information in this document applies to any platform.


If lookup data elements contain values like '&' (ampersand), these need to be substituted in order to obtain a well formed order xml, if it participates in a message exchange.

Having said that, this substitution is not happening and, as a result, such orders cannot participate for say EMail Plugin, XSLT, etc.

Below is a sample exception that can be seen in the logs when a lookup contains a value like "A&B" and subjected to XSLT transformation:

SystemId Unknown; Line #1; Column #1236; The reference to entity "T" must end with the ';'

Dec 2, 2008 6:50:46 PM com.mslv.oms.automation.plugin.XSLTSender makeRequest

SEVERE: [order ID=86 hist. ID=1757 task mnemonic=Test] XSLT result is not well-formed:

Dec 2, 2008 6:50:46 PM com.mslv.oms.automation.plugin.a a

SEVERE: [ order ID=86 hist. ID=1757 task mnemonic=Test] Automation exception thrown while running
XSLT plugin: XSLT result is not well-formed: .
com.mslv.oms.automation.AutomationException: XSLT result is not well-formed:
at com.mslv.oms.automation.plugin.XSLTSender.makeRequest(Unknown Source)
at Source)
at com.mslv.oms.automation.plugin.AbstractAutomator._runAutomator(Unknown Source)
at com.mslv.oms.automation.plugin.TestEJB_vno5ie_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.ServerRequest.sendReceive(
at weblogic.rmi.internal.BasicRemoteRef.invoke(
at com.mslv.oms.automation.plugin.TestEJB_vno5ie_EOImpl_921_WLStub._runAutomator(Unknown
at com.mslv.oms.automation.AutomationDispatcher.a(Unknown Source)
at com.mslv.oms.automation.plugin.AutomationEventHandlerImpl.processMessage(Unknown Source)
at com.mslv.oms.automation.AutomationDispatcher.onMessage(Unknown Source)
at weblogic.ejb.container.internal.MDListener.execute(
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(
at weblogic.ejb.container.internal.MDListener.onMessage(
at weblogic.jms.client.JMSSession.onMessage(
at weblogic.jms.client.JMSSession.execute(
at weblogic.jms.client.JMSSession$
at weblogic.kernel.ExecuteThread.execute(


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.