Search Results admp_get_aa_dtl

Overview

IGS_AD_GEN_002 is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, validated as VALID in both the 12.1.1 and 12.2.2 releases. It belongs to the Oracle Student System/Recruiting and Admissions (IGS) product family, specifically the Admissions (IGS_AD) module, and is classified as an OTHER API rather than a public or private API. The package encapsulates a large body of shared admissions business logic — primarily offer management, application instance status validation, and decision processing — that is consumed by other admissions packages rather than being called directly by external interfaces.

The package's central role is evident from its dependency profile: it references only two objects directly, IGS_AD_PS_APPL_INST and IGS_AD_PS_APPL_INST_ALL, which are the application-instance tables at the core of the admissions offer process. Conversely, it is referenced by 35 other packages, including IGS_ADMAPPLICATION_PUB, IGS_AD_APPL_EVAL_PKG, IGS_AD_OFFRESP_STATUS_WF, IGS_AD_PRC_TAC_OFFER, and numerous IGS_AD_VAL_* validation packages. This makes IGS_AD_GEN_002 a foundational utility layer within the admissions module, supporting offer response processing, application completion checks, and reconsideration logic.

Key Procedures and Functions

The ETRM metadata documents 24 procedures and functions. The ADMP_GET_* family provides read-only accessors for admissions data, including ADMP_GET_APPL_ID (retrieves the application identifier), ADMP_GET_AA_AAS, ADMP_GET_AA_CREATED, ADMP_GET_AA_DTL, ADMP_GET_AAL_SENT_DT, ADMP_GET_ACAI_ACADCD, ADMP_GET_ACAI_AOS_DT, and ADMP_GET_FEE_STATUS, which returns the current fee status for an application. These accessors are used throughout the admissions module to avoid duplicating retrieval logic.

Offer-response processing is handled by ADMP_EXT_TAC_ARTS, ADMP_EXT_VTAC_RETURN, and ADMS_EXT_TAC_ARTS, which support the extraction and return of TAC (offer) response data. Status and validation logic includes CHECK_ADM_APPL_INST_STAT, VALID_OFR_RESP_STATUS (validates offer response status values), RES_PENDING_FEE_STATUS (checks pending-fee status for a response), CHECK_ANY_OFFER_INST (determines whether any offer instance exists), and IS_APP_INST_COMPLETE (evaluates whether an application instance is complete).

Reconsideration and resubmission logic is implemented through ADMP_RESUB_INST, IS_INST_RECON_ALLOWED, RECONSIDER_APPL_INST, and RECON_APPL_INST, which govern whether an applicant may reconsider or resubmit an application instance and perform the associated updates. Together these procedures form the reusable admissions decision engine.

Tables Accessed

Through APPS synonyms the package reads and writes admissions tables including IGS_AD_PS_APPL_INST_ALL (the base application-instance table), IGS_AD_APPL_ALL, IGS_AD_APPL_LTR, IGS_AD_APPL_STAT, IGS_AD_APP_REQ, IGS_AD_CODE_CLASSES, IGS_AD_OFRDFRMT_STAT, IGS_AD_OFR_RESP_STAT, and IGS_AD_OU_STAT. These support application, letter, status, requirement, offer-response, and organizational-unit status processing.

Additional tables include HZ_PARTIES (party/person data), IGS_AS_GRD_SCH_GRADE (grade and schedule information), IGS_CA_INST_REL and IGS_CA_TYPE (instance relationships and calendar types), and the exclusion tables IGS_PE_COURSE_EXCL and IGS_PE_CRS_GRP_EXCL. These are consulted for eligibility, exclusion, and cross-module validation during offer and application-instance processing.

Usage Notes

IGS_AD_GEN_002 is an internal admissions package and is not intended for direct invocation by external custom code. It is called by the public API IGS_ADMAPPLICATION_PUB, by validation packages such as IGS_AD_VAL_AA, IGS_AD_VAL_AAL, IGS_AD_VAL_ACAI, and IGS_AD_VAL_ACAI_STATUS, and by workflow and processing packages including IGS_AD_OFFRESP_STATUS_WF and IGS_AD_PRC_TAC_OFFER. In practice it is invoked from Admissions forms, concurrent application-processing programs, and the offer-response workflow. Because its procedures are undocumented in parameter terms in the ETRM metadata, integrators should reference the validated API wrappers rather than calling these procedures directly.