Search Results ra_account_defaults_u1

Overview

AR.RA_ACCOUNT_DEFAULTS_ALL is a transactional configuration table in the Oracle Receivables module of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. It stores the accounting default rules that determine how Receivables derives general ledger account combinations for automatic accounting events during AutoAccounting processing. Each row represents a distinct default rule keyed by a generated identifier, and is associated with sub-rows held in RA_ACCOUNT_DEFAULT_SEGMENTS that define the individual GL account segment values to be assembled. The table is defined with the FND Design Data name AR.RA_ACCOUNT_DEFAULTS_ALL, resides in the APPS_TS_TX_DATA tablespace, and is exposed through a multi-org view that returns only the rows for the current operating unit.

Applying heuristic Data Vault modeling, this object is classified as hub-leaning. It holds the stable, uniquely identified set of accounting default definitions, with descriptive and flexfield attributes attached. In a formal Data Vault design it would most closely resemble a hub with a small satellite for the descriptive flexfield and type attributes.

Key Information Stored

The most significant columns documented for this table are:

• GL_DEFAULT_ID — the surrogate primary key and the single business-key candidate. It is the sole column of the unique index RA_ACCOUNT_DEFAULTS_U1 and of the primary key constraint RA_ACCOUNT_DEFAULTS_PK, uniquely identifying each default rule.
• TYPE — the classification of the accounting default rule, distinguishing which AutoAccounting event or source (such as revenue, tax, freight, or receivables) the rule applies to.
• ORG_ID — the operating unit identifier enabling the multi-org view to isolate data per current organization, since the table is defined with a multi-org view.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield structure definition and segment columns, allowing customers to extend the default definitions with site-specific attributes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — standard WHO audit columns capturing the user and timestamp of row creation and last modification, with foreign key references to FND_USER and FND_LOGINS.

The GL_DEFAULT_ID is purely a surrogate identity column; there is no documented composite natural key, so uniqueness of a rule is enforced solely through this sequence-generated identifier.

Common Use Cases and Queries

This table is principally queried to audit or diagnose AutoAccounting setups, particularly when account generation fails or derives an unexpected GL account combination. Typical reporting includes listing all default rules by type for a given operating unit, and tracing the segments that complete each rule.

A representative query to list defaults for the current operating unit:

• SELECT gl_default_id, type, org_id, last_update_date FROM ar.ra_account_defaults_all WHERE org_id = :org_id ORDER BY type;

To trace a rule to its segment values:

• SELECT d.gl_default_id, d.type, s.segment_name, s.segment_value FROM ar.ra_account_defaults_all d, ar.ra_account_default_segments s WHERE d.gl_default_id = s.gl_default_id;

These patterns support setup validation, migration comparison between environments, and reconciliation of why a particular accounting entry received a given account combination.

Related Objects

The most significant related object is AR.RA_ACCOUNT_DEFAULT_SEGMENTS, which references this table through the foreign key GL_DEFAULT_ID → RA_ACCOUNT_DEFAULTS_ALL.GL_DEFAULT_ID. This child table stores the individual GL account segment values assembled by each default rule, so the two tables are always queried together to reconstruct a complete AutoAccounting definition. The WHO audit columns reference FND_USER (via CREATED_BY and LAST_UPDATED_BY) and FND_LOGINS (via LAST_UPDATE_LOGIN) for user and login attribution. As the configuration backing AutoAccounting, the table is consumed by Receivables accounting and posting processes, and it works in conjunction with the multi-org view definition over ORG_ID that governs operating-unit data isolation. Together these dependencies make RA_ACCOUNT_DEFAULTS_ALL a controlling configuration hub for Receivables account derivation.