How To Use OAM To License JA (Asia/Pacific Localizations), JE (European Localizations), JG (Regional Localizations) and JL (Latin-American Localizations) in Oracle Applications ?

(Doc ID 351900.1)

Last updated on SEPTEMBER 26, 2017

Applies to:

Oracle Applications DBA - Version 11.5.9 to 12.0.5 [Release 11.5 to 12]
Oracle Financials for EMEA - Version 11.5.9 to 12.0.5 [Release 11.5 to 12]
Oracle Financials Common Country - Version 11.5.9 to 12.0.5 [Release 11.5 to 12]
Oracle Application Object Library - Version 11.5.9 to 12.0.5 [Release 11.5 to 12]
Oracle Financials for the Americas - Version 11.5.9 to 12.0.5 [Release 11.5 to 12]
Information in this document applies to any platform.
***Checked for relevance on 26-Aug-2014***
Application Install - Version: 11.5.9 to 12.0.5
Financials for EMEA - Version: 11.5.9 to 12.0.5
Financials Common Country - Version: 11.5.9 to 12.0.5
Financials for the Americas - Version: 11.5.9 to 12.0.5
Financials for Asia/Pacific - Version: 11.5.9 to 12.0.5
OAM
TABLE: fnd_product_installations
TABLE: AD_Bugs


Goal

How To Use The OAM To License JA (Asia/Pacific Localizations), JE (European Localizations),  JL (Latin-American Localizations) and JG (Regional Localizations) in Oracle Applications ?

Script output adutconf.lst shows that these products are not installed.

--> Product Installation Status, Version Info and Patch Level
    JA       Inactive       11.5.0   11i.JA.I
    JE       Inactive       11.5.0   11i.JE.J
    JL       Inactive       11.5.0   11i.JL.M  
    JG       Inactive       11.5.0   11i.JG.K

You also may run the following SQL*plus statement to achieve the above list:
--
SELECT application_id, patch_level, status
FROM fnd_product_installations
WHERE application_id in (101, 200, 222, 7002, 7003, 7004, 600, 275);
--

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms