Search Results xla_acctg_method_rules_u1

Overview

The XLA.XLA_ACCTG_METHOD_RULES table is a core configuration repository within the Oracle E-Business Suite Subledger Accounting (SLA) architecture, owned by the XLA schema. It stores the Accounting Method rules that bind an Accounting Method to a specific Application Accounting Definition, thereby defining how a given subledger application generates journal entries for a particular accounting method context. This object is central to the Accounting Methods Builder (AMB), which is the framework used to create, version, and apply accounting definitions across subledger applications in both EBS 12.1.1 and 12.2.2.

Each row represents an accounting method rule scoped by application, AMB context, and product rule type/code. The effective-dating columns allow Oracle to maintain historical and future-dated versions of the same rule. Given the FK/PK metadata, this object is heuristically classified as a standalone entity in a Data Vault modeling sense — it does not directly participate as a classic hub, link, or satellite in the documented relationship graph, though functionally it behaves like a configuration hub keyed by accounting method and application scope.

Key Information Stored

The table contains 15 documented columns. The most significant are:

• ACCTG_METHOD_RULE_ID — Surrogate identifier for the rule; the leading column of the unique index XLA_ACCTG_METHOD_RULES_U1 and a member of the composite primary key XLA_ACCTG_METHOD_RULES_PK.
• ACCOUNTING_METHOD_TYPE_CODE — Type classification of the accounting method; part of the primary key.
• ACCOUNTING_METHOD_CODE — The accounting method code (max 30 characters); part of the primary key and a business-key candidate.
• APPLICATION_ID — Internal ID of the owning application; part of the primary key and the leading column of the non-unique index XLA_ACCTG_METHOD_RULES_N1.
• AMB_CONTEXT_CODE — Accounting Methods Builder context (max 30 characters); indexed via N1 and used to scope rule resolution.
• PRODUCT_RULE_TYPE_CODE — Application Accounting Definition type code; indexed via N1.
• PRODUCT_RULE_CODE — Application Accounting Definition code (max 30 characters); indexed via N1.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effective dating range controlling when the rule is active.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns referencing FND_USER and FND_LOGINS.
• ZD_EDITION_NAME — Editioning column present in the 12.2.2 physical schema; also part of the unique index XLA_ACCTG_METHOD_RULES_U1.

Common Use Cases and Queries

Typical uses include diagnosing why a subledger transaction produced (or failed to produce) journal entries under a specific accounting method, auditing effective-dated rule changes, and reporting the configuration of Application Accounting Definitions per application.

• Identify rules for a given application and accounting method: SELECT * FROM XLA.XLA_ACCTG_METHOD_RULES WHERE APPLICATION_ID = :app AND ACCOUNTING_METHOD_CODE = :method;
• Resolve rules active on a specific date: filter where START_DATE_ACTIVE <= :eff_date AND (END_DATE_ACTIVE IS NULL OR END_DATE_ACTIVE >= :eff_date).
• Trace a rule via its business key using XLA_ACCTG_METHOD_RULES_U1 on ACCTG_METHOD_RULE_ID.
• Report by AMB context: SELECT AMB_CONTEXT_CODE, COUNT(*) FROM XLA.XLA_ACCTG_METHOD_RULES GROUP BY AMB_CONTEXT_CODE;

Related Objects

Because the documented relationship data classifies this object as standalone, direct foreign-key joins are limited. The following are the most significant related objects based on the AMB and Subledger Accounting model:

• XLA_ACCTG_METHODS_B / XLA_ACCTG_METHODS_TL — Accounting method definitions referenced by ACCOUNTING_METHOD_CODE and APPLICATIONS_ID.
• XLA_AMB_CONTEXTS / XLA_AMB_CONTEXT_TYPES — Define the AMB_CONTEXT_CODE used here.
• XLA_APPLN_ACCT_DEFNS_B / XLA_APPLN_ACCT_DEFNS_TL — Application Accounting Definitions matching PRODUCT_RULE_CODE and PRODUCT_RULE_TYPE_CODE.
• XLA_ACCTG_METHOD_RULE_DTLS — Detail lines belonging to each rule identified by ACCTG_METHOD_RULE_ID.
• FND_APPLICATION — Resolves APPLICATION_ID to an application short name.
• FND_USER / FND_LOGINS — Join targets for the WHO audit columns.