Results for “category_usage_id”

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

Overview

OTFV_TRAINING_EVENT_CATEGORIES is an APPS-owned business view template in the Oracle E-Business Suite Learning Management module (OTA). It serves as the definitional source from which Oracle's flexfield view generation process derives a runtime flexfield view. The view presents a consolidated picture of scheduled training events and the category inclusions attached to them, exposing both descriptive attributes (business group, event title, activity name) and the category usage semantics that govern how a given activity is classified. Because the view is a template rather than a purely ad hoc reporting object, its column set and joins are deliberately aligned with the OTA_ACT_CAT_INCLUSIONS descriptive flexfield structure, as evidenced by the embedded "_DF" discriminator literal '_DF:OTA:OTA_ACT_CAT_INCLUSIONS:ACI'.

In EBS 12.1.1 and 12.2.2, OTFV_TRAINING_EVENT_CATEGORIES functions as a read-only, business-group-scoped projection. It is commonly surfaced through OTA learning administration windows and through Oracle Discoverer / BI Publisher report definitions that need to resolve a training event back to the category usages that include it. The view is defined WITH READ ONLY, so it is never a transaction entry point.

Underlying Base Objects

The view is constructed from a join across the core OTA tables and HR lookups. The principal base objects are:

• OTA_EVENTS — filtered to EVENT_TYPE = 'SCHEDULED', providing event identity, offering reference, and business group.
• OTA_ACTIVITY_VERSIONS — the versioned activity definition linked to the event via ACTIVITY_VERSION_ID.
• OTA_ACTIVITY_DEFINITIONS (and its TL counterpart) — supplying the activity type name.
• OTA_ACT_CAT_INCLUSIONS — the inclusion records that tie an activity version to a category usage, carrying comments, start/end dates, and the primary flag.
• OTA_CATEGORY_USAGES (and TL) — supplying the CATEGORY_TYPE value resolved through HR_BIS lookups.
• HR_ALL_ORGANIZATION_UNITS / _TL — supplying the business group name in the user's session language.
• HR_BIS and OTA_GENERAL — PL/SQL packages called inside the SQL for lookup decoding and business-group filtering.

The join from OTA_ACT_CAT_INCLUSIONS to OTA_CATEGORY_USAGES is outer (TCU.CATEGORY_USAGE_ID(+)), so inclusion rows persist even when no category usage is defined. The business group predicate uses NVL(OTA_GENERAL.GET_BUSINESS_GROUP_ID, EVT.BUSINESS_GROUP_ID) to scope results.

Key Columns

• CATEGORY_TYPE — the looked-up category type from OTA_CATEGORY_USAGES.TYPE, decoded via HR_BIS.BIS_DECODE_LOOKUP('CATEGORY_TYPE', ...). This is the column most directly associated with the "category_type" search term.
• CATEGORY_NAME — decoded ACTIVITY_CATEGORY value describing the inclusion category.
• PRIMARY_FLAG — YES/NO decode indicating the primary inclusion for the activity version.
• INCLUSION_COMMENTS, START_DATE, END_DATE — free-text and effective dating for the inclusion.
• EVENT_NAME, EVENT_ID, OFFERING_ID — event identification context.
• ACTIVITY_TYPE, ACTIVITY_NAME, ACTIVITY_DESCRIPTION, ACTIVITY_ID, ACTIVITY_VERSION_ID — activity definition and version context.
• BUSINESS_GROUP_NAME, BUSINESS_GROUP_ID, RCO_ID, CATEGORY_USAGE_ID — scoping and surrogate keys.
• "_DF" — the flexfield discriminator literal used by the view generator.

Common Use Cases and Queries

Typical reporting needs include listing all category inclusions for scheduled events in a business group, filtering by a specific category type, or identifying the primary category for an activity version.

SELECT event_name, category_name, category_type, primary_flag
FROM   apps.otfv_training_event_categories
WHERE  category_type = :p_category_type
AND    business_group_id = :p_business_group_id;

SELECT event_name, activity_name, start_date, end_date
FROM   apps.otfv_training_event_categories
WHERE  SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE + 1);

Because the CATEGORY_TYPE value is a decoded lookup meaning, report parameters and LOVs should reference the same 'CATEGORY_TYPE' lookup type found in HR_BIS so that user-supplied values match the decoded column. Direct DML against the view is not permitted.