Search Results igr_epu_category_upg




Overview
Explore in AI Chat

Overview

IGR_EPU_CATEGORY_UPG is a temporary (staging) table owned by the IGS schema within the Oracle E-Business Suite Student System (IGS) module. It exists to support a one-time or periodic data migration in which Entry Status values, Program Codes, and Unit Sets are mapped and loaded into the Oracle Product Category model (the MTL_CATEGORIES_B and MTL_CATEGORY_SETS_B structures). As a transient upgrade/migration object rather than a transactional or master entity, its rows are populated during the migration run, consumed by the migration program, and subsequently purged. It is not part of the day-to-day operational data model of the Student System.

Under the heuristic Data Vault classification mined from its foreign key structure, this table is best modeled as a link. A link table captures associations between business entities, and IGR_EPU_CATEGORY_UPG performs exactly that role by associating Student System reference values (Entry Status, Program Code, Unit Set) with inventory/product category definitions. It is not a hub (it carries no natural business key of its own) and not a pure satellite (it holds no descriptive attribute history beyond the mapping it represents). This classification should be treated as a modeling suggestion for analytical or reporting environments rather than as an implementation constraint on the EBS table itself.

Key Information Stored

The documented physical schema for the 12.1.1 release contains five columns, each of which is significant to the migration mapping:

  • ENTRY_STATUS_ID — identifies the Student System Entry Status being migrated. It is a business-key candidate that ties the migration row back to the admission entry status reference entity.
  • PROGRAM_CODE_ID — identifies the Program Code being migrated from the Student System. A foreign key references FV_DMS_CODE_DEFINITIONS_ALL, confirming that program codes are drawn from the shared code-definition infrastructure.
  • UNIT_SET_ID — identifies the Unit Set being migrated, with a foreign key to IGS_AD_UNIT_SETS. Unit Sets define collections of academic units used in program and admission rules.
  • PRODUCT_CATEGORY_ID — the target product category within MTL_CATEGORIES_B. This is a foreign key into the inventory categories table and represents the destination side of the migration.
  • PRODUCT_CATEGORY_SET_ID — the target category set within MTL_CATEGORY_SETS_B, the structural container that groups categories. This FK defines which category set the migrated product category belongs to.

No surrogate primary key is documented for this staging table, which is consistent with its role as a temporary load structure. The meaningful uniqueness is the combination of the source-side identifiers (ENTRY_STATUS_ID, PROGRAM_CODE_ID, UNIT_SET_ID) mapped against the destination category references. Because it is a staging table, the ETRM metadata records no primary key or unique index definitions, and downstream uniqueness is enforced by the migration logic rather than the database.

Common Use Cases and Queries

The principal use case is verifying and reconciling a category migration before and after the load into MTL_CATEGORIES_B and MTL_CATEGORY_SETS_B. Typical validation queries check for orphaned source identifiers, duplicate mappings, or missing destination categories:

  • Orphan detection — join the staging table to MTL_CATEGORIES_B on PRODUCT_CATEGORY_ID and to MTL_CATEGORY_SETS_B on PRODUCT_CATEGORY_SET_ID, filtering for NULL destination rows to identify mappings that failed to resolve.
  • Mapping report — select ENTRY_STATUS_ID, PROGRAM_CODE_ID, UNIT_SET_ID alongside the resolved category name and category set name to produce a human-readable reconciliation report for data stewards.
  • Source coverage check — outer join to FV_DMS_CODE_DEFINITIONS_ALL on PROGRAM_CODE_ID and to IGS_AD_UNIT_SETS on UNIT_SET_ID to confirm that every source reference has a corresponding staging row.
  • Duplicate analysis — group by the source-side key columns to surface any source value mapped to more than one destination category, which would indicate a migration definition conflict.

Because this table is temporary, reporting should be performed during the migration window. For ongoing operational reporting on product categories, query MTL_CATEGORIES_B and MTL_CATEGORY_SETS_B directly rather than this staging object.

Related Objects

The following objects are the most significant dependencies, based on the documented foreign key relationships:

  • MTL_CATEGORIES_B — referenced via PRODUCT_CATEGORY_ID; the destination master table for product categories.
  • MTL_CATEGORY_SETS_B — referenced via PRODUCT_CATEGORY_SET_ID; defines the category set that groups migrated categories.
  • FV_DMS_CODE_DEFINITIONS_ALL — referenced via PROGRAM_CODE_ID; the shared code-definition source for program codes.
  • IGS_AD_UNIT_SETS — referenced via UNIT_SET_ID; the Student System source of unit set definitions.
  • IGR_EPU_CATEGORY (implied companion) — the operational or post-migration counterpart that the staging data ultimately populates or validates against, alongside the MTL category tables it feeds.

Together these relationships define the migration flow from Student System reference data into the Oracle Inventory product category model, with this table acting as the linking staging structure between source and destination.