Search Results location_segment_value




Overview
Explore in AI Chat

Overview

The AR_LOCATION_VALUES_OLD table is a core data structure within Oracle E-Business Suite Receivables (AR) that defines the hierarchical values for the Sales Tax Location flexfield. This flexfield is critical for configuring and determining tax jurisdictions based on geographic segmentation, such as country, state, county, and city. The table's primary role is to store the valid values, their descriptions, and the hierarchical relationships between them, enabling the system to accurately assign tax locations to transactions and parties. Its designation as "_OLD" suggests it is a legacy table, likely maintained for backward compatibility, with newer transactional data potentially referencing it for historical tax determination logic.

Key Information Stored

The table's structure centers on storing flexfield segment values and their relationships. Key columns include LOCATION_SEGMENT_ID, a unique identifier for each value; LOCATION_SEGMENT_QUALIFIER and LOCATION_SEGMENT_VALUE, which together define the specific code for a segment level (e.g., 'STATE' and 'CA'); and PARENT_SEGMENT_ID, which establishes the hierarchical parent-child relationship (e.g., a city's parent is a county). The TAX_ACCOUNT_CCID column links a specific location value to a General Ledger (GL) account combination for tax accounting purposes. The presence of multiple unique keys (UK1, UK2, UK4) enforces data integrity for the various ways the application queries this hierarchical data.

Common Use Cases and Queries

A primary use case is tracing the tax jurisdiction hierarchy for a given transaction line or customer site. For reporting, it is often joined to transaction lines or tax setup tables to provide descriptive location information. A common query pattern involves recursive SQL or hierarchical queries to build a complete location string from the segmented values.

  • Sample Query for Location Hierarchy:
    SELECT lv.segment_qualifier, lv.segment_value
    FROM ar_location_values_old lv
    START WITH lv.location_segment_id = :p_segment_id
    CONNECT BY PRIOR lv.parent_segment_id = lv.location_segment_id;
  • Joining to Transaction Data:
    SELECT rctl.line_number, lv.segment_qualifier, lv.segment_value
    FROM ra_customer_trx_lines_all rctl,
    ar_location_values_old lv
    WHERE rctl.location_segment_id = lv.location_segment_id
    AND rctl.customer_trx_id = :p_trx_id;

Related Objects

The table maintains integral relationships with several core and localized objects, as evidenced by its foreign key constraints. It is directly referenced by transaction lines and specialized tax tables.

  • RA_CUSTOMER_TRX_LINES_ALL: Links via LOCATION_SEGMENT_ID to store the tax location for an invoice line.
  • GL_CODE_COMBINATIONS: Linked via TAX_ACCOUNT_CCID to assign a specific accounting flexfield combination for tax liability.
  • Self-Referential: The PARENT_SEGMENT_ID column is a foreign key to the table's own LOCATION_SEGMENT_ID, defining the value hierarchy.
  • Localization Tables: Heavily referenced by country-specific tax tables, including JL_BR_AR_TX_LOCN_ALL and the user-searched object JL_ZZ_AR_TX_LOCN_ALL, via the SHIP_TO_SEGMENT_ID column for Brazil and other regional tax calculations.