Search Results psp_import

Overview

The APPS.IGS_PS_GENERIC_PUB package body is the public API layer of the Oracle E-Business Suite student systems product family, specifically the Student Records (IGS) module associated with the Oracle Student System. The _PUB suffix identifies it as a published, externally callable API package conforming to the Oracle Application Object Library public API naming standard, while the actual business logic is delegated to the private package IGS_PS_GENERIC_PVT. The package provides a controlled, wrapper-based entry point into the generic prospect and admissions processing routines that would otherwise be inaccessible to external callers. Its status is recorded as VALID in the APPS schema, confirming that the compiled specification and body are consistent and that all referenced dependencies resolve correctly in both Oracle EBS 12.1.1 and 12.2.2 environments.

Key Procedures and Functions

The ETRM metadata documents a single public procedure in this package: PSP_IMPORT. Consistent with Oracle's public API design convention, PSP_IMPORT is an import routine intended to ingest external data into the IGS prospect and admissions schema. It operates as a thin public wrapper that validates the incoming parameters and message tokens, then invokes the corresponding private implementation in IGS_PS_GENERIC_PVT or a related legacy handler such as IGS_PS_UNIT_LGCY_PVT. Because the documented metadata exposes only the procedure name and not its formal parameter list, no parameter signatures or argument orders should be assumed; integrators must consult the specification source before invocation.

Tables Accessed

Although the object metadata does not enumerate SQL statements in the excerpt, the dependent-code listings and the documented table references establish the data footprint. The package writes to and reads from the core student admissions and enrolment tables, including IGS_PS_NSUS_RTN and IGS_PS_NSUS_RTN_DTL (non-standard use return records and their detail lines), IGS_PS_LGCY_UR_INT (legacy unit rule interface), IGS_PS_RSV_USEC_PRF and IGS_PS_RSV_USEC_PRI (reserved use preference and priority definitions), IGS_PS_RPT_FMLY_ALL (reporting family), IGS_PS_RPT_FMLY_ALL-related configuration, and IGS_PS_NSUS_RTN. Reference and cross-module data are drawn from IGS_AD_BUILDING_ALL and IGS_AD_ROOM_ALL for location and room validation, IGS_CA_INST_ALL for calendar instances, IGS_AS_US_AI_GROUP for assessment groups, IGS_EN_NSTD_USEC_DL and IGS_EN_USEC_DISC_DL for enrolment use-code and discipline details, and IGS_GE_NOTE and IGS_GE_REF_CD for notes and reference-code lookups. Party data is validated against HZ_PARTIES, the TCA party registry, ensuring that any person imported through the routine maps to a valid trading community record.

Usage Notes

IGS_PS_GENERIC_PUB is not referenced by any database object in the documented dependency graph, which indicates it is designed for inbound invocation rather than internal server-side composition. It is typically called from Student System concurrent programs, from OAF or Forms-based maintenance pages, or from custom PL/SQL integration routines that need to load prospect, unit, or non-standard-use data. The package relies on FND_API, FND_MESSAGE, and FND_MSG_PUB for its standard error-handling and message-stack contract, so callers should declare the standard API result record and check the return status rather than relying on exceptions. Because it is referenced by seven other packages, changes to its specification should be treated as a public interface change and regression-tested across the student records module. All error handling, validation, and rollback semantics are inherited from the underlying private package.