Results for “bic_dimv_operating_units”

22 results




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

Overview

BIC_DIMV_OPERATING_UNITS is a dimension view owned by the APPS schema in Oracle E-Business Suite. It is catalogued under the BIC (Customer Intelligence) product, which carries an Obsolete status in the ETRM repository for releases 12.1.1 and 12.2.2. The view is documented as a dimension view for operating units, meaning its purpose is to expose a denormalised, reporting-friendly representation of the operating unit dimension rather than transactional data. Dimension views of this class are typically consumed by business intelligence layers, data warehouse extractions, and custom concurrent programs that need a stable, low-complexity source of organisational context to join against fact-style queries.

The view is defined with the READ ONLY clause and is marked VALID in the data dictionary. Its structure is intentionally minimal: it flattens the operating unit identity into a surrogate key, an identifier, and a descriptive name, and it prepends a synthetic "ALL" row so that aggregations across every operating unit can be produced without special-casing the absence of a filter.

Underlying Base Objects

According to the documented view text, BIC_DIMV_OPERATING_UNITS is defined over a single referenced base object: HR_OPERATING_UNITS, itself a view in the APPS schema rather than a base table. HR_OPERATING_UNITS is the standard Oracle HRMS security view that resolves operating units from the underlying HR_ALL_ORGANIZATION_UNITS and related organisation structures, applying business group and security profile logic. Because the dimension view sits on top of HR_OPERATING_UNITS, it inherits that view's security behaviour by default and does not add any additional filtering, joins, or transformations of its own.

The definition is a straightforward projection: SELECT 'ALL' ALL_FK, ORGANIZATION_ID ORG_ID, NAME ORG_NAME FROM HR_OPERATING_UNITS WITH READ ONLY. There are no WHERE clauses, GROUP BY operations, or outer joins, which makes the view inexpensive to query and easy to reason about for downstream consumers.

Key Columns

  • ALL_FK — A literal character value of 'ALL' repeated on every row. This serves as a constant foreign key that allows a dimension-aware query to join unconditionally against an "all values" placeholder, simplifying the construction of aggregate reports that must not be restricted to a single operating unit.
  • ORG_ID — The operating unit identifier, sourced from ORGANIZATION_ID in HR_OPERATING_UNITS. This is the value conventionally used to filter transactional data by operating unit and to join to fact tables or other views keyed on ORG_ID.
  • ORG_NAME — The operating unit name, sourced from the NAME column of HR_OPERATING_UNITS. It provides the human-readable label used in report headings, list-of-values displays, and pivot layouts.

Common Use Cases and Queries

The principal use case is supplying organisational context to reporting queries, either as a lookup for display names or as a driving list of operating units. A typical name-resolution query joins the dimension to a transactional source:

  • SELECT d.ORG_NAME, COUNT(*) FROM BIC_DIMV_OPERATING_UNITS d, MY_FACT_TAB f WHERE f.ORG_ID = d.ORG_ID GROUP BY d.ORG_NAME;
  • SELECT ORG_ID, ORG_NAME FROM BIC_DIMV_OPERATING_UNITS ORDER BY ORG_NAME;
  • SELECT ORG_ID, ORG_NAME FROM BIC_DIMV_OPERATING_UNITS WHERE ALL_FK = 'ALL';

Because the BIC product is flagged Obsolete, new development should treat this view as a legacy artefact. Where equivalent functionality is required on current releases, the recommended approach is to query HR_OPERATING_UNITS directly or to use the supported operating unit views supplied by the relevant application module. Existing customisations that reference BIC_DIMV_OPERATING_UNITS should be inventoried prior to upgrade, since obsolete objects are not guaranteed to be carried forward. Note also that results are subject to the security profile of the connecting user, as the view performs no independent security filtering.