Oracle Fusion Technical

Applications Object Library (AOL)

AOL Concepts (Applications Object Library) is a foundational framework within Oracle
Applications. It encompasses various components and functionalities that support the development,
management, and security of applications.

AOL encompasses a wide range of components that are essential for the development and
operation of Oracle Applications.
Here are some of what it includes:
1. Value Sets:

Define acceptable values for data fields to ensure data consistency and integrity
2. Lookups:
Define lists of values for specific fields, enabling users to select from predefined options.
3. Flexfields:
▪ Descriptive Flexfields (DFFs): Customizable fields to capture additional information.
▪ Key Flexfields (KFFs): Structured fields for unique identifiers.

Value sets
A value set is a uniquely identifiable set of valid concept representations, where any concept
representation can be tested to determine whether or not it is a member of the value set. A value set
is typically used to represent the possible values of a coded data element in an information model.
Create Value sets
▪ In the Setup and Maintenance work area, use the search bar to find "Manage Value Sets".
▪ Click on the Create button.

▪ Enter the Name and Description for the value set.

▪ Select the Type of value set you want to create (e.g., Independent, Dependent, Table, etc.).
 Types of Value sets

▪ Format Only Valueset

The format only validation type enables end users to enter any value, as long as it meets your
specified formatting rules. That is, the value must not exceed the maximum length you
define for your value set, and it must meet any format requirements for that value set.
Independent Value set : Used to validate input against a list that isn't stored in an application
table, and not dependent on a subset of another independent value set.
▪ Dependent Valueset
The available values in a dependent list and the meaning of a given value depend on which
value was selected for the independently validated segment. For every independent value
from parent value set, we can add one/many values in the dependent value set. For example,
the valid holidays depend on which country you are in
▪ Subset Valueset
Used to limit the list of values based on a valueset. However instead of creating a new
valueset, we can re-use the existing independent valueset for values and choose the values
that you want to create for the subset valueset.
▪ Table Valueset
Used when the values you want to use are already maintained in an application table, such as
a table of vendor names. Specify the table column that contains the valid value. You can
optionally specify the description and ID columns, a WHERE clause to limit the values to
use for your set, and an ORDER BY clause.

For more details

https://www.youtube.com/watch?v=4Sy0-9yeKzc
Use Cases for Valuesets
• All types of Valuesets can be used to validate the data for the flex field segments (DFF, EFF and
KFF),
• Only Table type Valuesets are used to get data from the application tables and then they can be used
in the fast formulas when there are NO database items defined.
• Only Table type Valuesets are used to get data in HCM Extracts when database items are not
defined.
Lookups
Define Lookups
Lookups are containers for the list items that appear in an application. Users select one of the items
from such lists to enter a value on the application UI.

Categories of lookups / Types of Lookups

Lookup Type Description

Standard Lists the available codes and translated meanings.

Set-enabled Associates a reference data set with the lookup codes.

Common Legacy lookups or lookups that have attributes.

What is the difference between Standard Lookups and Common Lookups

▪ Standard Lookups: Predefined by Oracle, used for consistent application values, limited
customization.
▪ Common Lookups: Custom-defined by users, used for unique business needs, fully
managed by the organization.
To add a lookup type
▪ Select Common Setup > Lookups.
▪ On the Lookup Types page click Add for the Lookup Type grid.
Lookup Element Description

Lookup Type A lookup type is a static list of values users view to make
entries in the application. The application references a
lookup type to display its list of values.

Lookup Value A lookup value is a single item contained within a lookup

type. For example, Paid is a lookup value for the Fee
Status lookup type. Lookup types typically contain
numerous lookup values.

▪ On the Lookup Type Details page, enter these values

• Lookup Type (The value you enter must be uppercase and can’t begin with
the prefix ORA_, which is used to distinguish your custom lookup types from
delivered lookup types.)
• Meaning
• Module
• Description
Page Element Description

Lookup Type Identifies the lookup type within the application.

Application Identifies the application that uses the lookup type. For example, Permits, Common
Components, and so on.

Meaning The actual UI display name used to represent the list of values contained in the lookup type.

Configuration Level Indicates at what level the lookup can be modified. Options are:
• System: Only Oracle development teams can modify lookup types at this configuration
level.
• Extension: Customers can perform minimal tasks, such as add lookup values.
• User: Customers can add lookup values, delete lookup values, update the meaning, and
update the description.

Working with Configuration Levels

The configuration level attribute determines who can modify a lookup type and what can be modified.

Task User Extension System

Add a lookup type Yes No No

Delete a lookup type Yes No No

Modify lookup type meaning Yes No No

Modify lookup type description Yes No No

Add lookup values Yes Yes No

Delete lookup values Yes (if you created it) Yes (if you created it) No

Modify lookup value attributes Yes (except for Yes (if you created it, and No
Lookup Code) except for Lookup Code)
Page Element Description

Module The internal application module using the lookup type, such as Billing Entry, Billing Setup, and
so on.

Description Identifies the purpose and use of the lookup type.

▪ Click Add for the Lookup Value grid for each lookup value you need to add to the lookup
type.

Page Element Description

Lookup Code An internal application code for each lookup value that is not visible to
users. It is typically a shorter, less user-friendly representation of the item.
For example, ORA_DRIVER_LIC for State Driver’s License, or LEN for
Length, if listing units of measurement.
Note: Lookup lists created in the designer for user-defined fields on an
intake form begin with PSC.

Display Sequence Control in what sequence the lookup value appears in the list displayed to
users, where 2 appears above 3. If you do not specify a sequence, the
application displays the items in the order they were entered.
 Page Element Description

Enabled Turn on to make a lookup value active. If a lookup value is not enabled, then
the application does not display it to the end user in the list of values for that
lookup type.
Note: It is not recommended to disable lookup values once your
implementation is in production because this can invalidate existing
transaction data.

Start Date Set a start date for the lookup value to become active. Even if the lookup
value is enabled, if a start date is set, the application does not display the
lookup value until the start date is reached.

End Date Set an end date for a lookup value to no longer be displayed in a list of
values.

Meaning The display name for the lookup value. End users see this value in the list of
values displayed at run time. They do not see the Lookup Code value.

Description Provide any additional information to help identify the purpose of the lookup
value or clarification regarding what it represents.

Tag Tags allow you to add a label to your lookup codes. A tag can be used to
categorize lookups based on facilitating searches or guiding how a lookup
should be used.

▪ Click Save.

Example of a Standard Lookup

https://docs.oracle.com/en/cloud/saas/applications-common/24a/facia/example-of-a-standard-
lookup.html#s20030151
Create an ESS with Parameters using Lookup
▪ Create Lookup

Login to your Oracle Cloud ERP instance and navigate to Setup and Maintenance and from the
Task List click on Search.

▪ Search with Manage Common Lookups.

▪ Click on the search result. This will take us to the Manage Common Lookups page,
where we will create the Lookup and add Lookup Values.
▪ Click on the + icon to create the Lookup.
 ▪ Add the details for the Lookup as per the table below.
Lookup Type XXRM_OBJECT_OWNER_LKP
Meaning XXRM_OBJECT_OWNER_LKP
Description List of Object Owners
Module Application Toolkit
Lookup Configuration Level User
[Default]
REST Access Secured Secure

▪ Click Save. This will enable the section to add the Lookup Values. Click on the + icon to
insert the values for the lookup.

▪ Add the Lookup Value and click Save. Repeat this step for each Lookup Value that you
want to add. I have added a few Lookup Values as shown in the screenshot below:

▪ Once you are done with adding the Lookup Values, click on Save and Close. You have
successfully created the Lookup. Next step is to create the List Of Values.
 ▪ Create List Of Values

To create the List Of Values, navigate to Setup and Maintenance and from the Task List click
on Search. Search with Manage%Enterprise%Scheduler%. In my last post I had created the
ESS Job under ‘Manage Enterprise Scheduler Job Definitions and Job Sets for Financial,
Supply Chain Management, and Related Applications‘. I select the same here.

▪ Now, navigate to the Manage List of Values Sources tab.

▪ Click on the + icon to create the List of Values Source.

▪ Fill up the details as per the table below:

Application Name Application Toolkit
User List of Values Source Name XXRM_OBJECT_OWNER_LOV
Description XXRM_OBJECT_OWNER_LOV
LOV Type Predefined
List of Values Source Definition Name oracle.apps.fnd.applcore.lookups.model.publicView.CommonLookupPVO
 ▪ Once you have filled in the details click on Save and Close.

▪ Attach the List of Values to the Parameter of the ESS Job

Navigate to the Manage Job Definitions page and search for the Job XXRM Test Object List
Report, which we created earlier. Click the Edit button.

When the ESS Job window pops up, click on the Edit button in the Parameters section.

When we created the parameter earlier, we created it as a Text Box. We’ll now change it to List
of Values.
 ▪ Once you select List of values as the Page Element, select the List of Values Source
– XXRM_OBJECT_OWNER_LOV, that we created in Step 4, from the list.

Select LookupCode as the Attribute. In Display Attributes section, I want

the LookupCode to be displayed in the LOV, so I will select LookupCode from the list of
available attributes and move it to the right, as shown in the screenshot below. If you want to
display any other attributes, please follow the same process. Click Save and Close.
 ▪ Click on the Manage Dependencies icon to open up the Manage List of Values
Dependencies page.

▪ Select ByLookupType as the View Criteria. This will enable the Bind Variables section.

Insert the lookup type, we created – [ XXRM_OBJECT_OWNER_LKP ], within single

quotes [ ‘ ], as the Default Value. Then click OK. Then Save and Close the ESS Job.
 ▪ Submit the ESS Job

Now we are all set to execute the ESS Job. To submit the job, navigate to Tools > Scheduled
Processes. Click on Schedule New Process. You should be able to see all the Lookup Values we
configured in the parameter of the ESS Job, in form of a LOV.

▪ Select any value from the LOV and click on Submit. Here, I select FUSION_SEED.
▪ Request Id is displayed. Note down the Request ID. Wait for the job to complete
successfully. Once the ESS Job succeeds, view the output to confirm that the records are
fetched based on the object owner we selected as the parameter.

For More details

https://www.youtube.com/watch?v=RXMEnfkVn1Y
Import Lookups
https://www.youtube.com/watch?v=hvtgCpzm88M
https://www.youtube.com/watch?v=wJYSA78CeOE
https://www.youtube.com/watch?v=21A1XDrZbAU

File Format for Importing Lookups

https://docs.oracle.com/en/cloud/saas/applications-common/24a/facia/file-format-for-importing-
lookups.html#s20055910

What's the difference between a lookup type and a value set?

Area of Difference Lookup Type Value Set

List of values Static Dynamic if the list is table-

validated

Validation of values One to one match of meaning to Validation by format or inclusion

code included in a lookup view, or in a table
through the determinant of a
reference data set

Format type of values char varchar2, number, and so on

Length of value Text string up to 30 characters Any type of variable length from
1 to 4000

Duplication of values Never. Values are unique. Duplicate values allowed

Management Both administrators and end-users Usually administrators maintain

manage these, except system these, except some product
lookups or predefined lookups at flexfield codes, such as GL for
the system configuration level, Oracle Fusion General Ledger
which can't be modified. that the end-users maintain.
Flexfields
▪ Flexfields are place holder fields associated with a specific business object.
▪ They are designed for customers to store additional data in our application with no coding
changes.
▪ Each business object has been enabled with a list of flexfields which can be configured to
have additional fields listed on the business object.

There are three types of flexfields

▪ Descriptive flexfield (DFF)
▪ Extensible flexfield (EFF)
▪ Key flexfield (KFF)

Descriptive flexfield
▪ DFF has the flexibility to capture customers specific information if there is no standard field
to capture such information.
▪ DFF’s are stored in attributes on the same business object base table, 15 date,20 number
and 50 character attributes columns are reserved for the DFF’s data in each base table.

DFF’s have two different type of segment

▪ Global: A global segment is basically those segments in DFF that is available throughout the
enterprise.
▪ Context-sensitive fields: A context sensitive segment is a segment that may or may not
appear depending upon what other information is present in your form.

Add Descriptive flexfield

▪ Search for "Manage Descriptive Flexfields."
Extensible flexfield
▪ An EFF is similar to DFF but with the following additional features
▪ Attributes are grouped into contexts ( or information categories ) so they will always be
presented together in the user interface.
▪ Values are stored in a separate database record related to a specific business object, like job
or person and this gives you greater flexibility
▪ You can define as many contexts as you want without any limitation
▪ You can define a multi row context in case of one to many relationship use cases
Key Flexfield
▪ Key flexfields are configurable multi-part intelligent keys , where each element of the key
may be individually meaningful, as well as the combination of a whole.
▪ For example General Ledger accounts. Accounting flexfields consists of various segments
such as company code , cost center, account , product line and sub account.
▪ In fusion HCM, KFF’s are only used for People Group and Cost allocation.

How to Call Value Set in DFF

▪ Search with person .
▪ Click on person attributes
▪ Edit person page.
▪ Here we call our value sets in DFF.
▪ Give dff name code and API name will be taken automatically.

▪ Here you can search value set which you want to call in DFF.
▪ Select value set and click on OK.
▪ Similarly you can cal another valuesets .
▪ Click on Navigator.>> My Client Groups >> Person Management>> Search for the person
>> Click on person.
▪ Fusion_Format only DFF is free text button here you can enter anything.
▪ Fusion_Independent is one of value set here you can see our independent value set.

▪ Here we can select India , under india we created two dependent values.
▪ If we can select US We can see below States.

▪ By using of subset we can restrict value sets . Here we can see our subset.
 ▪ Fusion_Table here we can see ten person numbers .

In table value set we wrote where condition “ rownum<=10”

That’s why it shows tem employees.