Search Results igs_pr_milestone_pkg




Overview
Explore in AI Chat

Overview

The package body APPS.IGS_PR_MILESTONE_PKG is a server-side PL/SQL construct belonging to the Oracle E-Business Suite application schema APPS. It resides within the student management family of modules—commonly associated with Oracle Student System and related institutional records—as implied by the IGS_ prefix used across its dependencies. Its classification within the ETRM (Enterprise Transaction Repository Model) metadata is OTHER, indicating that it is an internal implementation construct rather than a published, versioned open interface or public API.

Functionally, the package encapsulates the persistence and validation logic for admission "milestone" records. Milestones in this context represent administrative checkpoints applied to an applicant or candidature, such as the completion of a review stage, submission of documentation, or transition of a status. The package body provides the standard table-handler pattern used throughout Oracle EBS: an INSERT_ROW / UPDATE_ROW / DELETE_ROW triad alongside an ADD_ROW convenience wrapper and a BEFORE_DML trigger-support routine. Because the object is a package body with no documented public synonym or published API contract, it is intended primarily for consumption by other EBS packages and by the base table's database triggers rather than by end users or external systems.

Key Procedures and Functions

The ETRM metadata for release 12.1.1 documents twelve procedures and functions. Naming and purpose are as follows; no parameter signatures are asserted here beyond what the metadata confirms.

  • INSERT_ROW — Performs the physical insert of a new milestone row into the base table.
  • UPDATE_ROW — Applies modifications to an existing milestone row.
  • DELETE_ROW — Removes a milestone row, subject to the referential and validation checks enforced by the package.
  • ADD_ROW — A higher-level wrapper that coordinates the insert workflow, typically combining key derivation, defaulting, and the call to INSERT_ROW.
  • LOCK_ROW — Selects the target row with a locking clause to serialize concurrent modification before an update or delete.
  • BEFORE_DML — Invoked from the table's BEFORE INSERT OR UPDATE trigger to populate WHO columns via FND_GLOBAL, derive surrogate keys, and enforce attribute-level rules prior to physical DML.
  • CHECK_CONSTRAINTS — Centralizes the validation of business constraints that cannot be expressed as simple database constraints, raising conditions through APP_EXCEPTION and FND_MESSAGE.
  • GET_PK_FOR_VALIDATION — Returns the primary key of the row being processed so that dependent validation routines (for example IGS_RE_VAL_MIL) can reference the correct record.
  • GET_FK_IGS_RE_CANDIDATURE — Resolves or exposes the foreign key relationship to the candidature entity maintained by IGS_RE_CANDIDATURE_PKG.
  • GET_FK_IGS_PR_MILESTONE — Handles the self-referencing foreign key within IGS_PR_MILESTONE_ALL, used where milestones form a parent/child hierarchy.
  • GET_FK_IGS_PR_MS_STAT — Resolves the foreign key to the milestone status entity owned by IGS_PR_MS_STAT_PKG.
  • GET_FK_IGS_PR_MILESTONE_TYPE — Resolves the foreign key to the milestone type entity owned by IGS_PR_MILESTONE_TYP_PKG.

Tables Accessed

The only base table documented as referenced through APPS synonyms is IGS_PR_MILESTONE_ALL. This table stores the milestone instances themselves and is accessed for the full range of DML operations supported by the package body—insert, update, delete, and locked select. The three GET_FK_* routines read (or derive keys against) the parent entities that the table depends upon: the candidature record, the milestone status, the milestone type, and the table's own self-referencing parent. The metadata does not identify any additional tables written by the package body.

Usage Notes

IGS_PR_MILESTONE_PKG is an internal dependency rather than a user-facing entry point. It is referenced by seven other database objects, and its dependency list shows calls into IGS_RE_CANDIDATURE_PKG, IGS_RE_VAL_MIL, IGS_RE_GEN_003, IGS_RE_WORKFLOW, IGS_PR_MILESTONE_TYP_PKG, IGS_PR_MS_STAT_PKG, IGS_AS_VAL_SUAAP, and the shared utilities IGS_GE_DATE, IGS_GE_NUMBER, IGS_GE_GEN_003, and IGS_GE_MSG_STACK. Invocation therefore occurs from within other PL/SQL packages and from the base table's DML triggers, most commonly in response to admissions workflow activity driven by IGS_RE_WORKFLOW or status changes routed through IGS_PR_MS_STAT_PKG. It is not documented as being directly called by a concurrent program or a form. Custom extensions should not call this body directly; where integration is required, the supported path is the base table plus its triggers, or the owning public APIs. Because the metadata records no dependents outside this internal set, the package may be modified by patching without affecting external interfaces.