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

Last updated on OCTOBER 13, 2022

Applies to:

Goal

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_id 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 site is shared among different operating units.

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

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

Solution

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