Search Results sevis_authorization_code

Overview

IGS_EN_SVS_AUTH_V is a seeded Oracle Application Object Library view owned by the APPS schema within the IGS — Student System product family. It exposes SEVIS (Student and Exchange Visitor Information System) authorization records maintained against a person, joining the underlying authorization entity to the lookup values that decode the authorization code into a readable meaning. The view is delivered as part of the Oracle E-Business Suite 12.1.1 and 12.2.2 code lines and carries a VALID status in the data dictionary.

Its role is primarily reporting, extraction, and integration. Because SEVIS authorization data is exchanged with the United States Student and Exchange Visitor Program, institutions frequently need person-level extracts that combine the raw authorization code with its descriptive meaning. This view provides that denormalized presentation without requiring the caller to manually join the lookup table, which simplifies both ad hoc reporting and interface programs that populate downstream regulatory files.

Underlying Base Objects

Per the documented view text, IGS_EN_SVS_AUTH_V is defined over two objects:

• IGS_EN_SVS_AUTH — the base authorization table holding the SEVIS authorization records, including the person reference, authorization number, authorization code, effective dates, cancellation flag, and standard WHO columns.
• IGS_LOOKUP_VALUES — the Oracle EBS lookup values table, restricted in the join to the lookup type IGS_EN_SEVIS_AUTH_CODES, which supplies the descriptive meaning for each authorization code.

The join is an inner join: the lookup type is fixed to IGS_EN_SEVIS_AUTH_CODES and the lookup code is matched to the authorization code on the base table. Consequently, an authorization record whose code has no corresponding lookup value under that lookup type will not appear in this view. The view also exposes ESA.ROWID aliased as ROW_ID, allowing row-level identification of the underlying authorization record.

Key Columns

• ROW_ID — the ROWID of the underlying IGS_EN_SVS_AUTH row; useful for updates and row-level tracing.
• SEVIS_AUTH_ID — the primary key of the authorization record.
• PERSON_ID — the identifier of the person (student or scholar) to whom the authorization applies; the principal link to person and student records.
• SEVIS_AUTHORIZATION_NO — the externally issued SEVIS authorization number.
• SEVIS_AUTHORIZATION_CODE — the coded value describing the authorization type.
• SEVIS_AUTH_CD_MEANING — the decoded description of the authorization code, sourced from IGS_LOOKUP_VALUES.MEANING.
• START_DT / END_DT — the validity window of the authorization.
• CANCEL_FLAG — indicates whether the authorization has been cancelled.
• COMMENTS — free-text remarks on the authorization.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context columns recording the process that last touched the row.

Common Use Cases and Queries

Typical uses include SEVIS compliance reporting, verification of active authorizations for a given person, and interface extracts for regulatory submission. The following query lists current, uncancelled authorizations with decoded meanings for a specific person:

SELECT person_id,
       sevis_authorization_no,
       sevis_authorization_code,
       sevis_auth_cd_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    SYSDATE BETWEEN start_dt AND NVL(end_dt, SYSDATE);

Because the view already resolves the code meaning, it is well suited to summaries by authorization type using GROUP BY sevis_auth_cd_meaning. For bulk extracts, filtering on start_dt and end_dt supports reporting within a reporting period, while program_id and request_id help audit which concurrent process last updated a given authorization.

As with all APPS views, access should be granted through the standard EBS responsibility and security model, and reporting should rely on the documented columns to remain compatible across 12.1.1 and 12.2.2. Oracle E-Business Suite product data is Oracle proprietary and confidential.