Search Results writes_level




Overview

The view IGS_AD_LANGUAGE_INT is a reporting and integration object belonging to the IGS – Student System product family, which is documented as obsolete in Oracle EBS 12.1.1 and 12.2.2. It presents a denormalized, read-oriented projection of the language competency interface records maintained by the Student System admissions area. The view is defined over IGS_AD_LANGUAGE_INT_ALL, the multi-organization base table, and exposes the full set of interface attributes alongside operational control columns such as STATUS, MATCH_IND, and ERROR_CODE.

Because the underlying table carries the _ALL suffix, it is partitioned by operating unit; the view surfaces ORG_ID as the first functional column, enabling operating-unit-scoped querying. The view text additionally constructs a synthetic ROW_ID column from TAB.ROWID, providing a logical identifier even though the interface table does not expose a dedicated primary key in the projection. This makes the view suitable for reconciliation reports and for driving correction logic within inbound language competency interfaces.

Underlying Base Objects

The documented view text references exactly one base object: IGS_AD_LANGUAGE_INT_ALL, aliased as TAB. No other tables, joins, or functions are present in the view definition, so the view inherits the row count, operating-unit partitioning, and audit behavior of the base interface table. The ETRM metadata records no additional referenced base objects, and the view description indicates it is not implemented in every database, reflecting the obsolescence and optional provisioning of the IGS Student System modules.

In practical terms, the view is a straight column projection: every column listed in the projection corresponds one-to-one with a column on IGS_AD_LANGUAGE_INT_ALL, with only ROW_ID being derived rather than stored. Consequently, the view imposes no filtering predicates of its own, and row visibility is determined entirely by the privileges of the querying user on the base table.

Key Columns

Common Use Cases and Queries

Typical usage includes auditing inbound language competency loads, identifying rejected records, and reporting proficiency by reading level. A query targeting reading proficiency for a specific interface run might resemble the following:

SELECT ORG_ID, INTERFACE_LANGUAGE_ID, LANGUAGE_NAME,
       READS_LEVEL, SPEAKS_LEVEL, WRITES_LEVEL,
       STATUS, MATCH_IND, ERROR_CODE
FROM   IGS_AD_LANGUAGE_INT
WHERE  READS_LEVEL IS NOT NULL
AND    STATUS = 'ERROR';

Reconciliation against a completed load can be performed by grouping on STATUS and MATCH_IND, while row-level correction work can leverage ROW_ID to isolate the exact base row. Because the object is documented as obsolete, implementations should confirm its presence before relying on it in new customizations.