Results for “igs_as_untas_pattern_all”

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

Overview

IGS_AS_UNTAS_PATTERN_ALL is a table within the IGS (Student System) product family in Oracle E-Business Suite. The ETRM documentation classifies this object as Obsolete and explicitly notes that it is not implemented in this database. In EBS 12.1.1 and 12.2.2 environments, the object may persist in schemas upgraded from earlier releases or remain as a dormant definition, but it is not part of the active, supported data model. Practitioners should treat any reference to it as legacy and validate existence before relying on it.

Functionally, the table stores UNTAS (unit assessment) patterns — reusable assessment templates tied to a unit, version, calendar type, and sequence. The ASS_PATTERN_ID surrogate key identifies each pattern, while the ALL suffix indicates it is a multi-organization (operating unit) table controlled by ORG_ID. Based on the foreign-key structure, the heuristic Data Vault classification is satellite-leaning: the table carries descriptive attributes (pattern code, description, unit class/mode, default flag, logical-delete date) attached to business keys rather than acting as a hub or pure link.

Key Information Stored

The documented schema contains 23 columns. The most significant include:

• ASS_PATTERN_ID — Surrogate primary key (via IGS_AS_UNTAS_PATTERN_PK and unique index IGS_AS_UNTAS_PATTERN_U2).
• UNIT_CD, VERSION_NUMBER, CAL_TYPE, CI_SEQUENCE_NUMBER — The composite business key (unique index IGS_AS_UNTAS_PATTERN_U1) that ties the pattern to a specific unit offering and calendar/sequence context.
• ASS_PATTERN_CD — Human-readable pattern code.
• DESCRIPTION — Free-text description of the pattern.
• LOCATION_CD — Location reference (self-referencing FK documented).
• UNIT_CLASS, UNIT_MODE — Classification and delivery mode attributes of the unit.
• DFLT_PATTERN_IND — Default-pattern indicator.
• LOGICAL_DELETE_DT, ACTION_DT — Soft-delete and action timestamps.
• ORG_ID — Multi-org partition key.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Because the table is obsolete, primary usage is historical reporting, data migration, and impact analysis.

• Retrieve patterns for a unit offering:

  SELECT ass_pattern_id, ass_pattern_cd, description
  FROM   igs_as_untas_pattern_all
  WHERE  unit_cd = :unit_cd
  AND    version_number = :version
  AND    cal_type = :cal_type
  AND    org_id = :org_id;

• Find the default pattern:

  SELECT * FROM igs_as_untas_pattern_all
  WHERE dflt_pattern_ind = 'Y'
  AND   logical_delete_dt IS NULL;

• Audit active vs. logically deleted rows via LOGICAL_DELETE_DT.
• Trace attempt records back to their originating pattern using ASS_PATTERN_ID.

Related Objects

FK metadata identifies these dependencies:

• IGS_AS_SU_ATMPT_ITM — references this table via ASS_PATTERN_ID.
• IGS_AS_SU_ATMPT_PAT — references this table via ASS_PATTERN_ID.
• Self-referencing keys on LOCATION_CD, UNIT_CD, VERSION_NUMBER, CAL_TYPE, CI_SEQUENCE_NUMBER.
• Unique indexes IGS_AS_UNTAS_PATTERN_U1 and IGS_AS_UNTAS_PATTERN_U2 enforce business and surrogate keys.