Search Results location_id_segment_10

Overview

AR_LOCATION_COMBINATIONS is an APPS-owned database view in Oracle E-Business Suite (validated against 12.1.1 and 12.2.2). Although the name suggests an Accounts Receivable artifact, the object is catalogued under the FND – Application Object Library product and is registered as VALID in the ETRM repository. Its purpose is to expose the individual geographic segments that make up a location identifier in a flat, one-row-per-location structure, rather than requiring the caller to parse the raw geography identifier path maintained in the Oracle geography model.

In the Oracle geography hierarchy, a location is identified by a hierarchical GEO_ID_PATH string in which levels are delimited by pipe characters ("|") and prefixed by a leading delimiter. Consumers that need to decompose such a path — for reporting, integration, or correlation with a flexfield-style concatenated identifier — would otherwise have to implement repeated SUBSTR/INSTR logic. AR_LOCATION_COMBINATIONS encapsulates this normalization by translating the hierarchy into discrete numbered location identifiers, which makes it useful where a location is treated as a logical combination of geography levels.

Underlying Base Objects

The view's documented metadata shows it is defined over the following synonyms in the APPS schema:

• HZ_HIERARCHY_NODES — the primary source of the location identifier and its GEO_ID_PATH.
• HZ_GEOGRAPHIES — provides the geography identifiers referenced within the path.
• HZ_GEO_STRUCTURE_LEVELS — defines the levels (LEVEL1 through LEVEL5) against which the DECODE/SIGN logic tests path depth.
• HZ_GEO_NAME_REFERENCES — supplies geography name references associated with the underlying nodes.

The view text selects G.LOCATION_ID LOCATION_ID and then derives LOCATION_ID_SEGMENT_1 through LOCATION_ID_SEGMENT_5 by stripping the leading delimiter from GEO_ID_PATH, converting pipe delimiters to periods, and extracting the substring between successive periods. The DECODE(SIGN(V.LEVEL1-n)…) constructs suppress segments that do not exist at the current hierarchy depth, so a location at level 3 returns values in segments 1–3 and NULL in segments 4–5. This is a pure read-only projection; no DML is possible against the view, and it inherits security from the underlying HZ geography hierarchy.

Key Columns

• LOCATION_ID — the location identifier (G.LOCATION_ID) for the row.
• LOCATION_ID_SEGMENT_1 — the first geography level extracted from the path; always available for any valid location.
• LOCATION_ID_SEGMENT_2 — the second level; NULL when the hierarchy does not extend to level 2.
• LOCATION_ID_SEGMENT_3, _4, _5 — successive levels, each conditionally populated based on the depth checks against LEVEL1-3, LEVEL1-4, and LEVEL1-5.

Collectively the segment columns represent the "combination" of geography hierarchy nodes that defines the location, mirroring the concatenated-key concept used elsewhere in EBS.

Common Use Cases and Queries

Typical applications include validating that location identifiers respect the geography hierarchy, exporting locations to downstream systems in flattened form, and reconciling EBS locations against external geographic reference data.

To inspect the individual segments for a specific location:

• SELECT location_id, location_id_segment_1, location_id_segment_2, location_id_segment_3, location_id_segment_4, location_id_segment_5 FROM apps.ar_location_combinations WHERE location_id = :p_location_id;

To find all locations whose third segment is populated:

• SELECT location_id FROM apps.ar_location_combinations WHERE location_id_segment_3 IS NOT NULL;

To join back to geography names for presentation:

• Join the view to HZ_GEOGRAPHIES on each segment column, or to HZ_GEO_STRUCTURE_LEVELS for level context, to render a readable location description. Because AR_LOCATION_COMBINATIONS is a view over seeded HZ tables, query performance depends on indexing on the underlying HZ_HIERARCHY_NODES and HZ_GEOGRAPHIES tables; no independent storage exists for the view itself.