Search Results xla_product_rules_b




Overview
Explore in AI Chat

Overview

XLA_PRODUCT_RULES_B is the base table within the Oracle Subledger Accounting (XLA) schema that stores the standard product accounting rules defined for an application. These rules describe how subledger transactions are transformed into accounting entries, and they are deliberately defined independently of any particular chart of accounts. This design allows a single product rule to be applied across multiple ledgers and accounting configurations, with the chart-of-accounts-specific mapping resolved through separate context and detail tables at runtime.

Within the ETRM 12.2.2 physical schema, XLA_PRODUCT_RULES_B resides in the XLA schema and contains 23 documented columns. The table is primarily keyed on the combination of APPLICATION_ID, AMB_CONTEXT_CODE, PRODUCT_RULE_TYPE_CODE, and PRODUCT_RULE_CODE, which uniquely identifies each product rule for an owning application and accounting method builder context. From a Data Vault modeling perspective, the heuristic classification for this object is standalone. This suggests the table may be modeled as a hub with its own business key, rather than as a dependent link or satellite, although the presence of descriptive and lifecycle columns indicates that a satellite construct would typically accompany such a hub in a dimensional warehouse.

Key Information Stored

The most important columns in XLA_PRODUCT_RULES_B relate to rule identity, ownership, and operational status. The primary key, XLA_PRODUCT_RULES_B_PK, is composed of APPLICATION_ID, AMB_CONTEXT_CODE, PRODUCT_RULE_TYPE_CODE, and PRODUCT_RULE_CODE. Together these four columns form the surrogate and natural identifier for each rule.

The unique index XLA_PRODUCT_RULES_B_U1 extends this business-key candidate by adding ZD_EDITION_NAME, reflecting the edition-aware design used in later EBS releases and supporting multi-edition or patch-level differentiation of the same logical rule.

  • APPLICATION_ID — identifies the owning Oracle application (for example Payables, Receivables, or Assets) to which the product rule belongs.
  • AMB_CONTEXT_CODE — the Accounting Methods Builder context that scopes the rule, linking it to a specific accounting method or event context.
  • PRODUCT_RULE_TYPE_CODE — classifies the rule by type, distinguishing categories of accounting logic such as transaction or accounting rules.
  • PRODUCT_RULE_CODE — the user-visible or internal identifier for the rule itself.
  • TRANSACTION_COA_ID and ACCOUNTING_COA_ID — reference the chart of accounts used for transaction and accounting purposes, allowing the rule to span ledgers.
  • ENABLED_FLAG — indicates whether the rule is active and eligible for processing at runtime.
  • PRODUCT_RULE_VERSION and VERSION_NUM — support versioning and historical tracking of rule definitions.
  • COMPILE_STATUS_CODE and LOCKING_STATUS_FLAG — reflect compilation and locking state during rule generation and validation.
  • PRODUCT_RULE_HASH_ID — stores a hash used for change detection and cache invalidation.
  • REQUEST_ID, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — standard audit columns recording the concurrent request and user context for rule creation and maintenance.
  • PROGRAM_UPDATE_DATE, PROGRAM_APPLICATION_ID, and PROGRAM_ID — identify the concurrent program that last modified the rule.
  • UPDATED_FLAG — a transient flag used by internal processes to signal pending updates.
  • ZD_EDITION_NAME — the edition identifier used in EBS 12.2 edition-based redefinition.

Common Use Cases and Queries

XLA_PRODUCT_RULES_B is queried primarily during subledger accounting setup, troubleshooting, and rule migration activities. A common reporting need is to list all enabled product rules for a given application and accounting method context:

  • SELECT product_rule_code, product_rule_type_code, enabled_flag FROM xla_product_rules_b WHERE application_id = :app_id AND amb_context_code = :ctx;
  • Auditing recent changes: joining CREATED_BY and LAST_UPDATED_BY to FND_USER to identify who modified rule definitions.
  • Version analysis: filtering on PRODUCT_RULE_VERSION or VERSION_NUM to compare historical rule definitions.
  • Compilation monitoring: selecting rules where COMPILE_STATUS_CODE indicates failure or pending compilation.

Related Objects

The following objects are most significant in relation to XLA_PRODUCT_RULES_B:

  • XLA_PRODUCT_RULES_TL — the translation table holding language-specific names and descriptions, joined on APPLICATION_ID, AMB_CONTEXT_CODE, PRODUCT_RULE_TYPE_CODE, and PRODUCT_RULE_CODE.
  • XLA_PRODUCT_RULES_D or analogous rule detail tables — hold the rule lines and account derivation logic that depend on the header defined here.
  • XLA_EVENT_TYPES_B / XLA_EVENT_CLASSES_B — define the event framework that consumes product rules.
  • XLA_ACCOUNTING_METHODS_B — the accounting methods that reference product rules during event processing.
  • FND_APPLICATION — provides the application name for APPLICATION_ID.
  • FND_CONCURRENT_REQUESTS — used to resolve REQUEST_ID and PROGRAM_ID audit references.

Because the table is heuristic-standalone and does not carry documented foreign keys, joins are typically driven by the shared business-key columns rather than enforced referential constraints.