Results for “accounting_required_flag”

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

Overview

XLA_PROD_ACCT_HEADERS is a Subledger Accounting (XLA) configuration table in the XLA schema of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It optionally stores accounting header types for an Application Accounting Definition in combination with an event class or event type. When an accounting header entry is not defined for a given combination, a flag on the corresponding record indicates that no accounting is required, allowing the Subledger Accounting engine to bypass journal creation for that event.

The table therefore acts as a control and definition point within the accounting rules repository. It participates in the creation of subledger journal entries by declaring the fundamental accounting header metadata that governs how an event is processed. Heuristically, the mined Data Vault classification is standalone; this suggests a modeling view in which the table functions as an independent hub-like reference object, keyed by its composite business identifier rather than participating in a dependent link or satellite structure.

Key Information Stored

Each row is uniquely identified by the composite primary key XLA_PROD_ACCT_HEADERS_PK, which spans APPLICATION_ID, AMB_CONTEXT_CODE, PRODUCT_RULE_TYPE_CODE, PRODUCT_RULE_CODE, ENTITY_CODE, EVENT_CLASS_CODE, and EVENT_TYPE_CODE. A second unique index, XLA_PROD_ACCT_HEADERS_U1, adds ZD_EDITION_NAME to the same set of columns, serving as the business-key candidate that includes the edition dimension. The most significant columns are:

• APPLICATION_ID – identifies the subledger application owning the rule.
• AMB_CONTEXT_CODE – the Accounting Methods Builder context qualifying the definition.
• PRODUCT_RULE_TYPE_CODE and PRODUCT_RULE_CODE – the application accounting definition type and its code.
• ENTITY_CODE – the entity (transaction type mapping) for which the accounting header applies.
• EVENT_CLASS_CODE and EVENT_TYPE_CODE – the event class and, optionally, the specific event type governed.
• DESCRIPTION_TYPE_CODE and DESCRIPTION_CODE – the accounting header description used on the resulting journal.
• ACCOUNTING_REQUIRED_FLAG – indicates whether accounting must be generated for the combination, or explicitly suppressed.
• VALIDATION_STATUS_CODE and LOCKING_STATUS_FLAG – control the validation and locking state of the definition.
• ZD_EDITION_NAME – the edition identifier supporting the 12.2.2 editioning model.
• Audit columns – CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical use cases include diagnosing why a subledger event failed to produce a journal entry, auditing accounting definitions configured through the Accounting Methods Builder, and reporting on the set of event classes and event types for which accounting is suppressed. A common pattern joins this table to the broader XLA definition tables by APPLICATION_ID, AMB_CONTEXT_CODE, and PRODUCT_RULE_CODE to resolve the application accounting definition context.

• Query all event classes where ACCOUNTING_REQUIRED_FLAG equals 'N' to identify intentionally unaccounted events.
• Validate that no duplicate header definitions exist per edition by grouping on the unique-index columns.
• Report validation and locking status to identify stale or incomplete accounting setup.
• Correlate DESCRIPTION_CODE values with downstream journal header generation rules.

Related Objects

The table is joined through its composite key to the following significant XLA objects:

• XLA_AMB_CONTEXTS – joins on AMB_CONTEXT_CODE.
• XLA_PROD_RULES / application accounting definition tables – join on APPLICATION_ID, PRODUCT_RULE_TYPE_CODE, and PRODUCT_RULE_CODE.
• XLA_ENTITIES – joins on ENTITY_CODE.
• XLA_EVENT_CLASSES and XLA_EVENT_TYPES – join on EVENT_CLASS_CODE and EVENT_TYPE_CODE.
• XLA_ACCOUNTING_HEADERS / XLA_ACCT_HEADERS – resolves the accounting header definitions referenced here.
• XLA_DESCRIPTIONS – joins on DESCRIPTION_TYPE_CODE and DESCRIPTION_CODE.
• XLA_AE_HEADERS – the resulting subledger journal header table populated during accounting generation.

The Accounting Methods Builder APIs and the Create Accounting program both consume records from XLA_PROD_ACCT_HEADERS as configuration input.