Results for “child_value”

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

Overview

AR_LOC_ONE_LEVEL_V is a dictionary view owned by the APPS schema in Oracle E-Business Suite, classified under the Receivables (AR) product family. Its documented description in the ETRM repository carries the qualifier "(Release 10SC Only)", indicating that the view originated in an early Oracle Receivables release and has been retained in the data dictionary for backward compatibility. In EBS 12.1.1 and 12.2.2 the object remains VALID, but its functional scope is narrow and legacy in nature.

The view exposes a single-level projection of location segment values, presenting one row per location segment record rather than the hierarchical parent/child explosion associated with full location hierarchy reporting. It is therefore not a general-purpose location hierarchy view. Its principal role is to surface the descriptive attributes of individual segment values — including the segment value itself, its user-facing value, its qualifier, and its associated country code — for reporting, data conversion, and integration scenarios that need flat, denormalized access to Receivables location value data without joining to additional segment or structure definitions.

Underlying Base Objects

The view text is defined over a single referenced base object: AR_LOCATION_VALUES, which is itself documented in the ETRM metadata as a VIEW rather than a table. The SELECT statement aliases AR_LOCATION_VALUES as CHILD, and every column in the projection is drawn from that alias. There is no join, no filter predicate, and no aggregation. AR_LOC_ONE_LEVEL_V is therefore a thin column-renaming and column-subsetting wrapper over AR_LOCATION_VALUES: it does not add business logic, restrict rows, or introduce hierarchy resolution. This is significant for tuning and troubleshooting, because any query against AR_LOC_ONE_LEVEL_V resolves entirely to the underlying AR_LOCATION_VALUES view, and ultimately to the base location value tables beneath it. Because the definition is unqualified by a WHERE clause, the view exposes the full contents of AR_LOCATION_VALUES, including rows for all location structures.

Key Columns

• LOCATION_STRUCTURE_ID — Identifier of the location structure (geography or key flexfield structure) to which the segment value belongs. This is the primary grouping key when segment values must be partitioned by structure.
• CHILD_ID — Surrogate identifier of the child location segment record, sourced from CHILD.LOCATION_SEGMENT_ID. It uniquely identifies the segment value row within the structure.
• CHILD_VALUE — The internal, stored segment value from CHILD.LOCATION_SEGMENT_VALUE. This is the value used in foreign key relationships and stored data.
• CHILD_USER_VALUE — The user-facing or "flexfield" value from CHILD.LOCATION_SEGMENT_USER_VALUE, as displayed in the Receivables application.
• CHILD_QUALIFIER — The qualifier of the segment value, from CHILD.LOCATION_SEGMENT_QUALIFIER. This is the column most directly associated with the search term "child_qualifier". The qualifier distinguishes the semantic role of a segment value, such as country, state, province, city, or postal code, within the location structure.
• COUNTRY_CODE — The country code associated with the segment value row, taken directly from the base view without transformation.

Common Use Cases and Queries

Because the view is a flat projection, it is typically used for lookups, validation extracts, and diagnostic queries rather than for hierarchical traversal. A common pattern is to enumerate all segment values for a given structure with their qualifiers:

SELECT child_id, child_value, child_user_value, child_qualifier, country_code FROM apps.ar_loc_one_level_v WHERE location_structure_id = :structure_id ORDER BY child_qualifier, child_value;

A second pattern isolates values by qualifier, for example retrieving only country-level entries or only city-level entries for a conversion or interface program:

SELECT child_value, child_user_value, country_code FROM apps.ar_loc_one_level_v WHERE child_qualifier = :qualifier AND country_code = :country;

A third pattern maps internal values to user values for reconciliation between interface tables and application-displayed values:

SELECT child_value, child_user_value FROM apps.ar_loc_one_level_v WHERE location_structure_id = :structure_id;

Analysts should note that in current 12.1.1 and 12.2.2 environments, the reference and supported location hierarchy views are the preferred objects. AR_LOC_ONE_LEVEL_V should be treated as a legacy compatibility artifact, and any dependency on it should be reviewed before upgrades, since its retention reflects historical continuity rather than active development.