Web Service NATIVETOXMLSERVICE Not Translating EDI Composite Data Correctly (Doc ID 1540544.1)

Last updated on NOVEMBER 19, 2016

Applies to:

Oracle B2B (Business to Business) - Version 11.1.1.6.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.1.1.6.0 version, EDI Protocol 

ACTUAL BEHAVIOR
---------------
When using the B2B web service NativeToXMLService to convert a native EDI document to XML, the composite element (C040) data is placed in Element-128.

EXPECTED BEHAVIOR
-----------------------
The composite data subelements should go in Element-128 and Element-127.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1) Go to http://localhost:8001/b2b/services in browser.
2) Then execute these steps:
- go to NativeToXMLService
- set transactionSetOnly = true
- set documentTypeName
- set documentProtocolVersion
- enter payload containing composite element (C040) data

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms