Search Results training_reference

Overview

APPS.OTA_CTRNG_HISTORIES_V is a supplementary Oracle E-Business Suite view owned by the APPS schema and registered in FND Design Data as OTA.OTA_CTRNG_HISTORIES_V. It presents consolidated training history records for persons tracked within Oracle Training Administration (OTA), part of the Oracle Learning Management (OLM) product family. In the context of Oracle EBS 12.1.1 and 12.2.2, the view is classified as a "supplementary view used to simplify forms coding." Oracle's own documentation carries an explicit warning: the view is not recommended for direct querying or data alteration, since its definition may change dramatically in subsequent minor or major releases. The object status is VALID in the documented environment.

Functionally, the view exposes a flattened, denormalized picture of a delegate's training history — the training title, date, delivery site, status, attendance outcome, failure reason, scholastic rating, provider, and duration — resolving several descriptive attributes into their translated or meaning-based forms. This makes it convenient for forms-based display, but it is equally useful as a read-only reporting source when the consumer accepts the stability caveat.

Underlying Base Objects

The documented dependency list shows the view is constructed over the following objects:

• OTA_DELEGATE_BOOKINGS — the transactional record of a delegate's enrollment on an event.
• OTA_EVENTS and OTA_EVENTS_TL — event header and its translatable (language-dependent) descriptions.
• OTA_ACTIVITY_VERSIONS_TL — the equivalent OTA activity version name.
• OTA_BOOKING_STATUS_TYPES_TL — provides the booking/delegate status meaning.
• HR_ALL_ORGANIZATION_UNITS_TL — resolves the event center or site name.
• PO_VENDORS — resolves the training provider (supplier) name.
• HR_GENERAL (PACKAGE) — supplies the HR security/utility logic used by the view.
• OTA_NOTRNG_HISTORIES_V (VIEW) — a companion view supplying the non-training (not-training) history portion, which OTA_CTRNG_HISTORIES_V unions or otherwise consolidates with training records.

The relationship is therefore one of aggregation: the delegate booking transaction is joined to event, activity version, status, vendor, and organization lookup objects to produce a single readable history row per training record.

Key Columns

• REFERENCE_DATE (DATE) — the date of the training.
• REFERENCE_TITLE (VARCHAR2 80) — the title of the training.
• EVENT_CENTER_MEANING (VARCHAR2 240) — the name of the site where the training was taken.
• EVENT_ACTIVITY_VERSION_NAME (VARCHAR2 80) — the name of an equivalent OTA activity.
• REFERENCE_STATUS (VARCHAR2 4000) — the current status of the training.
• SUCCESSFUL_ATTENDANCE_MEANING (VARCHAR2 4000) — the attendance outcome (successful/unsuccessful).
• FAILURE_REASON_MEANING (VARCHAR2 4000) — the Delegate Booking Failure Reason.
• SCHOLASTIC_RATING (VARCHAR2 40) — the scholastic rating achieved.
• PROVIDER (VARCHAR2 240) — the training provider (derived from PO_VENDORS).
• TRAINING_REFERENCE (VARCHAR2 10) — a short cross-reference code for the training.
• PERSON_ID (NUMBER 10) — the person to whom the training history applies.
• CONTACT_ID (NUMBER) — the contact person associated with the training.
• DURATION (NUMBER) and DURATION_UNITS (VARCHAR2 4000) — the event duration and its unit meaning.
• Standard audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY, plus ORGANIZATION_ID and CUSTOMER_ID.

Common Use Cases and Queries

Typical uses include competency/training-history reports, compliance verification for a person, and integration extracts into third-party LMS or HR data warehouses. A minimal query retrieving the full documented column list is:

• SELECT REFERENCE_DATE, REFERENCE_TITLE, EVENT_CENTER_MEANING, EVENT_ACTIVITY_VERSION_NAME, REFERENCE_STATUS, SUCCESSFUL_ATTENDANCE_MEANING, FAILURE_REASON_MEANING, SCHOLASTIC_RATING, PROVIDER, TRAINING_REFERENCE, PERSON_ID, CONTACT_ID, DURATION, DURATION_UNITS, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY, ORGANIZATION_ID, CUSTOMER_ID FROM APPS.OTA_CTRNG_HISTORIES_V;

To isolate history for one employee: SELECT REFERENCE_DATE, REFERENCE_TITLE, REFERENCE_STATUS, SUCCESSFUL_ATTENDANCE_MEANING FROM APPS.OTA_CTRNG_HISTORIES_V WHERE PERSON_ID = :p_person_id ORDER BY REFERENCE_DATE DESC. To find failures with reasons: SELECT PERSON_ID, REFERENCE_TITLE, FAILURE_REASON_MEANING FROM APPS.OTA_CTRNG_HISTORIES_V WHERE SUCCESSFUL_ATTENDANCE_MEANING = 'No'. Because the view is documented as subject to significant change, production integrations should prefer the underlying base tables plus the supported OTA public APIs.