Results for “igw_business_rules”

16 results




Overview
Explore in AI Chat

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

Overview

IGW_BUSINESS_RULES is a read-only Oracle EBS view owned by the APPS schema within the IGW (Grants Proposal) product family. It exposes the business rule definitions that govern grants-related processing for every organization that belongs to the operating unit in which the session is currently operating. In Release 12.1.1 and 12.2.2 the object is registered as a VALID view in the ETRM data dictionary, and it functions as the operational, single-organization window onto the multi-organization base object IGW_BUSINESS_RULES_ALL.

The view performs an implicit operating unit (ORG_ID) security filter. Instead of prompting the user for an organization identifier, it derives the current organization from the session client information and returns only the rows whose ORG_ID matches that value. This makes the view suitable for direct use in Forms-based inquiry windows, Oracle Reports, BI Publisher data templates, and inbound/outbound integration interfaces that must respect EBS multi-org access control without coding an explicit WHERE clause.

Underlying Base Objects

ETRM documentation identifies the defining source as IGW_BUSINESS_RULES_ALL, with no other referenced base objects recorded. IGW_BUSINESS_RULES_ALL is the multi-organization table that stores the complete set of rule rows across all operating units. The view is the intersection of that table with the current ORG_ID, expressed as:

Rows whose ORG_ID carries a NULL value (for example, global rules not bound to a specific operating unit) are collapsed to the sentinel -99, so they are returned only when the session client information similarly resolves to -99. Because the view is defined over an _ALL table, there is no corresponding DML path through the view itself; inserts, updates, and deletes must target IGW_BUSINESS_RULES_ALL.

Key Columns

  • RULE_ID — Primary identifier of the business rule record.
  • RULE_SEQUENCE_NUMBER — Ordering attribute that controls the evaluation or display sequence of rules; this is the column most frequently searched by implementers validating rule precedence.
  • ORGANIZATION_ID — The inventory organization associated with the rule.
  • ORG_ID — The operating unit to which the rule belongs; the column driving the view's security filter.
  • RULE_NAME — Descriptive name of the rule.
  • RULE_TYPE — Classification of the rule, used to distinguish rule categories in grants processing.
  • MAP_ID — Identifier linking the rule to its associated mapping record.
  • VALID_FLAG — Indicator of whether the rule is currently active; typically Y/N.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — Effective date range bounding the rule's applicability.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns for change tracking and reconciliation.

Common Use Cases and Queries

The view is principally used to list, sequence, and audit grants business rules for the logged-in operating unit. Typical validations include confirming that RULE_SEQUENCE_NUMBER values are contiguous and unique, checking that exactly one active rule exists per RULE_TYPE, and verifying effective dates do not overlap within a rule set.

  • Enumerating ordered rules: SELECT rule_sequence_number, rule_name, rule_type FROM igw_business_rules ORDER BY rule_sequence_number;
  • Filtering active rules only: SELECT rule_id, rule_name FROM igw_business_rules WHERE valid_flag = 'Y' AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1);
  • Detecting duplicate sequence numbers: SELECT rule_sequence_number, COUNT(*) FROM igw_business_rules GROUP BY rule_sequence_number HAVING COUNT(*) > 1;
  • Auditing recent changes: SELECT rule_id, rule_name, last_updated_by, last_update_date FROM igw_business_rules ORDER BY last_update_date DESC;

Because the ORG_ID predicate is embedded in the view text, results are always scoped to the session's operating unit; cross-operating-unit analysis requires querying IGW_BUSINESS_RULES_ALL directly under appropriate multi-org privileges.