Search Results display_to_learner_flag

Overview

The OTA_LEARNING_PATHS_VL view is a public, language-sensitive (MLS) view in the Oracle E-Business Suite Learning Management module (OTA). It presents learning path definitions — structured sequences of courses or offerings that learners complete to satisfy a development objective — combining translatable descriptive attributes with the non-translatable operational attributes of the parent learning path record. The _VL suffix signals that the view joins a base entity table to its translation table and filters rows by the session language using USERENV('LANG'), so each query returns description text in the language of the current user session rather than in all defined languages.

In Oracle EBS 12.1.1 and 12.2.2, this view is the reporting and integration counterpart to the learning path maintenance forms. It is the object of choice for concurrent programs, BI Publisher data models, OBIEE extracts, and inbound/outbound interfaces that need a single flat row per learning path. Because it exposes both the technical keys (LEARNING_PATH_ID, BUSINESS_GROUP_ID) and the descriptive attributes (NAME, DESCRIPTION, OBJECTIVES, PURPOSE), it supports both operational joins and end-user reporting without requiring the report author to resolve language joins manually.

The user search term competency_update_level maps directly to the COMPETENCY_UPDATE_LEVEL column exposed by this view, which governs how a learning path completion propagates proficiency updates to the competencies associated with the path's contents.

Underlying Base Objects

The view is owned by the APPS schema and is defined over two documented base objects, both referenced through synonyms:

• OTA_LEARNING_PATHS (alias OLP) — the base, non-translatable table holding the learning path header: identifiers, business group, duration, date range, source information, personalization flags, descriptive flexfields, and COMPETENCY_UPDATE_LEVEL.
• OTA_LEARNING_PATHS_TL (alias OLT) — the translation table holding the language-dependent text columns: NAME, DESCRIPTION, OBJECTIVES, KEYWORDS, and PURPOSE.

The two tables are joined on LEARNING_PATH_ID, and the translation side is constrained by OLT.LANGUAGE = USERENV('LANG'). This inner join means a learning path appears in the view only when a translation row exists in the session language. The view is not a simple select of the base table; it consolidates the MLS pattern into a single queryable object, and it projects OLP.ROWID to preserve row addressing for downstream processing.

Key Columns

• LEARNING_PATH_ID — primary key of the learning path; the join key to catalog membership, offering links, and enrollment records.
• BUSINESS_GROUP_ID — the HR business group that owns the record; critical for multi-organization data security in queries.
• NAME, DESCRIPTION, OBJECTIVES, KEYWORDS, PURPOSE — translatable descriptive text from OTA_LEARNING_PATHS_TL, returned in the session language.
• DURATION / DURATION_UNITS — expected effort of the path and its unit of measure.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective window; a null end date indicates the path is open-ended.
• PATH_SOURCE_CODE, SOURCE_FUNCTION_CODE, SOURCE_ID, ASSIGNMENT_ID, PERSON_ID, CONTACT_ID — trace the origin of the path (for example, catalog, succession, or assignment-driven creation) and the associated person or assignment.
• DISPLAY_TO_LEARNER_FLAG, PUBLIC_FLAG — control self-service visibility and general availability.
• NOTIFY_DAYS_BEFORE_TARGET — lead time for target-date notifications.
• COMPETENCY_UPDATE_LEVEL — the level at which competency proficiency is updated when the learning path is completed (for example, at the path level, at the course/offering level, or not updated). This is the column matching the user's search term and is frequently used in competency and talent reporting.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Who columns for audit and incremental extraction.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE20 — descriptive flexfield segments for customer-specific extensions.

Common Use Cases and Queries

Typical uses include learning path catalogs for reporting, competency-impact analysis, and incremental integration extracts keyed on LAST_UPDATE_DATE.

Catalog listing for a business group:

SELECT learning_path_id, name, duration, duration_units,
       start_date_active, end_date_active, public_flag
FROM   apps.ota_learning_paths_vl
WHERE  business_group_id = :p_business_group_id
AND    (end_date_active IS NULL OR end_date_active >= TRUNC(SYSDATE))
ORDER BY name;

Reporting on the competency update behavior (the searched column):

SELECT learning_path_id, name, competency_update_level
FROM   apps.ota_learning_paths_vl
WHERE  competency_update_level IS NOT NULL
ORDER BY name;

Incremental extract for an interface or data warehouse:

SELECT learning_path_id, business_group_id, name, description,
       path_source_code, source_function_code,
       display_to_learner_flag, public_flag,
       competency_update_level, last_update_date, last_updated_by
FROM   apps.ota_learning_paths_vl
WHERE  last_update_date >= :p_since_date;

Because the view applies the session-language filter internally, always initialize the language environment (FND_GLOBAL.APPS_INITIALIZE or an equivalent USERENV('LANG') setting) in PL/SQL or concurrent processing before querying, and qualify the view with the APPS schema when accessed from outside the APPS context. For multi-language extracts, query OTA_LEARNING_PATHS_TL directly and join to OTA_LEARNING_PATHS rather than relying on this view.