Search Results next_session_start_date




Overview
Explore in AI Chat

Overview

IGS_SV_CRT_CONT_BLK_V is a Self-Service Web view owned by the APPS schema in Oracle E-Business Suite, registered under the FND Design Data reference IGS.IGS_SV_CRT_CONT_BLK_V. Its status is VALID in both the 12.1.1 and 12.2.2 releases. The view is purpose-built to simplify access from Oracle Self-Service Web Applications and exposes information used to construct the XML block describing the "create continuation" request for a student. In the SEVIS (Student and Exchange Visitor Information System) compliance area of Oracle Student System, a continuation request extends a student's record when the current session ends and instruction resumes in a subsequent session. This view therefore serves as a reporting and integration interface rather than a transactional base object: it flattens the descriptors required for the continuation XML payload into a single, query-friendly projection.

Underlying Base Objects

The documented dependency list is deliberately minimal. The view references APPS.IGS_SV_PERSONS, the SEVIS person-level table that stores student identity and SEVIS-relevant person attributes such as the person identifier and associated batch context. The ETRM metadata records no further base objects, and the view is not referenced by any database object — it is a terminal, read-only projection consumed by Web/XML rendering layers rather than a source for other views or tables. Because it is defined over IGS_SV_PERSONS with additional derivation logic, the view abstracts the join and formatting work away from the Self-Service application code, which is the standard Oracle pattern for Web views of this type. Practitioners should treat IGS_SV_PERSONS as the authoritative anchor when tracing data lineage back from this view.

Key Columns

  • BATCH_ID (NUMBER, 14) — Batch identifier for the requested run; groups the continuation records produced by a single processing pass.
  • PERSON_ID (NUMBER, 15) — Person identifier for the student in the request; the principal key linking to IGS_SV_PERSONS and to student records elsewhere in the Student System.
  • PRINT_FORM (VARCHAR2) — Flag indicating whether the form is to be printed by SEVIS or not.
  • ISSUE_REASON (VARCHAR2, 30) — Issuing reason captured for the student request.
  • CURR_SESSION_END_DATE (VARCHAR2, 10) — The student's current session end date, exposed as a character string. The varchar2(10) shape corresponds to the date literal format expected by the SEVIS XML block.
  • NEXT_SESSION_START_DATE (VARCHAR2, 10) — The student's next session start date, also exposed as a character-typed value. This is the column most frequently sought when users search for "next_session_start_date," since it is the field that drives the continuation window and is consumed directly into the outbound XML block.

Common Use Cases and Queries

Typical usage falls into two categories: validation of the data that will populate the SEVIS continuation XML block, and operational reporting on pending continuation batches. A representative query retrieves the columns in their documented order:

SELECT batch_id
     , person_id
     , print_form
     , issue_reason
     , curr_session_end_date
     , next_session_start_date
  FROM apps.igs_sv_crt_cont_blk_v;

To isolate a single student's continuation record, filter on PERSON_ID; to review an entire processing run, filter on BATCH_ID. Because both session date columns are VARCHAR2(10), date-range predicates require explicit conversion, for example TO_DATE(next_session_start_date,'YYYY/MM/DD'), and developers should confirm the stored date format before applying NLS-sensitive conversions. Analysts commonly use this view to confirm that every student selected for a continuation batch has a populated NEXT_SESSION_START_DATE, and to reconcile PRINT_FORM and ISSUE_REASON values against the SEVIS submission requirements before the XML block is generated. As the view exposes no rows of its own and references only IGS_SV_PERSONS, all such queries are read-only and safe for ad hoc reporting in both 12.1.1 and 12.2.2 environments.