Results for “special_information_type_id”

50+ results




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

Overview

OTA_SKILLS_V is a reporting view owned by the APPS schema in Oracle EBS 12.1.1 and 12.2.2, delivered as part of the OTA (Learning Management) product family. Its stated purpose is to list all types of Skills defined within an enterprise. Rather than storing data itself, the view consolidates skill-type definitions drawn from Oracle HRMS flexfield and special information infrastructure so that Learning Management and downstream reporting components can resolve skill identifiers to descriptive names.

In EBS, skills are modeled as special information types tied to a specific category. OTA_SKILLS_V isolates the subset of those types whose usage category equals 'SKILL', presenting only the rows relevant to competency and skills tracking. This makes the view the canonical read interface for any component that must enumerate valid skill types without reproducing the underlying HRMS join logic.

Underlying Base Objects

The view is defined over two documented base objects, plus an inline existence check against a third:

Because PER_SPECIAL_INFO_TYPES and PER_SPECIAL_INFO_TYPE_USAGES are referenced as synonyms, the view remains insulated from the physical HRMS base table names, while FND_ID_FLEX_STRUCTURES_VL is a translated (_VL) flexfield structure view, meaning skill names may be presented in the session language.

Key Columns

  • ROW_ID — the ROWID of the underlying PER_SPECIAL_INFO_TYPES row; useful as a unique row locator but not stable across reorganizations.
  • BUSINESS_GROUP_ID — the business group (HR operating unit) to which the skill type belongs, enforcing multi-tenant separation of HR data.
  • SPECIAL_INFORMATION_TYPE_ID — the primary identifier of the skill type; the key joined against usage and enrollment data.
  • ID_FLEX_NUM — the descriptive flexfield structure number that backs the skill type.
  • SKILL_NAME — the descriptive flexfield structure name surfaced as the human-readable skill label (documented column list includes this, mapped from IFS.ID_FLEX_STRUCTURE_NAME).

Common Use Cases and Queries

Typical scenarios include populating skill selection lists in Learning Management enrollment forms, validating skill identifiers during competency data loads, and reporting on which skill types exist within a business group. A basic enumeration query follows:

SELECT business_group_id, special_information_type_id, skill_name FROM apps.ota_skills_v WHERE business_group_id = :p_business_group_id ORDER BY skill_name;

To resolve a specific skill for a single record:

SELECT skill_name FROM apps.ota_skills_v WHERE special_information_type_id = :p_type_id;

Because the view filters on the SKILL usage category internally, no additional category predicate is required; consumers simply filter by business group or join on SPECIAL_INFORMATION_TYPE_ID to related competency and enrollment objects.