Search Results warn_yn




Overview
Explore in AI Chat

Overview

OKC_RULES_B is the base table that stores rule definitions within the Contracts Core (OKC) module of Oracle E-Business Suite. It is owned by the OKC schema and is classified as VALID in both Oracle EBS 12.1.1 and 12.2.2. The table represents the structured, machine-readable form of conditional logic that governs how contract clauses, articles, and related documents are assembled, validated, and rendered. Where free-format text in an ARTICLE holds narrative content, OKC_RULES_B holds the operational rule that binds that content to specific business objects, answer sets, and evaluation criteria.

Under a heuristic Data Vault classification, OKC_RULES_B is hub-leaning. It carries its own surrogate primary key (ID) and holds durable business keys in its unique index (OKC_RULES_B_U1), which positions it as a central anchor for rule-related entities rather than a pure transactional satellite. Practitioners modeling this domain may treat OKC_RULES_B as a hub whose descriptive attributes (priority, warnings, template flags) and foreign-key references populate surrounding link and satellite structures.

Key Information Stored

The table contains 60 documented columns. The most significant are summarized below.

Common Use Cases and Queries

Typical reporting scenarios include listing all rules belonging to a rule group, tracing rules to their referenced object types, and auditing template-derived rules. A representative query joining rules to groups and objects follows:

  • SELECT r.ID, r.RGP_ID, g.NAME, r.JTOT_OBJECT1_CODE, r.PRIORITY, r.WARN_YN FROM OKC_RULES_B r, OKC_RULE_GROUPS_B g WHERE r.RGP_ID = g.ID AND r.RGP_ID = :group_id ORDER BY r.PRIORITY;
  • SELECT r.ID, r.JTOT_OBJECT1_CODE, o.NAME FROM OKC_RULES_B r, JTF_OBJECTS_B o WHERE r.JTOT_OBJECT1_CODE = o.OBJECT_CODE;
  • SELECT ID, DNZ_CHR_ID, PRIORITY FROM OKC_RULES_B WHERE DNZ_CHR_ID = :contract_id AND STD_TEMPLATE_YN = 'Y';

These patterns support clause-assembly debugging, rule priority audits, and template governance reporting. Because the table is referenced by several dependent entities, any delete or update should account for the child records listed below.

Related Objects

  • JTF_OBJECTS_B — Referenced three times via JTOT_OBJECT1_CODE, JTOT_OBJECT2_CODE, and JTOT_OBJECT3_CODE; defines the object types a rule can target. This is the object the user searched for.
  • OKC_RULE_GROUPS_B — Parent group via RGP_ID; groups related rules.
  • FND_SECURITY_GROUPS — Referenced through SECURITY_GROUP_ID for security scoping.
  • OKC_ARTICLE_TRANS — References OKC_RULES_B.RUL_ID, linking rules to article translations.
  • OKC_COVER_TIMES — References RUL_ID, associating rules with coverage periods.
  • OKC_REACT_INTERVALS — References RUL_ID for reaction interval definitions.
  • OKL_ANSWERS — References RUL_ID, linking lease answer records to rules.
  • OKL_OVD_RUL_TMLS — References RUL_ID for overdue rule templates.
  • OKS_LEVEL_ELEMENTS — References RUL_ID for service level elements.

Collectively these relationships establish OKC_RULES_B as a central rule hub within the Contracts Core and adjacent leasing and service modules.