Results for “rule_changed_flag”

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

Overview

AX_SETUP_POSTING_BOOKS is a configuration table owned by the AX schema (Global Accounting Engine) in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store posting sets of books information per main set of books. In other words, it defines how the Global Accounting Engine (AX) maps a main set of books, together with an inventory source organization, to one or more posting sets of books — the ledgers into which AX-generated subledger and transfer journal entries are ultimately written.

Because the table records associations between a main set of books, a source organization, and derived posting sets of books, its heuristic Data Vault classification is a link (relationship) table. Under this modeling suggestion, it behaves as a junction connecting reference hubs such as the main set of books, posting set of books, and source organization, with a satellite-like set of descriptive rule attributes attached.

Key Information Stored

The documented primary key is AX_SETUP_POSTING_BOOKS_PK, composed of the four business-identifying columns APPLICATION_ID, MAIN_SET_OF_BOOKS_ID, SOURCE_ORG_ID, and POSTING_SET_OF_BOOKS_ID. A unique index (AX_SETUP_POSTING_BOOKS_U1) uses the same four columns, confirming these as the business-key candidates. The table documents 28 columns in total. The principal columns are:

• APPLICATION_ID — the application context (Global Accounting Engine components) to which the posting set applies.
• MAIN_SET_OF_BOOKS_ID — the primary ledger whose accounting activity is being transferred or mirrored.
• SOURCE_ORG_ID — the inventory/operating organization associated with the posting rule.
• POSTING_SET_OF_BOOKS_ID — the target set of books that receives the posted journals.
• TRANSFER_TO_GL — controls whether entries are transferred to the General Ledger.
• GL_POST_REQUIRED and DUAL_POSTING_FLAG — govern GL posting behavior and dual-posting configuration.
• RULE_NAME, RULE_VERSION, RULE_SUB_VERSION, RULE_REVISION, RULE_CHANGED_FLAG — identify the posting rule and its versioning metadata.
• JE_LINE_TYPE — the journal entry line type applied during posting.
• PERIOD_FROM / PERIOD_TO — the effective accounting period range.
• GL_CONSOLIDATION_ID — the consolidation identifier used during transfer.
• LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, REQUEST_ID — standard audit and concurrent-program tracking columns.

Common Use Cases and Queries

Typical reporting scenarios include verifying which posting books are configured for a main set of books, auditing rule-version changes, and tracing journal transfers to the General Ledger. A representative query joins posting books to GL_SETS_OF_BOOKS to resolve ledger names:

SELECT p.main_set_of_books_id, p.source_org_id, p.posting_set_of_books_id, g.name, p.transfer_to_gl, p.gl_post_required FROM ax.ax_setup_posting_books p, gl_sets_of_books g WHERE p.posting_set_of_books_id = g.set_of_books_id;

Analysts also filter on TRANSFER_TO_GL or RULE_CHANGED_FLAG to identify ledgers not transferred to GL or rules recently revised. Period-restricted queries using PERIOD_FROM and PERIOD_TO help confirm the effective configuration for a given accounting period.

Related Objects

• AX_SETUP_SUBLEDGERS — joined via APPLICATION_ID and MAIN_SET_OF_BOOKS_ID to define subledger setup.
• AX_TRANS_PROGRAMS — joined via APPLICATION_ID, MAIN_SET_OF_BOOKS_ID, and POSTING_SET_OF_BOOKS_ID to tie posting books to transfer programs.
• GL_SETS_OF_BOOKS — referenced via POSTING_SET_OF_BOOKS_ID, supplying ledger definitions.

These foreign-key relationships make AX_SETUP_POSTING_BOOKS a central linking point between AX subledger configuration and General Ledger ledger definitions.