Results for “view_application_name”

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

Overview

OKE_TERMS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the OKE – Project Contracts product family. It presents a denormalized, user-readable projection of contract terms and conditions, joining the base terms entity to its translations, term type definitions, and the lookup and application reference data that govern how each term is classified and rendered. Because contract terms are stored in normalized _B / _TL table pairs, direct queries against the base tables require multiple joins and language-handling logic. OKE_TERMS_V encapsulates that logic, exposing a single flattened row per term for the session language.

In EBS 12.1.1 and 12.2.2 the view carries a VALID status and is treated as a stable integration surface. Its principal reporting value lies in the fact that it resolves the VIEW_APPLICATION_ID foreign key into human-legend APPLICATION_SHORT_NAME and APPLICATION_NAME values, and resolves LOOKUP_TYPE into a descriptive LOOKUP_TYPE_NAME. This is precisely the context in which searches for "view_application_name" arise: consumers are looking for the column that identifies which Oracle application owns or scopes a given contract term, and OKE_TERMS_V provides that through the APPLICATION_NAME column rather than forcing a manual join to FND_APPLICATION_VL. The view is therefore commonly used in Project Contracts reporting, contract template analysis, and downstream integrations that need term metadata without navigating the OKE base schema.

Underlying Base Objects

The documented 12.2.2 metadata identifies five referenced objects. OKE_TERMS_B and OKE_TERMS_TL are accessed as synonyms and supply the core term rows and translated name/description respectively. OKE_TERM_TYPES_V, itself a view, supplies the term type name. FND_APPLICATION_VL and FND_LOOKUP_TYPES_VL are the Applications foundation views that supply application and lookup reference data. The view text is notable for two behaviors:

• The translation join on OKE_TERMS_TL is an inner join filtered by T.LANGUAGE = USERENV('LANG'), so only the current session language row is returned.
• The joins to OKE_TERM_TYPES_V, FND_APPLICATION_VL and FND_LOOKUP_TYPES_VL are all outer joins (marked (+)), meaning terms without a term type, an owning application, or a lookup type still return a row, with the corresponding descriptive columns null.

This outer-join pattern is important: it guarantees that every active term definition is visible even when its classification references are incomplete, which supports data-quality auditing as well as normal reporting.

Key Columns

The view projects the standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) plus a ROW_ID pseudo-column for row addressing. The business columns are:

• TERM_CODE — the primary business key of the term, shared between the _B and _TL rows.
• TERM_NAME and DESCRIPTION — the translated name and description for the session language.
• TERM_TYPE_CODE and TERM_TYPE_NAME — the term's type and its readable name from OKE_TERM_TYPES_V.
• USER_DEFINED_FLAG — indicates whether the term was seeded by Oracle or user-defined.
• VIEW_APPLICATION_ID — the application identifier that scopes the term.
• VIEW_APPL_SHORT_NAME and VIEW_APPLICATION_NAME — the short name and full application name resolved from FND_APPLICATION_VL; these columns directly answer the "view_application_name" query intent.
• LOOKUP_TYPE and LOOKUP_TYPE_NAME — the lookup type code and its translated description from FND_LOOKUP_TYPES_VL.

Common Use Cases and Queries

Typical scenarios include enumerating the terms available to Project Contracts, filtering user-defined versus seeded terms, and auditing which application owns each term. A representative query listing terms with their owning application is:

• SELECT term_code, term_name, term_type_name, view_application_name FROM oke_terms_v ORDER BY term_name;
• SELECT term_code, term_name FROM oke_terms_v WHERE user_defined_flag = 'Y';
• SELECT view_application_name, COUNT(*) FROM oke_terms_v GROUP BY view_application_name;

Because OKE_TERM_TYPES_V is itself a view over the term type base tables and FND_APPLICATION_VL is a translated view, the join depth should be considered when tuning high-volume extracts. For integration purposes, exposing VIEW_APPLICATION_NAME removes the need for consumers to join FND_APPLICATION_VL directly.