Search Results okc_rule_defs_b




Overview
Explore in AI Chat

Overview

The OKC_RULE_DEFS_B table is a core data object within the Oracle E-Business Suite Contracts Core (OKC) module. It functions as the base table for storing the definitions of business rules that govern contract terms and conditions. As indicated by its description, it holds "rules striped" data, meaning it contains the fundamental, non-translatable attributes of a rule definition. This table is central to the rule engine in Oracle Contracts, enabling the systematic application of standardized business logic, validations, and defaulting behaviors across contract authoring and management processes in both EBS 12.1.1 and 12.2.2.

Key Information Stored

The primary data stored in OKC_RULE_DEFS_B pertains to the unique identification and structural definition of a rule. The table's structure is anchored by the RULE_CODE column, which serves as the primary key (OKC_RULE_DEFS_B_PK). This column uniquely identifies each rule definition within the system. While the provided metadata does not list additional columns, typical columns in such a base table would include essential attributes like the rule's internal name, an effective start date (EFFECTIVE_FROM_DATE), an effective end date (EFFECTIVE_TO_DATE) for managing rule versioning, and a creation date. The table stores the invariant, non-language-dependent components of a rule, separating them from translatable descriptive text, which is typically stored in a related multi-language table (e.g., OKC_RULE_DEFS_TL).

Common Use Cases and Queries

This table is primarily accessed for rule administration, integration, and troubleshooting. Common scenarios include identifying all active rule definitions for system configuration audits or extracting rule metadata for integration with external systems. A typical query would involve joining with the corresponding translation table to retrieve a comprehensible rule list. For example, to list all currently effective rules, one might use a SQL pattern such as:

  • SELECT b.RULE_CODE, tl.RULE_NAME
  • FROM OKC_RULE_DEFS_B b, OKC_RULE_DEFS_TL tl
  • WHERE b.RULE_CODE = tl.RULE_CODE
  • AND tl.LANGUAGE = USERENV('LANG')
  • AND SYSDATE BETWEEN b.EFFECTIVE_FROM_DATE AND NVL(b.EFFECTIVE_TO_DATE, SYSDATE+1);

Data from this table is also critical for diagnosing issues where contract terms are not defaulting or validating as expected, by verifying the underlying rule definition's existence and active status.

Related Objects

OKC_RULE_DEFS_B is intrinsically linked to several other objects within the Contracts Core schema. Its most direct relationship is with the translation table OKC_RULE_DEFS_TL, which holds the language-specific names and descriptions for each RULE_CODE. The rule definitions are referenced by operational tables that apply these rules to specific contracts or contract lines. Furthermore, this base table is likely accessed by key public APIs within the OKC module, such as the Rule Definition and Rule Application APIs, which provide the supported methods for creating, updating, and applying these business rules programmatically. The primary key constraint, OKC_RULE_DEFS_B_PK, ensures referential integrity for all foreign key relationships from dependent tables that store rule assignments or instances.