Results for “activity_type”

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

Overview

OTFV_SKILL_PROVISIONS is an APPS-owned database view within the Oracle E-Business Suite OTA (Learning Management) product family. The ETRM metadata classifies it as a "Business view template from which the flexfield view is generated," indicating that it belongs to the family of OTFV_* objects used by Oracle Training Administration and its descriptive flexfield infrastructure rather than being a standalone reporting entity. The view consolidates skill provision records with their associated activity definitions and versions and with the personnel analysis criteria used to qualify a provision, exposing both business attributes and flexfield context information so that consumers can render descriptive flexfield segments without joining directly to the underlying transaction tables.

The view is documented as VALID in the APPS schema and carries the standard Oracle proprietary and confidential notices. It appears in documented 12.2.2 metadata and is consistent with the 12.1.1 OTA data model, where the OTFV_* view templates are shipped by the Learning Management application to support flexfield-enabled business views.

Underlying Base Objects

The view text selects from four base objects through synonyms owned by APPS: OTA_SKILL_PROVISIONS (TSP), OTA_ACTIVITY_DEFINITIONS (TAD), OTA_ACTIVITY_VERSIONS (TAV), and PER_ANALYSIS_CRITERIA (ANC). It also calls the HR_BIS.BIS_DECODE_LOOKUP function to translate the stored skill provision type code into a meaningful lookup value.

The join structure is strictly enforced by the WHERE clause:

• TSP.ACTIVITY_VERSION_ID = TAV.ACTIVITY_VERSION_ID links each skill provision to the specific version of the activity it provides.
• TAV.ACTIVITY_ID = TAD.ACTIVITY_ID links that version back to the parent activity definition.
• ANC.ANALYSIS_CRITERIA_ID = TSP.ANALYSIS_CRITERIA_ID links the provision to the personnel analysis criteria record that qualifies it.

The documented referenced objects also include the translation tables OTA_ACTIVITY_DEFINITIONS_TL and OTA_ACTIVITY_VERSIONS_TL, which supply the translated NAME and VERSION_NAME attributes surfaced by the view. The view is defined WITH READ ONLY, so it cannot be used as a DML target.

Key Columns

• SKILL_PROVISION_ID — Primary identifier of the OTA_SKILL_PROVISIONS row; the natural driving key of the view.
• SKILL_PROVISION_TYPE — Decoded value produced by HR_BIS.BIS_DECODE_LOOKUP against the SKILL_PROVISION_TYPE lookup type.
• SKILL_PROVISION_COMMENTS — Free-text comments stored on the provision.
• ANALYSIS_CRITERIA_ID — Identifier of the PER_ANALYSIS_CRITERIA record that qualifies the provision. This is the column most frequently searched by users querying the view directly.
• ACTIVITY_VERSION_ID / ACTIVITY_ID — Keys to the activity version and its parent activity definition.
• ACTIVITY_NAME / ACTIVITY_TYPE — Translated version name and activity type name, usable for display without additional joins.
• RCO_ID — Responsible organization or routing identifier carried on the activity version.
• "_KF:PER:PEA:ANC" and "_DF:OTA:OTA_SKILL_PROVISIONS:TSP" — Flexfield context markers emitted by the template so the generated flexfield view can bind key flexfield and descriptive flexfield segments.

Common Use Cases and Queries

The most common use is reporting on which personnel analysis criteria are attached to skill provisions, or listing all provisions tied to a given criteria set. A representative query keyed on the searched column is:

SELECT skill_provision_id, skill_provision_type, activity_name, analysis_criteria_id FROM apps.otfv_skill_provisions WHERE analysis_criteria_id = :p_criteria_id;

A second scenario joins the view back to PER_ANALYSIS_CRITERIA and the criteria details to build competency-to-activity matrices for learning compliance reporting. A third uses ACTIVITY_TYPE and ACTIVITY_NAME as a denormalized catalogue of provisioned activities for enrollment and certification dashboards, relying on the view's READ ONLY nature for safe ad hoc access. Because the view embeds flexfield context columns, report builders can also extract descriptive flexfield values for OTA_SKILL_PROVISIONS without writing their own context resolution logic.