Search Results ar_location_values_v




Overview

AR_LOCATION_VALUES_V is a Receivables (AR) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes location segment definitions and their associated accounting flexfield assignments, joining descriptive segment metadata to the account code combinations configured for each location. The view consolidates two underlying objects—AR_LOCATION_VALUES_OLD and AR_LOCATION_ACCOUNTS—into a single, denormalized read interface that reporting tools, concurrent programs, and integrations can query without navigating the parent/child relationship directly. Its principal value lies in surfacing the various Receivables account Code Combination IDs (CCIDs) mapped to a given location segment, including tax, adjustment, discount, and finance charge accounts.

The "V" suffix indicates a view, and the naming reflects its origin in location value setup used by the Receivables and Tax configuration. The view carries no separate description in the ETRM metadata but its SELECT text is fully documented, providing a precise picture of its derivation.

Underlying Base Objects

AR_LOCATION_VALUES_V is defined over two documented base objects, both exposed through synonyms:

  • AR_LOCATION_VALUES_OLD (aliased ARLV) — supplies location segment attributes such as segment identifier, user value, structure identifier, qualifier, description, parent segment, and the DFF attribute columns (ATTRIBUTE_CATEGORY through ATTRIBUTE15).
  • AR_LOCATION_ACCOUNTS (aliased ARLVA) — supplies the accounting CCIDs and audit columns.

The join is an outer join: ARLV.LOCATION_SEGMENT_ID = ARLVA.LOCATION_SEGMENT_ID(+). This means every location segment row survives even when no matching account row exists, with account-related columns returning NULL. The ROW_ID is derived from ARLV.ROWID, and the audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) are sourced from ARLVA.

Key Columns

Common Use Cases and Queries

The view is most frequently queried to inspect the accounting configuration attached to a Receivables location, particularly the tax and finance charge mappings. The user search term finchrg_non_rec_tax_ccid corresponds directly to the FINCHRG_NON_REC_TAX_CCID column, which reports the code combination used to record non-recoverable tax on finance charges. A representative query is:

  • SELECT location_segment_id, location_segment_user_value, finchrg_ccid, finchrg_non_rec_tax_ccid, adj_non_rec_tax_ccid FROM apps.ar_location_values_v WHERE finchrg_non_rec_tax_ccid IS NOT NULL;

Additional scenarios include auditing which location segments have missing account assignments (using the outer join's NULL rows), reconciling CCIDs against the accounting flexfield, and driving tax reporting extracts. Because the view carries Receivables audit columns, it also supports change-tracking queries filtered on LAST_UPDATE_DATE. Reports and interfaces targeting location-based tax and finance charge accounting should query this view rather than the base tables to inherit the resolved, fully joined column set.