Results for “attr_parent”

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

Overview

OE_INLINE_TWO_LEVEL_V is an APPS-owned, VALID database view in Oracle E-Business Suite Release 12.1.1 and 12.2.2, registered under the Order Management (ONT) product family. Its documented purpose is support of the "Add Customer" flow, where order entry users create or extend customer and location information inline without navigating away from the order. The view is defined over the AR_LOCATION_VALUES table and exposes a self-joined, two-level hierarchy of location segment values: each row pairs a child location segment with its immediate parent segment within the same location structure.

Because it presents both child and parent attributes side by side, the view is well suited to hierarchical lookups and reporting where the parent value must be resolved alongside the child. In the context of a search for "child_value," the column CHILD_VALUE is the operative field; it carries the location segment value at the lower level of the pairing, with PARENT_VALUE supplying the corresponding upper-level value.

Underlying Base Objects

The view text joins AR_LOCATION_VALUES to itself. The CHILD alias supplies the lower-level segment, and the PARENT alias supplies the upper-level segment. The join predicates are CHILD.PARENT_SEGMENT_ID = PARENT.LOCATION_SEGMENT_ID and CHILD.LOCATION_STRUCTURE_ID = PARENT.LOCATION_STRUCTURE_ID. The second predicate ensures that child and parent rows belong to the same location structure, preventing cross-structure matches.

The 12.2.2 ETRM metadata records the following referenced base objects for the documented definition: FND_ID_FLEX_SEGMENTS (SYNONYM), FND_SEGMENT_ATTRIBUTE_VALUES (SYNONYM), HZ_GEOGRAPHIES (SYNONYM), and HZ_RELATIONSHIPS (SYNONYM). These reflect the location flexfield and geography context in which location segment values are maintained, and they should be treated as the authoritative dependency list for the documented release.

Key Columns

• LOCATION_STRUCTURE_ID — Identifies the location structure to which both child and parent segments belong. It is the principal correlation key for the row.
• CHILD_ID — The LOCATION_SEGMENT_ID of the child (lower-level) segment.
• CHILD_VALUE — The stored location segment value of the child. This is the column retrieved in "child_value" searches.
• CHILD_USER_VALUE — The user-facing (translated or displayed) value corresponding to the child segment.
• CHILD_QUALIFIER — The segment qualifier associated with the child value.
• CHILD_COUNTRY_CODE — Country code carried on the child segment row.
• PARENT_ID — The LOCATION_SEGMENT_ID of the parent (upper-level) segment.
• PARENT_VALUE — The stored value of the parent segment.
• PARENT_USER_VALUE — The user-facing value of the parent segment.
• PARENT_LOC_STRUCT_ID — The location structure identifier as sourced from the parent row; it mirrors LOCATION_STRUCTURE_ID under the join conditions.

Common Use Cases and Queries

Typical uses include resolving the parent value for a given child location segment, validating that a child value exists beneath an expected parent, and driving inline list-of-values behaviour during order entry and customer creation.

To retrieve full child-to-parent pairs for a structure:

• SELECT location_structure_id, child_id, child_value, parent_id, parent_value FROM oe_inline_two_level_v WHERE location_structure_id = :structure_id;

To locate a specific child value and its parent:

• SELECT child_value, parent_value FROM oe_inline_two_level_v WHERE child_value = :child_value;

To list all children under a known parent value:

• SELECT child_id, child_value FROM oe_inline_two_level_v WHERE parent_value = :parent_value ORDER BY child_value;

Queries should filter on LOCATION_STRUCTURE_ID wherever the structure is known, since the view does not otherwise restrict scope, and joins to FND_ID_FLEX_SEGMENTS or HZ_GEOGRAPHIES should be added only when descriptive flexfield or geography attributes are required.