Results for “igs_ad_imp_004”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGS_AD_IMP_004 is an Oracle EBS PL/SQL package owned by the APPS schema and classified under the ETRM metadata as OTHER (a general-purpose package rather than a published public API). It belongs to the Oracle Student System (formerly Oracle iLearning/Student Administration) Admissions module, as indicated by the IGS_AD prefix. The package header declares AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the invoking user rather than the definer, a common convention for internal interface-processing routines that operate on interface staging data.

Its principal role is the processing of admissions application interface records. The single documented procedure, PRC_APPCLN, is designed to process staged application data held in the admissions interface tables, applying configuration rules and legacy indicators to determine how each interface row is validated, transformed, and subsequently loaded into the live admissions tables. The source header ($Header: IGSAD82S.pls 115.12 2003/12/09) confirms this is long-standing code carried forward into EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes exactly one documented procedure:

• PRC_APPCLN — The application-clearing / application-processing routine. Based on its documented parameters, it accepts an interface run identifier (p_interface_run_id), a processing rule selector (p_rule), a logging enablement flag (p_enable_log), and a legacy indicator (p_legacy_ind). The interface run identifier scopes the procedure to a specific batch of interface rows created by a prior import step. The rule parameter selects the validation or matching logic to apply, the logging flag controls whether processing diagnostics are written, and the legacy indicator distinguishes data originating from legacy systems from data captured natively in Oracle Student System. The procedure coordinates the reading of interface rows, application of business rules, and writing of processed results.

The package body is not documented beyond this procedure, so no additional callable units should be assumed.

Tables Accessed

The package references a broad set of admissions and related reference tables through APPS synonyms:

• IGS_AD_INTERFACE_ALL — the master admissions interface table, holding staged records and the interface_run_id used to scope processing.
• IGS_AD_APL_INT, IGS_AD_APPHIST_INT, IGS_AD_INSTHIST_INT, IGS_AD_PS_APPL_INST_INT — interface staging tables for applications, application history, institution history, and person/application institution data.
• IGS_AD_APPL_ALL, IGS_AD_APPL_STAT, IGS_AD_PS_APPL_INST_ALL — the live admissions application, application status, and application institution tables populated by the import.
• IGS_AD_CODE_CLASSES, IGS_AD_FEE_STAT, IGS_AD_SS_APPL_TYP, IGS_CO_CAT, IGS_EN_ENROLMENT_CAT, IGS_FI_HECS_PAY_OPTN — configuration and reference data used to validate and categorise incoming records, including fee status, application type, course category, enrolment category, and HECS payment option.
• HZ_PARTIES — the TCA party table, used to match or create the person record associated with each application.

Usage Notes

PRC_APPCLN is typically invoked by an admissions import concurrent program or by the parent interface-processing package that references IGS_AD_IMP_004 (ETRM records one referencing package). It is not intended for direct interactive use from a form, although administrators may trigger it indirectly through the Student System admissions import submission screens.

Because the procedure is driven by an interface_run_id, callers must first stage data into the IGS_AD_INTERFACE_ALL and related _INT tables and capture the generated run identifier. The p_rule and p_legacy_ind parameters should be supplied consistently with the run configuration; mismatches can cause partial or rejected processing. The p_enable_log flag should be enabled during troubleshooting in development or test environments and generally disabled in production to avoid excessive logging. As an internal, undocumented package, customization carries upgrade risk across 12.1.1 and 12.2.2 patches, and Oracle support does not guarantee backward compatibility of its signature.