Search Results igs_ru_description_v




Overview

IGS_RU_DESCRIPTION_V is a view owned by the APPS schema in the Oracle E-Business Suite Student System (IGS) product. It is documented in the E-Business Suite Technical Reference Manual (ETRM) at the 12.1.1 and 12.2.2 release levels with a status of VALID. The view presents data drawn from the IGS_RU_DESCRIPTION table, which stores descriptive components of rule definitions used by the Student System's rules engine. Its documented purpose is to support the generation of Oracle Forms form RULF2000, which is the rule description maintenance form used by configuration and functional administrators when authoring or reviewing rule logic.

Because it is a view rather than a table, IGS_RU_DESCRIPTION_V carries no independent storage. It functions as a presentation and integration layer, normalizing and renaming selected columns from the base table so that the form, concurrent programs, and downstream reporting or interface code can reference a stable, predictable column set. In a reporting and integration context, the view is best understood as a read-oriented access path to rule description metadata, suitable for queries that need rule text components without touching the base table directly.

Underlying Base Objects

The view is defined over a single documented base object: IGS_RU_DESCRIPTION, aliased as RUD in the view text. The ETRM metadata lists no other referenced base objects, so the view is a straightforward, non-joined projection — it is not a join view and does not aggregate data. This distinction matters during performance tuning and upgrade impact analysis, because the view inherits the row cardinality and indexing characteristics of the base table without introducing additional join overhead.

One notable structural feature is the synthetic ROW_ID column, produced as RUD.ROWID. This exposes the physical row identifier of the underlying base-table row through the view. It is commonly used by Oracle Forms as a means of uniquely identifying a record for update or lock purposes. The view also introduces a literal column named RULE_TEXT, defined as an empty string (''), which is a placeholder rather than a mapped source column.

Key Columns

  • ROW_ID — The ROWID of the corresponding IGS_RU_DESCRIPTION row; used for row identification and Forms record handling.
  • SEQUENCE_NUMBER — Ordering attribute for description elements associated with a rule.
  • RULE_DESCRIPTION — The principal descriptive text of the rule, as maintained by the user.
  • S_RETURN_TYPE — Return-type indicator describing the expected result type of the rule expression.
  • DESCRIPTION — Additional free-format descriptive text.
  • RULE_TEXT — A literal empty string exposed by the view; not sourced from the base table.
  • PARENTHESIS_IND — Indicator controlling parenthesis placement in generated rule expressions.
  • S_TURIN_FUNCTION — Function reference used by the rules engine.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns, inherited unchanged from the base table.

Common Use Cases and Queries

Typical usage centers on diagnostics, reporting, and support of rule configuration. A basic retrieval of rule descriptions ordered by sequence is shown below:

  • SELECT row_id, sequence_number, rule_description, s_return_type, parenthesis_ind FROM igs_ru_description_v ORDER BY sequence_number;
  • SELECT rule_description, description, s_turin_function FROM igs_ru_description_v WHERE parenthesis_ind = 'Y';
  • SELECT row_id, rule_description, last_updated_by, last_update_date FROM igs_ru_description_v WHERE last_update_date >= SYSDATE - 30;

Because the view has no documented joins or filters, the optimizer generally merges it into the base table, and predicates applied against view columns are pushed down to IGS_RU_DESCRIPTION. Queries should therefore filter on SEQUENCE_NUMBER or audit columns where possible to leverage base-table indexes. When extending or troubleshooting form RULF2000 behavior, developers should validate against the base table IGS_RU_DESCRIPTION directly, since the view deliberately exposes a reduced and partly synthetic column set.