Results for “pm_text_hdr”

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

Overview

PM_TEXT_HDR is a table owned by the GME schema within the Oracle EBS Process Manufacturing Process Execution module. Its documented purpose is to store text types used by Production Management. In practical terms, the table acts as a master list of text code definitions — the tokens that identify categories of free-form or descriptive text that can be attached to process manufacturing entities such as batches, materials, operations, routing dependencies, and routing material lines. Rather than duplicating text-type metadata on every transactional or setup row, Oracle EBS normalizes it here and lets dependent tables reference a single TEXT_CODE value.

The provided metadata classifies PM_TEXT_HDR as hub-leaning under a Data Vault heuristic derived from foreign-key structure. In modeling terms, this suggests treating PM_TEXT_HDR as a hub: a relatively stable set of unique business keys (TEXT_CODE), with the dependent PM_* tables acting as satellites or links that carry the descriptive or transactional payload. This classification is a modeling suggestion rather than an enforced database constraint.

Key Information Stored

The documented physical schema for release 12.2.2 lists six columns in GME.PM_TEXT_HDR. The primary key is defined by the constraint PM_TEXT_HDR_PK, enforced on the TEXT_CODE column. TEXT_CODE is therefore both the surrogate identifier in the physical model and the business-key candidate: it is the value propagated to all dependent tables via foreign keys. There is no separate numeric sequence-based surrogate documented in the metadata, so TEXT_CODE serves as the operative unique key.

The remaining documented columns are standard Oracle EBS “WHO” audit attributes:

• TEXT_CODE — the primary key and business key; identifies a specific text type or text code used by Production Management.
• CREATION_DATE — timestamp when the row was created.
• CREATED_BY — the user ID that created the row.
• LAST_UPDATE_DATE — timestamp of the most recent update.
• LAST_UPDATED_BY — the user ID that performed the most recent update.
• LAST_UPDATE_LOGIN — the login session identifier associated with the last update.

Notably, the documented column set contains no separate descriptive-name or long-text column beyond the key and audit fields. Any human-readable description of a text type is therefore either implied by TEXT_CODE itself or held in a related object not enumerated in this metadata excerpt. Consumers should not assume additional attributes beyond those listed without verifying the actual 12.1.1 or 12.2.2 schema.

Common Use Cases and Queries

Because PM_TEXT_HDR is a reference or lookup hub, the most common pattern is a join from a transactional table to resolve text-code context. A typical reporting query joins batch headers to their text-code definitions:

• Identify which text types are used on a batch: SELECT b.BATCH_NO, h.TEXT_CODE FROM PM_BTCH_HDR b, PM_TEXT_HDR h WHERE b.TEXT_CODE = h.TEXT_CODE;
• Validate referential integrity before data conversion: query PM_TEXT_HDR for the full set of valid TEXT_CODE values and compare against values found in PM_MATL_DTL, PM_OPRN_DTL, PM_ROUT_DEP, or PM_ROUT_MTL.
• Audit and change tracking: use LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN to report which text codes were created or modified and by whom.
• Impact analysis: because the same TEXT_CODE can be referenced by multiple PM_* tables, determine downstream dependencies before retiring or renaming a text code.

Related Objects

Five dependent tables are documented as referencing PM_TEXT_HDR through their TEXT_CODE columns:

• PM_BTCH_HDR — batch header records; join on PM_BTCH_HDR.TEXT_CODE = PM_TEXT_HDR.TEXT_CODE.
• PM_MATL_DTL — batch material detail lines; join on PM_MATL_DTL.TEXT_CODE = PM_TEXT_HDR.TEXT_CODE.
• PM_OPRN_DTL — batch operation detail lines; join on PM_OPRN_DTL.TEXT_CODE = PM_TEXT_HDR.TEXT_CODE.
• PM_ROUT_DEP — routing dependency definitions; join on PM_ROUT_DEP.TEXT_CODE = PM_TEXT_HDR.TEXT_CODE.
• PM_ROUT_MTL — routing material lines; join on PM_ROUT_MTL.TEXT_CODE = PM_TEXT_HDR.TEXT_CODE.

These relationships confirm the hub role: PM_TEXT_HDR supplies the canonical TEXT_CODE, while each PM_* table stores transactional or setup data that depends on it.