Menu

OAUG News Blog

Let's Talk Localizations

The CSC will provide updates on localizations via this blog. In the meantime, there are helpful resources on the Oracle website.

The OAUG Customer Support Council participated in two sessions during COLLABORATE 18 concerning the issues and challenges that localizations present during the course of the E-Business Suite (EBS) life cycle. Also participating in the sessions were the OAUG Multi-National Special Interest Group (SIG), chaired by Hans Kolbe, and Oracle, represented by Brandy Robert and David Heisler. During the conference sessions, we were able to collect a variety of pain points that Oracle has agreed to address in the near future. Some of these include:

  • Improvement of the documentation in the patching readme files as well as the implementation guide.
  • EBS ugrades and new installation of localizations require the use of downtime mode in release 12.2.X
  • The lack of user guides in languages other than English.
  • Extending patch wizard to work with localization patching.
  • Some localizations do not work well with others.
  • Localizations sometimes override properly installed customizations.
  • Many localization packs are not consistently cumulative and the documentation does not properly address this.

We welcome feedback from our user community via the Customer Support Council. Please provide your additional ideas or concerns by commenting here in this blog, or email.


Joseph Imbimbo is an Oracle Applications DBA at PPG Industries. He also serves on the OAUG Board of Directors and OAUG Customer Support Council.  

Oracle Reaffirms Commitment to EBS Customers
New EBS Person Data Removal Tool from Oracle
 

Comments 2

Joe Wall on Thursday, 28 June 2018 06:33

In the broadest sense , the localization reports , since sometimes the companies requirements should also be included. So the reporting tool should be able to do soft customizations, so that when an upgrade or patch happens it does not affect the report. my guess is that Oracle should try an build a customization table that contains more that 15 flex fields , where by any country/company can add additional requirements

In the broadest sense , the localization reports , since sometimes the companies requirements should also be included. So the reporting tool should be able to do soft customizations, so that when an upgrade or patch happens it does not affect the report. my guess is that Oracle should try an build a customization table that contains more that 15 flex fields , where by any country/company can add additional requirements
David Heisler on Thursday, 28 June 2018 07:37

Following

Following
Already Registered? Login Here
Guest
Monday, 19 November 2018