Search Results igs_pe_dyn_sqlsegs_s

Overview

The APPS.IGS_PE_DYNAMIC_PERSID_GROUP package body forms part of the Oracle E-Business Suite person and identifier management layer that underpins the Student System (IGS) product family. Its central purpose is to resolve and evaluate dynamic person identifier (PersID) groups — groupings of people that are not stored as static membership sets, but instead are derived at runtime by executing a generated SQL statement. This design allows institutions to define flexible population criteria, such as attributes held in the person base view, and have the correct constituent members computed consistently whenever the group is queried or processed.

The package resides in the APPS schema with a VALID status, and is classified as an OTHER API type rather than a public open interface. It is a dependent component of the wider IGS person infrastructure and is itself referenced by 27 other packages, indicating that it is a foundational utility consumed across admissions, records, and administrative processing.

Key Procedures and Functions

The package body exposes five documented procedures and functions. Their names reflect a build-and-execute pattern around dynamic SQL retrieval.

• IGS_GET_DYNAMIC_SQL — the principal entry point for constructing and returning the dynamic SQL text that defines a person identifier group's membership.
• GET_DYNAMIC_SQL — a companion routine supporting the retrieval of the dynamic SQL definition, typically used by internal or wrapper callers.
• GET_DYNAMIC_SQL_FROM_FILE — an alternative retrieval path that sources the dynamic SQL definition from a file rather than from the stored segment definitions.
• DYN_PIG_MEMBER — determines membership of a person within a dynamic PersID group, evaluating whether a given person satisfies the generated group criteria.
• IGS_POST_SAVE_DOCUMENT — a post-save processing routine associated with the persistence or saving of a dynamic group document definition.

These routines collectively implement the generate-execute-verify lifecycle: the SQL is built or loaded, the group membership is resolved, and the resulting definition is persisted.

Tables Accessed

Table access is made through APPS synonyms. Three documented base and interface tables are involved.

• IGS_PE_DYN_SQLSEGS — the primary store of SQL segment definitions that are concatenated to form the dynamic group query. The _S variant, IGS_PE_DYN_SQLSEGS_S, acts as the corresponding sequence or supporting structure used during insert and key generation.
• IGS_PE_PERSID_GROUP_ALL — holds the person identifier group definitions, including the dynamic group headers that the package processes.
• IGS_PE_PERSID_GROUP_V and IGS_PE_PERSON_BASE_V — views referenced for validation and for resolving person attributes during membership evaluation.

Usage Notes

This package is not intended for direct ad hoc invocation by end users. It is invoked indirectly through Oracle Forms-based person identifier group maintenance screens, where a user defines or edits a dynamic group and the package generates and validates the underlying SQL. It is also called by concurrent programs and by the 27 downstream packages that depend on dynamic group resolution — typically during batch population of groups or when membership lists are needed for reporting, communications, or processing rules.

Because the package relies on FND_API, FND_MESSAGE, FND_MSG_PUB, FND_GLOBAL, and IGS_GE_MSG_STACK, it observes the standard EBS API error-handling and message-stack conventions, returning status and message information rather than raising unhandled exceptions. It also depends on APP_EXCEPTION and AMS_DISCOVERER_PVT. Customizations should call the documented entry points rather than replicating the dynamic SQL construction, since segment assembly logic and validation are centralized here.