Results for “rules_all”

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

Overview

APPS.IGWFV_GRNT_PRPSL_ROUT_RULE_LNE is a Business Intelligence System (BIS) view owned by the APPS schema within the Oracle E-Business Suite Grants Management module (product short name IGW). Its FND Design Data identifier is IGW.IGWFV_GRNT_PRPSL_ROUT_RULE_LNE, and it carries a VALID status in both the 12.1.1 and 12.2.2 releases. The view exposes the grant proposal routing rule line data model, presenting the individual expression rows that together compose a routing rule used to determine how grant proposals are distributed and approved.

In the EBS reporting and integration landscape, this view serves as a flattened, read-consistent presentation layer over the underlying rule definition tables. Because routing rules are stored in a normalized fashion, the view exposes one row per rule expression element, allowing external tools, BIS reports, and custom integrations to consume rule logic without navigating the base transactional tables directly. The naming convention (IGWFV_) indicates an interface view under the Grants Management workflow family, distinguishing it from the underlying base tables. The view is not referenced by any other database object, so it acts as a terminal reporting object rather than a building block for further dependencies.

Underlying Base Objects

The view is defined over two documented base tables within the APPS schema: IGW_BUSINESS_RULES_ALL and IGW_BUSINESS_RULE_LINES. IGW_BUSINESS_RULES_ALL stores the rule header information — the rule identity, name, and associated business context — while IGW_BUSINESS_RULE_LINES stores the individual expression lines that constitute the rule logic. The view joins these two objects to produce a single result set keyed by RULE_ID and EXPRESSION_ID, combining the header-level rule name with the line-level expression details. No additional base objects are documented, and the metadata confirms the view is not referenced by any downstream database object.

Key Columns

The view exposes sixteen columns, of which the following are most significant:

• RULE_NAME (VARCHAR2, 50) — the descriptive name of the routing rule, sourced from the rule header.
• EXPRESSION_SEQUENCE_NUMBER (NUMBER) — the ordinal position of the expression within the rule, defining evaluation order.
• EXPRESSION_TYPE (VARCHAR2) — classifies the expression element being evaluated.
• LEFT_BRACKETS / RIGHT_BRACKETS (VARCHAR2, 10) — parenthetical grouping tokens; RIGHT_BRACKETS is the column directly associated with the user search term "right_brackets," used to close grouping expressions in complex rule logic.
• LEFT_VALUE (VARCHAR2, 50) and RIGHT_VALUE (VARCHAR2, 200) — the operands on either side of the comparison or arithmetic operator.
• ARITHMATIC_OPERATOR (VARCHAR2) — the operator relating the left and right values (note the documented spelling).
• RGHT_VALUE_ID (VARCHAR2, 30) — an identifier qualifier for the right-hand value.
• LOGICAL_OPERATOR (VARCHAR2) — the connective (AND/OR) linking expressions in a compound rule.
• RULE_ID (NUMBER, 15) and EXPRESSION_ID (NUMBER, 10) — primary identifiers enabling joins to related rule objects.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, and CREATED_BY provide standard EBS who/when tracking.

Common Use Cases and Queries

Typical scenarios include auditing routing rule definitions, reconstructing rule logic for documentation, and feeding rule data into approval workflow analysis. A standard query selecting all columns is:

• SELECT RULE_NAME, EXPRESSION_SEQUENCE_NUMBER, EXPRESSION_TYPE, LEFT_BRACKETS, LEFT_VALUE, ARITHMATIC_OPERATOR, RIGHT_VALUE, RGHT_VALUE_ID, RIGHT_BRACKETS, LOGICAL_OPERATOR, RULE_ID, EXPRESSION_ID FROM APPS.IGWFV_GRNT_PRPSL_ROUT_RULE_LNE;
• To inspect bracket-balanced rules, filter on the bracket columns: WHERE RIGHT_BRACKETS IS NOT NULL OR LEFT_BRACKETS IS NOT NULL;
• To reconstruct a single rule's logic in evaluation order: WHERE RULE_ID = :rule_id ORDER BY EXPRESSION_SEQUENCE_NUMBER;
• For change tracking, attribute recent modifications: WHERE LAST_UPDATE_DATE >= :from_date.

Because the view is read-only and carries no downstream dependencies, it is safe to query from custom reports and integration extracts without impacting the base rule engine.