Results for “cls_code”

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

Overview

OKS_K_CATEGORIES_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite. It is documented as VALID in both 12.1.1 and 12.2.2 and belongs to the OKS (Service Contracts) product family. The view exists to support the object type OKS_K_CATEGORY, which is referenced by the update level attribute used in Mass Change processing. In practical terms, it provides a constrained, denormalized list of service-related category records that the Mass Change framework and related Service Contracts components can consume as a lookup source.

The view is deliberately narrow in scope. Its defining predicate restricts the result set to rows where CLS_CODE equals 'SERVICE', so it exposes only the service class subclass definitions rather than the full set of subclass values. This makes it a stable, purpose-built reporting and integration surface for objects that must resolve against service categories without scanning the complete subclass hierarchy.

Underlying Base Objects

Per the ETRM metadata, OKS_K_CATEGORIES_V is defined over a single referenced base object: OKC_SUBCLASSES_V, itself a view rather than a base table. That underlying view is part of the OKC (Contracts) core dictionary, which stores subclass and class code definitions used across contract and service contract modules.

The dependency chain is therefore APPS.OKS_K_CATEGORIES_V → OKC_SUBCLASSES_V, with any further dependencies resolved beneath OKC_SUBCLASSES_V in the standard OKC contract entities. Because the parent object is a view, the metadata exposes no direct base table joins; the join logic is inherited from OKC_SUBCLASSES_V. The view text is minimal:

• CODE is projected as ID1
• The literal '#' is projected as ID2
• MEANING is projected as NAME
• DESCRIPTION, CODE, and CLS_CODE pass through unchanged
• A WHERE clause filters on CLS_CODE = 'SERVICE'

Key Columns

• NAME — aliased from MEANING in OKC_SUBCLASSES_V; the display name for the service category shown to users and used as the mass change update label.
• DESCRIPTION — the descriptive text of the subclass record.
• CODE — the subclass code that identifies the category. It is also surfaced as ID1, indicating it functions as the primary identifier for the OKS_K_CATEGORY object.
• CLS_CODE — the class code, retained in the projection and constrained to the constant value 'SERVICE'. This column is the filter key that defines the view's scope and is the column most relevant to the user search term "cls_code".
• ID1 — the object identifier used by the Mass Change framework, populated from CODE.
• ID2 — a constant '#' literal, typically used as a composite-key delimiter or placeholder in generic ID keying conventions.

Common Use Cases and Queries

Typical uses include LOV and validation queries for service category selection, resolving the update level attribute in Mass Change, and ad-hoc reporting on service subclass definitions. Because CLS_CODE is constant, filtering by it in application SQL is redundant but harmless.

• List all service categories: SELECT code, name, description FROM apps.oks_k_categories_v ORDER BY name;
• Resolve a specific category by code: SELECT id1, id2, name FROM apps.oks_k_categories_v WHERE code = :p_code;
• Confirm scope: SELECT DISTINCT cls_code FROM apps.oks_k_categories_v; — always returns 'SERVICE'.
• Drive a Mass Change lookup: SELECT id1, name FROM apps.oks_k_categories_v WHERE name LIKE :search%.

The view should be treated as read-only reference data; updates must be performed against the underlying OKC subclass definitions.