Results for “basis_year”

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

Overview

IGS_AV_STD_ULVLBASIS is an Oracle E-Business Suite view owned by the APPS schema in the IGS (Student System / Advanced Placement and Credit) product family. It is a reportable, security-filtered projection of the underlying table IGS_AV_STD_ULVLBASIS_ALL, and it carries a status of VALID in the ETRM data dictionary for releases 12.1.1 and 12.2.2. The view exposes level-basis rules that describe how prior learning, exemptions, or completed work may be used to satisfy a standard unit or achievement level. Its principal role is to generalize access to the level-basis definition rows so that forms, concurrent programs, and ad hoc reports can retrieve them without directly querying the multi-org base table.

The view adds a ROW_ID column derived from the base table ROWID to support the Oracle Forms row identifier convention, and it enforces operating unit security using the client information stored in the session. Because the filtering is applied inside the view definition, consumers automatically see only the rows belonging to their current operating unit context.

Underlying Base Objects

The view is defined over a single documented base object, IGS_AV_STD_ULVLBASIS_ALL, which is the multi-organization (partitioned by ORG_ID) table holding the same attribute set. The relationship is a straightforward one-to-one projection: each qualifying row in the base table produces one row in the view. No additional joins, lookups, or reference tables are documented as part of the view definition.

The WHERE clause compares the row ORG_ID with the operating unit derived from USERENV('CLIENT_INFO'): the first ten characters of CLIENT_INFO are converted to a number, with a space in the first position treated as NULL and a fallback value of -99. This is the standard multi-org security predicate used throughout the IGS schemas. As a result, the view is effectively the operating-unit-secured window onto the ALL table and should be used in preference to it for inquiry and reporting.

Key Columns

• ROW_ID – Row identifier derived from the base table ROWID; used by Forms and by integration code that needs a stable row handle.
• ORG_ID – Operating unit that owns the level-basis rule; the column that drives the view's security predicate.
• AV_STND_UNIT_LVL_ID – Identifier of the standard unit level to which the basis rule applies.
• CRS_GROUP_IND – Course group indicator, distinguishing the grouping to which the basis belongs.
• EXEMPTION_INSTITUTION_CD – Code of the institution granting or recognized for the exemption.
• BASIS_COURSE_TYPE – Course type that qualifies as the basis for the level.
• BASIS_YEAR – Year associated with the basis course or qualification.
• BASIS_COMPLETION_IND – Flag indicating whether completion of the basis is required.
• PERSON_ID – Person associated with the basis record where the rule is person-specific.
• AS_COURSE_CD, AS_VERSION_NUMBER, S_ADV_STND_TYPE, UNIT_LEVEL – Course code, version, advanced standing type, and unit level describing the basis.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard WHO audit columns.

Common Use Cases and Queries

Typical uses include verifying that level-basis rules exist for an operating unit, feeding credit-transfer and advanced-standing reports, and diagnosing why a student was or was not credited at a given unit level.

• All rules for the current operating unit: SELECT av_stnd_unit_lvl_id, basis_course_type, basis_year, basis_completion_ind FROM igs_av_std_ulvlbasis;
• Rules for one standard unit level: SELECT basis_course_type, basis_year, exemption_institution_cd FROM igs_av_std_ulvlbasis WHERE av_stnd_unit_lvl_id = :level_id;
• Rules by advanced standing type: SELECT s_adv_stnd_type, unit_level, as_course_cd, as_version_number FROM igs_av_std_ulvlbasis WHERE s_adv_stnd_type = :type;
• Audit of recently maintained rows: SELECT av_stnd_unit_lvl_id, last_updated_by, last_update_date FROM igs_av_std_ulvlbasis WHERE last_update_date >= :since;

Because the view applies operating unit security automatically, queries should never re-implement the ORG_ID predicate; doing so risks conflicting filters and empty result sets. For cross-operating-unit analysis, the underlying IGS_AV_STD_ULVLBASIS_ALL table should be queried instead by a suitably privileged reporting account.