Search Results igs_sv_crt_stdt_faddr_v




Overview

The APPS.IGS_SV_CRT_STDT_FADDR_V view is a Student System (IGS) database object that exposes foreign address information for newly created Non-Immigrant students. Within the Oracle E-Business Suite 12.1.1 and 12.2.2 data model, it functions as a reporting and integration access point that isolates a specific subset of student address records — namely foreign addresses associated with Non-Immigrant student registration activity — without requiring downstream consumers to understand the full structure of the underlying address storage.

The view is defined in the APPS schema with a status of VALID. Its role is primarily read-only: it presents a denormalized, purpose-built projection of address data that can be consumed by concurrent programs, reports, PL/SQL packages, OAF pages, or external interfaces that need to retrieve foreign address details for Non-Immigrant students. By filtering on address type and activity site at the view layer, the object enforces business scoping while keeping the column naming intuitive for consumers (the FN_ prefix denoting "foreign").

Underlying Base Objects

The view is documented as being defined over a single base object: IGS_SV_ADDRESSES, aliased as FADD in the view text. The ETRM metadata records no other documented base objects, and the view definition contains no joins — it is a straightforward filtered projection from that one table.

Two predicates are applied against the base table:

  • FADD.ACTIVITY_SITE_CD IS NULL — restricts rows to addresses not tied to a specific activity site.
  • FADD.ADDRESS_TYPE = 'F' — restricts rows to the foreign address type.

Because the view derives entirely from IGS_SV_ADDRESSES, any change to the structure or data of that base table is directly reflected in the view. There are no materialized components, aggregates, or grouping clauses; the view is a pure selection-and-projection layer.

Key Columns

The view exposes eight columns, each mapped from the base table with a foreign-address alias where appropriate:

The BATCH_ID and PERSON_ID columns serve as the primary linkage keys for joining to batch and person-centric entities elsewhere in the Student System.

Common Use Cases and Queries

Typical usage centers on extracting foreign address details for Non-Immigrant students during admissions, registration, or government reporting cycles. A simple retrieval by batch is common:

  • SELECT person_id, fn_address_line1, fn_city, fn_country_code FROM apps.igs_sv_crt_stdt_faddr_v WHERE batch_id = :p_batch_id;

Retrieval for a specific student, or joining to person and batch entities, follows the same pattern:

  • SELECT person_id, fn_address_line1, fn_address_line2, fn_city, fn_province, fn_country_code, fn_postal_code FROM apps.igs_sv_crt_stdt_faddr_v WHERE person_id = :p_person_id;
  • SELECT v.person_id, v.fn_country_code, v.fn_city FROM apps.igs_sv_crt_stdt_faddr_v v WHERE v.batch_id IN (SELECT batch_id FROM apps.igs_sv_batches WHERE ...);

Because the view pre-applies the foreign address and null activity site filters, report developers can query it directly without re-implementing those predicates. This makes it well suited for concurrent program data sources, BI Publisher report queries, and inbound/outbound interface extracts that require foreign address data for Non-Immigrant student populations.