Results for “oks_rules_v”

20 results




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

Overview

OKS_RULES_V is a valid, Oracle-owned view in the APPS schema within Oracle E-Business Suite, belonging to the OKS — Service Contracts product family. Its documented purpose is to define an Object metadata record in JTF (the Java Technology Foundation / CRM Foundation layer used across Oracle's CRM applications). This is significant because it classifies OKS_RULES_V as a metadata-facilitating view rather than a conventional reporting view. JTF relies on such object metadata definitions to render, register, and reference application entities within the CRM framework, and OKS_RULES_V serves as one of the bridging definitions that exposes Service Contracts rule information to that framework. In the EBS 12.1.1 and 12.2.2 releases, the view remains VALID and is maintained exclusively by Oracle, meaning customer modifications are unsupported.

Underlying Base Objects

The view's implementation text is deliberately minimal:

The single documented referenced base object is OKC_RULES_V (VIEW), itself a view within the OKC — Service Contracts Core schema modules. OKS_RULES_V therefore adds a thin projection layer over OKC_RULES_V rather than querying base tables directly. The derivation of OKS (Service Contracts) from OKC (Contracts Core) reflects the standard layering in the Contracts family: OKC holds the core rules engine and contract structures, while OKS exposes service-contract-specific functionality. Because OKS_RULES_V does not read a physical table, it introduces no independent persistence; any performance or content behavior ultimately depends on OKC_RULES_V and the tables beneath it.

Key Columns

The view exposes three aliased columns, which are largely structural rather than descriptive:

  • ID1 — an alias of the underlying ID column from OKC_RULES_V. This carries the primary identifier of each rule record.
  • ID2 — a literal hash character ('#'). This is a static placeholder value, not derived from data, and typically exists to satisfy a fixed column signature expected by the JTF metadata registration mechanism.
  • NAME — hard-coded to NULL in the view text, overwriting any name value available from OKC_RULES_V. This confirms that OKS_RULES_V is not intended for name-based lookup or display.

The columns listed in the ETRM metadata include NAME; ID1 and ID2 appear in the view text. The presence of literal and NULL values indicates the view functions as a registration stub for JTF object metadata rather than as a data-presentation layer.

Common Use Cases and Queries

Practical use of OKS_RULES_V is narrow and specific. It is principally consumed by JTF metadata routines that enumerate or validate Service Contracts rule objects, not by end users running operational reports. Consultants examining the object during a JTF/CRM integration exercise may query it as follows:

  • SELECT id1, id2, name FROM apps.oks_rules_v; — returns the rule identifiers with the static '#' and NULL placeholder values, useful for confirming the view resolves and that underlying OKC_RULES_V data is accessible.
  • SELECT COUNT(*) FROM apps.oks_rules_v; — a quick validation that the OKC_RULES_V dependency is intact after patching or cloning.
  • Joining back to OKC_RULES_V on id1 = id — the standard technique to retrieve the actual rule attributes (names, descriptions) that OKS_RULES_V deliberately suppresses.

Because the view is a JTF metadata definition, developers integrating custom CRM objects alongside Service Contracts may reference OKS_RULES_V when mirroring Oracle's registration pattern. Any functional querying of rule content should target OKC_RULES_V directly, since NAME is nulled and ID2 is a constant in OKS_RULES_V. The object should be treated as read-only and Oracle-maintained in both 12.1.1 and 12.2.2.