Oracle® EMEA Add-on Localizations

Approach document for Localization Descriptive Flex Fields and

Forms invoked from Actions/Tools Menu
Release 12.2
March - 2014
Oracle EMEA Add-on Localizations Approach document for Localization Descriptive Flex Fields and
Forms invoked from Actions/Tools Menu, Release 12.2
Part No.

Copyright © 2009, 2011, Oracle and/or its affiliates. All rights reserved.

Primary Author: Gopi Krishna Reddy Julakanti

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their
respective owners.

This software and related documentation are provided under a license agreement containing restrictions on use and
disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or
allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit,
perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation
of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any
errors, please report them to us in writing.

If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S.
Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS

Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers
are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition
Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and
adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to
the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19,
Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA
94065.

This software or hardware is developed for general use in a variety of information management applications. It is not
developed or intended for use in any inherently dangerous applications, including applications that may create a risk of
personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all
appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates
disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

This software and documentation may provide access to or information on content, products and services from third
parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with
respect to third party content, products and services. Oracle Corporation and its affiliates will not be responsible for any
loss, costs, or damages incurred due to your access to or use of third party content, products or services.
 Approach to Enable/Disable E-Business Suite EMEA Add-on Localization Descriptive FlexFields and
EMEA Add-on Localization Forms from actions/tools.

In this document the acronym CLE stands for EMEA Add-on Localizations.

This Document explains how CLE:Localization DFF’s and CLE forms which are accessed from Actions/Tools menu
are used from release 12.2.

1. Profile options to be set to enable/disable Localization DFF menu and Form menus which are accessed from Actions.
2. Approach to Enable/Disable LDFF and CLE Forms which are accessed from tools menu using forms personalization.

1) Profile options to be set to enable/disable Localization DFF menu and Form menus which are accessed from Actions/Tools menu.

System Profile Options

Profile ‚CLE: Enable EMEA Add-on Localization Menu‛ has to be set to ‚Yes‛ or ‚No‛. This provides flexibility to customers to enable or not
LDFF. If customer uses the localizations, then the related LDFF need to be enabled.

The profile option will as well enable, under ‚Actions‛, the related menu items which give access to the LDFF Forms.

2) Approach to Enable/Disable LDFF and CLE Forms which are accessed from Actions/Tools menu using forms personalization.

Enable /Disable LDFF based on Non-Org specific forms.

Enabling/Hiding of LDFF’s based on Non-Org Specific forms depend on 2 Profiles ‚JG:Territory‛ and ‚CLE: Enable EMEA Add-on
Localization Menu‛

Example:
Scenario 1.
LDFF is enabled when ;
 JG:Territory Profile is set to country for which context is present and
 Profile CLE: Enable EMEA Add-on Localization Menu is set to ‘Yes‛

For example, LDFF CLE: Assets Addition information is enabled / disabled (visible/hidden) based on Profiles ‚JG:Territory‛ and ‚CLE: Enable
EMEA Add-on Localization Menu‛ profiles.

Set up profile JG:Territory to the Country for which the context is defined (In this example context for RU is defined for the LDFF ) and setup
profile CLE: Enable EMEA Add-on Localization Menu to ‘Yes’

In the below screen ,context is defined for RU which is considered for the example in next scenario
We see that the Profile JG:Terriotry is set to the country for which context is present (In this case Russian Federation for which the country code
is ‘RU’)

Profile option ‚CLE: Enable EMEA Add-on Localization Menu‛ is set to ‘Yes‛ at the site level( This profile can be set at site level or
responsibility level or Application level or user level).Let us take an example by setting this profile at site level.

As per the scenario LDFF should be enabled and in this case you can see below that the LDFF is enabled in Tools.

Scenario 2:
a)LDFF is disabled when
 Profile JG:Territory is set to other country for which context is not defined and
 CLE: Enable EMEA Add-on Localization Menu profile to ‘Yes’

b) LDFF is disabled when

  Profile JG:Territory is set to country for which context is defined and
 CLE: Enable EMEA Add-on Localization Menu profile to ‘No’

c) LDFF is disabled when

 Profile JG:Territory is set to other country for which context is not defined and
 CLE: Enable EMEA Add-on Localization Menu profile to ‘No’

Screen shots for case a)

 JG:Territory is set to other country for which context is not defined

 CLE: Enable EMEA Add-on Localization Menu profile to ‘Yes’

Screenshots for case b)

 JG:Territory is set to country for which context is defined

 CLE: Enable EMEA Add-on Localization Menu profile to ‘No’

Screenshots for case c)

 JG:Territory is set to other country for which context
  CLE: Enable EMEA Add-on Localization Menu profile to ‘No’

You can see that for all the above 3 combinations of profiles (scenario2)the LDFF is disabled (In this case as this LDFF is the only one which is
present in Tools menu, Complete Tools menu is disabled).

LDFF’s on Org Specific Forms:

These LDFF’s will be visible and enabled or hidden) based on Org_id(Operating Unit) and CLE: Enable Localization DFF profiles.

Let us take the example of CLE:Additional information on Invoice which is based on Invoice form(Org Specific Form).
There is no context defined for Russia (RU) on LDFF ‚CLE:Additional information on Invoice ‚ so the LDFF menu in Action is hidden (Action
menu itself is disappeared as there are no other menus exists in Action )

Scenario 1:
When
 Operating unit is Hungary and the context is present for Hungary and
  CLE: Enable EMEA Add-on Localization Menu profile is set to ‘Yes’
then the LDFF CLE:Additional Info on Invoice is enabled in Actions.

In the screenshot you can see the contexts for the countries that are defined.(In our case we are taking an example of to Hungary HU.CLE_VAT
context )

 Profile CLE: Enable EMEA Add-on Localization Menu is set to ‘Yes’

 Operating Unit is Vision Hungary and you can see that the LDFF in Enabled as per scenario1
Scenario 2:

a)LDFF is not enabled when

 context is not defined for the operating unit and
 Profile CLE: Enable EMEA Add-on Localization Menu is set to ‘Yes‛

b) LDFF is not enabled when

 Context is defined for Operating Unit and
 Profile CLE: Enable EMEA Add-on Localization Menu is set to ‘No’

c) LDFF is not enabled when

 Context is not defined for the operating unit and
 Profile CLE: Enable EMEA Add-on Localization Menu is set to ‘No‛
Here you can see the Profile CLE: Enable EMEA Add-on Localization Menu set to ‘Yes’ but context is not defined for Operating Unit country
(RU) .So, LDFF menu is diabled (Actions is hidden).

Screenshots for case a)

 When context is not setup for Russia but CLE: Enable EMEA Add-on Localization Menu is set to ‘Yes’

Screesnshots for case b)

 When context is setup for Russia but CLE: Enable EMEA Add-on Localization Menu is set to ‘No’
Screenshots for case c)
 When context is not setup for Russia and CLE: Enable EMEA Add-on Localization Menu is set to ‘No’
To Enable CLE Forms accessed from Actions/Tools menu:

CLE forms which are accessed from Action will be visible and enabled/hidden based on profile options ‚JG: Territory‛ and ‚CLE: Enable
EMEA Add-on Localization Menu‛

Scenario 1)
CLE Form is enabled when
 JG:Territory Profile is set to the country for which this feature was implemented and
 CLE: Enable EMEA Add-on Localization Menu Profile is set to Yes.

Let’s take an example of existing personalization for CLE form (CLE: AP Multi-period Deferred Cost Schedule) on Invoices Workbench for our
scenario.

 Profile JG: Territory is set to Poland for which this feature is implemented for.

 Profile CLE: Enable EMEA Add-on Localization Menu is set to ‘Yes’

As per our scenario you can see that the CLE form is enabled in Actions

Scenario 2)

a) This form should not be enabled when

 JG:Territory profile is set to a country for which thisfeature is not implemented and
 CLE:Enable Localization feature is set to ‘Yes’

b) This form should not be enabled when

 JG:Territory profile is set to country for which this feature is implemented and
 CLE:Enable Localization feature is set to ‘No’

c) This form should not be enabled when

 JG:Territory profile is set to a country for which this feature is not implemented and
 CLE:Enable Localization feature is set to ‘No’

Screenshots for case a)

 JG:Territory Profile is set to Russia for which this feature is not implemented
  CLE: Enable EMEA Add-on Localization Menu is set to ‘Yes’

Screenshot for case b)

 JG:Territory Profile is set to Poland for which this feature is implemented

 CLE: Enable EMEA Add-on Localization Menu is set to ‘No’

Sceenshot for case c)

 JG:Territory Profile is set to Russia for which this feature is not implemented
  CLE: Enable EMEA Add-on Localization Menu/Actions is set to ‘No’

For all the 3 cases in scenario 2, we can see the result in the below screenshot, the menu ‚CLE: AP Multi-period Deferred Cost Schedule‛ is not
displayed.