Results for “sy_text_hdr”
49 results
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.
-
Master table for creation and storage of OPM text codes associated with GMA tables.
-
Master table for creation and storage of OPM text codes associated with GMA tables.
-
TABLE: GMA.SY_TEXT_HDR 12.1.1
-
TABLE: GMA.SY_TEXT_HDR 12.2.2
-
SYNONYM: APPS.SY_TEXT_HDR 12.1.1
-
SYNONYM: APPS.SY_TEXT_HDR 12.2.2
-
VIEW: GMA.SY_TEXT_HDR# 12.2.2
-
eTRM - GMA Tables and Views 12.2.2
Table for associating Units of Measure and UOM Types. Not yet used.
-
eTRM - GMA Tables and Views 12.1.1
Table for associating Units of Measure and UOM Types. Not yet used.
-
VIEW: GMA.SY_TEXT_HDR# 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
Table: SY_UOMS_TYP 12.1.1
Unit of measure type master for Oracle Process Manufacturing products. Define unit of measure types here, which categorize Units of Measure. Synchronized with MTL_UOM_CLASSES
Not implemented in this database·Explore GMA module →
-
Table: SY_UOMS_TYP 12.2.2
Unit of measure type master for Oracle Process Manufacturing products. Define unit of measure types here, which categorize Units of Measure. Synchronized with MTL_UOM_CLASSES
Not implemented in this database·Explore GMA module →
-
OPM Purge and Archive table used to store the criteria entered specific to a Purge ID.
-
Oracle Process Manufacturing Document master. This table stores document definitions
-
Table: SY_REAS_CDS 12.2.2
The Reason Code table is used to store Reason Code definitions which provide information on the increase or decrease in inventory. Reason codes are used to flag transactions and attach reasons to them.
Not implemented in this database·Explore GMA module →
-
Table: SY_REAS_CDS 12.1.1
The Reason Code table is used to store Reason Code definitions which provide information on the increase or decrease in inventory. Reason codes are used to flag transactions and attach reasons to them.
Not implemented in this database·Explore GMA module →
-
Stores OPM Text Token definitions
-
Stores OPM Text Token definitions
-
OPM Purge and Archive table used to store the criteria entered specific to a Purge ID.
-
Geographic regions.
-
Geographic regions.
-
Oracle Process Manufacturing Document master. This table stores document definitions
-
OPM Purge and Archive definitions are stored in this table
-
eTRM - GMA Tables and Views 12.1.1
Table for associating Units of Measure and UOM Types. Not yet used.
-
Designates the Action to be performed by OPM Purge and Archive on a table by table basis.
-
Designates the Action to be performed by OPM Purge and Archive on a table by table basis.
-
The Reason Code table is used to store Reason Code definitions which provide information on the increase or decrease in inventory. Reason codes are used to flag transactions and attach reasons to them.
-
Table: SY_ORGN_MST 12.1.1
Organization code master.
Not implemented in this database·Explore GMA module →
-
OPM Purge and Archive definitions are stored in this table
-
Table: SY_ORGN_MST 12.2.2
Organization code master.
Not implemented in this database·Explore GMA module →
-
Stores the Purge Criteria tags. These criteria are used to determine what rows will be archived and purged.
-
Stores the Purge Criteria tags. These criteria are used to determine what rows will be archived and purged.
-
Document sequencing by organization.
-
The Reason Code table is used to store Reason Code definitions which provide information on the increase or decrease in inventory. Reason codes are used to flag transactions and attach reasons to them.
-
eTRM - GMA Tables and Views 12.2.2
Table for associating Units of Measure and UOM Types. Not yet used.
-
Table: SY_UOMS_MST 12.2.2
Unit of measure master for Oracle Process Manufacturing. Synchronized with MTL_UNITS_OF_MEASURE and associated tables when Oracle Financials is used.
Not implemented in this database·Explore GMA module →
-
Document sequencing by organization.
-
Table: SY_UOMS_MST 12.1.1
Unit of measure master for Oracle Process Manufacturing. Synchronized with MTL_UNITS_OF_MEASURE and associated tables when Oracle Financials is used.
Not implemented in this database·Explore GMA module →
-
Table storing data of all OPM Archives/Purges that have been run
-
Table storing data of all OPM Archives/Purges that have been run
-
Organization code master Base Table.
-
Organization code master Base Table.
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1