Results for “ota_plan_measurement_type”

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

Overview

APPS.OTA_TRAINING_PLAN_BUDGETS_V is a reporting view within the Oracle E-Business Suite (EBS) Enterprise Training Management (ETRM) module, historically delivered under Oracle Learning Management (OLM). It exposes budget information associated with training plans, presenting plan budgets in a consolidated, query-friendly format. Rather than storing data itself, the view derives its result set from the underlying Oracle HRMS budgeting tables (PER_BUDGETS and related entities) joined to ETRM-specific measurement and training plan objects, and is available in both release 12.1.1 and 12.2.2.

The view plays an important role in ETRM reporting and integration because training plan budgets are persisted in the generic PER_BUDGETS framework, which is shared across Oracle HRMS applications. Analysts, concurrent programs, and external integrations that require training-plan-specific budget figures query this view rather than navigating the normalized budget schema directly. The view exposes a literal discriminator of 'PLAN_BUDGET' to identify the budget source, aligning it with the broader OTA budget abstraction used elsewhere in ETRM.

Underlying Base Objects

The documented view text joins the following synonyms:

• PER_BUDGETS (PB) — the budget header, supplying the budget unit and unit of measure.
• PER_BUDGET_VERSIONS (PBR) — budget version rows, providing BUDGET_VERSION_ID.
• PER_BUDGET_ELEMENTS (PBE) — budget elements linking a budget to a training plan via TRAINING_PLAN_ID.
• PER_BUDGET_VALUES (PBV) — the stored budget amounts (VALUE) and descriptive/attribute flexfield columns.
• OTA_TP_MEASUREMENT_TYPES (TMT) — ETRM measurement metadata such as budget level and whether multiple budget values are permitted.
• FND_LOOKUP_VALUES (LU1, LU2) — used to translate unit codes into their lookup meanings.
• OTA_TRAINING_PLAN_MEMBERS — membership context for training plans.
• Additional referenced objects include OTA_ACTIVITY_DEFINITIONS, OTA_ACTIVITY_VERSIONS, and OTA_EVENTS, which support the wider ETRM plan/activity model.

The view is therefore a join layer that maps the generic HRMS budget model onto training plan semantics.

Key Columns

• TRAINING_PLAN_ID — identifier of the training plan to which the budget belongs.
• BUDGET_ID / BUDGET_VERSION_ID / BUDGET_ELEMENT_ID / BUDGET_VALUE_ID — primary and foreign keys tracing a value back through the budget hierarchy.
• UNIT and BUDGET_LEVEL — the budget unit and the level at which the budget is defined (for example, plan or activity level).
• VALUE — the actual budgeted amount.
• MANY_BUDGET_VALUES_FLAG — indicates whether multiple values are permitted for the measurement.
• PERIOD_SET_NAME and BUSINESS_GROUP_ID — accounting period context and the owning business group.
• INFORMATION_CATEGORY and BUDGET_INFORMATION1–30 — descriptive flexfield information stored against the budget value.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–30 — key/descriptive flexfield attributes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical uses include reporting total budgeted amounts per training plan, validating budget entry against measurement types, and feeding budget values into integration interfaces. A representative query:

SELECT training_plan_id, budget_id, unit, value, period_set_name FROM apps.ota_training_plan_budgets_v WHERE business_group_id = :p_bg_id ORDER BY training_plan_id;

For aggregation by plan:

SELECT training_plan_id, SUM(value) total_budget FROM apps.ota_training_plan_budgets_v GROUP BY training_plan_id;

Because the view is read-only and subject to standard EBS security, ensure the querying responsibility holds the appropriate business group and training plan access.