My Oracle Support Banner

B2B Inbound messages containing Japanese characters are not translated correctly (Doc ID 2372602.1)

Last updated on MARCH 27, 2019

Applies to:

Oracle SOA Suite - Version 11.1.1.7.8 to 11.1.1.7.8 [Release 11gR1]
Information in this document applies to any platform.

Symptoms

On : 11.1.1.7.8 version, B2B Runtime

Customer is using B2B 11.1.1.7.8 to process inbound positional flat files.
When the file is processed, B2B marks the file as complete but the files are
not translated correctly from wire message to application message.

The generated application message contains following :
The Application message contains certain elements that are not correctly translated.

For example :

<Field-WholesalerDepotCodeL1>Sï½</Field-WholesalerDepotCodeL1>
<Field-OrderDateL1>² 1801</Field-OrderDateL1>

<Field-OrderDateL2>S 1801</Field-OrderDateL2>

Expected value : <Field-OrderDateL1>180115</Field-OrderDateL1>

The issue is not only for orderDate but for other elements also.

This issue occurs after 11.1.1.7.8 bundle patchset is applied.

 

Changes

 

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!


In this Document
Symptoms
Changes
Cause
Solution
References


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