Search Results igs_en_sevis_auth_codes

Overview

APPS.IGS_EN_SVS_AUTH_V is a Student System (IGS) view in Oracle E-Business Suite 12.1.1 and 12.2.2 that exposes SEVIS authorization data for enrolled persons. It presents rows from the underlying authorization entity joined to the lookup values that decode the SEVIS authorization code into a user-readable meaning. The view is classified as a view object with no independently documented base object list under ETRM, but the view SQL clearly denormalizes a single transactional table with a lookup table. Its primary role is to provide a reporting- and integration-friendly projection of SEVIS authorization records, including surrogate key, person reference, authorization number and code, descriptive meaning, effective dates, cancellation flag, free-text comments, and the standard Oracle EBS WHO/audit columns. It is typically consumed by SEVIS-related extracts, compliance reporting, and downstream interfaces that require the descriptive meaning of the authorization code rather than the raw code value.

Underlying Base Objects

The view is defined over two objects, per its documented view text:

• IGS_EN_SVS_AUTH (aliased ESA) — the primary SEVIS authorization table supplying ROWID, all identifiers, dates, flags, comments, and audit columns.
• IGS_LOOKUP_VALUES (aliased LKV) — the lookup table supplying the decoded MEANING for the authorization code.

The join is an inner join driven by two predicates: LKV.LOOKUP_TYPE = 'IGS_EN_SEVIS_AUTH_CODES' and LKV.LOOKUP_CODE = ESA.SEVIS_AUTHORIZATION_CODE. Because the join is by equality on both lookup type and code, only authorization rows whose code exists in the IGS_EN_SEVIS_AUTH_CODES lookup type are returned. Rows with an unmapped or null code are excluded. The lookup type name corresponds directly to the search term igs_en_sevis_auth_codes, confirming that the view is the canonical consumer of that lookup type within the Student System.

Key Columns

• ROW_ID — the ROWID of the underlying IGS_EN_SVS_AUTH row; useful for uniquely addressing the base record.
• SEVIS_AUTH_ID — primary key of the authorization record.
• PERSON_ID — the person (student) to whom the authorization pertains.
• SEVIS_AUTHORIZATION_NO — the SEVIS authorization number.
• SEVIS_AUTHORIZATION_CODE — the raw code value stored on the base table and used as the join key to the lookup.
• MEANING — the decoded description of the authorization code from IGS_LOOKUP_VALUES.
• START_DT, END_DT — validity period of the authorization.
• CANCEL_FLAG — indicates whether the authorization has been cancelled.
• COMMENTS — free-text remarks.
• Audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, plus the concurrent program columns REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical usage includes active-authorization reporting, per-person SEVIS extracts, and reconciliation of codes against the lookup. The following query lists current, non-cancelled authorizations for a given person:

• SELECT sevis_authorization_no, sevis_authorization_code, meaning, start_dt, end_dt
• FROM apps.igs_en_svs_auth_v
• WHERE person_id = :p_person_id
• AND NVL(cancel_flag,'N') = 'N'
• AND TRUNC(SYSDATE) BETWEEN start_dt AND NVL(end_dt, TRUNC(SYSDATE)+1);

For audit and extraction purposes, the WHO columns and ROW_ID support incremental and traceability requirements:

• SELECT row_id, sevis_auth_id, person_id, sevis_authorization_code, meaning, last_update_date
• FROM apps.igs_en_svs_auth_v
• WHERE last_update_date >= :p_since_date
• ORDER BY person_id, start_dt;

Because the view performs the lookup decode internally, consumers should avoid re-joining IGS_LOOKUP_VALUES for the same purpose. Where blank or unexpected meanings appear, verify that the corresponding IGS_EN_SEVIS_AUTH_CODES lookup row exists and is enabled for the appropriate language.