Search Results pre_create_application

Overview

APPS.IGS_PRECREATE_APPL_PUB is a public PL/SQL package in the Oracle E-Business Suite Advanced Admissions (Student System) module. Its business purpose is to pre-create admissions applications from staged data. In the Oracle Student System admissions model, applicant and application data is first loaded into staging tables by external channels such as web self-service entry, bulk data loads, or third-party integrations. The pre-create process validates and promotes that staged information into the live application tables, establishing the applicant party, the program choices, and the associated application of record before fee assessment and workflow processing occur. The package is designated with an API classification of PUB, indicating it forms part of the supported public interface surface and may be called by external and internal consumers. Its status is VALID in the APPS schema for both 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM metadata documents three callable units within this package.

• PRE_CREATE_APPLICATION — The primary entry point for creating an admissions application. It processes a staged application record and drives the creation of the corresponding applicant party and application entities in the destination tables. Because only the name is documented, no parameter list is asserted here.
• PRE_CREATE_APPLICATION_INST — The instance-oriented variant of the pre-create routine, intended for processing a specific application instance record. It supports the case where an application is being materialized for a particular institution or offering context.
• INSERT_STG_FEE_REQ_DET — Inserts staging fee request detail. This unit bridges the pre-create process with the admissions fee engine by capturing the fee requirements that apply to the newly pre-created application.

Tables Accessed

The package reads and writes several groups of tables through APPS synonyms. Staging and application tables — IGS_SS_ADM_APPL_STG, IGS_SS_ADM_APPL_S, IGS_SS_ADMAPPL_PGM_S, and IGS_SS_APP_PGM_STG — hold the incoming staged application and program-choice data and the target application and program records. Setup and code validation tables — IGS_AD_CODE_CLASSES, IGS_AD_PRD_AD_PRC_CA, IGS_AD_SCHL_APLY_TO, IGS_AD_SS_APPL_TYP, IGS_CA_INST_REL, IGS_CA_STAT, and IGS_CA_TYPE — supply the admissions code classes, product pricing/calendar associations, school apply-to rules, application types, and the institution/calendar instance, status, and type definitions used to validate the promotion. Party data — HZ_PARTIES and IGS_PE_HZ_PARTIES — establishes or links the applicant's party record. Finally, FND_COLUMNS and FND_TABLES are Oracle Application Object Library dictionary tables, typically queried for dynamic metadata or column-level processing support.

Usage Notes

IGS_PRECREATE_APPL_PUB is an internal admissions API rather than an end-user form object. Its documented dependency graph shows it depends on FND_API, the Oracle EBS API error-handling and messaging standard used to return success, warning, and error status to callers, and is referenced by IGS_AD_WF_P2A, an admissions workflow package. This indicates the package is most commonly invoked as a step within the admissions workflow and pre-create processing chain, or by custom integration code that loads applicants from an external front end. Because FND_API conventions apply, callers should expect API-style status returns and should handle error and warning messages accordingly. Custom code should invoke only the documented public procedures and should not rely on package internals, which are subject to change across 12.1.1 and 12.2.2 maintenance levels.