Search Results ax_distrib_plans




Overview
Explore in AI Chat

Overview

The AX_DISTRIB_PLANS table is a core configuration object in the AX (Global Accounting Engine) product of Oracle E-Business Suite, documented as VALID in both release 12.1.1 and 12.2.2. It stores the distribution plans associated with translation schemes, defining how the Global Accounting Engine distributes balances and journal entries across accounts, cost centers, and reporting structures during the translation and consolidation process. In the context of EBS financials, the AX schema serves as the repository for the accounting engine that sits beneath General Ledger, enabling subledger-level translation and revaluation rules. A distribution plan therefore acts as the rule set that determines where translated amounts land in the chart of accounts.

From a Data Vault modeling perspective, the metadata classifies AX_DISTRIB_PLANS as satellite-leaning. This is a heuristic suggestion rather than an enforced construct: the table behaves as a descriptive attribute satellite attached to the business key composed of SET_OF_BOOKS_ID, APPLICATION_ID, TRANSLATION_SCHEME, and PLAN_NAME. Its attributes evolve over time and depend on upstream translation scheme definitions, which is characteristic satellite behavior rather than that of a hub or link.

Key Information Stored

The table is documented with eleven physical columns. The most operationally significant are the following:

  • SET_OF_BOOKS_ID — Identifies the set of books (ledger) to which the distribution plan applies. Part of the composite primary key and the primary foreign key relationship.
  • APPLICATION_ID — The application owning the translation context, distinguishing source application data within the accounting engine.
  • TRANSLATION_SCHEME — The translation scheme with which this distribution plan is associated; a critical join key to AX_TRANS_SCHEMES.
  • PLAN_NAME — The user-defined name of the distribution plan; the descriptive business identifier within a given translation scheme.
  • PLAN_TYPE — Classifies the nature or behavior of the distribution plan, governing how the engine applies the plan rules.
  • CR_DR_FLAG — Indicates the debit or credit side to which the distribution logic applies, a decisive factor in account derivation.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing who created and last modified each plan and when.

The surrogate primary key is AX_DISTRIB_PLANS_PK, defined on (SET_OF_BOOKS_ID, APPLICATION_ID, TRANSLATION_SCHEME, PLAN_NAME). The unique index AX_DISTRIB_PLANS_U1 covers the same four columns, confirming this composite as the business-key candidate. Practitioners should treat this quartet as the natural identifier for integration and ETL purposes.

Common Use Cases and Queries

Typical scenarios include validating that every active translation scheme has a corresponding distribution plan, auditing changes to distribution logic ahead of period-end close, and reporting plan configurations across ledgers. A representative query joins the table to its parent translation schemes:

  • SELECT p.set_of_books_id, p.translation_scheme, p.plan_name, p.plan_type, p.cr_dr_flag FROM ax.ax_distrib_plans p WHERE p.set_of_books_id = :ledger_id;
  • Detect orphaned plans: SELECT p.* FROM ax.ax_distrib_plans p WHERE NOT EXISTS (SELECT 1 FROM ax.ax_trans_schemes s WHERE s.set_of_books_id = p.set_of_books_id AND s.application_id = p.application_id AND s.translation_scheme = p.translation_scheme);
  • Audit recently modified plans: filter on LAST_UPDATE_DATE and LAST_UPDATED_BY to trace configuration drift during implementation or support cycles.

Related Objects

The referential relationships define a clear hierarchy around this object:

  • AX_TRANS_SCHEMES — Parent table referenced via SET_OF_BOOKS_ID, APPLICATION_ID, and TRANSLATION_SCHEME; distribution plans belong to translation schemes.
  • AX_STRUCTURES — Child table referencing AX_DISTRIB_PLANS through SET_OF_BOOKS_ID, APPLICATION_ID, TRANSLATION_SCHEME, and PLAN_NAME; it holds the account structure lines that the plan drives.
  • Standard EBS audit and lookup infrastructure (FND_USER via CREATED_BY/LAST_UPDATED_BY) supports attribution and change tracking.

Together, AX_TRANS_SCHEMES, AX_DISTRIB_PLANS, and AX_STRUCTURES form the configuration backbone for AX translation processing, and any modification to distribution plans should be evaluated against downstream AX_STRUCTURES entries.