Results for “parent_user_value”

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

Overview

AR_LOC_TWO_LEVEL_V is a read-only view in the APPS schema within Oracle E-Business Suite Receivables (AR). Its description is annotated "(Release 10SC Only)," indicating that it originated in the 10SC release cycle and was retained for backward compatibility in later releases, including 12.1.1 and 12.2.2, where it continues to be reported as VALID. The view presents a self-joined, two-level hierarchy of Receivables location flexfield segment values, pairing each child segment value with its immediate parent segment value. This flattened parent/child presentation is used primarily in reporting and integration contexts, where a denormalized view of the location hierarchy is more convenient than traversing AR_LOCATION_VALUES recursively.

The view exposes the child's identifiers and descriptive values alongside the corresponding parent identifiers and values, all scoped to a single location structure. It is not a transactional view; it is a reference structure used to resolve hierarchy relationships in the Receivables location key flexfield.

Underlying Base Objects

The documented base object is AR_LOCATION_VALUES, itself a view in the APPS schema. AR_LOC_TWO_LEVEL_V is constructed by joining AR_LOCATION_VALUES to itself, aliasing one instance as CHILD and the other as PARENT. The join condition requires two matching predicates: CHILD.PARENT_SEGMENT_ID must equal PARENT.LOCATION_SEGMENT_ID, and CHILD.LOCATION_STRUCTURE_ID must equal PARENT.LOCATION_STRUCTURE_ID. The second predicate ensures the parent and child rows belong to the same location structure, preventing cross-structure contamination. Because the view references AR_LOCATION_VALUES rather than the underlying physical segment table directly, any change to the definition of AR_LOCATION_VALUES propagates to AR_LOC_TWO_LEVEL_V. The view contains no aggregate functions, DISTINCT clause, or filter predicates beyond the join conditions, so it returns the full set of two-level parent/child pairs present in the underlying location values.

Key Columns

• LOCATION_STRUCTURE_ID — Identifies the location flexfield structure to which the pair belongs; inherited from the child row and equal to the parent row's structure.
• CHILD_ID — The LOCATION_SEGMENT_ID of the child segment value.
• CHILD_VALUE — The stored segment value of the child, matching the search term "child_value."
• CHILD_USER_VALUE — The user-facing (translated or descriptive) value for the child segment.
• CHILD_QUALIFIER — The qualifier assigned to the child segment value.
• PARENT_ID — The LOCATION_SEGMENT_ID of the parent segment value.
• PARENT_VALUE — The stored segment value of the parent.
• PARENT_USER_VALUE — The user-facing value for the parent segment.
• COUNTRY_CODE — The country code associated with the child location value, useful for country-specific location hierarchies.

Common Use Cases and Queries

Typical uses include reporting on location hierarchies, validating that child locations are attached to the correct parent, and exporting two-level hierarchies to external systems. A basic query retrieving child and parent values for a given structure is:

• SELECT child_value, child_user_value, parent_value, parent_user_value FROM apps.ar_loc_two_level_v WHERE location_structure_id = :structure_id ORDER BY child_value;
• SELECT child_value, parent_value FROM apps.ar_loc_two_level_v WHERE country_code = 'US';
• SELECT COUNT(*) FROM apps.ar_loc_two_level_v WHERE location_structure_id = :structure_id;

Because the object was documented as Release 10SC Only, implementers on 12.1.1 and 12.2.2 should treat it as a legacy compatibility view and confirm its continued validity in their specific instance before building dependent logic, preferring current API or base-table access patterns where an equivalent supported structure exists.