After Translation to Native SIU Document SCH-11.4 Field Shifts to SCH-11.3
(Doc ID 2090849.1)
Last updated on NOVEMBER 19, 2016
Applies to:
Oracle SOA Suite - Version 11.1.1.7.0 and later Information in this document applies to any platform.
Symptoms
On : 11.1.1.7.0 version, B2B Engine
ACTUAL BEHAVIOR --------------- You are performing a simple pass-through test that receives and passes back out a Generic HL7 2.3 SIU Document type. In the message, if fields SCH-11.1, SCH-11.2, and SCH-11.3 are blank, and SCH-11.4 is filled, field SCH-11.4 shifts to field SCH-11.3. In the SSHI Console, the business message (XML document) shows the data in the correct field. But upon translation to the native document the field shifting occurs.
EXPECTED BEHAVIOR ----------------------- The native document should match the source XML document.
STEPS ----------------------- The issue can be reproduced at will with the following steps: 1. Create a pass-through SSHI application. 2. Send a 2.3.1 version SIU document with blank SCH-11.1, SCH-11.2, SCH-11.3 fields and a populated SCH-11.4 field. 3. Check wire document on outbound side to find the data in the SCH-11.4 field has shifted to the SCH-11.3 field.
Cause
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
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.
