Results for “ar_location_accounts_u2”

10 results




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

Overview

AR.AR_LOCATION_ACCOUNTS_ALL is a transactional configuration table in the Oracle Receivables (AR) schema that stores tax accounting information for records in AR_LOCATION_VALUES that carry a Tax Account location segment qualifier. In Oracle EBS 12.1.1 and 12.2.2, this table drives the automatic derivation of accounting flexfield combinations (CCIDs) used when Receivables posts tax-related, discount-related, finance charge, and adjustment activity to the General Ledger. It allows a single tax location to resolve to multiple, distinct accounting accounts depending on the nature of the transaction line being processed, rather than forcing all tax activity through one account.

From a dimensional modeling perspective, the mined foreign key structure suggests a satellite-leaning classification: the table extends the AR_LOCATION_VALUES dimension with a set of descriptive accounting attributes. Understood this way, LOCATION_SEGMENT_ID functions as the link back to the parent location record, while LOCATION_VALUE_ACCOUNT_ID serves as the surrogate primary key for the satellite row. Its status is documented as VALID, with FND Design Data registered as AR.AR_LOCATION_ACCOUNTS_ALL. Storage resides in the APPS_TS_TX_DATA tablespace with PCT FREE 10; indexes are held separately in APPS_TS_TX_IDX, following standard Oracle Applications segregation of data and index storage.

Key Information Stored

The table contains 38 documented columns. The most operationally significant are listed below.

The business-key candidate is the composite unique index AR_LOCATION_ACCOUNTS_U2 over (LOCATION_SEGMENT_ID, ORG_ID), which guarantees exactly one accounting configuration row per location segment per operating unit.

Common Use Cases and Queries

Typical scenarios include validating that every tax-qualified location segment has a complete accounting configuration, diagnosing AutoAccounting derivation failures, and reporting the chart-of-accounts mapping used for tax and discount postings.

  • Detecting missing configurations: query AR_LOCATION_VALUES LEFT JOIN AR_LOCATION_ACCOUNTS_ALL on LOCATION_SEGMENT_ID where the account row is NULL.
  • Resolving the tax account for postings: SELECT TAX_ACCOUNT_CCID FROM AR_LOCATION_ACCOUNTS_ALL WHERE LOCATION_SEGMENT_ID = :p_segment_id AND ORG_ID = :p_org_id.
  • Joining to GL_CODE_COMBINATIONS via any *_CCID column to display the concatenated accounting flexfield for reporting.
  • Auditing recent changes using LAST_UPDATE_DATE and PROGRAM_ID for concurrent program traceability.

Related Objects

  • AR.AR_LOCATION_VALUES — parent location table; join on AR_LOCATION_ACCOUNTS_ALL.LOCATION_SEGMENT_ID = AR_LOCATION_VALUES.LOCATION_SEGMENT_ID.
  • GL.GL_CODE_COMBINATIONS — resolves each *_CCID into a valid account combination.
  • AR.AR_LOCATION_ACCOUNTS_ALL (DTF/Define Tax Accounts form) — the primary maintenance UI; AutoAccounting rules consume the stored CCIDs at posting time.
  • AR.AR_TAX_ACCOUNTS / tax setup views — read these mappings when deriving tax lines.
  • FND Operating Unit (FND_ORG_ACCESS / ORG_ID) — enforces multi-org data isolation on ORG_ID.