Results for “base_item_id”

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

Overview

IGS_CO_COV_LTR_RELS is a table in the IGS schema belonging to the Oracle E-Business Suite Student System (IGS) product family. Its documented purpose is to maintain the relationships between templates that were created during preview. In practical terms, the object functions as a relationship or association table that records how correspondence or letter templates referenced one another at the moment they were previewed, preserving the parent-child hierarchy that existed between those templates.

The object is documented with status VALID in both EBS 12.1.1 and 12.2.2, and carries nine physical columns. The heuristic Data Vault classification mined from its foreign key structure is standalone. Under a Data Vault modeling suggestion, this classification indicates the table is not strongly integrated into a broader hub-and-link network through declared constraints; it can be treated as an independent relationship structure rather than a conventional hub or satellite. Note that this is a modeling convenience only—the table's actual role in the Student System is as a relational bridge between template instances.

Key Information Stored

The table is anchored by the primary key IGS_CO_COV_LTR_RELS_PK, which is a composite business key rather than a single surrogate sequence. The key comprises three columns:

• PARENT_ITEM_ID — Identifies the higher-level template in the relationship. This is the column most relevant to the parent_item_id search term: it stores the reference to the parent template from which a child template descends or is derived during preview.
• CHILD_ITEM_ID — Identifies the subordinate template attached to the parent. Together with PARENT_ITEM_ID it defines the direction of the template relationship.
• BASE_ITEM_ID — Identifies the base template against which the parent-child relationship is evaluated, providing a third dimension to the key so that a given parent-child pairing can exist in more than one base context.

In addition to the composite key, the table carries standard Oracle EBS audit and concurrency columns: OBJECT_VERSION_NUMBER, which supports optimistic locking for the row; CREATED_BY and CREATION_DATE, which capture the creating user and timestamp; and LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and LAST_UPDATE_DATE, which capture the most recent change, the login that performed it, and its timestamp. Because the metadata documents only the key columns and the audit columns, no descriptive attributes are confirmed beyond these nine.

Common Use Cases and Queries

Typical scenarios involve reconstructing the template hierarchy generated during preview, diagnosing orphaned or duplicated template links, and reporting on which templates are reused as children across multiple parents. A straightforward query to expand the hierarchy by parent is:

• SELECT PARENT_ITEM_ID, CHILD_ITEM_ID, BASE_ITEM_ID FROM IGS.IGS_CO_COV_LTR_RELS WHERE PARENT_ITEM_ID = :p_parent; — returns every child template attached to a given parent.
• SELECT CHILD_ITEM_ID, COUNT(*) FROM IGS.IGS_CO_COV_LTR_RELS GROUP BY CHILD_ITEM_ID; — identifies the most frequently reused child templates.
• SELECT * FROM IGS.IGS_CO_COV_LTR_RELS WHERE BASE_ITEM_ID = :p_base AND PARENT_ITEM_ID IS NULL; — a pattern useful for locating malformed relationships where a base is defined but no parent was captured.
• Audit-driven reporting on LAST_UPDATE_DATE and LAST_UPDATED_BY supports troubleshooting changes made after a preview cycle completed.

Because the PK is composite and covers PARENT_ITEM_ID, CHILD_ITEM_ID, and BASE_ITEM_ID, equality predicates on those columns yield the most efficient access paths. Reporting joins should carry all three key columns forward to avoid row multiplication.

Related Objects

The metadata documents the table as standalone with no declared foreign key relationships, so the related objects below are inferred from the IGS Student System domain rather than from explicit constraints. The most significant relationships are:

• IGS_CO_COV_LTR_RELS self-join on PARENT_ITEM_ID = CHILD_ITEM_ID — the canonical pattern for walking multi-level template hierarchies.
• Correspondence / letter preview template objects in the IGS correspondence module, joined through PARENT_ITEM_ID, CHILD_ITEM_ID, and BASE_ITEM_ID.
• IGS_CO_ correspondence tables that hold template definitions, joined to BASE_ITEM_ID as the contextual anchor.
• Standard EBS audit infrastructure referenced by CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN, including FND_USER.

Given the absence of declared foreign keys, any join must be validated against actual data, and referential integrity is enforced by the application layer rather than the database.