Results for “cm_text_hdr”

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

Overview

CM_TEXT_HDR is a Process Manufacturing Financials (GMF) table that stores the header information for free-form text entered through the Edit Text option. In Oracle EBS 12.1.1 and 12.2.2, this table serves as the central repository for text blocks that are attached to a wide variety of process manufacturing master and detail records, including recipes, routings, quality analyses, cost components, warehouses, and allocation bases. Rather than duplicating descriptive text across every operational table, the Process Manufacturing applications centralize it here and reference each text block through a numeric TEXT_CODE.

Under the heuristic Data Vault classification derived from its foreign key structure, CM_TEXT_HDR is hub-leaning. This suggests a modeling approach in which TEXT_CODE acts as a business key, and the table functions as a central hub that many surrounding satellite and detail tables reference. In relational terms, it is a shared reference or lookup parent whose primary key is reused across dozens of child tables.

Key Information Stored

The table is defined in the GMF schema and contains six documented columns:

• TEXT_CODE — The unique identifier for each text header record. It is both the primary key column of the CM_TEXT_HDR_PK constraint and the sole business-key candidate. Every dependent table stores this value to reference its associated text block.
• CREATED_BY — The user ID of the person who created the text header record.
• CREATION_DATE — The date and time the record was inserted.
• LAST_UPDATED_BY — The user ID of the person who most recently modified the record.
• LAST_UPDATE_DATE — The timestamp of the most recent modification, used widely in EBS audit tracking and incremental data extraction.
• LAST_UPDATE_LOGIN — The login session identifier associated with the last update, useful for forensic and concurrency analysis.

The table itself carries no descriptive text column; the actual text lines are stored in a companion detail table keyed by the same TEXT_CODE. CM_TEXT_HDR therefore acts purely as the identity and audit anchor for each text block, while the surrogate-to-business key mapping collapses to a single attribute because TEXT_CODE is simultaneously the natural and unique key.

Common Use Cases and Queries

Typical reporting scenarios include identifying which records carry user-entered text, tracing orphaned or unused text codes, and auditing text entry activity by user or date. A common pattern is to join the header to the text detail table:

• Retrieving header metadata for a known code: SELECT text_code, created_by, creation_date, last_updated_by, last_update_date FROM gmf.cm_text_hdr WHERE text_code = :p_code;
• Listing recently modified text blocks: SELECT * FROM gmf.cm_text_hdr WHERE last_update_date >= :since_date ORDER BY last_update_date DESC;
• Finding parent records that reference text, for example recipes: SELECT m.* FROM gmf.cm_cmpt_mst m, gmf.cm_text_hdr t WHERE m.text_code = t.text_code;
• Identifying unused text headers: SELECT t.text_code FROM gmf.cm_text_hdr t WHERE NOT EXISTS (SELECT 1 FROM gmf.cm_cmpt_mst m WHERE m.text_code = t.text_code);

Because the table is small and almost entirely static after creation, it is a low-cost dimension-style join in any process manufacturing report that surfaces narrative instructions or comments.

Related Objects

CM_TEXT_HDR is referenced by a broad set of GMF tables through the TEXT_CODE column. The most significant documented relationships are:

• CM_CMPT_MST / CM_CMPT_MST_B — Formula and recipe master records that carry text instructions (CM_CMPT_MST.TEXT_CODE → CM_TEXT_HDR).
• CM_CMPT_DTL, CM_CMPT_GRP, CM_CMPT_MTL — Component detail, group, and material records in formulas and recipes.
• CM_CLDR_HDR / CM_CLDR_HDR_B, CM_CLDR_DTL — Recipe calendar header and detail records.
• CM_MTHD_MST — Routing or method master records.
• CM_ALYS_MST — Quality analysis master records that include textual specifications.
• CM_ADJS_DTL and CM_APCM_MST — Adjustment detail and cost component master records.
• CM_BRDN_DTL and CM_RSRC_DTL — Burden and resource detail records.
• CM_REAS_CDS — Reason code definitions carrying explanatory text.
• CM_WHSE_ASC, CM_WHSE_EFF, CM_WHSE_SRC, GL_ALOC_BAS — Warehouse association, effectivity, source, and allocation basis records.

These dependencies confirm that CM_TEXT_HDR is a cross-cutting reference hub in Process Manufacturing Financials, and any deletion or renumbering of TEXT_CODE values would cascade widely across formula, routing, costing, and warehouse configuration data.