Results for “ctznship_cntry_code”

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

Overview

IGS_SV_EDT_BIO_V is a view owned by the APPS schema within the IGS (Student System) product family of Oracle E-Business Suite. Its documented purpose is to fetch biographic information, and it functions as a controlled presentation layer over the underlying student biographic data stored in the IGS batch-processing tables. In EBS 12.1.1 and 12.2.2, such views are typically consumed by concurrent programs, extracts, and third-party integrations that require a stable, denormalized projection of person-level biographical attributes without exposing the full internal table structure.

The view’s design reflects an EDT (external data transfer) or batch-oriented context. The driving logic joins the biographic detail table to a batch summary table and filters on a specific tag code and admission action code, meaning the view returns only rows that are part of an active, send-ready biographical batch. This makes it a task-specific reporting object rather than a general-purpose person view.

Underlying Base Objects

The view is defined over two documented base objects:

• IGS_SV_BIO_INFO (aliased BIO) — holds the actual biographic detail: names, birth date, gender, country codes, commuter flag, and suffix.
• IGS_SV_BTCH_SUMMARY (aliased BIOSUMM) — holds batch-level control information, including the batch identifier, person identifier, tag code, and admission action code.

The join is performed on BATCH_ID and PERSON_ID, and the result set is restricted by two predicates: BIOSUMM.TAG_CODE = 'SV_BIO' and BIOSUMM.ADM_ACTION_CODE = 'SEND'. Only records that satisfy both conditions are exposed, which ensures the view reflects biographic records staged for transmission rather than the complete biographic history. No further base objects are documented in the ETRM metadata.

Key Columns

• BATCH_ID — identifier of the batch to which the biographic record belongs; supports grouping of related records.
• PERSON_ID — the person identifier linking the record to the student or applicant.
• PRINT_FORM — flag or code indicating whether the record is destined for printed output.
• FIRST_NAME, LAST_NAME, MIDDLE_NAME, SUFFIX — the name components of the individual.
• BIRTH_DATE — date of birth.
• GENDER — gender code for the person.
• BIRTH_CNTRY_CODE — country of birth.
• CTZNSHIP_CNTRY_CODE — citizenship country code. This column is an alias: the view selects BIO.CITIZEN_CNTRY_CODE and renames it to CTZNSHIP_CNTRY_CODE in the output.
• COMMUTER — commuter indicator used in student administrative processing.

The aliasing of CITIZEN_CNTRY_CODE to CTZNSHIP_CNTRY_CODE is significant: an application or report searching for the token ctznship_cntry_code must query the view, not the base table, because the base table column carries a different name.

Common Use Cases and Queries

Typical uses include validating citizenship data ahead of a transmission batch, producing printed biographic forms, and feeding downstream systems that expect the CTZNSHIP_CNTRY_CODE naming convention. A representative query is:

SELECT person_id, first_name, last_name, birth_cntry_code, ctznship_cntry_code FROM apps.igs_sv_edt_bio_v WHERE batch_id = :batch_id;

Because the view already applies the SEND filter, callers do not need to replicate the tag and action predicates, which reduces the risk of inconsistent filtering across integrations. When troubleshooting missing citizenship values, developers should confirm the source column CITIZEN_CNTRY_CODE is populated in IGS_SV_BIO_INFO and that the corresponding IGS_SV_BTCH_SUMMARY row carries TAG_CODE 'SV_BIO' with ADM_ACTION_CODE 'SEND'.