Search Results tc_hrchy_version_id




Overview
Explore in AI Chat

Overview

APPS.HRIBV_TRNCNTR_HRCHY_ROLLUP is a reporting view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 data model, owned by the APPS schema and registered under FND Design Data as HRI.HRIBV_TRNCNTR_HRCHY_ROLLUP. The object is documented as VALID in ETRM. Its name indicates that it presents a rolled-up hierarchy of training centers (TRNCNTR), resolving a hierarchical organization structure into parent and child training center relationships. In practice, the view supplies a flattened, denormalized representation of training center hierarchy members together with their hierarchy version validity windows, which makes it suitable for reporting and downstream integration rather than for transactional processing.

Oracle explicitly marks the object with "Oracle Internal Use Only" and warns that the Corporation does not support access to applications data through it except from standard Oracle Applications programs. Any use in custom reporting should therefore be treated as a read-only convenience layer over supported base tables, subject to change between point releases.

Underlying Base Objects

According to the documented dependency metadata, HRIBV_TRNCNTR_HRCHY_ROLLUP references APPS.HRI_OR, and the underlying documented objects include HRI_ORG_HRCHY_SUMMARY (SYNONYM), HR_ALL_ORGANIZATION_UNITS_TL (SYNONYM), HR_BIS (PACKAGE), HR_GENERAL (PACKAGE), HR_ORGANIZATION_INFORMATION (SYNONYM), OTA_GENERAL (PACKAGE), PER_ORGANIZATION_STRUCTURES (SYNONYM), and PER_ORG_STRUCTURE_VERSIONS (SYNONYM). The hierarchy composition is driven by HR organization structures and their versions, while the training center identity is sourced from the translated organization unit table and organization information. The HRI_ORG_HRCHY_SUMMARY synonym carries the summarized hierarchy rollup, and the HR_BIS, HR_GENERAL, and OTA_GENERAL packages provide the business-group and training-specific logic used to derive the exposed columns.

Key Columns

The view exposes both descriptive hierarchy attributes and the surrogate identifiers needed for joins. Core descriptive columns include HIERARCHY_NAME, HRCHY_BUSINESS_GROUP_NAME, HRCHY_PRIMARY_FLAG, and HIERARCHY_VERSION. The columns most relevant to the searched term are HIERARCHY_VERSION_DATE_FROM and HIERARCHY_VERSION_DATE_TO, which define the effective date range of a given hierarchy version; HRCHY_VERSION_DATE_TO_NN provides a non-null variant useful for filtering open-ended versions. Training center resolution is provided by TRAINING_CENTER_NAME, TRAINING_CENTER_LEVEL, SUB_TRAINING_CENTER_NAME, SUB_TRAINING_CENTER_LEVEL, and SUB_RO_TRAINING_CENTER_LEVEL, which together describe the parent/child position of each training center within the rollup. Identifying columns include TC_HIERARCHY_ID, TC_HRCHY_BUSINESS_GROUP_ID, TC_HRCHY_VERSION_ID, TC_BUSINESS_GROUP_ID, TRAINING_CENTER_ID, and the corresponding SUB_ and SUB_RO_ identifiers.

Common Use Cases and Queries

Typical usage is to report the training center hierarchy as of a specific effective date, or to find the current version of a hierarchy. Because HIERARCHY_VERSION_DATE_FROM and HIERARCHY_VERSION_DATE_TO bound each version, the view is queried with a date predicate, for example:

  • Point-in-time version lookup: SELECT hierarchy_name, hierarchy_version, training_center_name FROM apps.hribv_trncnter_hrchy_rollup WHERE SYSDATE BETWEEN hierarchy_version_date_from AND NVL(hierarchy_version_date_to, SYSDATE);
  • Current active hierarchy: SELECT * FROM apps.hribv_trncnter_hrchy_rollup WHERE hierarchy_version_date_from <= SYSDATE AND (hierarchy_version_date_to IS NULL OR hierarchy_version_date_to >= SYSDATE);
  • Rollup by level for aggregation, grouping on training_center_level and sub_training_center_level while constraining on hierarchy_version_date_from to a reporting period.

Because the object is unsupported for direct customer access, implementations should prefer extracting results into a staging table and referencing documented base tables where possible.