Results for “igw_bus_rule_lines_u1”

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

Overview

IGW.IGW_BUSINESS_RULE_LINES is a transactional configuration table in the Oracle E-Business Suite grants management schema (IGW). It stores the individual expressions that make up a business rule. A single business rule is not held as one row; instead, each rule is decomposed into one or more expression rows, and those expressions are joined together by logical AND or OR operators. This row-per-expression design allows a comprehensive rule to be assembled dynamically and evaluated sequentially at runtime. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and its indexes are held separately in APPS_TS_TX_IDX.

From a heuristic Data Vault modeling perspective, the mined foreign key structure classifies this object as satellite-leaning. It hangs off IGW_BUSINESS_RULES_ALL through its RULE_ID foreign key, recording descriptive and operational attributes of the parent rule rather than acting as an independent hub or as a pure link between two hubs. This classification is a modeling suggestion only; in native EBS terms the table is a child detail table of the business rules header.

Key Information Stored

The primary key is IGW_BUS_RULE_LINES_PK, defined on the composite of RULE_ID and EXPRESSION_ID. A unique index, IGW_BUS_RULE_LINES_U1, is defined on the same two columns (RULE_ID, EXPRESSION_ID) in the APPS_TS_TX_IDX tablespace; this index is the business-key candidate that most queries will probe. The most important columns are:

• RULE_ID — Rule identifier; foreign key to IGW_BUSINESS_RULES_ALL and the first component of both the primary key and the unique index.
• EXPRESSION_ID — Rule expression identifier; the second component of the composite key.
• EXPRESSION_SEQUENCE_NUMBER — Order in which the expression is evaluated within the rule.
• EXPRESSION_TYPE — Type of expression: Q for Question, C for Column, or F for Function.
• LVALUE — Left-hand side of the expression; sourced from lookup IGW_RULE_COLUMNS when EXPRESSION_TYPE is C, and from IGW_RULE_FUNCTIONS when EXPRESSION_TYPE is F.
• OPERATOR — Comparison operator, constrained by expression type (Equals / Not Equal to for F; the full set including Less Than, Greater Than and their inclusive variants for C).
• RVALUE and RVALUE_ID — Right-hand side of the expression and its identifier. For Q and C types RVALUE_ID equals RVALUE; for F type it carries a distinct identifier.
• LBRACKETS and RBRACKETS — Left and right parentheses used to control grouping and precedence.
• LOGICAL_OPERATOR — AND or OR, joining this expression to the next.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Who audit columns.

Common Use Cases and Queries

Typical uses include rule auditing, migration validation, and generating human-readable rule documentation. Because expressions are ordered fragments, the most common access path retrieves all lines for a rule in sequence:

SELECT expression_sequence_number, lbrackets, lvalue, operator, rvalue, rbrackets, logical_operator
FROM   igw.igw_business_rule_lines
WHERE  rule_id = :p_rule_id
ORDER  BY expression_sequence_number;

Reporting queries frequently filter by expression type to separate question-driven conditions from column or function comparisons, for example counting expressions by EXPRESSION_TYPE per rule. Joining to IGW_BUSINESS_RULES_ALL supplies the rule header and name alongside each line. Because the unique index IGW_BUS_RULE_LINES_U1 leads on RULE_ID, equality predicates on RULE_ID benefit from an index range scan. Auditing queries comparing LAST_UPDATE_DATE across the header and lines help identify recently modified rules.

Related Objects

• IGW.IGW_BUSINESS_RULES_ALL — Parent header table; join on IGW_BUSINESS_RULE_LINES.RULE_ID = IGW_BUSINESS_RULES_ALL.RULE_ID.
• Lookup IGW_RULE_COLUMNS — Supplies valid LVALUE entries when EXPRESSION_TYPE is C.
• Lookup IGW_RULE_FUNCTIONS — Supplies valid LVALUE entries when EXPRESSION_TYPE is F.
• IGW_BUS_RULE_LINES_U1 — Unique index over RULE_ID and EXPRESSION_ID used for business-key lookups.
• IGW_BUS_RULE_LINES_PK — Primary key constraint over RULE_ID and EXPRESSION_ID.
• Oracle Grants Management rule engine APIs — Consume these rows at runtime to evaluate eligibility and compliance rules.