Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Order and Service Management (Communications Industry) (MOSC)

OSM Order fallout error message

Nov 8, 2013 4:03PM edited Nov 17, 2013 4:10PM in Order and Service Management (Communications Industry) (MOSC) 4 commentsAnswered

HI We have noticed that namespaces info and bpel # is being prepended to order fallout message that are sent to Siebel. This causes confusion for our customer service reps. IS there a way to remove those before the message is sent in trouble ticket? Why are they there? This does not happen with all error messages.

lt::orderfalloutdata:ErrorMessage xmlns:aiacommsdate=quot::
xmlns:aiacommsdate=quot::http://www.oracle.com/XSL/Transform/java/oracle.apps.aia.industry.comms.util.AIAGetDateOffsetquot::
xmlns:orderfalloutdata=quot::http://xmlns.oracle.com/ABCS/OrderFalloutNotification/V1quot::
xmlns=quot::http://xmlns.oracle.com/ABCS/OrderFalloutNotification/V1quot:

0

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month