Search Results proof_of_immun

Overview

IGS_AD_INTERFACE_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, residing in the Student System (IGS) product family. It exposes the staging interface used by the Admissions and Student Data (AD) module to load person, applicant, and student records into the core TCA person registry. The view presents rows from an underlying interface table together with derived, user-readable values, so that concurrent interface programs and diagnostic reports can inspect inbound records before, during, and after a validation run. Because it is a view and not a table, it is read-only from a functional standpoint; corrections are made to the base interface table and the load is resubmitted.

The _V suffix indicates a validation/reporting view rather than a form-block view. Its principal role in EBS reporting and integration is to provide a self-describing staging layer: each row carries an interface identifier, batch and run identifiers, error and record status codes, and standard WHO and concurrent-program audit columns. The view exposes the column referenced in user searches — proof_of_immun — alongside proof_of_insurance and military_service_reg, which are admissions-specific person attributes captured during the interface load.

Underlying Base Objects

The ETRM metadata for this object documents no referenced base objects at the 12.2.2 level. In practice the view is defined with a simple single-table SELECT over the IGS_AD_INTERFACE staging table, aliased as i, using i.rowid as the row_id pseudo-column. The only subquery in the definition resolves the gender lookup: a correlated scalar subquery against FND_LOOKUP_VALUES supplies sex_meaning when i.sex is not null, filtering on LOOKUP_TYPE = 'HZ_GENDER', VIEW_APPLICATION_ID = 222, SECURITY_GROUP_ID = 0, and LANGUAGE = USERENV('LANG').

Relationally, therefore, IGS_AD_INTERFACE_V is a one-to-one projection of its base staging table: one row in the table yields exactly one row in the view. It carries no join logic that would fan out or restrict rows, which makes its cardinality identical to the underlying interface table. The dependency on FND_LOOKUP_VALUES means that gender descriptions returned by the view are language-sensitive and respect the session's NLS language setting.

Key Columns

• interface_id, interface_run_id, batch_id — uniquely identify an inbound record, its processing run, and its batch grouping; used for restart and purge logic.
• person_number, person_id, match_ind, person_match_ind — identity and deduplication controls indicating whether the row matched an existing person.
• surname, given_names, middle_name, preferred_given_name, pre_name_adjunct, title, suffix — person name components.
• sex and sex_meaning — coded gender value and its translated lookup meaning.
• birth_dt, pref_alternate_id, level_of_qual — demographic and prior-qualification attributes.
• proof_of_insurance, proof_of_immun, military_service_reg, veteran — admissions-specific certifications and service indicators.
• status, record_status, error_code — processing outcome and validation failure diagnostics.
• attribute_category and attribute1 through attribute24 — the descriptive flexfield segment columns for institution-defined data.
• created_by, creation_date, last_updated_by, last_update_date, last_update_login, request_id, program_application_id, program_id, program_update_date — standard WHO and concurrent request audit columns.

Common Use Cases and Queries

Typical uses include pre-load data verification, post-load error triage, reconciliation of interface batches against created persons, and ad hoc institutional reporting on admissions attributes such as immunization proof. A representative query counts records pending processing within a batch:

SELECT batch_id, status, COUNT(*) FROM apps.igs_ad_interface_v WHERE record_status = 'P' GROUP BY batch_id, status;

To isolate records carrying immunization data together with translated gender:

SELECT interface_id, person_number, surname, given_names, sex_meaning, proof_of_immun, error_code FROM apps.igs_ad_interface_v WHERE proof_of_immun IS NOT NULL AND error_code IS NOT NULL ORDER BY creation_date DESC;

Because the view exposes row_id, it can also be used to drive targeted corrections on the base staging table, for example updating a specific interface row identified through the view, then resubmitting the interface concurrent program to reprocess the batch.