Search Results xtr_gl_references




Overview
Explore in AI Chat

Overview

XTR_GL_REFERENCES is a Treasury (XTR) module table in Oracle E-Business Suite, owned by the XTR schema and documented as valid in both 12.1.1 and 12.2.2. The ETRM metadata records its origin as an entity named "XTR GL REFERENCE," created by Oracle on 06-MAY-93, indicating it is one of the earliest architectural elements of the Treasury product. Its purpose is to associate Treasury business records with General Ledger accounting flexfield combinations, maintaining the linkage between Treasury transactions and the General Ledger accounts to which they are posted.

The table's foreign key structure places it as a reference or association table whose primary relationship is to GL_CODE_COMBINATIONS via CODE_COMBINATION_ID. The heuristic Data Vault classification derived from the FK topology is satellite-leaning, meaning the table is best modeled as a satellite attached to a parent Treasury hub or link, carrying descriptive reference attributes rather than acting as an independent business entity hub. This classification should be treated as a modeling suggestion rather than a documented constraint.

Key Information Stored

The documented physical schema consists of eight columns, with a unique index, XTR_GL_REFERENCES_U1, defined on the column pair (CODE_COMBINATION_ID, COMPANY_CODE). The most significant columns are:

  • CODE_COMBINATION_ID — The accounting flexfield combination identifier, foreign keyed to GL_CODE_COMBINATIONS. This is the principal join column linking Treasury data to General Ledger account definitions.
  • COMPANY_CODE — The company or legal entity identifier that scopes the GL reference. Together with CODE_COMBINATION_ID it forms the documented business-key candidate via the unique index.
  • TREASURY_REFERENCE — The Treasury-side reference value that ties the GL combination back to a specific Treasury record or transaction.
  • AUDIT_INDICATOR — A flag controlling audit-related behavior or status for the reference row.
  • CREATED_BY, CREATED_ON — Standard Oracle WHO columns recording the creating user and timestamp.
  • UPDATED_BY, UPDATED_ON — Standard Oracle WHO columns recording the last updating user and timestamp.

The metadata does not document a single-column surrogate primary key; the uniqueness constraint is expressed through the composite unique index XTR_GL_REFERENCES_U1. The WHO columns and AUDIT_INDICATOR provide the auditability expected of a Treasury-to-GL reference structure.

Common Use Cases and Queries

Typical usage centers on reconciling Treasury activity to General Ledger accounts and validating that the correct accounting flexfield combinations are assigned. A common join pattern resolves the stored combination ID to a human-readable GL account:

  • Join XTR_GL_REFERENCES to GL_CODE_COMBINATIONS on CODE_COMBINATION_ID to retrieve concatenated account segments for reporting.
  • Filter by COMPANY_CODE to isolate references for a specific legal entity or company segment.
  • Resolve TREASURY_REFERENCE values to trace a GL account assignment back to its originating Treasury transaction.
  • Audit queries using CREATED_ON, UPDATED_ON, and AUDIT_INDICATOR to identify stale, duplicate, or recently modified reference rows.

A representative pattern: select G.concatenated_segments, R.COMPANY_CODE, R.TREASURY_REFERENCE from XTR_GL_REFERENCES R, GL_CODE_COMBINATIONS_KFV G where R.CODE_COMBINATION_ID = G.CODE_COMBINATION_ID order by R.COMPANY_CODE. Reconciliation reports grouped by COMPANY_CODE help verify that each Treasury entity maps to the intended GL combinations.

Related Objects

The documented foreign key identifies the single most significant related object, and Treasury module context suggests additional dependents:

  • GL_CODE_COMBINATIONS — Referenced through XTR_GL_REFERENCES.CODE_COMBINATION_ID, the accounting flexfield definition table.
  • GL_CODE_COMBINATIONS_KFV — The key flexfield view commonly used to display concatenated account segments alongside the reference rows.
  • XTR_GL_REFERENCES_U1 — The composite unique index on (CODE_COMBINATION_ID, COMPANY_CODE) that enforces business-key uniqueness.
  • Other XTR Treasury transaction and setup tables that consume the TREASURY_REFERENCE linkage to determine GL posting accounts.

Maintainers should treat XTR_GL_REFERENCES as a supporting reference layer within the Treasury schema, preserving the CODE_COMBINATION_ID relationship to GL_CODE_COMBINATIONS and the composite unique constraint as the core integrity rules.