Search Results igs_sv_act_dpnd_blk_v

Overview

IGS_SV_ACT_DPND_BLK_V is a reporting view owned by the APPS schema in the Oracle E-Business Suite Student System (IGS) product family. Its documented purpose is to supply the data required to construct an XML block describing the activation of a dependent for a student. In practice, this view serves as a pre-joined, purpose-built extraction layer that feeds XML-based integrations and concurrent-program reporting where dependent activation records must be rendered in a structured payload. The view is marked VALID in ETRM and is available in both Oracle EBS 12.1.1 and 12.2.2 environments.

The view is narrowly scoped: its defining query restricts output to a single dependent action type, namely 'R', which represents a reactivation action. As a result, the view does not present the full universe of dependent records but only those rows whose DEPDNT_ACTION_TYPE equals 'R'. This filter is embedded directly in the view text, so consumers receive a pre-qualified dataset without needing to apply the predicate themselves.

Underlying Base Objects

The view is defined over a single documented source object: IGS_SV_DEPDNT_INFO, aliased as DPDT in the view text. This table stores dependent information used by the Student System for SEVIS-related processing, including batch identifiers, person identifiers, dependent identifiers, print-form flags, remarks, and action type codes.

The relationship between the view and its base table is essentially horizontal: the view projects a subset of columns from IGS_SV_DEPDNT_INFO and applies a constant row filter on DEPDNT_ACTION_TYPE = 'R'. No join to other tables is present in the documented view text, so the view introduces no additional cardinality beyond that of the filtered base table. Two columns are synthesized rather than drawn from the base table: PERSON_NUMBER and PERSON_ID_LONG are both defined as NULL literals, indicating placeholders retained for interface consistency.

Key Columns

• BATCH_ID — Identifier of the batch that processed the dependent record; useful for grouping records produced by a single run.
• PERSON_ID — The internal identifier of the person (student) associated with the dependent activation.
• PRINT_FORM — Indicator controlling whether a form should be produced for the record, typically relevant to SEVIS output.
• DEPDNT_ID — Identifier of the dependent record itself.
• PERSON_NUMBER — Generated as NULL in the view text; retained as a placeholder for consumers expecting a person number element.
• DEPDNT_SEVIS_ID — The SEVIS identifier for the dependent, used in SEVIS-bound XML messages.
• REACTIVATE_DEPENDENT — Alias for the base table's REMARKS column; carries free-text or code information about the reactivation action.
• PERSON_ID_LONG — Generated as NULL; a placeholder for a long-format person identifier in the XML block.

Common Use Cases and Queries

This view is typically consumed by extraction programs and interfaces that assemble XML messages for dependents whose status has been reactivated. A common operational scenario is the nightly or on-demand generation of SEVIS-related output, where the batch identifier is used to isolate records belonging to a specific processing run.

A representative query retrieving the full reactivation set for a batch is:

• SELECT batch_id, person_id, print_form, depdnt_id, depdnt_sevis_id, reactivate_dependent FROM igs_sv_act_dpnd_blk_v WHERE batch_id = :p_batch_id;

Because the view already restricts rows to DEPDNT_ACTION_TYPE = 'R', no additional action filter is required. To enumerate the distinct batches available, a query such as SELECT DISTINCT batch_id FROM igs_sv_act_dpnd_blk_v; is sufficient. Joining the view back to broader person or student tables on PERSON_ID allows enrichment with biographical data when the XML block requires additional fields. When consuming the output, note that PERSON_NUMBER and PERSON_ID_LONG are always NULL by design and must not be used as filtering or join keys.