Results for “sequence_no”

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

Overview

IGS_EN_UNIT_SET_MAP_V is a reporting view in the Oracle E-Business Suite Student System (IGS) product family, owned by the APPS schema and shipped in a VALID state. Its documented purpose is the "Unit Set Mapping View," which exposes the relationship between a mapping set and the individual unit sets (also referred to as stream unit sets) that participate in that mapping. In the academic structure model, a unit set represents a collection of program or course requirements; a mapping set groups these unit sets into an ordered, validated sequence used for progression, articulation, or requirement satisfaction rules. The view denormalizes the mapping rows by joining each mapping to its parent unit set definition, so consumers can retrieve the mapping set code, the sequence in which a unit set appears, and descriptive attributes such as the unit set short title and its start date without issuing a second query against the unit set table.

Because it is a view rather than a table, IGS_EN_UNIT_SET_MAP_V holds no data of its own. It is intended for read-only reporting, extracts, and integration queries. In EBS 12.1.1 and 12.2.2 the definition is identical from a SQL perspective; the online patching model in 12.2.2 does not alter how a simple relational join view is resolved, so a query written against 12.1.1 remains portable.

Underlying Base Objects

The view is defined over two base tables, both in the IGS schema and referenced through APPS synonyms:

• IGS_EN_UNIT_SET_MAP (aliased USM) — the driving table holding the mapping rows, including the mapping set code, sequence number, stream unit set code, version number, and standard WHO audit columns.
• IGS_EN_UNIT_SET (aliased US) — the unit set definition table supplying SHORT_TITLE and START_DT.

The join is an equi-join on two predicates: STREAM_UNIT_SET_CD = UNIT_SET_CD and US_VERSION_NUMBER = VERSION_NUMBER. This means a mapping row is retained only when a matching unit set definition exists at the same version. Records whose unit set has been superseded at a newer version, or whose unit set definition is absent, will not appear. This effectively applies an inner-join filter, which is important when validating completeness of mapping data.

Key Columns

• MAPPING_SET_CD — identifier of the mapping set to which the row belongs.
• SEQUENCE_NO — ordinal position of the unit set within the mapping set; used for ordering results and for defining progression order.
• STREAM_UNIT_SET_CD — the unit set code referenced by the mapping; equals UNIT_SET_CD in the joined definition.
• US_VERSION_NUMBER — version of the unit set, matched to VERSION_NUMBER in IGS_EN_UNIT_SET.
• SHORT_TITLE — descriptive short name of the unit set, sourced from the unit set definition.
• START_DT — effective start date of the unit set definition.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns carried from the mapping table.

Common Use Cases and Queries

Typical uses include auditing which unit sets belong to a given mapping set, generating ordered requirement lists for student progression reporting, and reconciling mapping data between environments. The following examples reflect documented column names.

• List all mappings for a specific mapping set in sequence order:

SELECT mapping_set_cd, sequence_no, stream_unit_set_cd,
       us_version_number, short_title, start_dt
FROM   apps.igs_en_unit_set_map_v
WHERE  mapping_set_cd = :p_mapping_set_cd
ORDER  BY sequence_no;

• Find mappings whose referenced unit set no longer resolves (compare against the base mapping table, since the view suppresses orphans):

SELECT m.mapping_set_cd, m.stream_unit_set_cd, m.us_version_number
FROM   apps.igs_en_unit_set_map m
WHERE  NOT EXISTS
       (SELECT 1 FROM apps.igs_en_unit_set_map_v v
        WHERE  v.mapping_set_cd       = m.mapping_set_cd
        AND    v.sequence_no          = m.sequence_no
        AND    v.stream_unit_set_cd   = m.stream_unit_set_cd);

Note the metadata lists no foreign-key relationships for the view and documents no additional base objects; all columns originate from the two tables above.