Results for “rule_code”

50+ results




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

Overview

OKC_RULE_DEFS_B is the Contracts Rule Definitions base table within the Oracle Contracts Core (OKC) product module, owned by the OKC schema. It stores the definition of rules that govern contract behavior in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Each row represents a rule definition that is subsequently applied to contracts, contract templates, and related contract objects through the Contracts Core rule engine. The "B" suffix and the description "rules striped" indicate that this is the base (non-translated) table in the standard Oracle multi-language table convention, where translated descriptive columns would reside in a corresponding "_TL" table.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone, meaning it is not currently identified as a hub, link, or satellite through foreign key mining. This classification should be treated as a modeling suggestion only; the table functions logically as a reference or definition entity whose natural key is RULE_CODE.

Key Information Stored

The table contains eleven documented columns. The most significant include:

  • RULE_CODE — The primary key column, defined by the OKC_RULE_DEFS_B_PK constraint. It is the business identifier for each rule definition and is the value most frequently queried when users search for a specific contract rule.
  • APPLICATION_ID — Identifies the application that owns or registers the rule definition, typically linking to the Oracle Application Object Library.
  • DESCRIPTIVE_FLEXFIELD_NAME — Names the descriptive flexfield associated with the rule definition, enabling extensible attributes to be attached to rules.
  • OBJECT_VERSION_NUMBER — Supports optimistic locking and concurrency control during updates.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle audit columns recording who created and last modified the row and when.
  • SECURITY_GROUP_ID — Supports multi-tenant or security-group partitioning; it references FND_SECURITY_GROUPS.
  • ZD_EDITION_NAME — Editioning column supporting Oracle EBS 12.2 online patching and edition-based redefinition.

The unique index OKC_RULE_DEFS_B_U1 on (RULE_CODE, ZD_EDITION_NAME) serves as the effective business-key candidate, distinguishing the primary key surrogate from the combination used in edition-aware queries.

Common Use Cases and Queries

A typical use case is validating which rule definitions exist before writing contract logic or configuration. A search driven by the user's term "rule_code" would resemble:

SELECT rule_code, application_id, descriptive_flexfield_name,
       last_updated_by, last_update_date
FROM   okc.okc_rule_defs_b
WHERE  rule_code LIKE '&rule_code%';

Reporting use cases include auditing rule usage across applications, verifying that rule definitions are edition-consistent after an online patch upgrade, and reconciling security group assignments. Join patterns often extend to translated descriptions and to application lookups to produce readable rule listings. Because the table is small and definitional, queries against it are generally inexpensive and are commonly embedded in setup validation scripts and migration extracts.

Related Objects

  • FND_SECURITY_GROUPS — Referenced by OKC_RULE_DEFS_B.SECURITY_GROUP_ID, providing the security group definition for each rule row.
  • OKC_RULE_DEFS_TL — The translated sibling table supplying language-specific rule names and descriptions; joined on RULE_CODE and language.
  • OKC_RULE_DEFS_B_PK — The primary key constraint enforcing uniqueness of RULE_CODE.
  • OKC_RULE_DEFS_B_U1 — The unique index on RULE_CODE and ZD_EDITION_NAME supporting edition-based queries.
  • Contract rule application and condition tables within the OKC schema that consume RULE_CODE as a foreign reference.
  • Oracle Contracts Core APIs and concurrent programs that evaluate contract rules at runtime, resolving RULE_CODE through this base table.