Search Results auth_start_date




Overview
Explore in AI Chat

Overview

The IGS_SV_ADD_DROP_BLW_V view is a reporting and integration object within the Oracle E-Business Suite (EBS) IGS – Student System product module. It is owned by the APPS schema and is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. The view presents the details of authorization reasons associated with dropped or cancelled student registration activity. Specifically, its documented purpose is "fetching the details about the authorization reasons being cancelled."

In the broader Student System data model, drop and add processing generates authorization records that capture why a student registration action was permitted, rejected, or reversed. This view isolates a narrow slice of that data — records where the program action type is a drop ('DB') and the authorization action is an approval/authorization ('A'). This makes it a convenience layer for functional reporting, concurrent programs, and downstream integrations that need a clean, denormalized list of authorization reasons tied to dropped registrations, without having to join or re-implement the underlying filter logic themselves.

Because the view is a stored SQL definition rather than a table, it holds no data of its own. Its behavior is entirely determined by the state of the underlying base object at query time.

Underlying Base Objects

The view is defined over a single base object: IGS_SV_PRGMS_INFO, aliased in the view text as PRGMS. The documented ETRM metadata lists "none documented" for referenced base objects at the view level, but the view definition itself clearly references IGS_SV_PRGMS_INFO as the sole source.

The defining characteristic of the view is its filtering predicate, applied directly against the base table:

  • PRGMS.PRGM_ACTION_TYPE = 'DB' — restricts rows to the drop/cancel action type ('DB').
  • PRGMS.AUTH_ACTION_CODE = 'A' — restricts rows to the authorization action code ('A').

This combination means the view behaves as a filtered projection of IGS_SV_PRGMS_INFO: no joins, unions, or aggregations are involved. All columns returned are direct references to base table columns, several of which are renamed via column aliases. Because the view contains no outer joins and no aggregations, it is generally updatable in principle, though it is intended primarily for read/query access.

Key Columns

The view exposes eight columns, several of which are aliased from the base table. The following list documents the base column and the exposed name:

  • BATCH_ID — the batch identifier under which the program information record was processed.
  • PERSON_ID — the internal identifier of the person (typically the student) associated with the record.
  • PRINT_FORM — the print form indicator associated with the authorization record.
  • AUTH_REASON — alias of PRGMS.AUTHORIZATION_REASON; the descriptive reason the authorization was granted or cancelled.
  • AUTH_START_DATE — alias of PRGMS.PRGM_START_DATE; the effective start date of the authorization. This is the column most relevant to the search term auth_start_date.
  • AUTH_END_DATE — alias of PRGMS.PRGM_END_DATE; the effective end date of the authorization.
  • DBF_REMARKS — alias of PRGMS.REMARKS; free-text remarks recorded on the base record.
  • AUTH_ACTION_CODE — the authorization action code; fixed to 'A' for every row returned by this view.

Common Use Cases and Queries

Typical scenarios include auditing cancellation authorizations, reporting on the authorization window for dropped registrations, and driving downstream extracts or notifications keyed by batch, person, or date range.

Retrieve all cancellation authorizations for a specific person:

  • SELECT batch_id, person_id, auth_reason, auth_start_date, auth_end_date FROM apps.igs_sv_add_drop_blw_v WHERE person_id = :p_person_id;

Filter by authorization start date, using the aliased column directly:

  • SELECT batch_id, person_id, auth_reason, auth_start_date FROM apps.igs_sv_add_drop_blw_v WHERE auth_start_date >= :p_from_date AND auth_start_date < :p_to_date;

Because the view already constrains PRGM_ACTION_TYPE and AUTH_ACTION_CODE, consuming code should not re-apply those filters; doing so is redundant. For performance-sensitive reporting on large volumes, querying the base table IGS_SV_PRGMS_INFO with the same predicates plus any indexed filters may be preferable, since a view cannot be indexed independently. Always qualify the object with the APPS schema when querying from outside a standard EBS session.