Last updated on JANUARY 26, 2009
Applies to:Oracle Communications ASAP - Version: 5.2.3 to 5.2.3
This problem can occur on any platform.
-- Problem Statement:
On ASAP 5.2.3:
Find that the orderFailEvent coming from ASAP has an element defined as
but the same element has been defined in ASAP schema files as
Expect that the parameter sent upstream should be
-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1. Cause an order to fail.
2. Observe the orderFailEvent received upstream for the element techType
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms