Search Results igs_ru_turin_rule_gr_pkg




Overview
Explore in AI Chat

Overview

IGS_RU_TURIN_RULE_GR_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the ETRM (E-Business Suite Technical Reference Manual) as an "OTHER" API type. It belongs to the IGS (Student Systems / Higher Education) product family, specifically the RU (Regulatory Unit) module, and governs the persistence and integrity of the IGS_RU_TURIN_RULE_GR entity. In the Oracle EBS 12.1.1 and 12.2.2 releases, this package functions as a table-handler or gateway package that encapsulates DML operations against the IGS_RU_TURIN_RULE_GR table, exposing controlled procedure calls rather than permitting direct SQL manipulation. This design enforces validation rules, primary and foreign key consistency, and concurrency control for the underlying Turin rule group configuration data used within the regulatory unit framework.

Key Procedures and Functions

The ETRM documentation records eleven callable units. Their purposes are as follows:

  • INSERT_ROW — inserts a new row into the base table, applying column defaults and validation.
  • UPDATE_ROW — modifies an existing row identified by its primary key.
  • DELETE_ROW — removes a row from the base table.
  • LOCK_ROW — acquires a row-level lock to support optimistic concurrency control during multi-user updates.
  • ADD_ROW — a convenience wrapper combining insert behaviour, typically invoked after a preceding lock or existence check.
  • GET_PK_FOR_VALIDATION — derives or validates the primary key value (the unique identifier for a Turin rule group record).
  • GET_UK_FOR_VALIDATION — resolves the unique key used to verify that no duplicate rule-group combination exists.
  • GET_FK_IGS_RU_GROUP — retrieves and validates the foreign key relationship to the IGS_RU_GROUP parent entity.
  • GET_FK_IGS_RU_TRG_GROUP_CD — retrieves and validates the foreign key relationship to the IGS_RU_TRG_GROUP_CD target group code entity.
  • CHECK_CONSTRAINTS — performs generic constraint checks before DML is committed.
  • BEFORE_DML — a pre-DML hook that normalises and validates attribute values prior to insert or update.

Tables Accessed

The only documented table referenced through APPS synonyms is IGS_RU_TURIN_RULE_GR, which stores the association between regulatory unit groups and Turin rule definitions. The package reads, inserts, updates, and deletes rows in this table, and through GET_FK_IGS_RU_GROUP and GET_FK_IGS_RU_TRG_GROUP_CD it validates the referential integrity of that data against parent entities. The foreign-key helpers imply the table carries at least two foreign key columns: one to the IGS_RU_GROUP entity and one to IGS_RU_TRG_GROUP_CD. Because the table is accessed only via APPS synonyms, the package operates under standard EBS schema-synonym conventions.

Usage Notes

This package is not intended for ad-hoc direct invocation; it is a supporting gateway for higher-level RU configuration packages. Two documented dependents call it: IGS_RU_GROUP_PKG and IGS_RU_TRG_GROUP_CD_PKG (the latter also appears in the reference list as an internal self-reference). These callers invoke the DML procedures when maintaining group membership and rule-group assignments through the relevant OAF or Forms-based setup screens. In custom development, the package should be called only through its documented procedural interface—INSERT_ROW, UPDATE_ROW, DELETE_ROW, and their companions—rather than issuing direct SQL, so that validation, key derivation, and the BEFORE_DML logic remain enforced. It is not associated with a standalone concurrent program in the documentation, and the package body status is VALID in both 12.1.1 and 12.2.2. Because the ETRM exposes no parameter lists, implementers should inspect the live package specification via ALL_ARGUMENTS or the database object browser before writing custom callers.