Results for “text_code”

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

Overview

IC_TEXT_HDR is the master text-code repository within the Oracle EBS Process Manufacturing Inventory module (GMI schema). It serves as the central definition table for text codes — short identifiers that point to blocks of descriptive text that can be attached to a wide variety of inventory, lot, warehouse, costing, and quality-oriented entities. Rather than duplicating free-form text across dozens of transaction and master tables, Oracle Process Manufacturing normalizes this content through IC_TEXT_HDR, allowing a single text code to be reused wherever narrative annotation is required. The table is owned by the GMI schema and is marked VALID in the ETRM reference for release 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the mined foreign-key structure classifies IC_TEXT_HDR as hub-leaning. Its single-column primary key, TEXT_CODE, behaves like a natural business key and is referenced by dozens of dependent tables, making it a canonical integration point (a hub) around which text attachments are consolidated. This classification is heuristic and intended as a modeling suggestion, not as a description of the physical design.

Key Information Stored

The documented physical schema contains six columns. The table is intentionally narrow, with the business content carried by a single identifier and the remainder dedicated to standard Oracle EBS audit columns.

• TEXT_CODE — The primary key and sole business-key attribute. It is constrained by the unique index IC_TEXT_HDR_PK and acts as the surrogate-cum-natural key referenced throughout the GMI schema. Every dependent table stores this value as its TEXT_CODE column to point back to the master definition.
• CREATED_BY — The application user ID of the person who first created the text-code record.
• CREATION_DATE — The timestamp at which the text-code record was inserted.
• LAST_UPDATED_BY — The application user ID of the last person to modify the record.
• LAST_UPDATE_DATE — The timestamp of the most recent modification, frequently used for incremental extraction and audit reporting.
• LAST_UPDATE_LOGIN — The login identifier associated with the last update, used for row-level audit tracing in multi-user sessions.

No descriptive text column is documented in the physical schema excerpt, which implies the header simply holds the code and that the associated descriptive body resides in a companion detail table within the same text infrastructure. The audit columns follow the standard EBS WHO-column convention and support concurrency and change tracking.

Common Use Cases and Queries

Because IC_TEXT_HDR is a hub, the most common query pattern is a lookup or join that resolves a text code stored on a transactional or master record. Analysts frequently need to confirm that a text code exists, trace which entities reference it, or report on text-code usage across the process manufacturing footprint.

• Validation query: verifying that a code exists before attaching it to an item, lot, or warehouse record.
• Reverse-usage query: joining IC_TEXT_HDR to IC_ITEM_MST, IC_LOTS_MST, or IC_WHSE_MST on TEXT_CODE to list every entity that shares a given code.
• Audit query: filtering on LAST_UPDATE_DATE and LAST_UPDATED_BY to produce a change history of text-code definitions for SOX or internal control reporting.
• Migration query: extracting distinct TEXT_CODE values from dependent tables and outer-joining to IC_TEXT_HDR to detect orphaned references during data conversion.

A representative pattern is SELECT h.TEXT_CODE, h.LAST_UPDATE_DATE FROM GMI.IC_TEXT_HDR h WHERE h.TEXT_CODE = :code, with an optional join to the consuming table to retrieve contextual entity attributes.

Related Objects

The FK metadata confirms IC_TEXT_HDR as a heavily referenced parent. The most significant dependents include:

• IC_ITEM_MST and IC_ITEM_MST_B — join on TEXT_CODE to attach narrative to item definitions.
• IC_LOTS_MST and IC_LOTS_STS — lot master and status text attachments.
• IC_WHSE_MST, IC_WHSE_INV, and IC_WHSE_REL — warehouse definition, inventory, and relationship text.
• IC_LOCT_MST and IC_LOCT_INV — location-level text codes.
• IC_JRNL_MST — journal master annotation.
• IC_TRAN_ARC, IC_TRAN_CMP, and IC_TRAN_PND — archived, completed, and pending transaction text.
• IC_PHYS_CNT, IC_CYCL_HDR, and IC_CYCL_MSC — physical and cycle-count documentation.
• IC_COST_CLS, IC_PRCE_CLS, IC_INVN_CLS, and IC_GLED_CLS — classification tables referencing text codes.

In total, more than forty GMI tables — including PS_PLNG_CLS, IC_TAXN_CLS, IC_SHIP_CLS, and IC_RANK_MST — carry a foreign key on TEXT_CODE, confirming that IC_TEXT_HDR is a foundational reference object for process manufacturing text handling.