Results for “oke_termtype_avail_v”

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

Overview

OKE_TERMTYPE_AVAIL_V is a PL/SQL view owned by the APPS schema within the Oracle E-Business Suite Project Contracts (OKE) module. Its documented purpose, drawn from the ETRM 12.2.2 metadata, is to expose "contract terms and conditions that have not been classified." In practical terms, the view returns those term records whose TERM_TYPE_CODE has not yet been assigned, isolating the pool of unclassified contract terms for downstream processing, review, or classification workflows.

The view is defined as a "Valid" object in the data dictionary and is treated as a read-only presentation layer rather than a transactional entity. It does not store data itself; instead it projects a filtered, denormalized result set built from a single underlying base object. Its value in reporting and integration lies in the fact that it flattens this filter into a fixed column layout that callers can consume directly, sparing them from repeatedly writing the TERM_TYPE_CODE IS NULL predicate against the base view.

Underlying Base Objects

Per the documented metadata, OKE_TERMTYPE_AVAIL_V references exactly one base object: OKE_TERMS_VL. The _VL suffix indicates that OKE_TERMS_VL is itself a multi-language (translated) view that joins the base terms table to its translation table, delivering language-appropriate term names. Therefore OKE_TERMTYPE_AVAIL_V is a view layered over another view, which ultimately resolves to the contract terms entity and its translations.

The relationship is one of narrowing. Where OKE_TERMS_VL exposes all defined terms (both classified and unclassified), OKE_TERMTYPE_AVAIL_V applies the restriction TERM_TYPE_CODE IS NULL, so its result set is a strict subset of the base view. Because the definition embeds this filter, any change to the classification status of a term is reflected immediately the next time the view is queried. Since both the base and derived objects are read-only views, no inserts, updates, or deletes should be directed at either object.

Key Columns

The view text exposes a compact set of columns, several of which are literal constants rather than true data fields:

• INIT_STAT — a literal value of 0, supplied as a constant, typically consumed by UI tree or hierarchical components as an initial state indicator.
• DEPTH — a literal value of 1, denoting a single-level (root) node depth in the consumer's hierarchy.
• LABEL — the value TERM_NAME, used as the display label.
• ICON — the literal string 'OKEATTR', identifying the icon or node style applied by the client.
• DATA — the TERM_CODE, serving as the underlying key or value for the node.
• SORT_KEY — the TERM_NAME, again used for ordering the result set.

Notably, the constant columns (INIT_STAT, DEPTH, ICON) and the label/sort columns are configured to feed tree-style or LOV-style presentation components, while TERM_CODE and TERM_NAME carry the substantive contract-term identity. The filter that defines the view's purpose, TERM_TYPE_CODE IS NULL, is applied internally and is not itself projected as a column.

Common Use Cases and Queries

The primary scenario is identifying contract terms that still require classification. A typical query selects the term code and name for review or assignment:

SELECT DATA AS term_code, LABEL AS term_name FROM apps.oke_termtype_avail_v ORDER BY SORT_KEY;

Because the view includes presentation columns, it is frequently embedded in a value list or hierarchical tree within Project Contracts forms, where INIT_STAT, DEPTH, and ICON drive rendering. For reconciling counts against the full term set, an administrator might compare totals:

SELECT COUNT(*) FROM apps.oke_termtype_avail_v;

A third use is integration: an external interface can select TERM_CODE values from this view to build a worklist of unclassified terms for automated or batch classification, then update the base terms entity once the appropriate TERM_TYPE_CODE has been determined. In all cases the view is read-only, so any remediation of the classification itself must be performed against the underlying contract terms data, not through this view.