Results for “parent_segment_id”

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

Overview

AR_LOCATION_VALUES is a read-only view owned by the APPS schema and registered under the FND – Application Object Library product. Despite the "AR" prefix, which reflects the historical association with the Receivables location key flexfield, the object is catalogued under FND because its definition depends on Application Object Library flexfield metadata tables. The view is marked VALID and is present in both Oracle EBS 12.1.1 and 12.2.2. Its underlying base objects are unchanged between the two releases, which makes it a stable query surface for reporting.

Functionally, the view presents the value set of a location key flexfield. Each row describes one geography record that participates in a parent-child relationship structure and that satisfies the segment attribute configuration for the RLOC flexfield. It is used primarily for validation and lookup within location flexfield definitions rather than as a module-specific transactional object.

Underlying Base Objects

AR_LOCATION_VALUES is defined over four synonym-referenced base objects:

• HZ_GEOGRAPHIES — the master geography records, aliased GEO. This is the driver table that supplies segment values, descriptions, and audit columns.
• HZ_RELATIONSHIPS — the parent-child relationships between geographies, aliased REL, with RELATIONSHIP_CODE of 'CHILD_OF'.
• FND_SEGMENT_ATTRIBUTE_VALUES — referenced twice (ATTR_CHILD and ATTR_PARENT) to determine which segments are enabled for the RLOC flexfield.
• FND_ID_FLEX_SEGMENTS — referenced twice (SEG_CHILD and SEG_PARENT) to resolve the structure number and segment columns.

Joins are constrained to application_id = 222 and ID_FLEX_CODE = 'RLOC', so only Receivables location flexfield segments qualify. Geography records are further restricted to GEOGRAPHY_USE = 'MASTER_REF' and RELATIONSHIP_TYPE = 'MASTER_REF'.

Key Columns

• LOCATION_SEGMENT_ID — GEOGRAPHY_ID, the unique identifier of the geography record.
• LOCATION_STRUCTURE_ID — ID_FLEX_NUM, identifying the flexfield structure the segment belongs to.
• LOCATION_SEGMENT_QUALIFIER — GEOGRAPHY_TYPE, indicating the geography level (e.g., country, state, city).
• LOCATION_SEGMENT_VALUE and LOCATION_SEGMENT_DESCRIPTION — both mapped to GEOGRAPHY_NAME.
• LOCATION_SEGMENT_USER_VALUE — also GEOGRAPHY_NAME, supplied for flexfield value-set compatibility.
• PARENT_SEGMENT_ID — REL.OBJECT_ID, the parent geography in the hierarchy.
• COUNTRY_CODE — GEO.COUNTRY_CODE from the geography record.
• Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, plus REQUEST_ID, PROGRAM_APPLICATION_ID, and PROGRAM_ID.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield columns carried forward from HZ_GEOGRAPHIES.

PROGRAM_UPDATE_DATE is exposed as a literal NULL and carries no data.

Common Use Cases and Queries

The view is typically queried to validate geography values, to build reporting extracts of the location hierarchy, or to reconcile geography data against flexfield configuration. A representative query retrieves the enabled hierarchy for a structure:

• SELECT location_segment_id, location_segment_value, location_segment_qualifier FROM ar_location_values WHERE location_structure_id = :structure_id ORDER BY parent_segment_id NULLS FIRST;
• SELECT child.location_segment_value, parent.location_segment_value parent_value FROM ar_location_values child, ar_location_values parent WHERE child.parent_segment_id = parent.location_segment_id;
• SELECT country_code, COUNT(*) FROM ar_location_values GROUP BY country_code;

Because the definition relies on HZ tables, queries return one row per enabled geography segment; joins to top-level geographies must account for the MASTER_REF restrictions applied internally.