Results for “activity_success_criteria”

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

Overview

APPS.OTA_ACTIVITY_VERSIONS_V is an Oracle E-Business Suite view owned by the APPS schema that presents a denormalized, user-facing representation of activity versions within the Oracle Training Administration (OTA) module. Activity versions are the schedulable, deliverable instances of activities that are themselves defined in the activity catalog. This view resolves foreign-key lookups, translates lookup codes into descriptive values, retrieves language-specific content, and joins supporting descriptive columns (developer organization, controlling person, superseding version name, vendor name, currency, and language) so that reports, concurrent programs, and integrations can consume activity version data without performing the joins themselves.

The view is central to competency and training administration reporting in EBS 12.1.1 and 12.2.2. It exposes scheduling attributes (start and end dates, duration and units, minimum and maximum attendees), financial attributes (budgeted and actual cost, expenses allowed), professional credit information, and descriptive attributes such as objectives, intended audience, keywords, and success criteria. The SUCCESS_CRITERIA column, which decodes against the ACTIVITY_SUCCESS_CRITERIA lookup, is the specific attribute most commonly sought when querying this view by that name.

Underlying Base Objects

The view definition draws on the following documented base objects, all catalogued in the ETRM metadata:

• OTA_ACTIVITY_VERSIONS and OTA_ACTIVITY_VERSIONS_TL — the transactional and translated-language tables holding one row per version of an activity. These supply the primary key columns, dates, durations, costs, and credit attributes.
• OTA_ACTIVITY_DEFINITIONS and OTA_ACTIVITY_DEFINITIONS_TL — the underlying catalog definitions, supplying the activity name.
• HR_ALL_ORGANIZATION_UNITS_TL — resolved to provide the developer organization name.
• PER_ALL_PEOPLE_F — resolved to provide the controlling person's full name.
• PO_VENDORS — resolved to provide the vendor name for externally delivered activities.
• HR_GENERAL, OTA_GENERAL, and OTA_TAV_BUS — PL/SQL packages invoked within the view text to decode lookup values and derive names, notably HR_GENERAL.DECODE_LOOKUP for ACTIVITY_SUCCESS_CRITERIA, OTA_DURATION_UNITS, ACTIVITY_USER_STATUS, and PROFESSIONAL_CREDIT_TYPE.
• FND_SESSIONS — referenced for session or language context.

Key Columns

• ACTIVITY_VERSION_ID, ACTIVITY_ID, VERSION_NAME, VERSION_CODE — identification and versioning of the activity offering.
• SUCCESS_CRITERIA — the encoded lookup value indicating the completion or evaluation rule for the version; accompanied by a decoded description from HR_GENERAL.DECODE_LOOKUP('ACTIVITY_SUCCESS_CRITERIA', ...).
• START_DATE, END_DATE, DURATION, DURATION_UNITS — scheduling attributes.
• MINIMUM_ATTENDEES, MAXIMUM_ATTENDEES, MAXIMUM_INTERNAL_ATTENDEES — enrollment limits.
• ACTUAL_COST, BUDGET_COST, BUDGET_CURRENCY_CODE, EXPENSES_ALLOWED — financial attributes.
• PROFESSIONAL_CREDIT_TYPE, PROFESSIONAL_CREDITS, COMPETENCY_UPDATE_LEVEL — competency and certification linkage.
• DEVELOPER_ORGANIZATION_ID, CONTROLLING_PERSON_ID, VENDOR_ID — ownership and delivery source.
• OBJECTIVES, INTENDED_AUDIENCE, KEYWORDS — descriptive content from the translated table.
• SUPERSEDED_BY_ACT_VERSION_ID and the derived superseding version name — version lineage.
• Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) and OBJECT_VERSION_NUMBER.

Common Use Cases and Queries

Typical uses include training catalog reporting, competency gap analysis, and integration extracts feeding learning management or external systems. Attributes such as success criteria are frequently targeted for reporting on completion rules per offering.

Example: list versions with decoded success criteria for active offerings.

SELECT activity_version_id, version_name, name, start_date, end_date,
       success_criteria,
       hr_general.decode_lookup('ACTIVITY_SUCCESS_CRITERIA', success_criteria) success_criteria_meaning
FROM   apps.ota_activity_versions_v
WHERE  user_status = 'ACTIVE'
  AND  sysdate BETWEEN nvl(start_date, sysdate) AND nvl(end_date, sysdate + 1);

Example: summarize success criteria distribution across offerings.

SELECT hr_general.decode_lookup('ACTIVITY_SUCCESS_CRITERIA', success_criteria) success_criteria_meaning,
       count(*) version_count
FROM   apps.ota_activity_versions_v
GROUP  BY hr_general.decode_lookup('ACTIVITY_SUCCESS_CRITERIA', success_criteria);

Because lookup decoding is performed inside the view via PL/SQL functions, queries should avoid large cross-joins that force repeated function invocation. For high-volume extracts, filter on indexed columns such as ACTIVITY_ID or ACTIVITY_VERSION_ID to keep performance predictable.