Results for “okl_fnd_application_uv”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKL_FND_APPLICATION_UV is a read-only database view owned by the APPS schema and delivered as part of the OKL – Leasing and Finance Management product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The view presents a denormalized, driver-oriented list of Oracle EBS applications that have at least one registered key flexfield shorthand alias. Rather than exposing the entire FND_APPLICATION registry, it returns only those applications for which a row exists in FND_SHORTHAND_FLEX_ALIASES, thereby producing the set of applications that participate in the flexfield shorthand alias mechanism.

The suffix "_UV" denotes a user view, a common Oracle EBS convention indicating an object intended for customer-facing queries and integration rather than internal application processing. The view carries a VALID status in the data dictionary and is defined with a SELECT DISTINCT clause, guaranteeing that the reported application and flexfield code combinations are unique. Within the Leasing and Finance Management module, this view is typically joined to flexfield definition and value-set metadata to drive alias resolution during data entry, concurrent processing, or upstream/downstream integration that must map a short alias to its owning application and key flexfield.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through public synonyms resolved in the APPS schema:

• FND_APPLICATION – the Oracle Application Object Library registry of installed and registered EBS applications. It supplies APPLICATION_ID and APPLICATION_SHORT_NAME.
• FND_SHORTHAND_FLEX_ALIASES – the table that stores shorthand (brief) alias definitions associated with key flexfields. It supplies ID_FLEX_CODE and the APPLICATION_ID used to join back to FND_APPLICATION.

The join is an inner equijoin on APPLICATION_ID (FND.APPLICATION_ID = FNDSFA.APPLICATION_ID), so applications without any shorthand flex alias are excluded. Because the view is a pure projection over synonyms, it inherits the security and privileges of the caller against the underlying FND tables; no OKL-specific base table is directly referenced, which makes the view reusable across any module that needs the same application-to-flexfield mapping.

Key Columns

• APPLICATION_ID – Numeric primary identifier of the EBS application (from FND_APPLICATION). This is the standard foreign key used throughout FND and flexfield metadata tables.
• APPLICATION_SHORT_NAME – The short name (for example, SQLGL, AR, OKL) that uniquely identifies the application in profile options, concurrent program definitions, and flexfield qualifiers.
• ID_FLEX_CODE – The key flexfield code (for example, GL#, MCAT, CT#) for which shorthand aliases are registered against the application. Combined with APPLICATION_ID, it defines the granularity at which alias resolution should occur.

Because the view applies SELECT DISTINCT, consumers should treat the returned rows as a lookup set rather than a transactional record set; there is no alias value or description column exposed here, so obtaining the actual alias text requires an additional join to FND_SHORTHAND_FLEX_ALIASES.

Common Use Cases and Queries

Typical usage includes validating whether a given application supports shorthand aliasing, populating LOVs in custom leasing extensions, and diagnosing flexfield alias configuration issues where a user's shorthand entry cannot be resolved.

List all applications and flexfields that participate in shorthand aliasing:

• SELECT application_id, application_short_name, id_flex_code FROM apps.okl_fnd_application_uv ORDER BY application_short_name, id_flex_code;

Locate the flexfield code registered for a specific application, for example Leasing and Finance Management:

• SELECT application_short_name, id_flex_code FROM apps.okl_fnd_application_uv WHERE application_short_name = 'OKL';

Join the view to FND_APPLICATION to confirm display names or to FND_SHORTHAND_FLEX_ALIASES to retrieve the actual alias values for a chosen application and flexfield. Because the view is a thin projection over FND base tables, query performance depends largely on the indexes on FND_APPLICATION and FND_SHORTHAND_FLEX_ALIASES; filtering by APPLICATION_ID or ID_FLEX_CODE is recommended in high-volume integration jobs.