My Oracle Support Banner

Ability To Store Language For Customer At Org Level (Doc ID 402398.1)

Last updated on JULY 12, 2017

Applies to:

Oracle Receivables - Version: 11.5.10
Information in this document applies to any platform.
ARXCUDCI - Customers Standard


Starting from Bug 5001497, the table hz_cust_acct_sites_all.language column is obsolete.
Language is now stored in HZ_LOCATIONS table.

The problem is that HZ_LOCATIONS is not org driven.
The TRM states that the language column stores the operational language for the locations.

So this is fine when each site has its own location.

This is not always the case especially when the account is shared among different operating unit.

For printing issues, when you have multi language installed, you need to store the preferred language by operating unite in order to print only in the language of the operating unit (otherwise, MLS function spawns the report in all available language).

So in the case where different operating units share the same location, the choice of the language per operating unit is not possible anmyore as HZ_LOCATIONS is not org_id driven.

This is a regression for the customer.



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

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