Results for “cr_text_hdr”

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

Overview

CR_TEXT_HDR is a reference (lookup) table owned by the GMP schema, the database schema associated with Oracle Process Manufacturing (OPM) Process Planning. In Oracle EBS 12.1.1 and 12.2.2, this table stores the text type definitions used by the Capacity module. Each row represents a text code — a reusable identifier that categorizes or labels textual attributes attached to capacity-related entities such as resources, resource classes, resource details, and planning result records. Rather than duplicating descriptive text across every capacity record, the capacity tables carry a TEXT_CODE value that points back to this header table, centralizing the definition and management of text types.

The metadata structure shows CR_TEXT_HDR as a heavily referenced parent: nine separate child tables carry a TEXT_CODE foreign key pointing to it. This fan-in pattern is characteristic of a reference or lookup dimension. Under a heuristic Data Vault classification, the object is hub-leaning — it acts as a stable, business-key-bearing center that many dependent tables attach to via the TEXT_CODE column. As a modeling suggestion, it would best be represented as a hub entity with TEXT_CODE as the natural business key, with the surrounding capacity tables treated as satellites or links referencing that hub.

Key Information Stored

The documented physical schema lists six columns. The most significant are:

• TEXT_CODE — the primary key and business-key candidate, defined by the unique index CR_TEXT_HDR_PK. It holds the text type identifier that child capacity tables use as their foreign key value.
• CREATED_BY — the user identifier responsible for inserting the text type record.
• CREATION_DATE — the timestamp when the record was created.
• LAST_UPDATE_DATE — the timestamp of the most recent modification, commonly used for incremental extraction in interfaces and reports.
• LAST_UPDATED_BY — the user identifier who performed the last change.
• LAST_UPDATE_LOGIN — the login session identifier associated with the last update.

The surrogate-versus-business-key distinction is straightforward here: CR_TEXT_HDR_PK on TEXT_CODE is both the primary key and the unique business-key candidate, since no separate numeric surrogate column is documented. Columns CREATED_BY and LAST_UPDATED_BY are the standard EBS audit columns used for change tracking and data lineage in concurrent programs and interfaces.

Common Use Cases and Queries

Typical usage centers on resolving text codes from capacity tables into readable text-type descriptions and on validating referential integrity. A standard lookup join looks like this:

• Resolving text types: SELECT h.text_code, r.resource_code FROM cr_rsrc_mst r, cr_text_hdr h WHERE r.text_code = h.text_code;
• Finding orphaned children: query each child table for TEXT_CODE values that do not exist in CR_TEXT_HDR, useful when diagnosing capacity data migration problems.
• Incremental reporting: filter on LAST_UPDATE_DATE to extract recently changed text types for downstream planning reports.
• Audit review: group by CREATED_BY and LAST_UPDATED_BY to identify who maintains capacity text definitions.

Because CR_TEXT_HDR is a reference table with modest cardinality, it is well suited as a cached dimension in capacity reporting extracts.

Related Objects

Nine documented child tables share the TEXT_CODE foreign key into CR_TEXT_HDR:

• CR_RSRC_MST and CR_RSRC_MST_B — resource master base and interface tables (join on TEXT_CODE).
• CR_RSRC_DTL — resource detail records.
• CR_RSRC_CLS and CR_RSRC_CLS_B — resource class base and interface tables.
• CR_ARES_MST — associated resource master.
• CR_GLED_CLS — global ledger or calendar class reference.
• CR_SQDS_TBL and CR_SQDT_CLS — sequence detail table and class definitions.

These relationships confirm CR_TEXT_HDR's role as a shared capacity reference hub; deleting or altering a TEXT_CODE value cascades in significance across the OPM Process Planning capacity model.