Results for “person_id_long”

50+ results




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

Overview

IGS_SV_UPD_DPND_BLK_V is a PL/SQL view owned by the APPS schema in the Oracle E-Business Suite Student System (IGS) product family. Its documented purpose is to supply the row-level data required to construct the XML block that describes updated dependent information for a student. In the context of the IGS Student System, this view forms part of the seeding infrastructure used by the SEVIS (Student and Exchange Visitor Information System) processing and reporting flows, where dependent records that have undergone an update action must be extracted and formatted for transmission or reporting.

Because the view filters on the dependent action type, it presents a purpose-built result set rather than a full copy of the underlying dependent data. This makes it suitable for batch-driven integrations, concurrent program data sources, and XML generation routines that require only those dependent records flagged as updated.

Underlying Base Objects

The view is defined over a single documented base object, IGS_SV_DEPDNT_INFO, aliased as DPDT in the view text. The ETRM metadata records no additional referenced base objects. All columns exposed by the view are projected directly from IGS_SV_DEPDNT_INFO, with the exception of three columns that are populated as literal NULL values or aliases.

The defining predicate is WHERE DPDT.DEPDNT_ACTION_TYPE = 'U', restricting output to dependent records whose action type indicates an update. There is no join logic in the view, so each row in the view corresponds to exactly one qualifying row in IGS_SV_DEPDNT_INFO. The view therefore acts as a filtered projection, not an aggregation or a join-derived structure.

Key Columns

  • BATCH_ID — Identifier of the batch to which the dependent update record belongs, used to group output for processing runs.
  • PERSON_ID — The person identifier of the student or primary record associated with the dependent.
  • PRINT_FORM — Flag or indicator controlling whether the dependent record is included in printed form output.
  • DEPDNT_ID — The unique identifier for the dependent record itself.
  • PERSON_NUMBER — Exposed as a literal NULL in the view text; the person number is not sourced from the base table.
  • DEPDNT_SEVIS_ID — The SEVIS identifier assigned to the dependent, central to SEVIS reporting.
  • LAST_NAME, FIRST_NAME, MIDDLE_NAME, SUFFIX — Name components of the dependent.
  • BIRTH_DATE, GENDER, BIRTH_CNTRY_CODE — Demographic attributes of the dependent.
  • CITIZENSHIP_CNTRY_CODE — Exposed as an alias over the base column CITIZEN_CNTRYY_CODE.
  • VISA_TYPE, RELATIONSHIP, REMARKS — Visa classification, relationship to the student, and free-text remarks.
  • PERSON_ID_LONG — Listed in the view columns and returned as a literal NULL, matching the user's search term; no long person identifier is populated by this view.

Common Use Cases and Queries

The primary use case is extraction of updated dependent data for XML block generation within the IGS SEVIS interface. A typical query retrieves all updated dependents for a given batch:

  • SELECT batch_id, person_id, depdnt_id, last_name, first_name, relationship FROM igs_sv_upd_dpnd_blk_v WHERE batch_id = :p_batch_id;
  • SELECT person_id, depdnt_sevis_id, birth_date, gender FROM igs_sv_upd_dpnd_blk_v WHERE person_id = :p_person_id;
  • SELECT * FROM igs_sv_upd_dpnd_blk_v ORDER BY batch_id, depdnt_id;

Note that queries referencing PERSON_ID_LONG or PERSON_NUMBER will return NULL, since both columns are deliberately exposed as placeholders. Any downstream logic requiring the long person identifier must obtain it from another source.