Results for “igf_ap_adm_setup_all”

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

Overview

IGF_AP_ADM_SETUP_ALL is a table registered within the IGF (Financial Aid) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The ETRM metadata classifies the object as Obsolete, and the documented implementation note states that it is not implemented in this database. This means the table exists in the data model dictionary for historical or upgrade-reconciliation purposes only; it is not an active transactional or configuration object in a current EBS release. The IGF module historically supported student financial aid processing, including admissions (ADM) workflow logic, award disbursement, and integration with Oracle Payables. Objects with the IGF_AP_ prefix belong to the financial-aid-to-Payables integration area, where admission and outcome statuses were staged before downstream processing.

From a data-modeling perspective, the ETRM FK analysis suggests a hub-leaning classification under Data Vault heuristics. The table carries a single-column surrogate primary key, ADM_PROCESS_SEQ, and is referenced by a dependent child table, which is the typical signature of a hub surrounded by a link or satellite structure. Treat this as a modeling suggestion rather than a normative definition; because the object is obsolete, no physical restructuring should be undertaken.

Key Information Stored

The documented physical schema lists eleven columns, of which the most significant are listed below. Note that only columns appearing in the ETRM metadata are named here.

• ADM_PROCESS_SEQ — the surrogate primary key, enforced by IGF_AP_ADM_SETUP_ALL_PK and additionally by the unique index IGF_AP_ADM_SETUP_ALL_U1. Because a single unique index exists on this column, it serves simultaneously as the surrogate identifier and the business-key candidate.
• ADM_APPL_STAT — admission application status, capturing the state of an applicant within the admissions process.
• ADM_OUTCOME_STAT — admission outcome status, recording the resolved result of the admissions decision.
• ADM_FEE_STAT — admission fee status, tracking payment state for application or processing fees.
• ADM_OFFER_RESP_STAT — admission offer response status, holding the applicant's response to an issued offer.
• ORG_ID — the multi-organization identifier, enabling operating-unit-level partitioning of setup rows.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS audit columns, recording row provenance and the actor and timestamp of each change.

The four ADM_*_STAT columns function as status code references; their meaning depends on lookup or value-set definitions that were configured within the IGF module. No descriptive name or date-effective columns are documented, which reinforces the conclusion that the table acted as a lightweight setup or staging anchor.

Common Use Cases and Queries

In supported releases, this table would have been queried to resolve the current status of an admissions process for reporting, reconciliation, or feed generation into Oracle Payables. A typical join pattern connects the setup row to its dependent trigger records:

• Status reporting: SELECT s.ADM_PROCESS_SEQ, s.ADM_APPL_STAT, s.ADM_OUTCOME_STAT, s.ADM_OFFER_RESP_STAT FROM IGF.IGF_AP_ADM_SETUP_ALL s WHERE s.ORG_ID = :org_id;
• Child lookup: SELECT t.* FROM IGF.IGF_AP_FA_TRIGGERS_ALL t, IGF.IGF_AP_ADM_SETUP_ALL s WHERE t.ADM_PROCESS_SEQ = s.ADM_PROCESS_SEQ;
• Audit reconciliation: filtering on LAST_UPDATE_DATE to identify setup rows modified within a period.

Because the object is obsolete and not implemented, these patterns are relevant primarily during upgrade analysis, historical data migration, or when interpreting legacy extract files. Any new development should avoid dependencies on this table and instead use the currently supported financial aid or student system objects.

Related Objects

The documented FK relationship identifies one dependent table, and the surrounding IGF_AP family provides the practical context.

• IGF_AP_FA_TRIGGERS_ALL — the only documented child table. It references IGF_AP_ADM_SETUP_ALL through IGF_AP_FA_TRIGGERS_ALL.ADM_PROCESS_SEQ → IGF_AP_ADM_SETUP_ALL.ADM_PROCESS_SEQ. This trigger table records downstream events keyed to an admissions process.
• IGF_AP_ADM_SETUP_ALL_PK and IGF_AP_ADM_SETUP_ALL_U1 — the primary key constraint and unique index, both on ADM_PROCESS_SEQ.
• Oracle Payables (AP) integration objects — the IGF_AP naming prefix indicates that records in this family were staged for transfer into the Payables schema; the trigger table carries the linkage used to drive that transfer.
• IGF module value sets and lookups — the ADM_*_STAT columns depend on lookup definitions maintained within the IGF configuration, which determined the valid status codes.

In summary, IGF_AP_ADM_SETUP_ALL is a documented but obsolete hub-style table in the IGF schema, keyed on ADM_PROCESS_SEQ, holding admissions status codes and standard audit columns, and referenced by IGF_AP_FA_TRIGGERS_ALL. It should be treated as historical metadata rather than an active integration point.