Results for “ar_location_values_uk1”

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

Overview

AR_LOCATION_VALUES is an Oracle Receivables (AR) reference table that defines the location values and descriptions associated with the Sales Tax Location flexfield. Each row represents a discrete segment value used by the location flexfield structure, allowing Receivables to resolve ship-to, bill-to, and tax jurisdiction references consistently across transactions. The table functions as a central registry of location segment values, storing both the qualifier context and the actual segment value, along with parent-child hierarchical relationships between segments.

The ETRM metadata notes that this object is "Not implemented in this database," meaning no physical instance was detected in the source environment at the time of extraction. It should therefore be treated as a definitional reference rather than a confirmed live artifact. Under the heuristic Data Vault classification provided in the metadata, AR_LOCATION_VALUES is described as hub-leaning. In Data Vault modeling terms, this suggests the table behaves primarily as a hub — a stable, uniquely-keyed list of business entities (location segment values) — with a self-referencing parent relationship that could be modeled as a recursive link. The presence of descriptive columns alongside business keys is a typical indicator of hub-plus-satellite designs.

Key Information Stored

The documented metadata identifies the primary structural columns and unique keys that define the table's grain:

• LOCATION_SEGMENT_QUALIFIER — identifies the segment type or qualifier context for the value, distinguishing which part of the location flexfield the value belongs to.
• LOCATION_SEGMENT_VALUE — the actual business value of the segment as used in the Sales Tax Location flexfield.
• LOCATION_SEGMENT_ID — the surrogate identifier for the location segment, forming part of the UK2 and UK4 unique keys.
• PARENT_SEGMENT_ID — a self-referencing foreign key pointing back to AR_LOCATION_VALUES, establishing hierarchical relationships between location segments.
• TAX_ACCOUNT_CCID — foreign key to GL_CODE_COMBINATIONS, associating a tax accounting code combination with the location segment.

Three unique keys are documented: AR_LOCATION_VALUES_UK1 (LOCATION_SEGMENT_QUALIFIER, LOCATION_SEGMENT_VALUE, PARENT_SEGMENT_ID); AR_LOCATION_VALUES_UK2 (LOCATION_SEGMENT_QUALIFIER, LOCATION_SEGMENT_VALUE, LOCATION_SEGMENT_ID); and AR_LOCATION_VALUES_UK4 (LOCATION_SEGMENT_ID). The UK4 key establishes LOCATION_SEGMENT_ID as a strong surrogate candidate, while UK1 and UK2 represent business-key combinations. The user's search term, ar_location_values_uk1, refers directly to the first of these unique indexes.

Common Use Cases and Queries

Typical use cases revolve around tax location setup validation, hierarchy traversal, and diagnostic reporting during Receivables implementation or support.

• Retrieving location values by qualifier: SELECT location_segment_value, location_segment_id FROM ar_location_values WHERE location_segment_qualifier = :qualifier;
• Traversing parent-child hierarchies: self-joins on PARENT_SEGMENT_ID resolve multi-level location structures for reporting or migration validation.
• Duplicate detection: querying against UK1 to confirm that no two rows share the same qualifier, value, and parent combination before scripted inserts.
• Tax account reconciliation: joining TAX_ACCOUNT_CCID to GL_CODE_COMBINATIONS to verify that every location value maps to a valid accounting combination.
• Impact analysis: identifying all location segments referenced by AR_LOCATION_RATES before modifying or retiring a value.

Related Objects

• AR_LOCATION_RATES — references AR_LOCATION_VALUES via LOCATION_SEGMENT_ID, linking tax rates to location segments.
• AR_LOCATION_VALUES (self) — the PARENT_SEGMENT_ID self-reference models the segment hierarchy.
• GL_CODE_COMBINATIONS — parent of TAX_ACCOUNT_CCID, supplying the accounting flexfield combination for tax postings.
• GR_DOCUMENT_RTK — references the composite of LOCATION_SEGMENT_QUALIFIER, LOCATION_SEGMENT_VALUE, and PARENT_SEGMENT_ID for right-to-know documentation.
• GR_ITEM_RIGHT_TO_KNOW — references the same composite key columns for item-level regulatory reporting.