Search Results encumbrance_account




Overview

AX_MTL_CATEGORY_ACCOUNTS_V2 is a reporting view belonging to the AX - Global Accounting Engine (Global Accounting Engine, or AX) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The view exposes the full set of default inventory and valuation accounts associated with a given organization, subinventory, cost group, and inventory item combination. Its structure is identical to AX_MTL_CATEGORY_ACCOUNTS_V1; the ETRM metadata explicitly describes it as a duplicate of that object. The V2 suffix typically denotes a variant created to satisfy a distinct naming or compatibility requirement while preserving the same column signature and semantics.

Because the view surfaces the ENCUMBRANCE_ACCOUNT column, it is relevant to users searching for encumbrance account configuration. Encumbrance accounting records anticipated expenditures and liabilities for purchase orders and requisitions, and this view provides the item and cost-group level default from which the encumbrance account is derived during accounting event generation.

Underlying Base Objects

The ETRM metadata documents no referenced base tables for this view, and it is noted as "Not implemented in this database." The view text shows that AX_MTL_CATEGORY_ACCOUNTS_V2 selects directly from AX_MTL_CATEGORY_ACCOUNTS_V1, meaning it is a pass-through wrapper rather than an independently defined view:

  • AX_MTL_CATEGORY_ACCOUNTS_V1 — the single documented source object, supplying all eighteen columns.
  • No direct reference to MTL_SYSTEM_ITEMS, MTL_ITEM_CATEGORIES, or MTL_SECONDARY_INVENTORIES appears in the view text; any such joins are performed within V1.
  • Column names are preserved without transformation, consistent with a naming-variant duplicate.

Key Columns

Common Use Cases and Queries

The view is principally used to inspect or extract default account configurations, to reconcile AX analytical account setup, and to verify the encumbrance account assigned at item or cost-group level. A typical query targeting the encumbrance account might resemble the following:

SELECT organization_id, subinventory_code, inventory_item_id, cost_group_id, encumbrance_account FROM ax_mtl_category_accounts_v2 WHERE organization_id = :p_org_id AND inventory_item_id = :p_item_id;

Because V2 is a duplicate of V1, either view may be queried interchangeably for the same result set. Implementers should confirm that the view is deployed in the target instance, as the ETRM record indicates it was not implemented in the reference database from which the documentation was generated. When the view is absent, query AX_MTL_CATEGORY_ACCOUNTS_V1 or the underlying inventory account setup tables directly.