NLS Language (For European Language) passed in SOAP Header is Not Set Correctly Integrated SOA Gateway (ISG) Webservices Correct (Language Code is Not Selected When Setting the Apps Context)
Last updated on OCTOBER 17, 2017
Applies to:Oracle E-Business Suite Integrated SOA Gateway - Version 12.1.3 to 12.1.3 [Release 12.1]
Oracle E-Business Suite Integrated SOA Gateway - Version 12.2.3 to 12.2.6 [Release 12.2]
Information in this document applies to any platform.
Oracle E-Business Suite Integrated SOA Gateway on EBusiness Suite 12.1.3
Oracle E-Business Suite Integrated SOA Gateway on EBusiness Suite 12.2.x
When invoking the ISG SOAP Webservice from the SOAPUI for a European Language (like German , French etc.), the proper language code is not selected when setting the Apps Context.
The default apps context is instead set to Base Language installed for the Instance.
Steps to Reproduce:
Case (a): When testing this same package from the SQL Developer it picks the language code as German and shows the output
Case (b): When tested from the third party tool, by using a JDBC Connectivity and invoking the package -- This also shows the value as D in response
D is the Language Code for German
Case (c): When this same API is exposed as ISG Service and called from SOAPUI
Inspite of sending the Language Code as German, internally it appears to use US and the code returned in Output is showing as US instead of D
ISG Webservices should return the language Code as "D" (i.e. German) when Language Passed is German
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