Skip to main content

Understanding Oracle E-Business Suite Localizations





Globalization is the process of designing and deploying software that meets the needs of a global enterprise via Internationalizations, Translations and Localizations. While Internationalization and Translations involve national language support and UI translation strategies, Localizations focuses on the business processes to meet the statutory, legal, and cultural practices of a given locality. In Oracle E-Business Suite, this is achieved through national and regional extensions called "country-specific functionalities" or "Localizations". Because localization functionalities are all compatible with each other, installation of all required country-specific functionalities results in a globalized implementation.

An example of localization is the adjustment of the standard financials functionality of Oracle E-Business Suite to suit the legal and tax requirements for each country. The localized functionality is described in theCountry-Specific Financials User Guide for each region.
There are 3 types of Localizations:
    • Product Localizations: Delivered in the standard product by Oracle Applications Development
    • Add-on Localizations: Delivered by the Regional Field Centers (Add-on Localization Teams) via My Oracle Support
    • Partner Localizations: Delivered by partners including ISVs and system integrators

Product Localizations

Product Localizations are standard product features and are installed when you run Rapid Install. You simply need to license those you wish to use; this can be achieved from Rapid Install during the initial install, or from License Manager in Oracle Application Manager at a later stage. Some countries do not have Product Localization features either because the standard product is able to meet the local requirements, or because those requirements are beyond the scope of our current Product Localizations offering.
Product Localizations are available for Asia Pacific, Europe,Americas, China and India. They are divided into four main categories:
    • Regional Localizations (JG)
    •  Asia/Pacific Localizations (JA)
    •  European Localizations (JE)
    • Latin America Localizations (JL)
In general, the legal requirements apply to countries located on a particular region. Those functionalities are included in the localizations available for the region where the country is located. For example, if you want to install the localization for Argentina, then Latin American Localizations (JL) will be activated, In addition, there are other legal requirements that are common for several countries. Those "shared functionalities" are included in the Regional Localizations (JG). JG is automatically activated for any country that require localizations.
The main sources of information for Oracle E-Business Suite Localizations are:

Add-on Localizations

Add-on Localizations are additional localizations delivered by regional field centers. They are installed as extensions to the standard product and may require special configuration instructions.This type of localizations can't be activated from Rapid Install nor License Manager. Instead, they are installed via special patches and manual steps posted in My Oracle Support articles. Add-on localizations are available to all customers at no additional cost and are considered as "Service Deliverables". Add-on localizations are released on a country by country basis.
Please consult the following document for more information:
    • 429042.1: Introduction to Add-On Localizations for R12
Note: If a country is listed in the above note, then it is assumed that Add-On Localizations are available for that country.

Partner Localizations

Partner Localizations are delivered by partners including ISVs and system integrators. This type of localizations are not activated or maintained by the standard products included in Oracle E-Business Suite. Please contact your local partner for additional information.


SUMMARY

Country-specific functionalities provide the required business processes to meet the statutory, legal, and cultural practices of a given locality.
There are three types of localizations:
    • Product Localizations: Delivered in the standard product by Oracle E-Business Suite Development
    • Add-on Localizations: Delivered by the Regional Field Centers (Add-on Localization Teams) via My Oracle Support
    • Partner Localizations: Delivered by partners including ISVs and system integrators
These three types of localizations are activated differently in Oracle E-Business Suite. Only Product Localizations can be activated via Rapid Install or License Manager. Add-on Localizations are installed via special procedures created by the regional teams and partners.

Comments

Post a Comment

Popular posts from this blog

General Ledger FAQ

1.  What responsibility should I use when doing the set up for General Ledger? Use a seeded responsibility like 'Oracle General Ledger Super User'. You may also need to use the System Administrator responsibility. 2.  What are the pre-requisites required to define a new calendar? According to your business needs you need to decide the calendar type required i.e. monthly, weekly or biweekly, the number of periods, adjusting periods and the maximum number of periods within a fiscal year. 3. What are the pre-requisites required to define a new Ledger? Define a Calendar, Chart of Accounts and enable the functional Currency  and convention of subledger accounting method. 4. Why must I check the calendar definition before assigning to a Ledger? The calendar definition cannot be changed once it is assigned to a set of books so it is very important to check that the calendar definition is suitable to the specific business needs, has ...
Post a Comment
Read more

Difference Between MTS, ATO, MTO ,PTO ,CTO and ETO.

 Make-to-stock (MTS) In MTS environments, products are created before receipt of a customer order. Customer orders are then filled from existing stock, and then those stocks are replenished through production orders. MTS environments have the advantage of decoupling manufacturing processes from customer orders. Theoretically, this enables customer orders to be filled immediately from readily available stock. It also allows the manufacturer to organize production in ways that minimize costly changeovers and other disruptions. However, there are risks associated with placing finished goods into inventory without having a firm customer order or an established need. These risks tend to limit MTS environments to simple, low-variety, or commodity products whose demand can be forecasted readily.  Assemble-to-order (ATO) In ATO environments, products are assembled from components after the receipt of a customer order. The key components in the assembly or f...
Post a Comment
Read more

Accounting entries in Oracle Purchasing and Payables

This document gives in detail different accounts used and the accounting impact of various transactions that take place in Oracle Purchasing and Oracle Payables. Both Standard costing and Average costing methods are considered. The accounts are Oracle Applications specific and might differ from the conventional accounting names. Examples are given wherever required for better understanding of the concept. The sources of these accounts are given. PURCHASING:  Receiving – For Accrual Process for perpetual Accruals Receipts for inventory purchases are always accrued upon receipt. And also use perpetual accruals for expense purchases you want to record uninvoiced purchase liabilities immediately upon the receipt of the expense goods. Receiving Account (Receiving Account) To record the current balance of the material in receiving and inspection. Where to define in Apps: Define Organization           ...
Post a Comment
Read more