Search Results ra_account_defaults_pk

Overview

RA_ACCOUNT_DEFAULTS_ALL is the AutoAccounting definition table in the Oracle Receivables (AR) module of Oracle E-Business Suite 12.1.1 and 12.2.2. AutoAccounting is the rule engine that derives the individual general ledger account segments (company, cost center, account, and so on) that Receivables uses when it generates accounting entries for transactions, receipts, adjustments, credit memos, freight, and other subledger events. Each row in RA_ACCOUNT_DEFAULTS_ALL represents one AutoAccounting default rule keyed by a combination of AutoAccounting type and, where relevant, organization unit.

The table resides in the AR schema, is documented as VALID, and holds 24 columns. Its primary key is RA_ACCOUNT_DEFAULTS_PK, defined on GL_DEFAULT_ID. A unique index, RA_ACCOUNT_DEFAULTS_U1, also exists on GL_DEFAULT_ID, confirming it as the business-key candidate. Under the heuristic Data Vault classification supplied in the metadata, the table is hub-leaning: GL_DEFAULT_ID identifies each AutoAccounting rule as an independent business entity, while the segment-level details are carried by a dependent child table. That classification is a modeling suggestion rather than a physical design statement.

Key Information Stored

• GL_DEFAULT_ID — surrogate primary key and sole business-key candidate; uniquely identifies each AutoAccounting default record and is referenced by child segment rows.
• TYPE — the AutoAccounting type that determines which subledger event the rule governs (for example, transaction, receipt, adjustment, or freight account derivation).
• ORG_ID — the operating unit to which the rule applies, enabling multi-org (MOAC) separation of AutoAccounting configurations across business units.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield (DFF) columns. In this table they carry any client-defined context information that qualifies or extends the AutoAccounting rule.
• CREATION_DATE / CREATED_BY — audit columns capturing when and by which application user the rule was created.
• LAST_UPDATE_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN — audit columns recording the most recent modification and the login session responsible for it.

Notably, the actual source and segment values of each rule are not stored in this table's documented column list; they are held in the child table RA_ACCOUNT_DEFAULT_SEGMENTS, which links back through GL_DEFAULT_ID. RA_ACCOUNT_DEFAULTS_ALL therefore acts as the header or parent record for a given AutoAccounting definition.

Common Use Cases and Queries

Typical uses include auditing AutoAccounting configuration, comparing setups across operating units after a clone or upgrade, and migrating rules between instances. A common query joins the header to its segments to reconstruct complete rules:

• SELECT d.gl_default_id, d.type, d.org_id, s.* FROM ra_account_defaults_all d, ra_account_default_segments s WHERE d.gl_default_id = s.gl_default_id;
• Filtering by operating unit to verify that each org has a complete set of AutoAccounting types: SELECT type, org_id FROM ra_account_defaults_all WHERE org_id = :org_id;
• Identifying records changed since a cutoff for SOX or change-control reporting using LAST_UPDATE_DATE.
• Extracting DFF context values (ATTRIBUTE_CATEGORY, ATTRIBUTE1-15) for configuration documentation.

Related Objects

• RA_ACCOUNT_DEFAULT_SEGMENTS — the primary child table; joins on RA_ACCOUNT_DEFAULT_SEGMENTS.GL_DEFAULT_ID = RA_ACCOUNT_DEFAULTS_ALL.GL_DEFAULT_ID. This is the only documented foreign-key relationship and provides the segment derivation logic.
• AR AutoAccounting setup forms and the AutoAccounting Flexfield setup — the UI through which these rows are created and maintained.
• RA_CUST_TRX_TYPES_ALL and related Receivables transaction objects — consume the derived accounts at transaction entry time.
• GL_CODE_COMBINATIONS — the target chart of accounts against which generated account combinations are validated.
• AR_SUB LEDGER accounting / SLA events — the accounting program that reads AutoAccounting rules during subledger accounting.

Because the metadata documents only one FK relationship, RA_ACCOUNT_DEFAULT_SEGMENTS is the principal dependency; other integrations are functional rather than enforced by foreign keys.