Search Results igf_ap_housing_map_v




Overview
Explore in AI Chat

Overview

IGF_AP_HOUSING_MAP_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IGF (Financial Aid) product module. Its documented purpose is Housing Status Mapping. The view presents the institution's mapping of a student's housing status to a financial aid housing plan, resolved against two lookup types and an academic calendar instance. In EBS 12.1.1 and 12.2.2 the object is registered as a VALID view, meaning it is a supported, queryable artifact for reporting and integration rather than an internal, undocumented structure.

Because it is a view and not a table, it carries no independent storage and imposes no additional maintenance burden. It exposes the intersection of the housing mapping table with descriptive lookup meanings, which allows downstream consumers—Oracle Discoverer workbooks, BI Publisher reports, custom OAF pages, or inbound/outbound interfaces—to read human-readable descriptions without performing their own lookup joins. This is the primary value of the view: it denormalizes code values into meanings at the point of access.

Underlying Base Objects

The view is defined over four referenced objects. The driving table is IGF_AP_HOUSING_MAP (aliased APM), which stores the actual housing status mapping rows and is the source of the ROWID and the audit columns. IGS_LOOKUPS_VIEW (IGS) supplies the meaning for the housing status code from lookup type PE_TEA_PER_RES. IGF_LOOKUPS_VIEW (IGF) supplies the meaning for the housing plan code from lookup type IGF_SCHOOL_HOUSE_TYPE. IGS_CA_INST (CA) supplies the academic calendar instance attributes—start date, end date, and alternate code—for the calendar type and sequence number recorded on the mapping row.

  • IGF_AP_HOUSING_MAP (APM) — the mapping entity and the only table in the join; all other participants are views.
  • IGS_LOOKUPS_VIEW (IGS) — filtered to LOOKUP_TYPE = 'PE_TEA_PER_RES', joined on LOOKUP_CODE = APM.HOUSING_STAT_CODE.
  • IGF_LOOKUPS_VIEW (IGF) — filtered to LOOKUP_TYPE = 'IGF_SCHOOL_HOUSE_TYPE', joined on LOOKUP_CODE = APM.AP_HOUSE_PLAN_CODE.
  • IGS_CA_INST (CA) — joined on CAL_TYPE and SEQUENCE_NUMBER to resolve the calendar instance dates.

All three joins are inner joins with no outer-join syntax in the documented view text. Consequently, a mapping row is visible only when valid lookup codes exist for both the housing status and the housing plan, and when a matching calendar instance exists. Rows with orphaned or inactive lookup codes silently drop out of the result set.

Key Columns

Common Use Cases and Queries

Typical uses include reviewing the housing status mapping for a given calendar instance, validating that every mapping resolves to a live lookup meaning, and feeding reporting layers that display descriptions rather than codes.

  • Reporting the complete mapping for an aid year.
  • Auditing unmapped or stale lookup codes (best performed against the base table, since the view drops unmatched rows).
  • Driving needs-analysis or packaging rules that translate housing status into a housing plan.

Sample query listing mappings for a calendar instance, ordered by status:

SELECT ci_cal_type, ci_sequence_number, housing_stat_code, housing_stat_desc, ap_house_plan_code, ap_house_plan_desc, ci_start_dt, ci_end_dt FROM apps.igf_ap_housing_map_v WHERE ci_cal_type = :p_cal_type AND ci_sequence_number = :p_seq ORDER BY housing_stat_desc;

Sample query confirming coverage of the PE_TEA_PER_RES lookup by matching mapping rows:

SELECT housing_stat_code, housing_stat_desc, COUNT(*) FROM apps.igf_ap_housing_map_v GROUP BY housing_stat_code, housing_stat_desc ORDER BY housing_stat_code;