Search Results ax_trans_schemes




Overview
Explore in AI Chat

Overview

AX_TRANS_SCHEMES is a configuration table in the AX (Global Accounting Engine) product of Oracle E-Business Suite, documented as VALID in both 12.1.1 and 12.2.2. It stores translation scheme definitions that govern how the Global Accounting Engine derives subledger accounting entries from source event data. Each row defines a translation scheme for a specific set of books and originating application, allowing the engine to map event types, event mappings, and distribution rules to the appropriate accounting treatment.

From a Data Vault modeling perspective, the heuristic classification of AX_TRANS_SCHEMES is hub-leaning. Its composite unique key of SET_OF_BOOKS_ID, APPLICATION_ID, and TRANSLATION_SCHEME behaves as a natural business key, making it a candidate hub. The absence of descriptive foreign-key fan-out into other hubs (rather, other tables reference it) reinforces this hub interpretation, with the remaining descriptive columns acting as satellite-style attributes attached to that key.

Key Information Stored

The table contains 12 documented columns. The primary key, AX_TRANS_SCHEMES_PK, is defined on the composite of SET_OF_BOOKS_ID, APPLICATION_ID, and TRANSLATION_SCHEME. A unique index, AX_TRANS_SCHEMES_U1, is defined on the same three columns, confirming this triplet as the business-key candidate rather than a surrogate sequence identifier.

  • SET_OF_BOOKS_ID — identifies the ledger (set of books) to which the translation scheme applies; part of the primary key.
  • APPLICATION_ID — identifies the originating application (for example, a subledger source) associated with the scheme; part of the primary key.
  • TRANSLATION_SCHEME — the scheme identifier or code distinguishing one translation rule set from another; part of the primary key.
  • BASE_APPLICATION_ID — the base application whose events the scheme translates.
  • BASE_EVENT_TABLE — the source event table from which translation input is drawn.
  • ENABLED_FLAG — indicates whether the scheme is active and available for translation processing.
  • DESCRIPTION — free-text description of the scheme's purpose.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns recording who created and last modified the row and when.

Common Use Cases and Queries

Typical scenarios include verifying which translation schemes are enabled for a ledger, reviewing scheme configuration before running Global Accounting Engine processes, and joining scheme rows to dependent distribution and event tables for reconciliation.

  • Listing enabled schemes for a set of books:
    SELECT translation_scheme, description, base_event_table FROM ax.ax_trans_schemes WHERE set_of_books_id = :p_sob AND enabled_flag = 'Y';
  • Resolving a scheme's base event source:
    SELECT application_id, base_application_id, base_event_table FROM ax.ax_trans_schemes WHERE set_of_books_id = :p_sob AND translation_scheme = :p_scheme;
  • Auditing recent configuration changes:
    SELECT translation_scheme, last_updated_by, last_update_date FROM ax.ax_trans_schemes WHERE set_of_books_id = :p_sob ORDER BY last_update_date DESC;
  • Reconciliation reporting that joins high-volume distribution rows back to scheme metadata, filtered by set of books and application.

Related Objects

Several AX tables carry foreign-key references to this table through the SET_OF_BOOKS_ID, APPLICATION_ID, and TRANSLATION_SCHEME combination, making them the most significant dependents:

  • AX_DISTRIB_HEADERS — references AX_TRANS_SCHEMES via SET_OF_BOOKS_ID, APPLICATION_ID, and TRANSLATION_SCHEME.
  • AX_DISTRIB_PLANS — same join columns, linking distribution plans to their translation scheme.
  • AX_EVENT_MAPPINGS — same join columns, associating event mappings with a scheme.
  • AX_EVENT_TYPES — same join columns, associating event type definitions with a scheme.

Because the primary key is composite, joins to these tables must include set of books, application, and translation scheme to avoid ambiguous or cartesian results. All objects reside in the AX schema and are rendered under Oracle Proprietary, Confidential Information terms.