Search Results item_title

Overview

APPS.OTA_TP_MEASUREMENT_TYPES_V is a database view owned by the APPS schema in Oracle E-Business Suite, registered under FND Design Data as OTA.OTA_TP_MEASUREMENT_TYPES_V. It belongs to the Oracle Training Administration (OTA) product family and exposes the measurement type definitions used by the Enterprise Training and Tuition Reimbursement Management (ETRM) module. Measurement types describe the quantitative values that can be captured against a training event or enrollment, such as scores, completion percentages, or hours attended, together with the units in which those values are expressed.

The view is explicitly classified as a supplementary view used to simplify Forms coding. Oracle documentation attached to this object carries an important warning: Oracle does not recommend querying or altering data through this view, as its definition may change dramatically in subsequent minor or major releases. As a result, it should be treated as an internal presentation-layer object rather than a stable integration interface. Status is recorded as VALID in the documented environment, confirming the view compiles and resolves successfully in the 12.1.1 / 12.2.2 releases referenced.

The view is particularly relevant to the search term "item_title," because it exposes an ITEM_TITLE column alongside ITEM_TYPE_USAGE_ID and ITEM_SEQUENCE_NUMBER, allowing consumers to display the human-readable title of the summary item associated with each measurement type.

Underlying Base Objects

ETRM metadata for 12.2.2 documents the following referenced base objects:

• OTA_TP_MEASUREMENT_TYPES (SYNONYM) – the core synonym resolving to the base measurement type definition table, which supplies identifiers, codes, names, and units.
• HR_SUMMARY_ITEM_TYPE (VIEW) – provides summary item type definitions, including the item title.
• HR_SUMMARY_ITEM_TYPE_USAGE (VIEW) – links summary item types to their usage contexts, supporting ITEM_TYPE_USAGE_ID.
• HR_SUMMARY_TEMPLATE (VIEW) – supplies template identifiers and names (TEMPLATE_ID, TEMPLATE_NAME).
• HR_LOOKUPS (VIEW) – supplies lookup meaning and display values for coded columns such as UNIT or level indicators.
• HR_API (PACKAGE) – the HRMS business process API referenced by the dependent objects.

Functionally, the view joins measurement type definitions to the HRMS summary framework so that each measurement type can be presented with its associated template, summary item title, and unit description in a single row.

Key Columns

Key columns exposed by the view include:

• TP_MEASUREMENT_TYPE_ID – primary identifier of the measurement type; use this for joins and filters.
• TP_MEASUREMENT_CODE and MEASUREMENT_NAME – the internal code and user-facing name of the measurement.
• UNIT and UNIT_NAME – the measurement unit code and its display name, typically resolved through HR_LOOKUPS.
• ITEM_TYPE_USAGE_ID, ITEM_TITLE, ITEM_SEQUENCE_NUMBER – identify the summary item associated with the measurement type and its display order. ITEM_TITLE is the column most relevant to the user's search.
• TEMPLATE_ID and TEMPLATE_NAME – the summary template under which the item is organized.
• BUSINESS_GROUP_ID – multi-tenant partitioning key; every query must be restricted to the appropriate business group.
• OBJECT_VERSION_NUMBER – optimistic locking column.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard WHO audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30 – descriptive flexfield segments.

Common Use Cases and Queries

Typical scenarios include reporting the measurement types available for a training offering, validating that the correct units are defined, and surfacing item titles beside measurement codes in custom OAF or Forms extensions. Because of the Oracle warning, use this view for read-only reporting only, and prefer the base tables where a durable interface is required.

Sample query listing measurement types with item titles within a business group:

• SELECT tp_measurement_type_id, tp_measurement_code, measurement_name, unit_name, item_title, item_sequence_number FROM apps.ota_tp_measurement_types_v WHERE business_group_id = :p_bg_id ORDER BY template_name, item_sequence_number;

Sample query filtering on a specific item title:

• SELECT tp_measurement_code, measurement_name, unit_name FROM apps.ota_tp_measurement_types_v WHERE item_title = :p_item_title AND business_group_id = :p_bg_id;

Always qualify the APPS schema and constrain by BUSINESS_GROUP_ID to avoid cross-business-group leakage.