Search Results igs_pr_rule_pkg




Overview
Explore in AI Chat

Overview

IGS_PR_RULE_PKG is a PL/SQL package owned by the APPS schema within the Oracle E-Business Suite environment. It belongs to the iGS (Intelligent Grants System) product family, which supports the administration of grants, awards, and sponsored research. The package provides the core data-access and maintenance layer for eligibility and processing rules associated with the IGS_PR_RULE_ALL table, which is part of the Prospect Rule subsystem. In the grants processing model, prospect rules determine how applicants, proposals, or certification records are evaluated against configured eligibility criteria. IGS_PR_RULE_PKG encapsulates the procedural logic required to create, modify, lock, and delete rule records, and to enforce the referential and constraint integrity of those records before they are committed to the database.

The package is classified in the ETRM repository as an OTHER API type, meaning it is an internal infrastructure package rather than a public, externally facing business API. Its status is VALID, confirming that it compiles cleanly and is available in the documented 12.1.1 environment. The package consists of a specification and a body, and it depends directly on the SYS.STANDARD package, the fundamental PL/SQL package always present in an Oracle database.

Key Procedures and Functions

The ETRM documentation records ten procedures and functions within the package. They fall into three broad categories: row maintenance, key resolution, and DML constraint enforcement.

  • INSERT_ROW — Performs insertion of a new rule record into the underlying table, applying the package's standard column population logic.
  • UPDATE_ROW — Applies modifications to an existing rule record, typically after the row has been locked and validated.
  • ADD_ROW — Provides the combined lock-free creation path used when a caller needs to add a rule record through the package rather than through direct SQL.
  • DELETE_ROW — Removes an existing rule record, subject to the package's constraint checks.
  • LOCK_ROW — Acquires a row-level lock on the target record to serialize concurrent maintenance, preventing lost updates during the insert/update cycle.
  • GET_PK_FOR_VALIDATION — Resolves or validates the primary key of the rule record, ensuring a valid identifier exists before DML proceeds.
  • GET_FK_IGS_PR_RU_CAT — Retrieves the foreign key reference to the rule category entity, supporting category-based rule classification.
  • GET_FK_IGS_RU_RULE — Retrieves the foreign key reference linking the record to the parent rule definition.
  • BEFORE_DML — A pre-DML hook invoked to perform validation and defaulting prior to an insert or update being applied.
  • CHECK_CONSTRAINTS — Verifies that the record satisfies the documented integrity constraints, including required foreign key values and uniqueness rules, before the DML is permitted.

No parameter signatures are published in the ETRM excerpt; callers should treat these as internal entry points and reference the package specification in the database for exact signatures.

Tables Accessed

The package operates on a single documented table, IGS_PR_RULE_ALL, accessed through the APPS synonym layer. IGS_PR_RULE_ALL is the multi-organization-style base table holding prospect rule definitions. All maintenance procedures described above ultimately read from or write to this table. The foreign key helpers GET_FK_IGS_PR_RU_CAT and GET_FK_IGS_RU_RULE imply that IGS_PR_RULE_ALL carries references to a rule category table and a parent rule table, and these lookups are resolved by the package before DML is committed. Because the package is the sanctioned access path for this table, direct SQL against IGS_PR_RULE_ALL from custom code bypasses validation and is not recommended.

Usage Notes

IGS_PR_RULE_PKG is not intended to be invoked directly by end users. It is referenced by three other packages — IGS_PR_RULE_PKG itself (internal recursive reference in the dependency report), IGS_PR_RU_APPL_PKG, IGS_PR_RU_CAT_PKG, and the concurrent program / program unit IGS_RU_GEN_005 — indicating that rule application, rule category maintenance, and rule generation processes consume its procedures. Typical invocation therefore occurs from Oracle Forms-based maintenance screens in the iGS Grants modules, from the IGS_RU_GEN_005 concurrent program responsible for generating rule records, and from other PL/SQL packages that manage rule categories and rule application. Customizations should call the documented entry points in the same sequence used internally: lock, validate, check constraints, then insert or update. Because the package is owned by APPS and marked VALID, it is available without additional grants to code executing in the APPS schema, but direct references from other schemas would require explicit synonyms and privileges.