Search Results sys_ltr_code




Overview
Explore in AI Chat

Overview

IGS.IGS_CO_MAPPING is a transaction data table owned by the IGS (Intelligent Grants System / Oracle Student System) schema within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores mapping definitions that associate correspondence, letter, or communication document types with system letter codes and related processing attributes. In practice, the table acts as a configuration and control repository that drives how the student system identifies, generates, and schedules documents associated with letters, requirements, and student communications.

The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and it is indexed in APPS_TS_TX_IDX through a unique index (IGS_CO_MAPPING_U1) on MAP_ID and a non-unique index (IGS_CO_MAPPING_N1) on DOCUMENT_ID. The heuristic Data Vault classification for this object is hub-leaning, meaning it is best modeled as a hub or reference entity whose primary key anchors related descriptive and transactional satellites. This is consistent with its role as a stable mapping/reference definition referenced by other IGS tables such as IGS_CO_PREV_REQS.

Key Information Stored

The surrogate primary key is MAP_ID (NUMBER, 15), which is enforced by the unique index IGS_CO_MAPPING_U1 and serves as the internal unique identifier for each mapping record. Business-key candidates are expressed through the unique index on MAP_ID; the descriptive attributes below provide the semantic identity of each mapping.

  • MAP_CODE – Mapping type code (VARCHAR2, 30), classifying the purpose or category of the mapping.
  • DOC_CODE – Document type code (VARCHAR2, 30), identifying the document category being mapped.
  • DOCUMENT_ID – Document ID (NUMBER, 15), referencing the specific document instance; indexed non-uniquely for lookup.
  • SYS_LTR_CODE – System Letter Code (VARCHAR2, 10), the letter identifier used by the system and referenced by dependent tables.
  • MAP_DESCRIPTION – Description for the mapping (VARCHAR2, 250), a human-readable explanation of the mapping's purpose.
  • ATTR_DESCRIPTION – Description for the attributes (VARCHAR2, 250), clarifying the attribute set associated with the mapping.
  • ENABLE_FLAG – Enable Flag (VARCHAR2), controlling whether the mapping is active and processed.
  • ELAPSED_DAYS – Elapsed days for a document (NUMBER), used in scheduling or due-date calculations.
  • REPEAT_TIMES – Repeat days for a student (NUMBER), controlling recurrence of the associated communication.
  • Standard WHO columns – CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, providing audit and concurrency metadata.

Common Use Cases and Queries

Typical usage centers on resolving letter and document configuration, validating active mappings, and reporting on scheduled or repeated communications. Administrators query this table to confirm which system letter codes are enabled and how they map to documents. Developers join it to dependent tables to retrieve prerequisite requirements by SYS_LTR_CODE.

A representative query retrieves active mappings for a given letter code:

  • SELECT MAP_ID, MAP_CODE, DOC_CODE, DOCUMENT_ID, SYS_LTR_CODE, MAP_DESCRIPTION
  • FROM IGS.IGS_CO_MAPPING
  • WHERE SYS_LTR_CODE = :p_letter_code AND ENABLE_FLAG = 'Y';

Reporting scenarios include auditing mappings by DOCUMENT_ID (leveraging IGS_CO_MAPPING_N1), identifying mappings with elapsed-day and repeat-time scheduling, and extracting the full mapping set for data migration or interface loads using the documented column list.

Related Objects

The documented dependency evidence identifies IGS_CO_PREV_REQS as a table that references IGS_CO_MAPPING via the SYS_LTR_CODE column, indicating that prerequisite requirement records depend on the system letter code defined here. The APPS synonym IGS_CO_MAPPING exposes the table to application code, and the foreign-key relationship from IGS_CO_PREV_REQS.SYS_LTR_CODE to this table is the principal documented dependency. Other IGS correspondence and document tables operating on DOCUMENT_ID and DOC_CODE are likely consumers of this mapping definition, but only IGS_CO_PREV_REQS is explicitly confirmed in the provided metadata. When constructing joins, use SYS_LTR_CODE as the linkage between IGS_CO_PREV_REQS and IGS_CO_MAPPING, and MAP_ID or DOCUMENT_ID when resolving mapping-specific detail.