Search Results create_measure




Overview
Explore in AI Chat

Overview

APPS.OTA_TMT_API is a PL/SQL package body that constitutes a public application programming interface for the Oracle E-Business Suite Training Management (OTM) module. Its responsibility is to manage the definition and lifecycle of training measurements — the measurable budget items or metrics, such as costs, headcount, or training hours, that the enterprise associates with training plans, budgets, and item types. By exposing discrete create, update, and delete operations, the package encapsulates the validation, defaulting, and table maintenance logic required to keep training measurement definitions consistent across the training administration and budgeting schemas. In Oracle EBS 12.1.1 and 12.2.2, the package header (OTA_TMT_API) declares the callable interface, while this body (ottmtapi.pkb, version 115.5) implements the business rules behind it.

Key Procedures and Functions

The documented public interface exposes three procedures:

  • CREATE_MEASURE — Creates a new training measurement definition. The declaration in this package body accepts a validating flag, an effective date, a business group identifier, a training plan measurement code, unit of measure, budget level, cost level, and a flag indicating whether multiple budget values are permitted. It additionally accepts an optional reporting sequence, an item type usage identifier, and a full set of descriptive flexfield attributes (attribute category plus attributes 1 through 25). This parameter profile confirms that measurement definitions are date-effective and business-group-specific, and that they are extensible through descriptive flexfields.
  • UPDATE_MEASURE — Modifies an existing training measurement record. This procedure is the primary target of the user search term "update_measure". It applies changed attributes to a measurement that already exists, again honoring effective-dating and business group security.
  • DELETE_MEASURE — Removes an existing measurement definition from the training measurement setup.

The package also declares package variable g_package, which supplies the package name prefix used to compose error message strings raised by the validation logic.

Tables Accessed

Per the documented metadata, the package accesses the following tables through APPS synonyms:

  • PER_BUDGETS — Stores the budget definition rows against which training measurements are associated. The create, update, and delete operations maintain the budget linkage that determines how measurement values participate in training budget calculations.
  • PER_BUDGET_VERSIONS — Stores the dated versions of budgets. Because measurements are effective-dated, the API must resolve and validate the appropriate budget version when a measurement is created or changed.

Usage Notes

OTA_TMT_API is classified as an API, indicating it is intended as a supported programmatic entry point rather than an internal private package. It is typically invoked from the Training Management setup forms that maintain training plan measurements, from concurrent programs that seed or migrate measurement definitions, and from custom PL/SQL that must create, amend, or remove measurements in a supported manner rather than writing directly to the underlying tables. Callers should set p_validate to true to exercise validation without committing, and must supply a valid effective date and business group. The documented metadata notes that this package is referenced by one other package, confirming its role as a reusable building block within the OTM API layer. Because the underlying implementation carries an early header version, the procedures should always be called through the public package header.