Results for “ax_trans_schemes_v”

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

Overview

The AX_TRANS_SCHEMES_V view belongs to the Global Accounting Engine (AX) product family in Oracle E-Business Suite. It exposes translation scheme definitions used by the AX engine to derive accounting entries, and it presents a unified, query-ready list of translation schemes available to a given ledger. In the context of the search term "translation_scheme," this view is the primary dictionary object that EBS developers and functional consultants consult when they need to determine which schemes exist for a set of books, whether each scheme is enabled, and how each scheme is named for end users.

Its defining characteristic is that it is a UNION-based view. The first branch reads directly from the AX_TRANS_SCHEMES base table, while the second branch synthesizes an additional row by joining AX_TRANS_SCHEMES with AX_LOOKUPS restricted to LOOKUP_TYPE = 'AX_FIXED_SCHEMES' and LOOKUP_CODE = 'NOOP_SCHEME'. This construction ensures that a system-reserved "no operation" scheme is always presented alongside user-defined schemes, allowing downstream logic and reporting to treat fixed and user-defined schemes uniformly.

In the 12.1.1 and 12.2.2 releases, the view is best understood as a reporting and integration surface rather than a transactional object. The ETRM metadata explicitly records that the view is "Not implemented in this database" in the sampled environment, which is consistent with the fact that AX objects are only instantiated when the Global Accounting Engine is licensed and configured for the relevant ledger.

Underlying Base Objects

The documented view text references two base objects: AX_TRANS_SCHEMES and AX_LOOKUPS. The ETRM metadata states that no base objects are formally documented as referenced objects, so the authoritative source of the dependency information is the view SQL itself.

• AX_TRANS_SCHEMES — the primary table storing translation scheme definitions, keyed by SET_OF_BOOKS_ID and APPLICATION_ID, with the scheme name held in TRANSLATION_SCHEME and status in ENABLED_FLAG.
• AX_LOOKUPS — the lookup table supplying the fixed scheme entry, filtered on LOOKUP_TYPE = 'AX_FIXED_SCHEMES' and LOOKUP_CODE = 'NOOP_SCHEME'. The lookup's MEANING becomes the user-facing scheme name and LOOKUP_CODE becomes the internal scheme identifier for that synthesized row.

Because the view is a UNION rather than a join across all rows, the NOOP scheme is appended as a distinct row and is not merged with any like-named user scheme. Consumers should therefore expect at least one row per ledger even when no user-defined schemes have been configured.

Key Columns

• SET_OF_BOOKS_ID — identifies the ledger (set of books) to which the translation scheme belongs. This is the primary partitioning key for querying schemes in a multi-ledger environment.
• APPLICATION_ID — identifies the application that owns or defines the scheme, allowing schemes to be scoped by source application.
• USER_SCHEME — the display name of the scheme. In the first UNION branch this is the raw TRANSLATION_SCHEME value; in the second branch it is the lookup MEANING for the NOOP scheme.
• TRANSLATION_SCHEME — the scheme identifier used internally. In the first branch this is the scheme's own name; in the second branch it is the LOOKUP_CODE value ('NOOP_SCHEME').
• ENABLED_FLAG — indicates whether the scheme is active. Only schemes with an enabled flag should typically be offered to users or processed by the AX engine.

Common Use Cases and Queries

Typical scenarios include validating which schemes are active for a ledger, populating a translation scheme list of values, and diagnosing why an expected NOOP scheme is absent. The following query lists all enabled schemes for a given set of books:

• SELECT user_scheme, translation_scheme, enabled_flag FROM ax_trans_schemes_v WHERE set_of_books_id = :p_sob_id AND enabled_flag = 'Y' ORDER BY user_scheme;
• To isolate fixed versus user-defined schemes, filter on whether TRANSLATION_SCHEME equals 'NOOP_SCHEME'.
• To audit configuration across ledgers, group by SET_OF_BOOKS_ID and APPLICATION_ID and count enabled schemes.

Because the view is read-only in practice and derived from a UNION, it is suited to reporting and integration lookups rather than direct DML. All queries should bind SET_OF_BOOKS_ID to limit the result set to the ledger under review.