Results for “as_terr_rollups_immediate_v”

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

Overview

The view AS_TERR_ROLLUPS_IMMEDIATE_V is a Sales Foundation (AS) object in Oracle E-Business Suite that exposes the immediate, one-level territory rollup relationships defined in the Territory Manager data model. Its documented purpose is to present "territory rollups," meaning the parent-child associations by which a given territory reports upward into a higher-level (rollup) territory. In the context of Oracle EBS 12.1.1 and 12.2.2, this view serves reporting and integration consumers that require a flattened, query-friendly representation of the territory hierarchy without having to navigate the base value tables and seeded qualifier setup directly.

Within the Territory Manager subsystem, territories are organized into hierarchical structures to support sales crediting, quota assignment, and analytics. The "immediate" qualifier in the view name indicates that the view returns a single-step relationship — each row maps one territory to the territory immediately above it in the rollup hierarchy — rather than the fully transitive, expanded hierarchy. This distinction is important for consumers such as Power BI dashboards (for example, the Milford Rollstock operational reporting referenced in users' search patterns), where understanding direct parent linkage is often the prerequisite for building recursively expanded hierarchies inside the BI layer.

Underlying Base Objects

The documented view text defines AS_TERR_ROLLUPS_IMMEDIATE_V over two base objects:

• AS_TERRITORY_VALUES (aliased TERRVAL) — the table storing territory qualifier values, including the territory identifier and its associated seeded qualifier identifier.
• AS_TERR_SEED_QUALIFIERS_VL (aliased SEEDQUAL) — the seeded qualifiers view/lookup, filtered here to the TERRITORY_NAME qualifier code.

The join is performed on TERRVAL.SEEDED_QUALIFIER_ID = SEEDQUAL.SEEDED_QUALIFIER_ID, constrained by SEEDQUAL.QUALIFIER_CODE = 'TERRITORY_NAME'. As documented, the object is noted as "Not implemented in this database," and no owner or additional referenced base objects are listed in the ETRM metadata for 12.2.2. This suggests the object may be absent or unused in certain environments, and implementers should verify its existence before relying on it in custom code or BI extracts.

Key Columns

• ROW_ID — Exposed from TERRVAL.ROWID; provides a unique physical row identifier for the underlying territory value record. It is commonly used as a surrogate key in extraction queries.
• TERRITORY_ID — The child territory identifier being rolled up; identifies which territory holds the immediate parent relationship.
• ROLLUP_TERRITORY_ID — The immediate parent (rollup) territory identifier into which the child territory reports.

Together these columns allow a consumer to reconstruct the direct territory hierarchy: joining TERRITORY_ID to ROLLUP_TERRITORY_ID across rows yields the one-level rollup chain.

Common Use Cases and Queries

Typical scenarios include building territory hierarchies for sales dashboards, validating rollup configuration, and feeding BI semantic models that require parent-child mappings. A basic query is:

• SELECT ROW_ID, TERRITORY_ID, ROLLUP_TERRITORY_ID FROM AS_TERR_ROLLUPS_IMMEDIATE_V;
• To resolve the child territory's name, join TERRITORY_ID to the territory name/translation tables (for example, via AS_TERRITORIES_VL) and similarly resolve the parent through ROLLUP_TERRITORY_ID.
• For BI recursion (as with the Milford Rollstock Power BI model), load the view into a staging table and apply iterative or recursive joins in the reporting tool to expand from immediate to full rollup ancestry.

Because the view is documented as not implemented in a specific database and lists no additional base objects, validation against the target instance and review of the object's actual DDL in ALL_VIEWS/DBA_VIEWS are recommended before production use.