Search Results ax_trans_programs_u1

Overview

AX.AX_TRANS_PROGRAMS is a transactional setup table in the Application Exchange (AX) product family of Oracle E-Business Suite, documented as VALID in both release 12.1.1 and 12.2.2. It stores information about translator programs, which are the AX components responsible for converting subledger accounting events into General Ledger journal entries. The table contains one row for each combination of application, main set of books, and posting set of books for which a translator program is required. In effect, it defines the translation scope: which application's event data is processed, which main ledger provides the accounting definitions, and which posting ledger receives the resulting journals.

From a Data Vault modeling perspective, the ETRM relationship metadata classifies this object as hub-leaning. This is a heuristic suggestion rather than a physical implementation attribute. The classification reflects the fact that the three-part primary key (APPLICATION_ID, MAIN_SET_OF_BOOKS_ID, POSTING_SET_OF_BOOKS_ID) constitutes a durable business key, and the RULE_* attributes behave as descriptive satellite context attached to that key. Downstream objects such as AX_EVENT_TYPES and AX_SETUP_POSTING_BOOKS reference this key, reinforcing its role as a central integration anchor for translator configuration.

Key Information Stored

The columns of interest fall into three groups: the composite key, the translation rule metadata, and standard audit columns.

• APPLICATION_ID — identifier of the application whose events are translated; part of the primary key and of unique index AX_TRANS_PROGRAMS_U1.
• MAIN_SET_OF_BOOKS_ID — identifier of the main set of books (ledger) supplying accounting definitions; part of the primary key and AX_TRANS_PROGRAMS_U1.
• POSTING_SET_OF_BOOKS_ID — identifier of the posting set of books (ledger) receiving the translated journals; part of the primary key and AX_TRANS_PROGRAMS_U1.
• RULE_NAME — VARCHAR2(30) naming the rule set from which the translator program was loaded.
• RULE_VERSION, RULE_SUB_VERSION, RULE_REVISION — VARCHAR2(30) columns capturing the version lineage of the loaded rule set.
• FROZEN_DATE — date on which the translator program configuration was frozen.
• FROZEN_FLAG — retained for backward compatibility; documented as no longer used.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — standard Who and concurrent program audit columns.

The surrogate primary key AX_TRANS_PROGRAMS_PK and the unique index AX_TRANS_PROGRAMS_U1 are defined on the identical three-column composite. There is no separate single-column surrogate; the natural business key serves directly as the primary key, which is characteristic of configuration tables rather than high-volume fact tables. Note that AX_TRANS_PROGRAMS_U1 resides in the APPS_TS_TX_IDX tablespace while the table itself resides in APPS_TS_TX_DATA.

Common Use Cases and Queries

Typical queries confirm translation coverage and audit rule versions applied across ledgers. A join to FND_APPLICATION and GL_LEDGERS enriches the identifier columns with readable names. To list every translator configuration with its rule lineage:

• SELECT main_set_of_books_id, posting_set_of_books_id, rule_name, rule_version, rule_revision FROM ax.ax_trans_programs ORDER BY application_id, main_set_of_books_id;
• Identify rows frozen before a given date for change-management review: SELECT * FROM ax.ax_trans_programs WHERE frozen_date < :cutoff_date;
• Confirm that a specific application/ledger pair is configured before submitting the AX translation concurrent program: SELECT COUNT(*) FROM ax.ax_trans_programs WHERE application_id = :app_id AND main_set_of_books_id = :main_sob AND posting_set_of_books_id = :post_sob;
• Detect stale rule versions by comparing RULE_VERSION and RULE_REVISION against the currently installed AX rule set.

The creation and last-update audit columns, populated with the concurrent REQUEST_ID and PROGRAM_ID, support tracing which concurrent request loaded or refreshed a given translator configuration.

Related Objects

Referential relationships documented in the ETRM metadata show this table acting as a referenced parent. The two explicit foreign key sources are AX_EVENT_TYPES, which references APPLICATION_ID, and AX_SETUP_POSTING_BOOKS, which also references APPLICATION_ID. In addition, the three key columns resolve to standard EBS master data via FND_APPLICATION (APPLICATION_ID), GL_SETS_OF_BOOKS or GL_LEDGERS (MAIN_SET_OF_BOOKS_ID, POSTING_SET_OF_BOOKS_ID). Together these relationships confirm that AX_TRANS_PROGRAMS is the integration point between application-level event configuration, posting book setup, and translator rule versions, and that any change to its key columns has downstream consequences for event type and posting book processing.