Results for “access_level”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGS_DA_CNFG_V is a reporting and integration view within the Oracle E-Business Suite IGS (Student System) product family, which is documented as obsolete in ETRM metadata for releases 12.1.1 and 12.2.2. The view presents the configuration of degree audit access levels — a mapping that determines which responsibilities are authorized to perform specific degree audit request operations. It joins the degree audit configuration table to the FND responsibility repository and to the IGS lookup values that decode the access level code.

The view is not implemented as a database object in every environment; the ETRM metadata explicitly states "Not implemented in this database," indicating it exists only where the IGS degree audit configuration components have been deployed. Its principal value is as a denormalized, human-readable representation of configuration data that would otherwise require three separate lookups to interpret. This makes it well suited to configuration auditing, security review reporting, and integration extracts where external systems require the descriptive meaning of the access level rather than the internal code.

Underlying Base Objects

The view is defined over three base objects. The primary table is IGS_DA_CNFG, which stores the degree audit configuration rows and supplies the access level code, request type, responsibility key, and the standard WHO audit columns. The second object is FND_RESPONSIBILITY_VL, the seeded multilingual responsibility view in the Application Object Library, filtered to VERSION = 'W' and APPLICATION_ID = 8405, with the responsibility key joined to the IGS_DA_CNFG.RESPONSIBILITY_NAME column. The third is IGS_LOOKUP_VALUES, joined on LOOKUP_TYPE = 'IGS_DA_ACCESS_LEVEL' and LOOKUP_CODE = DAC.ACCESS_LEVEL, providing the descriptive meaning for each access level.

Because the responsibility join is an inner join to FND_RESPONSIBILITY_VL, any configuration row whose responsibility key does not resolve to an active, translated responsibility record will be excluded from the result set. This behavior is important when reconciling configuration counts between the base table and the view.

Key Columns

• ROW_ID — the ROWID of the IGS_DA_CNFG record, exposed for row-level identification.
• REQUEST_TYPE_ID — identifier of the degree audit request type to which the configuration applies.
• RESPONSIBILITY_NAME — the responsibility key stored on the configuration record.
• ACCESS_LEVEL — the coded access level assigned to the responsibility for the request type.
• RESPONSIBILITY_NAME_MEANING — the descriptive name of the responsibility derived from FND_RESPONSIBILITY_VL.DESCRIPTION.
• ACCESS_LEVEL_MEANING — the decoded meaning of the access level, pulled from IGS_LOOKUP_VALUES.MEANING for lookup type IGS_DA_ACCESS_LEVEL. This is the column most often referenced when users search for "access_level_meaning."
• CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns inherited from the base table.

Common Use Cases and Queries

Typical uses include auditing which responsibilities hold which degree audit access levels, producing security review extracts that show descriptive rather than coded values, and validating lookup completeness for the IGS_DA_ACCESS_LEVEL lookup type.

SELECT responsibility_name,
       responsibility_name_meaning,
       access_level,
       access_level_meaning,
       request_type_id
FROM   igs_da_cnfg_v
ORDER  BY responsibility_name_meaning, access_level;

To review configuration by access level meaning:

SELECT access_level_meaning,
       COUNT(*) AS responsibility_count
FROM   igs_da_cnfg_v
GROUP  BY access_level_meaning;

Because the product is obsolete, environments upgrading past the supported IGS releases may find the view and its base objects absent. In such cases the query returns an invalid object error, and configuration should be sourced from replacement functionality or archived extracts. Where the view remains deployed, these queries provide a reliable, decoded view of degree audit access configuration without requiring manual joins to the lookup and responsibility repositories.