Results for “text_code”

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

Overview

SY_TEXT_HDR is the master table for the creation and storage of OPM text codes associated with GMA (Process Manufacturing Systems) tables in Oracle E-Business Suite 12.1.1 and 12.2.2. Owned by the GMA schema, the table resides in the Process Manufacturing module and serves as a central repository from which textual descriptions and long-form notes are referenced by a broad set of configuration and master data entities. Rather than duplicating text content across each functional table, OPM modules store a TEXT_CODE value in the dependent table and resolve the associated text through SY_TEXT_HDR. This design provides a single point of maintenance for text records used across organizations, units of measure, purchasing defaults, reason codes, geographic definitions, and document sequencing.

From a dimensional modeling perspective, the heuristic Data Vault classification for this object is hub-leaning. SY_TEXT_HDR behaves as a hub because its primary key, TEXT_CODE, is a stable business key that is referenced by numerous surrounding tables through foreign key columns. The dependent tables (SY_DOCS_MST, SY_UOMS_MST, SY_REAS_CDS, and others) function as satellites or links attaching descriptive attributes and relationships to that central text code hub.

Key Information Stored

The documented physical schema for SY_TEXT_HDR contains six columns. The most significant are:

• TEXT_CODE — The primary key column and business-key candidate, defined by the unique index SY_TEXT_HDR_PK. It uniquely identifies each OPM text code and is the value propagated to all foreign-key referencing tables.
• CREATED_BY — The user ID that created the text code record, supporting audit traceability.
• CREATION_DATE — The date and time the text code record was first inserted.
• LAST_UPDATED_BY — The user ID responsible for the most recent modification.
• LAST_UPDATE_DATE — The timestamp of the most recent modification, used by concurrent programs, audit reports, and incremental extraction processes.
• LAST_UPDATE_LOGIN — The login session identifier associated with the last update, supporting forensic and audit analysis.

The surrogate key is TEXT_CODE, which also serves as the documented unique business-key candidate through SY_TEXT_HDR_PK. The remaining Who columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) constitute the standard Oracle Applications auditing columns. Because the table stores only the header-level identifier and audit metadata, the actual text content is held in related detail tables such as SY_TEXT_TKN_TL.

Common Use Cases and Queries

Typical usage centers on resolving text codes to their owning entities and auditing changes to text code records. A common pattern joins SY_TEXT_HDR to a dependent table on TEXT_CODE to identify which documents, organizations, UOMs, or reason codes carry a given text code:

• Reason code reporting: SELECT r.REASON_CODE, t.TEXT_CODE, t.LAST_UPDATE_DATE FROM SY_REAS_CDS r JOIN SY_TEXT_HDR t ON r.TEXT_CODE = t.TEXT_CODE;
• Organization text lookup: Join SY_ORGN_MST to SY_TEXT_HDR on TEXT_CODE to retrieve text references for inventory organizations.
• UOM documentation review: Join SY_UOMS_MST or SY_UOMS_TYP to SY_TEXT_HDR to list text codes assigned to units of measure.
• Audit queries: Filter on LAST_UPDATE_DATE or CREATED_BY to identify recently created or modified text codes for change-control reporting.
• Orphan detection: Left-join dependent tables to SY_TEXT_HDR to find text codes defined but never referenced.

Related Objects

SY_TEXT_HDR is referenced through the TEXT_CODE foreign key column by fifteen documented dependent tables. The most significant include:

• SY_DOCS_MST and SY_DOCS_SEQ — document master and sequence records referencing TEXT_CODE.
• SY_UOMS_MST and SY_UOMS_TYP — units of measure master and type definitions.
• SY_REAS_CDS and SY_REAS_CDS_B — reason code definitions and their base table counterpart.
• SY_ORGN_MST and SY_ORGN_MST_B — organization master and base records.
• SY_PURG_MST, SY_PURG_MST_CRIT, SY_PURG_DEF, SY_PURG_DEF_CRIT, and SY_PURG_DEF_ACT — purchasing master and default criteria tables.
• SY_TEXT_TKN_TL — the token/translation detail table that stores the actual text content keyed by TEXT_CODE.
• SY_GEOG_MST — geographic master data referencing TEXT_CODE.

Together these relationships establish SY_TEXT_HDR as the central hub for OPM textual reference data across the GMA schema.