Search Results okc_rule_def_sources_v




Overview
Explore in AI Chat

Overview

OKC_RULE_DEF_SOURCES_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, residing in the OKC (Contracts Core) product family. Its documented purpose is to expose the contents of the OKC_RULE_DEF_SOURCES base table in a query-friendly format for use by Oracle Contracts and dependent application modules. In both EBS 12.1.1 and 12.2.2 the view is registered as VALID, and its definition is a straightforward, unfiltered projection of the underlying table rather than a join or aggregation. As a result, it carries no transformation logic beyond column aliasing and the substitution of the physical ROWID with a logical ROW_ID column. The name "RULE_DEF_SOURCES" identifies the view as a source definition repository for Contracts rule hierarchies, which govern how contract terms, rule groups, and rule definitions are resolved at runtime for a given business context (buy or sell side, object type, and effective date range).

Underlying Base Objects

The view is defined exclusively over OKC_RULE_DEF_SOURCES, itself a synonym resolved within the APPS schema to the underlying OKC physical table. The view text selects every column of that table:

Because the view is a single-table projection, its rows are one-to-one with the base table. The inclusion of OBJECT_VERSION_NUMBER confirms that the base table participates in Oracle's object versioning (OAF/BC4J) model, an important consideration when the view is used for insert or update operations through an ADO-enabled entity.

Key Columns

  • ROW_ID — Surrogates the database ROWID of the base row; used for row identification in forms and integration payloads.
  • JTOT_OBJECT_CODE — The rule object type code (the value the user searched for). It identifies which Contracts object the rule definition source applies to, discriminating between contract templates, terms, and other rule-bearing entities recorded in JTOT.
  • RGR_RGD_CODE — Rule group definition code linking the source to a specific rule group.
  • RGR_RDF_CODE — Rule definition code identifying the individual rule within the group.
  • BUY_OR_SELL — Side flag determining whether the source applies to purchasing or sales contract scenarios.
  • START_DATE / END_DATE — Effective dating boundary; rules resolve only within this window.
  • OBJECT_VERSION_NUMBER / OBJECT_ID_NUMBER — Versioning and internal identifier columns supporting concurrent-safe DML.
  • ACCESS_LEVEL and the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) carry security and audit information.

Common Use Cases and Queries

The view is typically queried to diagnose rule resolution failures, audit rule source configuration, and feed integrations that synchronize contract rules. A representative query filtering on the searched object code is:

  • SELECT jtot_object_code, rgr_rgd_code, rgr_rdf_code, buy_or_sell, start_date, end_date FROM okc_rule_def_sources_v WHERE jtot_object_code = :object_code AND SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE + 1) AND access_level = 1;

A secondary pattern joins the view to rule group and rule definition views to reconstruct the full resolution chain, while audit queries select creation and update metadata. Because the view is unfiltered, DBAs should apply BUY_OR_SELL, ACCESS_LEVEL, and effective-date predicates in the calling query to restrict result sets, particularly in high-volume contract environments.