Results for “child_id”

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

Overview

The OE_INLINE_ONE_LEVEL_V view is a dictionary object owned by the APPS schema within Oracle Order Management (ONT). It is a single-level projection over the location value data used by the Order Management "Add Customer" functionality. The view is documented as used in the Add Customer flow and is defined exclusively over the AR_LOCATION_VALUES object. Its role is to expose a flattened, one-level representation of location segment values so that order entry and customer setup logic can resolve, validate, and default address and location segment data without traversing the full multi-level location hierarchy.

The name "INLINE_ONE_LEVEL" reflects its design intent: rather than returning an entire hierarchical tree of location segments, the view surfaces each location segment value together with its owning location structure in a single row. For reporting and integration purposes this makes the view convenient where a flat join is required, avoiding recursive hierarchy expansion while still retaining the relationship between a segment value and the structure to which it belongs. The view is registered as VALID in the EBS data dictionary for both 12.1.1 and 12.2.2.

Underlying Base Objects

Per the documented metadata, OE_INLINE_ONE_LEVEL_V is defined over a single referenced base object: AR_LOCATION_VALUES, which is itself documented as a view rather than a physical table. The AR_LOCATION_VALUES object supplies the location structure identifier, the location segment identifier, the segment value and user-facing value, the segment qualifier, and the country code used by the view.

The defining query aliases the source as CHILD, indicating that the view extracts the child (that is, the lower-level segment) side of the location value relationship. Each row therefore corresponds to a single location segment value, keyed by its owning structure and segment identifiers. The relationship to AR_LOCATION_VALUES is a direct pass-through: the view does not aggregate, filter by a hierarchy level beyond the single-level projection, or combine multiple base objects. Because the base object is a view, the ultimate lineage resolves through the location value model maintained by Oracle Receivables and shared with Order Management.

Key Columns

• LOCATION_STRUCTURE_ID — Identifies the location structure (the key flexfield structure) to which the segment value belongs. This is the primary grouping key that ties a child value to its owning geographical or address structure.
• CHILD_ID — The location segment identifier, mapping to CHILD.LOCATION_SEGMENT_ID. It uniquely identifies the individual segment value row within the structure.
• CHILD_VALUE — The stored location segment value (CHILD.LOCATION_SEGMENT_VALUE). This is the internal, flexfield value used for validation and joins.
• CHILD_USER_VALUE — The user-facing (display) value for the segment, corresponding to CHILD.LOCATION_SEGMENT_USER_VALUE. Reports typically present this rather than the internal value.
• CHILD_QUALIFIER — The segment qualifier, indicating the semantic role of the segment (for example country, region, or city qualifier).
• CHILD_COUNTRY_CODE — The country code associated with the segment value, used for address formatting and country-specific validation.

Common Use Cases and Queries

This view is most often joined to location or customer tables when a flat list of segment values is required for a given structure, such as when populating address validation lists or building customer-facing address reports. A representative query returning the user-facing values for a specific structure is shown below.

SELECT child_id, location_structure_id, child_value, child_user_value, child_qualifier, child_country_code FROM apps.oe_inline_one_level_v WHERE location_structure_id = :p_structure_id ORDER BY child_user_value;

For country-specific lookups, the country code column supports filtering:

SELECT child_value, child_user_value FROM apps.oe_inline_one_level_v WHERE child_country_code = 'US' AND child_qualifier = :p_qualifier;

Because the view exposes only one hierarchical level and no parentage columns, it is best suited to validation and display scenarios in the Add Customer flow rather than to full address hierarchy reconstruction. Where hierarchical navigation is required, callers should resolve the parent-child relationships from the underlying location value structures. In integration contexts, the view serves as a lightweight, stable interface for retrieving segment values keyed by structure, avoiding direct dependency on the internal definition of AR_LOCATION_VALUES.