Search Results igs_co_mapping




Overview
Explore in AI Chat

Overview

The IGS.IGS_CO_MAPPING table belongs to the IGS product family — the Oracle Student System module within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description is "Mapping and Attributes," indicating that it stores configuration data used to map codes and associate descriptive attributes with student-system entities such as documents, letters, and previous-requirement definitions. Rather than holding transactional student records, the table functions as a reference/master repository that governs how other IGS processes interpret codes and apply rules such as elapsed-day thresholds and repeat limits.

The ETRM metadata classifies this object heuristically as hub-leaning in Data Vault terms. In practice this is a modeling suggestion: the table carries a stable surrogate identifier (MAP_ID), a small set of descriptive attributes, and is referenced by foreign keys from downstream tables — characteristics consistent with a hub or reference entity rather than a transactional link or a pure satellite. Administrators and implementers should treat it as a controlled reference source rather than a fact table.

Key Information Stored

The table contains 15 documented columns. The most significant are:

The distinction between MAP_ID (surrogate key) and SYS_LTR_CODE (business key candidate) is important: integrations and joins generally use the code, while internal DBA operations rely on the numeric key.

Common Use Cases and Queries

Typical usage centers on validating configuration, resolving letter codes to document rules, and auditing enabled mappings. Common query patterns include:

  • Retrieving all active mappings: SELECT MAP_ID, MAP_CODE, SYS_LTR_CODE, DOC_CODE FROM IGS.IGS_CO_MAPPING WHERE ENABLE_FLAG = 'Y';
  • Resolving a specific system letter code: SELECT * FROM IGS.IGS_CO_MAPPING WHERE SYS_LTR_CODE = :p_code;
  • Reviewing timing and repetition parameters: SELECT MAP_CODE, ELAPSED_DAYS, REPEAT_TIMES FROM IGS.IGS_CO_MAPPING ORDER BY MAP_CODE;
  • Auditing recent changes: SELECT MAP_ID, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM IGS.IGS_CO_MAPPING WHERE LAST_UPDATE_DATE > SYSDATE - 30;

These queries support setup verification, migration comparison between environments, and operational reporting on mapping effectiveness.

Related Objects

The documented foreign-key relationship establishes IGS_CO_PREV_REQS as the principal dependent table. Its column SYS_LTR_CODE references IGS_CO_MAPPING, so any query joining previous-requirement records to their mapping definitions should join on SYS_LTR_CODE. Because the metadata provides only this single documented FK, other related IGS entities (document definitions, letter definitions, and attribute tables commonly associated with the IGS_CO_% family) should be treated as probable dependents pending confirmation against the actual schema. From an integration standpoint, the table is a reference source that downstream IGS processes consult using either MAP_ID or SYS_LTR_CODE as the lookup key.