Results for “fm_text_hdr”

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

Overview

FM_TEXT_HDR is a foundational table in the Oracle EBS Process Manufacturing Product Development module (GMD schema). It functions as the central repository for text type definitions, or "text codes," that drive the descriptive and instructional text attached to formulas, routings, operations, and related master data. Rather than storing the free-text content itself, FM_TEXT_HDR defines the categories or header records that describe what kind of text is being captured, making it a master reference object relied upon throughout the GMD product development schema.

From a Data Vault modeling perspective, the ETRM metadata classifies this object as hub-leaning. This reflects its role as a stable reference table whose primary key, TEXT_CODE, is referenced by a large number of downstream entity tables. No foreign key columns are documented for FM_TEXT_HDR itself, which is consistent with a hub pattern where the table holds a business-conformed key and is the target of many incoming references.

Key Information Stored

The documented physical schema contains six columns, headed by the primary key defined through the unique index FM_TEXT_HDR_PK on TEXT_CODE. The most important columns are:

• TEXT_CODE — The surrogate primary key and business-key candidate, uniquely identifying each text type stored in the header table. Every dependent GMD and FM table references this column.
• CREATED_BY — The user ID of the individual who created the text header record, supporting audit and accountability requirements.
• CREATION_DATE — The timestamp at which the record was created, used in audit trails and date-based reporting.
• LAST_UPDATE_DATE — The most recent modification timestamp, frequently used to drive incremental extraction and change detection in ETL processes.
• LAST_UPDATED_BY — The user ID of the last person to modify the record, essential for audit and segregation-of-duties analysis.
• LAST_UPDATE_LOGIN — The login ID associated with the last update, providing an additional trace for auditing user sessions.

Because the schema is narrow, nearly all columns documented are either the primary key or standard Oracle "WHO" audit columns. TEXT_CODE serves both as the surrogate primary key and as the unique business key, so there is no separate alternate-key column within this table.

Common Use Cases and Queries

Typical usage centers on looking up or validating text codes prior to joining them against the many dependent entity tables. A representative query joining a formula master to its text type is:

• SELECT m.formula_no, m.text_code, t.creation_date FROM fm_form_mst m, fm_text_hdr t WHERE m.text_code = t.text_code;

Reporting scenarios include generating text type inventories, auditing recently created text headers using CREATION_DATE, and tracking change activity through LAST_UPDATE_DATE for incremental data warehouse loads. A simple validation pattern checks for orphaned references:

• SELECT text_code FROM fm_form_mst WHERE text_code NOT IN (SELECT text_code FROM fm_text_hdr);

Because the table is a reference hub, it is also commonly used as a driver for parent-child mapping reports spanning formulas, routings, operations, and their associated classes.

Related Objects

FM_TEXT_HDR is referenced via the TEXT_CODE column by a broad set of GMD and FM tables. The most significant dependencies include:

• FM_FORM_MST / FM_FORM_MST_B — Formula master records joined on TEXT_CODE.
• FM_ROUT_HDR — Routing headers referencing text types.
• FM_OPRN_MST — Operation master records, with FM_OPRN_DTL and FM_OPRN_CLS providing operation detail and class references.
• FM_MATL_DTL — Material detail text references for formulas.
• GMD_FORMULA_CLASS_B, GMD_OPERATION_CLASS_B, GMD_ROUTING_CLASS_B, and GMD_ROUTINGS_B — GMD master and class tables that depend on TEXT_CODE.
• FM_ACTV_MST, FM_CONF_TBL, and MR_SHDY_HDR — Additional referenced entities spanning activities, configuration, and shadow headers.

Collectively these relationships confirm FM_TEXT_HDR as a central reference hub, with no documented outgoing foreign keys of its own, making it a stable anchor for text type definitions across the Process Manufacturing Product Development schema.