Search Results programme_id

Overview

APPS.OTA_CATEGORY_USAGES_V is a supplementary database view in the Oracle E-Business Suite (EBS) Applications (APPS) schema, associated with the Oracle Training Administration (OTA) product family. Its documented view type indicates that it is a "supplementary view used to simplify forms coding." Oracle explicitly warns that it does not recommend querying or altering data through this view, and that its definition may change dramatically in subsequent minor or major releases. Consequently, this view should be regarded as an internal forms-support construct rather than a formally supported integration or reporting interface.

The view is tied to the OTA_CATEGORY_USAGES entity, as indicated by its FND Design Data identifier (OTA.OTA_CATEGORY_USAGES_V) and its name. In the OTA data model, category usages link training categories to the classification, programme, and discount records that consume or reference them. Because the view is designed to service a specific Oracle Forms block, its shape—mixing identifiers, ROWIDs, and object version numbers (OVN)—reflects the optimistic locking and multi-record display requirements of that form rather than a normalized business reporting model.

Underlying Base Objects

According to the documented dependency metadata, APPS.OTA_CATEGORY_USAGES_V references the following objects:

• OTA_CATEGORY_USAGES (accessed through a synonym) — the primary base table supplying the category usage rows, including business group, category, and the classification/programme/discount association columns.
• HR_LOOKUPS (view) — the Oracle HR lookup view, used to resolve meaning text such as CATEGORY_MEANING from lookup codes.
• HR_API (package) — the HR API package, typically invoked by the view's underlying form logic or lookup resolution to derive code meanings and validation values.

In ETRM metadata, the dependency listing sometimes also attributes the view to FND_GLOBAL, which supplies session context such as the current business group and responsibility. The view is marked VALID and is not referenced by any other documented object, confirming its role as a leaf-level, forms-facing construct.

Key Columns

The view exposes the following columns:

• BUSINESS_GROUP_ID — the business group partitioning the category usage record; a core multi-tenancy key throughout HR and OTA.
• CATEGORY — the category code (VARCHAR2(240)) referencing the category being used.
• CATEGORY_MEANING — the descriptive meaning of the category, typically resolved from HR_LOOKUPS.
• CLASSIFICATION_TYPE — a CHAR discriminator indicating the type of the linked classification entity. This is the column of interest for the search term "classification_type," and it distinguishes which classification source a usage row points to.
• CLASSIFICATION_ID, CLASSIFICATION_ROW_ID, CLASSIFICATION_OVN — the classification entity's primary key, its ROWID, and its object version number (used for optimistic locking in the form).
• PROGRAMME_TYPE, PROGRAMME_ID, PROGRAMME_ROW_ID, PROGRAMME_OVN — the equivalent identifier/ROWID/version triad for a linked programme.
• DISCOUNT_TYPE, DISCOUNT_ID, DISCOUNT_ROW_ID, DISCOUNT_OVN — the equivalent triad for a linked discount.

The repeated TYPE/ID/ROW_ID/OVN pattern across classification, programme, and discount reflects the form's need to display and modify multiple related entities from a single block.

Common Use Cases and Queries

Because Oracle discourages direct querying, usage should be limited to diagnostics, troubleshooting, or migration analysis. A typical diagnostic query retrieves all usages for a category within a business group, filtered by classification type:

SELECT business_group_id, category, category_meaning, classification_type, classification_id
FROM apps.ota_category_usages_v
WHERE business_group_id = :p_bg_id
AND classification_type = :p_type
ORDER BY category;

A second common pattern joins the view back to the classification entity using CLASSIFICATION_ID to inspect what a category usage actually references, while a third selects the TYPE/ID/OVN columns to audit optimistic-locking values or to reconcile against OTA_CATEGORY_USAGES directly. In all cases, the supported alternative for production reporting is to build queries against the base table OTA_CATEGORY_USAGES and the relevant HR_LOOKUPS entries rather than relying on this volatile view.