Results for “cost_level”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OTA_TRAINING_COST_LEVELS_V is an APPS-owned database view in the Oracle E-Business Suite 12.1.1 and 12.2.2 Learning Management (OTA) module. Its purpose is to consolidate training plan cost data into a single, denormalized result set that exposes the applicable rollup level for each cost record. The view is the queryable interface that reporting tools, Oracle Learning Management cost analysis concurrent programs, and custom integrations rely upon when they need to see costs in the context of the reporting hierarchy in which they were rolled up.
The object is central to any search involving the keyword "rollup_level," because ROLLUP_LEVEL is a literal column generated directly by the view definition rather than being stored in a base table. The view assigns this value contextually, so a single SELECT against OTA_TRAINING_COST_LEVELS_V can retrieve plan-level costs and activity-version costs side by side without the caller having to reconcile different source tables or apply complex outer joins. It is defined as a compound query (UNION of multiple branches), which means Oracle Database materializes and de-duplicates the results at runtime rather than storing them physically.
Underlying Base Objects
The documented base objects referenced by the view are OTA_ACTIVITY_DEFINITIONS, OTA_ACTIVITY_VERSIONS, OTA_DELEGATE_BOOKINGS, OTA_EVENTS, OTA_TP_MEASUREMENT_TYPES, OTA_TRAINING_PLANS_V, and OTA_TRAINING_PLAN_COSTS. All except OTA_TRAINING_PLANS_V are synonyms pointing to the underlying OTA tables, and OTA_TRAINING_PLANS_V is itself a view over the training plan structure.
The core driving table is OTA_TRAINING_PLAN_COSTS, which stores individual cost rows with their measurement type, amount, currency, event, booking, and training plan references. OTA_TP_MEASUREMENT_TYPES supplies the measurement definition and, critically, a COST_LEVEL attribute that determines whether a measurement is a PLAN cost or an EVENT cost. OTA_TRAINING_PLANS_V provides the PERIOD_START_DATE for plan-level rows, while OTA_EVENTS contributes COURSE_START_DATE for event-level rows. OTA_ACTIVITY_VERSIONS supplies VERSION_NAME, which the view aliases as ITEM_NAME for activity-version records. OTA_ACTIVITY_DEFINITIONS and OTA_DELEGATE_BOOKINGS participate in the additional UNION branches that handle delegate bookings and definition-level cost attribution.
Key Columns
- ROLLUP_LEVEL — A literal discriminator identifying the granularity of the row. Documented values include 'PLAN', representing training plan level, and 'ACTIVITY_VERSION', representing rollups tied to a specific activity version.
- COST_LEVEL — A second literal discriminator distinguishing 'PLAN' costs from 'EVENT' costs, derived from the measurement type's COST_LEVEL.
- MEASUREMENT_TYPE_ID — Foreign key to OTA_TP_MEASUREMENT_TYPES; identifies which cost measurement (for example, a currency amount or a numeric quantity) the row represents.
- ITEM_NAME — Populated with VERSION_NAME for activity-version rows and padded with a blank for plan-level rows.
- AMOUNT and CURRENCY_CODE — The monetary value and currency of the cost record.
- UNIT — The unit of measure carried from the measurement type definition.
- PERIOD_START_DATE — The reporting period start; sourced from the training plan for plan rows and from the event course start date for event rows.
- EVENT_ID, BOOKING_ID, and TRAINING_PLAN_ID — Contextual identifiers linking the cost to its plan, event, or delegate booking.
Common Use Cases and Queries
Because the view normalizes rollup levels, it is the natural source for cost rollup reports that must present both plan-level and activity-version-level figures. A typical query filters on a specific plan and orders by rollup level:
SELECT training_plan_id, rollup_level, cost_level, item_name, amount, currency_code FROM ota_training_cost_levels_v WHERE training_plan_id = :p_plan_id ORDER BY rollup_level, cost_level;SELECT rollup_level, SUM(amount) total FROM ota_training_cost_levels_v WHERE currency_code = 'USD' GROUP BY rollup_level;SELECT measurement_type_id, item_name, amount FROM ota_training_cost_levels_v WHERE rollup_level = 'ACTIVITY_VERSION' AND event_id IS NOT NULL;
These patterns support cost aggregation dashboards, budget-versus-actual comparisons, and extracts feeding external financial systems. When tuning, note that the UNION branches filter on OTPC.EVENT_ID IS NOT NULL and OTPC.BOOKING_ID IS NULL to separate event costs from delegate booking costs; queries that include these predicates align with the view's internal access paths. The ROLLUP_LEVEL and COST_LEVEL columns should always be selected in report output so consumers can correctly interpret the grain of each returned amount.
-
APPS.OTA_TRAINING_COST_LEVELS_V·↳ OTA_ACTIVITY_DEFINITIONS·↳ OTA_ACTIVITY_VERSIONS·↳ OTA_DELEGATE_BOOKINGS·Explore OTA module →
-
Layer Cost Details
-
Cost component detail information for the item. Component details for the Accounting cost available in GL_ITEM_CST table.
-
Cost component detail information for the item. Component details for the Accounting cost available in GL_ITEM_CST table.
-
APPS.OTA_TRAINING_COST_LEVELS_V·↳ OTA_ACTIVITY_DEFINITIONS·↳ OTA_ACTIVITY_VERSIONS·↳ OTA_DELEGATE_BOOKINGS·Explore OTA module →
-
This table is the SLA Extract Lines table. The transactions for process inventory organizations are processed and all the necessary data for accounting are stored in this table. When the SLA accounting program is run data from this table
-
View: PMIBV_ITEM_COST_V 12.2.2
Costing info for an item. Costing info is retrieved from CM tables, OPM equivalent of the item_cost_from_GL view which retrieves data from the GL tables.
APPS.PMIBV_ITEM_COST_V·↳ CM_CMPT_DTL·↳ CM_CMPT_MST·Explore PMI module →
-
View: PMIFV_ITEM_COST_V 12.1.1
Costing information for an item retrieved from costing tables. This is the OPM costing tables equivalent of the item_cost_from_GL view which retrieves data from the GL tables.
APPS.PMIFV_ITEM_COST_V·↳ CM_CLDR_DTL·↳ CM_CLDR_HDR·↳ CM_CMPT_DTL·Explore PMI module →
-
Actual Costing Ledger Table. The purpose of this table is to serve as a depository of all actual costing transactions. These transactions may originate from Production Batch details (pm_matl_dtl) or POC resource details (pm_oprn_dtl) or Pu
-
View: CM_CMPT_DTL_VW1 12.2.2
View on cm_cmpt_dtl
APPS.CM_CMPT_DTL_VW1·↳ CM_CMPT_DTL·↳ CM_CMPT_MST·↳ CM_MTHD_MST·Explore GMF module →
-
This table is the SLA Extract Lines table. The transactions for process inventory organizations are processed and all the necessary data for accounting are stored in this table. When the SLA accounting program is run data from this table
-
Transaction Valuation table for process organizations
-
View: CM_CMPT_DTL_VW1 12.1.1
View on cm_cmpt_dtl
APPS.CM_CMPT_DTL_VW1·↳ CM_CMPT_DTL·↳ CM_CMPT_MST·↳ CM_MTHD_MST·Explore GMF module →
-
View: PMIFV_ITEM_COST_V 12.2.2
Costing information for an item retrieved from costing tables. This is the OPM costing tables equivalent of the item_cost_from_GL view which retrieves data from the GL tables.
APPS.PMIFV_ITEM_COST_V·↳ CM_CLDR_DTL·↳ CM_CLDR_HDR·↳ CM_CMPT_DTL·Explore PMI module →
-
APPS.OTA_TP_MEASUREMENT_TYPES_V·↳ HR_API·↳ HR_LOOKUPS·↳ HR_SUMMARY_ITEM_TYPE·Explore OTA module →
-
A measurement type is a statistic type used to record information about a training plan.
-
Table: GMF_LOT_COST_DETAILS 12.2.2
Lot Cost details table
-
Stores extract lines temporarily in a Session to create events in SLA. Once events get created, rows from this table are inserted into GMF_XLA_EXTRACT_LINES table.
-
Stores extract lines temporarily in a Session to create events in SLA. Once events get created, rows from this table are inserted into GMF_XLA_EXTRACT_LINES table.
-
APPS.OTA_TRAINING_PLAN_COSTS_V·↳ FND_COMMON_LOOKUPS·↳ FND_GLOBAL·↳ OTA_DELEGATE_BOOKINGS·Explore OTA module →
-
View: CST_DETAIL_COST_VIEW 12.2.2
Detail cost for reports : SINGLE-ORG view
APPS.CST_DETAIL_COST_VIEW·↳ BOM_DEPARTMENTS·↳ BOM_OPERATION_SEQUENCES·↳ BOM_RESOURCES·Explore BOM module →
-
View: CM_CMPT_DTL_VW 12.2.2
View of TOTAL_COST
-
View: PMIBV_ITEM_COST_V 12.1.1
Costing info for an item. Costing info is retrieved from CM tables, OPM equivalent of the item_cost_from_GL view which retrieves data from the GL tables.
APPS.PMIBV_ITEM_COST_V·↳ CM_CMPT_DTL·↳ CM_CMPT_MST·Explore PMI module →
-
Actual Costing Ledger Table. The purpose of this table is to serve as a depository of all actual costing transactions. These transactions may originate from Production Batch details (pm_matl_dtl) or POC resource details (pm_oprn_dtl) or Pu
-
View: CM_CMPT_DTL_VW 12.1.1
View of TOTAL_COST
-
APPS.OTA_TRAINING_PLAN_COSTS_V·↳ FND_COMMON_LOOKUPS·↳ FND_GLOBAL·↳ OTA_DELEGATE_BOOKINGS·Explore OTA module →
-
Cost Component Details
-
View: PMIFV_FORMULA_COST_V 12.2.2
Costing Information for product by formula
APPS.PMIFV_FORMULA_COST_V·↳ CM_CLDR_DTL·↳ CM_CLDR_HDR·↳ CM_CMPT_DTL·Explore PMI module →
-
View: PMIBV_FORMULA_COST_V 12.1.1
Costing Information for product by formula
APPS.PMIBV_FORMULA_COST_V·↳ CM_CLDR_DTL·↳ CM_CLDR_HDR·↳ CM_CMPT_DTL·Explore PMI module →
-
View: PMIFV_FORMULA_COST_V 12.1.1
Costing Information for product by formula
APPS.PMIFV_FORMULA_COST_V·↳ CM_CLDR_DTL·↳ CM_CLDR_HDR·↳ CM_CMPT_DTL·Explore PMI module →
-
Table: GMF_LOT_COST_DETAILS 12.1.1
Lot Cost details table
-
Transaction Valuation table for process organizations
-
A measurement type is a statistic type used to record information about a training plan.
-
View: CST_DETAIL_COST_VIEW 12.1.1
Detail cost for reports : SINGLE-ORG view
APPS.CST_DETAIL_COST_VIEW·↳ BOM_DEPARTMENTS·↳ BOM_OPERATION_SEQUENCES·↳ BOM_RESOURCES·Explore BOM module →
-
APPS.OTA_TP_MEASUREMENT_TYPES_V·↳ FND_GLOBAL·↳ HR_API·↳ HR_LOOKUPS·Explore OTA module →
-
Cost Component Details
-
View: PMIBV_FORMULA_COST_V 12.2.2
Costing Information for product by formula
APPS.PMIBV_FORMULA_COST_V·↳ CM_CLDR_DTL·↳ CM_CLDR_HDR·↳ CM_CMPT_DTL·Explore PMI module →
-
VIEW: GMF.GL_ITEM_DTL# 12.2.2
-
VIEW: GMF.CM_ACST_LED# 12.2.2
-
PACKAGE: APPS.OTA_TMT_SHD 12.2.2
-
TABLE: GMF.GL_ITEM_DTL 12.2.2