Search Results sv_other

Overview

IGS_SV_CRT_STDT_OTHER_V is a reporting view in the Oracle E-Business Suite Student System (IGS) schema, owned by APPS. Its name decomposes as IGS (Student System), SV (Student Visa / SEVIS-related processing), CRT_STDT (create/derive student data), and OTHER, indicating that it consolidates "other" personal identification attributes for a student population being prepared for an external regulatory or interface process. The view is closely associated with the SEVIS (Student and Exchange Visitor Information System) batch framework, in which person records are grouped into batches identified by BATCH_ID and tagged with a TAG_CODE such as SV_OTHER or SV_LEGAL, then tracked through an administrative action code (ADM_ACTION_CODE) such as 'SEND'.

The view's role in Oracle EBS reporting and integration is to present, in a single denormalized result set, the batch, person, admission, and identification attributes required when an "other information" record is being transmitted. It serves as a read-only source for outbound data extraction, concurrent-program reporting, and diagnostic queries rather than as a transactional object. Because it is a view, no data is stored in it; every query resolves against underlying IGS tables at run time.

Underlying Base Objects

The ETRM metadata does not document referenced base objects explicitly, but the view text itself names the tables on which it depends. These are:

• IGS_SV_PERSONS — the driving table (aliased PERS), supplying BATCH_ID and PERSON_ID for the primary result rows.
• IGS_SV_BTCH_SUMMARY — referenced twice, once as otherSumm and once as leglSumm, supplying the batch/person linkage and the TAG_CODE and ADM_ACTION_CODE filter criteria.
• IGS_SV_OTH_INFO — the "other information" detail table (aliased othr), supplying DRIVERS_LICENSE, DRIVERS_LICENSE_STATE, SSN, and TAX_ID.
• IGS_SV_LEGAL_INFO — the legal/admission detail table (aliased legl), supplying I94_NUMBER.

The two detail tables are joined to IGS_SV_PERSONS by BATCH_ID and PERSON_ID and are outer-joined (denoted by the (+) operator), so a person row survives even when no matching legal or other-information record exists. The batch-summary subqueries are restricted to TAG_CODE 'SV_OTHER' or 'SV_LEGAL' with ADM_ACTION_CODE = 'SEND'. An EXISTS clause against IGS_SV_BTCH_SUMMARY further requires that the person/batch combination carry at least one of those tags in a sendable state, ensuring only actionable records are returned.

Key Columns

• BATCH_ID — identifier of the processing batch to which the person record belongs; used to group and reconcile an extraction run.
• PERSON_ID — the internal unique identifier of the person (student or dependent) in the Student System.
• ADMISSION_NUMBER — column alias for LEGL.I94_NUMBER, the I-94 admission number associated with the legal information record.
• DRIVERS_LICENSE and DRIVERS_LICENSE_STATE — the driver's license number and issuing state from IGS_SV_OTH_INFO.
• SSN — the Social Security Number held for the person.
• TAX_ID — the tax identification number recorded for the person.

Common Use Cases and Queries

Typical scenarios include auditing which persons are queued for an "other information" send, reconciling batch contents before transmission, and extracting identification attributes for downstream reporting. A representative query retrieves all rows for a single batch:

• SELECT batch_id, person_id, admission_number, drivers_license, drivers_license_state, ssn, tax_id FROM apps.igs_sv_crt_stdt_other_v WHERE batch_id = :p_batch_id;
• SELECT person_id, ssn, tax_id FROM apps.igs_sv_crt_stdt_other_v WHERE person_id = :p_person_id;

Because the view applies the TAG_CODE and ADM_ACTION_CODE filters internally, callers need not repeat them; they need only restrict by batch or person. Reports should note that outer joins may yield NULL identification values for persons lacking matching detail records.