Search Results ar_location_accounts




Overview
Explore in AI Chat

Overview

APPS.AR_LOCATION_VALUES_V is a Receivables (AR) view that joins location segment definitions with the accounting flexfield combinations assigned to those location values. It is the reporting-facing view that answers the business question "which accounts are associated with this location?" — making it the authoritative source for the ar_location_accounts search pattern. In Oracle E-Business Suite 12.1.1 and 12.2.2, the view exposes, on a single row, both the descriptive attributes of a location segment value (value, description, qualifier, parent) and the set of General Ledger code combinations used for tax, adjustment, discount, finance charge, and related accounting treatment for that location.

Because it is defined in the APPS schema, it inherits the standard EBS security model: responsibility-level access, MOAC filtering through the AR security profile, and the typical requirement to set the FND application context (ORG_ID or operating unit) before querying from a custom report or concurrent program.

Underlying Base Objects

The documented view is defined over two base objects:

The relationship between the two is an outer join on LOCATION_SEGMENT_ID:

ARLV.LOCATION_SEGMENT_ID = ARLVA.LOCATION_SEGMENT_ID(+)

In other words, the view returns every location segment value, whether or not an account assignment exists. Where no assignment exists, the ARLVA columns (including all CCIDs) come back as NULL. This outer-join behavior is significant for reporting: a simple inner-join query would silently drop unconfigured locations.

Key Columns

  • LOCATION_SEGMENT_ID — primary identifier of the location segment value; the join key between the two base objects.
  • LOCATION_SEGMENT_VALUE / LOCATION_SEGMENT_USER_VALUE — the segment value as stored and as presented to the user.
  • LOCATION_SEGMENT_DESCRIPTION / LOCATION_SEGMENT_QUALIFIER — descriptive text and the qualifier that drives which account fields apply.
  • LOCATION_STRUCTURE_ID / PARENT_SEGMENT_ID — the key flexfield structure and hierarchical parentage.
  • LOCATION_VALUE_ACCOUNT_ID — identifier of the account assignment row itself.
  • Accounting CCIDs, the core of the "location accounts" concept: TAX_ACCOUNT_CCID, INTERIM_TAX_CCID, ADJ_CCID, EDISC_CCID, UNEDISC_CCID, FINCHRG_CCID, and their non-recoverable tax counterparts ADJ_NON_REC_TAX_CCID, EDISC_NON_REC_TAX_CCID, UNEDISC_NON_REC_TAX_CCID, FINCHRG_NON_REC_TAX_CCID. Each is a foreign key to GL_CODE_COMBINATIONS.
  • ATTRIBUTE_CATEGORY / ATTRIBUTE1–15 — flexfield descriptive attributes inherited from the location value record.
  • WHO and concurrent program columns — audit and provenance information taken from AR_LOCATION_ACCOUNTS.

Common Use Cases and Queries

Typical uses include location-account reconciliation, Receivables tax setup review, migration or data-conversion validation, and custom inquiries that a form does not already provide. To display the account number rather than a raw CCID, join to GL_CODE_COMBINATIONS.

List locations with their tax and adjustment accounts:

SELECT l.LOCATION_SEGMENT_VALUE, l.LOCATION_SEGMENT_DESCRIPTION, gcc.CONCATENATED_SEGMENTS TAX_ACCOUNT
FROM APPS.AR_LOCATION_VALUES_V l, APPS.GL_CODE_COMBINATIONS_KFV gcc
WHERE l.TAX_ACCOUNT_CCID = gcc.CODE_COMBINATION_ID
AND l.TAX_ACCOUNT_CCID IS NOT NULL
ORDER BY l.LOCATION_SEGMENT_VALUE;

Identify location values with no account assignment (outer-join gaps):

SELECT LOCATION_SEGMENT_ID, LOCATION_SEGMENT_VALUE
FROM APPS.AR_LOCATION_VALUES_V
WHERE LOCATION_VALUE_ACCOUNT_ID IS NULL;

Audit recent account-assignment maintenance:

SELECT LOCATION_SEGMENT_VALUE, LAST_UPDATED_BY, LAST_UPDATE_DATE
FROM APPS.AR_LOCATION_VALUES_V
WHERE LAST_UPDATE_DATE >= SYSDATE - 30;

Before executing any of these, initialize the application context (for example via FND_GLOBAL.APPS_INITIALIZE or by running within the correct responsibility) so that MOAC and security policies return the intended operating unit's data.