Results for “control_rule_id”

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

Overview

IGC_CC_CONTROL_RULES is a configuration table within the IGC (Contract Commitment) product family of Oracle E-Business Suite. It stores contract type authorization rules — the control definitions that govern which contract types a user, responsibility, or organizational context is permitted to create, modify, or process. In essence, the table codifies the authorization matrix that the Contract Commitment module applies when validating contract-related transactions against configured control policies.

The ETRM metadata records the table as "Not implemented in this database," indicating that the object is delivered as part of the IGC schema definition but may not be instantiated or populated in every environment. Its presence is nonetheless relevant for installations that license and deploy the Contract Commitment functionality, since the rules it holds drive runtime authorization behavior.

The metadata assigns a Data Vault classification of standalone based on a heuristic analysis of foreign key structure. From a modeling perspective, this suggests the table behaves as an independent reference construct rather than a dependent satellite or an associative link. If the table is modeled in a Data Vault, it would typically be represented as a hub keyed on the control rule identifier, with descriptive attributes either denormalized into the hub or split into a companion satellite depending on volatility. Because no foreign key relationships were mined, no natural parent-child link is documented.

Key Information Stored

The documented metadata identifies the primary key constraint as ICCR_PK, defined on the column CONTROL_RULE_ID. This is the surrogate key that uniquely identifies each authorization rule record.

• CONTROL_RULE_ID — Surrogate primary key (constraint ICCR_PK) uniquely identifying each contract type authorization rule. This is the column most frequently referenced in joins and lookups.

Because the ETRM excerpt supplies only the primary key column and a functional description, the precise business-key columns (such as contract type, responsibility, or rule code) are not enumerated in the documented metadata. In practice, a rules table of this nature typically carries the contract type identifier, the authorization or control dimension being constrained, and one or more enablement or restriction flags. Where a unique index exists beyond ICCR_PK, the constituent columns would serve as business-key candidates; the metadata does not document such an index, so CONTROL_RULE_ID should be treated as the sole confirmed key.

Common Use Cases and Queries

Typical scenarios include auditing which authorization rules are active for a given contract type, tracing why a contract operation was permitted or rejected, and validating configuration completeness before go-live. A representative lookup by surrogate key follows:

• SELECT * FROM IGC_CC_CONTROL_RULES WHERE CONTROL_RULE_ID = :control_rule_id;
• SELECT COUNT(*) FROM IGC_CC_CONTROL_RULES; — used to confirm whether the table is populated in a given environment, since the metadata notes it may not be implemented.

Reporting use cases center on control-rule inventories and configuration comparisons across environments (development, test, production), ensuring that the authorization matrix deployed to production matches the approved design. Because the table is classified as standalone, reporting queries generally do not require joins to resolve the key; the rule row is self-contained.

Related Objects

The ETRM metadata provides no foreign key relationships for IGC_CC_CONTROL_RULES, so the following are conceptual associations rather than documented joins. They should be verified against the actual schema before use in production SQL.

• Contract type definition tables (IGC contract type / contract template objects) — reference the contract types that the authorization rules constrain.
• Responsibilities and user authorization tables — supply the security context against which control rules are evaluated.
• Contract Commitment transaction tables — the runtime transactions whose validity is determined by these rules.
• IGC_CC_* configuration tables — sibling control and setup objects sharing the ICCR or IGC_CC naming convention.
• FND_* security objects — standard EBS responsibility and function security constructs that may interact with contract-type authorization.

Because the metadata explicitly labels the object standalone and notes it is not implemented in the reference database, consultants should inspect DBA_TAB_COLUMNS, DBA_CONSTRAINTS, and DBA_CONS_COLUMNS for the target instance to confirm which columns and constraints actually exist before building dependent logic or reports.