Search Results reactivate_dependent

Overview

IGS_SV_ACT_DPND_BLK_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Student Systems (IGS) product family that supports the higher-education Student Information System components of EBS 12.1.1 and 12.2.2. The view exposes rows used by the SEVIS (Student and Exchange Visitor Information System) dependent-processing flow, restricted to dependent records whose action type is a reactivation. In functional terms, it supports the batch generation of dependent-related output such as print forms and SEVIS identifiers when a previously terminated or inactive dependent must be reactivated.

The view is deliberately narrow: it supplies the identifiers and code values needed to drive downstream printing or interface logic, rather than a full attribute set. Notably, it returns placeholder NULL values for the descriptive columns PERSON_NUMBER and PERSON_ID_LONG, which are surfaced as named columns purely to satisfy the expected cursor or report signature. This design pattern is common in IGS views that feed concurrent programs, where the shape of the result set must match a documented interface even when a given source table cannot supply every column.

Underlying Base Objects

The ETRM metadata for this object documents no referenced base objects, but the embedded view text is definitive: the single source is IGS_SV_DEPDNT_INFO, aliased in the query as DPDT. Every column in the projection is drawn from that table except PERSON_NUMBER and PERSON_ID_LONG, which are literal NULLs.

IGS_SV_DEPDNT_INFO is the IGS staging and processing table for SEVIS dependents. It holds the batch identifier, the person identifier of the primary student or scholar, the dependent identifier, the SEVIS identifier assigned to the dependent, print-form information, remarks text, and an action-type discriminator. The WHERE clause restricts output to DEPDNT_ACTION_TYPE = 'R', meaning the view is a functional subset of the base table dedicated to reactivation processing. The ETRM metadata lists the owner as blank and records no dependencies, so the base table relationship should be confirmed against the data dictionary in the target instance rather than assumed from documentation alone.

Key Columns

• BATCH_ID — Identifier of the processing batch to which the dependent record belongs; used to group and retrieve records for a single run.
• PERSON_ID — Internal identifier of the primary person (student, scholar, or exchange visitor) associated with the dependent.
• PRINT_FORM — Indicator of the form to be produced for the dependent, consumed by print or output logic.
• DEPDNT_ID — Internal identifier of the dependent record itself.
• PERSON_NUMBER — Exposed as NULL; retained only for interface or cursor compatibility.
• DEPDNT_SEVIS_ID — SEVIS identifier associated with the dependent, used in SEVIS-facing output.
• REACTIVATE_DEPENDENT — Alias for DP.DEPDNT_ACTION_TYPE-related remarks text, carrying the free-text note attached to the reactivation.
• PERSON_ID_LONG — Exposed as NULL. This is the column referenced by the search term "person_id_long"; it exists in the projection only as a placeholder and will always be null when queried directly.

Common Use Cases and Queries

Typical consumers are SEVIS reactivation concurrent programs, dependent print routines, and ad hoc diagnostics run by institutions verifying which dependents are queued for reactivation in a given batch.

Select all reactivation dependents for a batch:

SELECT batch_id, person_id, depdnt_id, depdnt_sevis_id, print_form
FROM   apps.igs_sv_act_dpnd_blk_v
WHERE  batch_id = :p_batch_id;

Retrieve the print-form and SEVIS identifier for a specific dependent:

SELECT person_id, depdnt_sevis_id, print_form, reactivate_dependent
FROM   apps.igs_sv_act_dpnd_blk_v
WHERE  depdnt_id = :p_depdnt_id;

Joining to the base table is unnecessary for action-type filtering, since the view already restricts to 'R'. Analysts searching on "person_id_long" should note that the column is defined as NULL and cannot serve as a join or filter key; the same applies to PERSON_NUMBER. Where a real person number or the long person identifier is required, obtain it from the person or dependent base tables rather than from this view.

Because the view is thin and carries no aggregation, performance is governed entirely by IGS_SV_DEPDNT_INFO and its indexes on BATCH_ID, PERSON_ID, and the action-type column. Reports should always supply a batch or person predicate to avoid full scans.