Search Results contract_type_class

Overview

APPS.OKE_K_TYPES_VL is a multilingual (VL) Oracle E-Business Suite view that exposes the master definition of Oracle Contracts (OKE) contract types along with their translated names, descriptions, and the decoded classification of each contract type. The view joins the base table OKE_K_TYPES_B to its translation table OKE_K_TYPES_TL and further decodes the TYPE_CLASS_CODE column against the FND_LOOKUP_VALUES_VL lookup set 'CONTRACT_TYPE_CLASS' (an Oracle Contracts lookup owned by application 777). It also optionally resolves the approval path name assigned to a contract type. The "_VL" suffix indicates that the view is language-aware, returning translation rows matching the session language established by USERENV('LANG').

Because the underlying base table stores only a lookup code for the contract type classification, the view supplies the human-readable MEANING via the lookup join — which is precisely why a search on "contract_type_class" surfaces this view. It is the canonical source for reporting on how each contract type is classified (for example, as a purchase, sales, lease, or services contract type).

Underlying Base Objects

The view is defined over four documented objects:

• OKE_K_TYPES_B (synonym) — the base "K types" table holding one row per contract type and its operational columns (K_TYPE_CODE, TYPE_CLASS_CODE, INTENT, APPROVAL_PATH_ID, dates, and the ATTRIBUTE1–15 DFF columns). It is the driving table, aliased B.
• OKE_K_TYPES_TL (synonym) — the translation table (aliased T), supplying K_TYPE_NAME, DESCRIPTION, and other translated attributes, filtered to T.LANGUAGE = USERENV('LANG').
• FND_LOOKUP_VALUES_VL (view) — the reference lookup view (aliased TC), filtered on LOOKUP_TYPE = 'CONTRACT_TYPE_CLASS' and constrained to VIEW_APPLICATION_ID = 777, providing the MEANING for each TYPE_CLASS_CODE.
• OKE_APPROVAL_PATHS_TL (synonym) — the translated approval-path table (aliased A), outer-joined on APPROVAL_PATH_ID and language, returning the path NAME when one is assigned.

The join between OKE_K_TYPES_B and OKE_K_TYPES_TL is an inner join (no outer marker), and the approval-path join is explicitly outer (+), meaning a contract type without an assigned approval path still appears in the result set.

Key Columns

• K_TYPE_CODE — primary business key of the contract type; also the join to the translation table.
• K_TYPE_NAME — the translated, user-facing name of the contract type.
• TYPE_CLASS_CODE — the raw classification code stored on the base table.
• MEANING — the decoded, display value of the contract type class (the "contract_type_class" lookup meaning).
• INTENT — the intended usage/behavior flag of the contract type.
• APPROVAL_PATH_ID / NAME — the approval path identifier and its translated name (may be NULL if none is assigned).
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range controlling whether the type is active.
• ATTRIBUTE1–15 and ATTRIBUTE_CATEGORY — descriptive flexfield segments, available for extensibility.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, ROWID) — audit and row addressing.

Common Use Cases and Queries

Typical uses include reporting on available contract types and their classifications, driving pick-lists, auditing which approval paths are attached, and joining to contract headers to analyze contracts by type class. A representative query listing active contract types with their decoded class is:

• SELECT k_type_code, k_type_name, type_class_code, meaning, intent, name AS approval_path, start_date_active, end_date_active FROM apps.oke_k_types_vl WHERE (end_date_active IS NULL OR end_date_active > SYSDATE) ORDER BY type_class_code, k_type_name;
• SELECT meaning, COUNT(*) FROM apps.oke_k_types_vl GROUP BY meaning; — to profile contract types by class meaning.
• Filter on a specific class: SELECT k_type_code, k_type_name FROM apps.oke_k_types_vl WHERE type_class_code = :p_class;

Because the view filters on USERENV('LANG'), it is safe for multilingual environments and should be preferred over ad-hoc joins to the base tables when the decoded class meaning or the approval path name is required.