Search Results ota_tp_measurement_types_v




Overview
Explore in AI Chat

Overview

The OTA_TP_MEASUREMENT_TYPES_V view is a reporting and integration object in the Oracle E-Business Suite Learning Management module (OTA), owned by the APPS schema. It is defined as a VALID database view in both Oracle EBS 12.1.1 and 12.2.2. Its role is to consolidate the configuration of Training Plan measurement types — the metrics used to capture planned versus actual training budget, cost, and delivery data — into a single, denormalized read interface.

The view joins the transaction table OTA_TP_MEASUREMENT_TYPES to lookup definitions and to the HR summary template framework, decoding internal codes into user-facing meanings. This makes it suitable for reporting, self-service pages, concurrent programs, and inbound/outbound interfaces that require human-readable measurement type definitions rather than raw coded values. The presence of a ROWID column and the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) confirms it is a standard EBS seeded view intended both for inquiry and, where the underlying synonym permits, for transactional access.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, the view references the following base objects: the OTA_TP_MEASUREMENT_TYPES synonym (which resolves to the APPS base table), the lookup view HR_LOOKUPS, and three HR Summary framework views — HR_SUMMARY_ITEM_TYPE, HR_SUMMARY_ITEM_TYPE_USAGE, and HR_SUMMARY_TEMPLATE. The package HR_API is also referenced as a dependent object.

The joins operate as follows. Two references to HR_LOOKUPS decode codes: one matches TP_MEASUREMENT_CODE against LOOKUP_TYPE = 'OTA_PLAN_MEASUREMENT_TYPE', and a second matches UNIT against LOOKUP_TYPE = 'UNITS'. The HR Summary views are joined with outer-join semantics — ITEM_TYPE_USAGE_ID links to HR_SUMMARY_ITEM_TYPE_USAGE, which in turn links to HR_SUMMARY_TEMPLATE via TEMPLATE_ID and to HR_SUMMARY_ITEM_TYPE via ITEM_TYPE_ID. This outer-join pattern means a measurement type is still returned even when it is not attached to a summary template or item type.

Key Columns

Common Use Cases and Queries

Because the user searched on reporting_sequence, the most frequent requirement is to list measurement types in their configured report order. A typical query is:

  • SELECT tp_measurement_code, measurement_name, unit_name, reporting_sequence FROM ota_tp_measurement_types_v WHERE business_group_id = :p_bg_id ORDER BY reporting_sequence;
  • Reporting which measurement types are budget-enabled: SELECT measurement_name, budget_level, cost_level FROM ota_tp_measurement_types_v WHERE budget_level IS NOT NULL;
  • Identifying template associations: SELECT measurement_name, template_name, item_title, item_sequence_number FROM ota_tp_measurement_types_v WHERE template_id IS NOT NULL;
  • Detecting unassigned types (outer-join gaps): SELECT measurement_name FROM ota_tp_measurement_types_v WHERE item_type_usage_id IS NULL;

Always filter by BUSINESS_GROUP_ID to respect multi-org access, and rely on REPORTING_SEQUENCE as the canonical sort key for consistent presentation in learning reports and interfaces.