Search Results unit_meaning

Overview

OTA_TRAINING_PLAN_COSTS_V is a VALID view owned by the APPS schema within the OTA - Learning Management product of Oracle E-Business Suite. It exposes the cost structure associated with training plans, resolving internal identifiers into user-facing lookup meanings so that cost information can be reported without additional joins to the lookup tables. The view is designed as a reporting and integration surface: it presents training plan cost rows together with descriptive measurement and unit meanings, and it complements the related booking- and event-level cost views by tagging each row with a COST_LEVEL discriminator. For the plan-level rows returned here, COST_LEVEL is set to the literal value 'PLAN', distinguishing them from delegate- or event-oriented rows produced by sibling views. Columns such as BOOKING_ID, DELEGATE_PERSON_ID, DELEGATE_FULL_NAME, EVENT_ID, and EVENT_TITLE are deliberately returned as typed NULLs, preserving a uniform result shape across the cost view family.

Underlying Base Objects

The documented base objects referenced by the view are OTA_TRAINING_PLAN_COSTS, OTA_TP_MEASUREMENT_TYPES, FND_COMMON_LOOKUPS, FND_GLOBAL, OTA_EVENTS, OTA_DELEGATE_BOOKINGS, and PER_ALL_PEOPLE_F. The primary driver is OTA_TRAINING_PLAN_COSTS, aliased TPC, which supplies the training plan cost identifier, amount, currency, business group, object version number, and the full ATTRIBUTE and TP_COST_INFORMATION descriptive flexfield column sets. OTA_TP_MEASUREMENT_TYPES (alias TMT) supplies the measurement code, unit, and measurement type identifier that classify each cost line. FND_COMMON_LOOKUPS is joined twice, aliased LU1 and LU2, to translate the measurement type and unit codes into their displayed MEANING values. The remaining objects - OTA_EVENTS, OTA_DELEGATE_BOOKINGS, PER_ALL_PEOPLE_F, and the FND_GLOBAL package - support the shared view family; in this plan-level view the event, booking, and person columns are materialized as NULL placeholders rather than populated from those sources. The view text also exposes ROWID as ROW_ID, providing a stable, unique handle for each underlying cost row.

Key Columns

• ROW_ID - the ROWID of the OTA_TRAINING_PLAN_COSTS row, used as the unique row identifier.
• COST_LEVEL - discriminator literal, 'PLAN' in this view, identifying the granularity of the cost record.
• TRAINING_PLAN_COST_ID - primary key of the underlying cost record.
• TP_MEASUREMENT_TYPE_ID / TP_MEASUREMENT_CODE - identifier and code of the cost measurement type.
• MEASUREMENT_MEANING - the decoded meaning of the measurement type from FND_COMMON_LOOKUPS (LU1).
• UNIT - the unit code stored on the measurement type.
• UNIT_MEANING - the decoded meaning of the unit from FND_COMMON_LOOKUPS (LU2), which is the column most frequently sought when users investigate a unit code.
• ITEM_TYPE_USAGE_ID - reference to the item type usage associated with the measurement type.
• TRAINING_PLAN_ID - the training plan to which the cost belongs.
• AMOUNT / CURRENCY_CODE - the monetary value and the currency in which it is expressed.
• BUSINESS_GROUP_ID / OBJECT_VERSION_NUMBER - multi-tenant and optimistic locking columns.
• ATTRIBUTE1-30, TP_COST_INFORMATION1-29, INFORMATION_CATEGORY - descriptive flexfield context and segment values for extensible cost attributes.

Common Use Cases and Queries

The view is typically used to report plan-level training costs with their measurement and unit descriptions resolved, and to reconcile cost records against their flexfield detail. A basic listing joins the view back to the plan header by TRAINING_PLAN_ID:

SELECT training_plan_id, tp_measurement_code, measurement_meaning, unit_meaning, amount, currency_code
FROM apps.ota_training_plan_costs_v
WHERE cost_level = 'PLAN'
ORDER BY training_plan_id, tp_measurement_code;

To analyze costs by unit, aggregate on the decoded unit meaning:

SELECT unit_meaning, currency_code, SUM(amount) total_amount
FROM apps.ota_training_plan_costs_v
GROUP BY unit_meaning, currency_code;

Because COST_LEVEL is constant and the event, booking, and person columns are NULL at this level, queries that must span all cost granularities should use a UNION ALL across this view and its booking and event counterparts, filtering where necessary on COST_LEVEL. Direct DML is not appropriate against the view; maintenance is performed on OTA_TRAINING_PLAN_COSTS through the supported Learning Management forms and APIs.