Search Results igs_ad_citizen_int

Overview

The view IGS_AD_CITIZEN_INT belongs to the Oracle E-Business Suite product group IGS – Student System, which is flagged as obsolete in the ETRM repository for releases 12.1.1 and 12.2.2. The view is a single-table view defined over IGS_AD_CITIZEN_INT_ALL, the open-interface (staging) table used by the Student System admissions module to hold incoming citizenship and residency records prior to validation and import into the base citizen tables. Its primary purpose is to expose the interface table with a stable, documented column list and to apply the organization-level security predicate implied by the _ALL suffix on the underlying table.

Because the object is an interface view rather than a transactional entity view, it does not represent a reporting endpoint for production admissions data. Instead, it is the read layer consumed by concurrent programs, import routines, and diagnostic queries that examine records pending conversion. ETRM records the implementation status as "Not implemented in this database," meaning the view is shipped as part of the IGS schema definition but is not present in every installation, typically because the Student System product is not licensed or has been superseded.

Underlying Base Objects

The view text selects exclusively from IGS_AD_CITIZEN_INT_ALL, using the alias TAB. Every column exposed by the view is a direct projection of the corresponding column in the base interface table, prefixed in the source query by TAB. There are no joins, unions, subqueries, or aggregations in the definition. The view also exposes TAB.ROWID as ROW_ID, which allows consumers to address individual interface rows for update or deletion during processing.

The ETRM metadata lists no referenced base objects beyond the interface table itself, which is consistent with a pass-through definition. The _ALL designation on the base table indicates that the organization identifier ORG_ID participates in the data model and is surfaced unchanged by the view; filtering by organization is therefore the responsibility of the calling application or report rather than the view definition.

Key Columns

• INTERFACE_CITIZEN_ID, INTERFACE_ID — Primary and grouping identifiers for the staged interface record.
• DOCUMENT_TYPE, DOCUMENT_REFERENCE — Classification and external reference of the supporting document associated with the citizenship record. The user's search term document_reference maps directly to the DOCUMENT_REFERENCE column, which carries the free-text identifier of the document supplied by the student or captured during data entry.
• COUNTRY_CODE — Country to which the citizenship, residency, or document applies.
• DATE_RECOGNIZED, DATE_DISOWNED, END_DATE — Effective dating for the citizenship claim, including the date it was formally recognized and the date it ceased to apply.
• STATUS, MATCH_IND, ERROR_CODE — Processing state of the interface row: whether it has been validated, whether it matched an existing person record, and the error returned when validation fails.
• DUP_CITIZENSHIP_ID — Points to a suspected duplicate citizenship record detected during processing.
• BIRTH_OR_SELECTED — Flag distinguishing citizenship acquired by birth from citizenship selected or elected by the person.
• Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, REQUEST_ID, PROGRAM_UPDATE_DATE, ORG_ID.

Common Use Cases and Queries

Typical usage is pre-import validation and exception reporting. A common pattern is to inspect errored rows before re-running the import:

• SELECT interface_citizen_id, document_type, document_reference, country_code, error_code FROM igs_ad_citizen_int WHERE status = 'E' AND org_id = :org_id;
• SELECT document_reference, country_code, date_recognized FROM igs_ad_citizen_int WHERE document_type = :doc_type AND match_ind IS NULL;
• SELECT * FROM igs_ad_citizen_int WHERE request_id = :request_id; — reviewing rows created by a specific concurrent request.

Because the view performs no filtering, all organization and status predicates must be supplied explicitly. Queries against obsolete IGS objects should be limited to historical auditing and migration analysis in releases 12.1.1 and 12.2.2.