Search Results okc_rule_def_sources




Overview
Explore in AI Chat

Overview

The OKC_RULE_DEF_SOURCES table is a core reference table within the Oracle E-Business Suite Contracts Core (OKC) module. It functions as a control table that defines the valid data sources for a rule when that rule is utilized within a specific rule group. This table is essential for enforcing data integrity and business logic within the complex rule engine of Oracle Contracts, ensuring that rules can only draw data from authorized and structurally compatible sources. Its role is pivotal in the configuration and validation of contract terms, deliverables, and business rules, linking abstract rule definitions to concrete application objects and data entities.

Key Information Stored

The table stores metadata that maps a rule within a rule group to permissible data sources. Its composite primary key underscores the specificity of each record. Key columns include BUY_OR_SELL, which indicates the transaction context (Buy-Side or Sell-Side Contract). The RGR_RGD_CODE and RGR_RDF_CODE columns together form a foreign key to the OKC_RG_DEF_RULES table, identifying the specific rule definition within a rule group. The START_DATE manages the effective dating of the source mapping. A critical column is OBJECT_ID_NUMBER, which, in conjunction with JTOT_OBJECT_CODE (a foreign key to JTF_OBJECTS_B), identifies the specific application object or entity that serves as a valid data source for the rule, such as a contract header, line, or party.

Common Use Cases and Queries

A primary use case is during the setup or audit of contract business rules, where an administrator needs to verify which data entities a particular rule can access. For instance, to list all valid data sources for a specific rule definition within a 'Payment Terms' rule group, a query would join OKC_RULE_DEF_SOURCES to OKC_RG_DEF_RULES and JTF_OBJECTS_B. Another common scenario is impact analysis before modifying an object structure; determining which rules depend on a given object (like 'OKC_HEADERS') requires querying this table via the OBJECT_ID_NUMBER and JTOT_OBJECT_CODE. Sample SQL to find sources for a rule would be:

  • SELECT rds.*, job.OBJECT_NAME FROM OKC_RULE_DEF_SOURCES rds, JTF_OBJECTS_B job WHERE rds.JTOT_OBJECT_CODE = job.OBJECT_CODE AND rds.RGR_RGD_CODE = '&RGD_CODE' AND rds.RGR_RDF_CODE = '&RDF_CODE';

Related Objects

The table maintains documented foreign key relationships with two critical objects, forming the backbone of its referential integrity. First, it references JTF_OBJECTS_B via the JTOT_OBJECT_CODE column. This links the rule source to the centralized repository of application objects within EBS. Second, it references OKC_RG_DEF_RULES via the composite columns RGR_RGD_CODE and RGR_RDF_CODE. This ties the data source definition back to the specific rule within a rule group. The table itself is referenced by the primary key constraint OKC_RULE_DEF_SOURCES_PK, which is likely utilized by various Contracts Core APIs and user interfaces that manage rule configuration.