Results for “sch_apl_to_id”

50+ results




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

Overview

The IGS_AD_SCHL_APLY_TO table resides in the IGS product family, commonly known as the Oracle Student System, and is documented as obsolete within Oracle EBS 12.1.1 and 12.2.2. Despite its legacy status, the table remains part of the historical schema shipped with the Student System module and is referenced by downstream admissions and application-staging tables. It stores information about the school or academic institution that an applicant is applying to, scoped under a specific organization unit. This enables the Student System to model the relationship between a prospective applicant and the target school or institution as identified during the admissions process.

From a Data Vault modeling perspective, the heuristic classification of this table is hub-leaning. This suggests the table functions primarily as a hub entity, where SCH_APL_TO_ID serves as the durable business key that uniquely identifies a "school applying to" record, independent of its surrounding descriptive attributes. The presence of a natural unique key on SCHOOL_APPLYING_TO and ORG_UNIT_CD reinforces this interpretation, since the combination of these two columns provides an alternate means of uniquely identifying the same business concept. Surrounding descriptive columns such as DESCRIPTION and CLOSED_IND would typically be modeled as satellite attributes in a formal Data Vault design.

Key Information Stored

The table contains ten documented columns. The most significant are summarized below, distinguishing the surrogate primary key from business-key candidates.

  • SCH_APL_TO_ID — The primary surrogate key, defined by the primary key IGS_AD_SCHL_APLY_TO_PK and also enforced through the unique index IGS_AD_SCHL_APLY_TO_U1. This identifier is the one propagated to dependent admissions tables.
  • SCHOOL_APPLYING_TO — A business-key candidate that holds the code or identifier of the school or institution the applicant is applying to. Combined with ORG_UNIT_CD, it forms the unique index IGS_AD_SCHL_APLY_TO_U2.
  • ORG_UNIT_CD — The organization unit code, which scopes the school-applying-to record to a particular organizational context. It is the second half of the U2 unique key.
  • DESCRIPTION — A descriptive text field providing a human-readable label or explanation of the school-applying-to record.
  • CLOSED_IND — A status indicator denoting whether the school-applying-to record is closed or inactive.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns capturing who created and last modified the record, when those actions occurred, and the login context of the last update.

Common Use Cases and Queries

Because IGS_AD_SCHL_APLY_TO is obsolete, direct querying of the table is uncommon in active implementations. However, in historical data migrations or when resolving stale foreign-key references, analysts may still need to join it to admissions and application-staging tables. A typical query pattern resolves the school description for a given applicant application:

  • Join IGS_SS_ADM_APPL_ALL to IGS_AD_SCHL_APLY_TO on SCH_APL_TO_ID to retrieve the school applied-to that is associated with each admission application.
  • Join IGS_SS_APP_PGM_STG to IGS_AD_SCHL_APLY_TO on SCH_APL_TO_ID to enrich staging records with the school-applying-to description before program-application processing.
  • Join IGS_AD_PS_APPL_INST_ALL or IGS_AD_PS_APPL_INST_INT on SCH_APL_TO_ID to associate external interface application records with the institution applied to.
  • Filter on CLOSED_IND to report only active school-applying-to definitions, and filter on ORG_UNIT_CD to scope results to a specific organization.

A representative SQL pattern is: SELECT a.SCH_APL_TO_ID, s.SCHOOL_APPLYING_TO, s.DESCRIPTION FROM IGS_SS_ADM_APPL_ALL a, IGS_AD_SCHL_APLY_TO s WHERE a.SCH_APL_TO_ID = s.SCH_APL_TO_ID;

Related Objects

The table is referenced by several admissions and application-staging objects through the SCH_APL_TO_ID foreign key, confirming its role as a hub-leaning reference entity.

  • IGS_SS_APP_PGM_STG — References IGS_AD_SCHL_APLY_TO through SCH_APL_TO_ID.
  • IGS_SS_ADM_APPL_ALL — References IGS_AD_SCHL_APLY_TO through SCH_APL_TO_ID.
  • IGS_AD_PS_APPL_INST_INT — References IGS_AD_SCHL_APLY_TO through SCH_APL_TO_ID.
  • IGS_AD_PS_APPL_INST_ALL — References IGS_AD_SCHL_APLY_TO through SCH_APL_TO_ID.

These relationships indicate that the school-applying-to entity is primarily consumed by the admissions application and applicant-institution interface processes. Given the table's obsolete classification, any dependent customizations or reports should be reviewed against current Student System replacements before continued use.