Results for “left_value”

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

Overview

IGWBV_GRNT_PRPSL_ROUT_RULE_LNE is an APPS-owned, read-only database view within the Oracle E-Business Suite Grants Proposal (IGW) module. It exposes the line-level components of routing rules used by the Grants Proposal business rule engine. In EBS 12.1.1 and 12.2.2 the object is delivered in VALID status and is defined with a WITH READ ONLY clause, meaning it cannot be used as an update target. The view presents each expression line of a routing rule as a discrete row, allowing downstream reports, concurrent programs, and integration feeds to interrogate the boolean and arithmetic conditions that determine how a proposal is routed for review and approval.

Because the object is a view rather than a table, it carries no storage of its own and no DBA-level indexes. Its primary role is to provide a stable, denormalised read interface over the underlying business rule line data, shielding consumers from the physical column naming and joining conventions of the base table. This is consistent with Oracle's convention of prefixing reporting views with a "BV" (business view) marker.

Underlying Base Objects

The view is defined exclusively over a single base table, IGW_BUSINESS_RULE_LINES, aliased as RULE_LINES in the defining SQL. No other base tables or views are referenced, and the ETRM metadata documents no additional referenced base objects. The defining predicate is a trivial WHERE 1 = 1, so the view returns every row present in the underlying table without filtering. The WITH READ ONLY clause enforces that no DML can be issued against the view.

Column renaming occurs at the view layer. The base column LVALUE is projected as LEFT_VALUE, and RVALUE is projected as RIGHT_VALUE. Likewise, LBRACKETS maps to LEFT_BRACKETS and RBRACKETS maps to RIGHT_BRACKETS, while OPERATOR is exposed as ARITHMATIC_OPERATOR (note the delivered spelling). The remaining columns retain their base names.

Key Columns

• EXPRESSION_SEQUENCE_NUMBER — Ordering of the expression line within its parent rule.
• EXPRESSION_TYPE — Classification of the expression, distinguishing value comparisons from other constructs.
• LEFT_VALUE — The left-hand operand of the condition (renamed from LVALUE). This is the column most commonly targeted by consumers searching for the literal token "left_value".
• LEFT_BRACKETS / RIGHT_BRACKETS — Parenthesis indicators used to reconstruct grouped boolean logic.
• ARITHMATIC_OPERATOR — The comparison or arithmetic operator joining left and right operands.
• RIGHT_VALUE / RIGHT_VALUE_ID — The right-hand operand literal and its optional identifier reference.
• LOGICAL_OPERATOR — The AND/OR connective linking the line to the next expression.
• RULE_ID / EXPRESSION_ID — Foreign keys to the parent rule and expression headers.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE.

Common Use Cases and Queries

Typical scenarios include auditing configured routing logic, troubleshooting proposal routing failures, and exporting rule definitions for migration between environments.

SELECT rule_id, expression_sequence_number,
       left_value, arithmatic_operator, right_value, logical_operator
FROM   apps.igwbv_grnt_prpsl_rout_rule_lne
WHERE  rule_id = :p_rule_id
ORDER  BY expression_sequence_number;

To locate a specific operand:

SELECT rule_id, expression_id, left_value, right_value
FROM   apps.igwbv_grnt_prpsl_rout_rule_lne
WHERE  UPPER(left_value) LIKE '%' || UPPER(:search_term) || '%';

Because the view is read-only and unfiltered, it is safe for ad-hoc querying and read-only extraction in both 12.1.1 and 12.2.2.