Search Results ota_competence_languages_v




Overview
Explore in AI Chat

Overview

OTA_COMPETENCE_LANGUAGES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the OTA (Learning Management) product family. It presents the language requirements attached to competencies — that is, the languages in which a learner must demonstrate proficiency for a given competency — together with the descriptive attributes of that requirement and the associated minimum proficiency rating. The view is a denormalized, presentation-ready projection over the transactional table OTA_COMPETENCE_LANGUAGES, joining competence and rating-level reference data so that consumers receive human-readable names rather than raw foreign keys. Its role in Oracle EBS reporting/integration is to expose OTA competence-language configuration to forms, concurrent programs, and external interfaces without requiring them to resolve lookups across the underlying PER and OTA tables themselves. The object is documented as VALID in ETRM 12.2.2.

Underlying Base Objects

The view is defined over a three-way join of OTA_COMPETENCE_LANGUAGES (aliased OCL), PER_RATING_LEVELS (aliased RATL), and PER_COMPETENCES (aliased CPN), with a reference to FND_SESSIONS. The documented referenced base objects are FND_SESSIONS (synonym), OTA_COMPETENCE_LANGUAGES (synonym), OTA_UTILITY (package), PER_COMPETENCES (synonym), and PER_RATING_LEVELS (synonym). The join conditions are: OCL.COMPETENCE_ID = CPN.COMPETENCE_ID, OCL.MIN_PROFICIENCY_LEVEL_ID = RATL.RATING_LEVEL_ID(+) (an outer join, so a competence-language row may exist without a defined minimum proficiency level), and FND.SESSION_ID = USERENV('SESSIONID'). Because OTA_COMPETENCE_LANGUAGES is the driving table, the view returns one row per competence-language definition. The outer join against PER_RATING_LEVELS means rows survive when the minimum proficiency level is null.

Key Columns

Common Use Cases and Queries

Typical scenarios include listing all language requirements for a competency, extracting DFF-segment values held in OCL_INFORMATION1, and feeding downstream integrations with resolved language and proficiency descriptions. The following query lists competence-language requirements and exposes the flexfield segment the user searched for:

  • SELECT competence_name, language_description, min_proficiency_level_name, ocl_information_category, ocl_information1 FROM ota_competence_languages_v WHERE competence_id = :p_competence_id;
  • SELECT competence_language_id, competence_name, language_id FROM ota_competence_languages_v WHERE business_group_id = :p_bg AND ocl_information1 IS NOT NULL;

Because the view includes ROW_ID, it can also be queried to identify rows for correction or update of the underlying competency-language record. All queries should include BUSINESS_GROUP_ID where multi-organization data segregation is required.