Results for “gl_text_hdr”

34 results




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

Overview

GL_TEXT_HDR is a table owned by the GMF schema (Process Manufacturing Financials) in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store text types used by General Ledger within the Process Manufacturing Financials product. In practical terms, the table functions as a master registry of text codes that classify or label GL-related records held in downstream accounting and policy tables. Because those dependent tables each carry a foreign key to GL_TEXT_HDR on the TEXT_CODE column, the table acts as a centralized reference point for text classification across several GL-related entities.

From a data modeling perspective, the ETRM metadata classifies GL_TEXT_HDR as hub-leaning. This heuristic classification, derived from the foreign key structure, suggests modeling GL_TEXT_HDR as a hub in a Data Vault design, with TEXT_CODE serving as the business key. The classification is a modeling suggestion rather than a documented design assertion, and the relatively small column footprint (six columns) combined with the multiple inbound foreign keys supports treating the table as a stable reference hub.

Key Information Stored

The documented schema for GL_TEXT_HDR contains six columns, of which the most important are described below. The table is small by design, reflecting its role as a lookup or reference entity rather than a transactional store.

  • TEXT_CODE — The single documented primary key column, enforced by the unique index GL_TEXT_HDR_PK. It is also the unique business-key candidate and the column referenced by every inbound foreign key. This is the primary identifier used to link text type definitions to dependent GL records.
  • CREATED_BY — Standard Oracle EBS who-column capturing the application user who inserted the row.
  • CREATION_DATE — Standard who-column recording the row insert timestamp.
  • LAST_UPDATE_DATE — Standard who-column recording the most recent modification timestamp; useful for incremental and change-data-capture extracts.
  • LAST_UPDATED_BY — Standard who-column identifying the user who last modified the row.
  • LAST_UPDATE_LOGIN — Standard who-column recording the login identifier associated with the last update, useful for audit and troubleshooting.

The surrogate primary key (TEXT_CODE, via GL_TEXT_HDR_PK) coincides with the documented unique business-key candidate, so no separate surrogate column is exposed in the metadata. The remaining columns follow the conventional Oracle EBS audit pattern and are not business attributes.

Common Use Cases and Queries

Typical use cases center on resolving text codes in dependent GL tables back to their header definitions, validating referential integrity, and supporting reporting on GL account and policy classifications. A common pattern joins a dependent table to GL_TEXT_HDR to label records:

  • Reference lookup: SELECT h.TEXT_CODE FROM GMF.GL_TEXT_HDR h WHERE h.TEXT_CODE = :text_code;
  • Integrity check: Identify orphaned foreign keys by comparing dependent tables against the header, for example SELECT k.TEXT_CODE FROM GMF.GL_ACCT_KEY k WHERE NOT EXISTS (SELECT 1 FROM GMF.GL_TEXT_HDR h WHERE h.TEXT_CODE = k.TEXT_CODE);
  • Change tracking: Extract rows modified since a given date using LAST_UPDATE_DATE for incremental ETL or reconciliation.
  • Impact analysis: Enumerate all tables referencing a given TEXT_CODE to assess downstream effects before maintenance.

Related Objects

GL_TEXT_HDR is referenced by five documented foreign keys, each on the TEXT_CODE column. These represent the principal dependent objects:

  • GL_ACCT_KEY — references GL_TEXT_HDR via GL_ACCT_KEY.TEXT_CODE.
  • GL_ACCT_MST — references GL_TEXT_HDR via GL_ACCT_MST.TEXT_CODE.
  • GL_ACCT_TYP — references GL_TEXT_HDR via GL_ACCT_TYP.TEXT_CODE.
  • GL_ACCT_VAL — references GL_TEXT_HDR via GL_ACCT_VAL.TEXT_CODE.
  • GL_PLCY_MST — references GL_TEXT_HDR via GL_PLCY_MST.TEXT_CODE.

Together these tables form the account key, master, type, value, and policy structures that depend on GL_TEXT_HDR for text classification. Any maintenance to TEXT_CODE values must account for these dependencies to avoid breaking referential integrity across the Process Manufacturing Financials GL schema.