Search Results activity_language

Overview

APPS.OTFV_RESOURCE_CHECKLIST is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is registered in the application design layer under FND Design Data OTA.OTFV_RESOURCE_CHECKLIST and is documented as VALID. The view exposes information about the minimum resources required to conduct an activity within the Oracle Training Administration (OTA) module of Oracle EBS. Because it is a BIS view, it is intended primarily for reporting, ad-hoc querying, and downstream integration rather than for direct transactional DML; it denormalizes data drawn from several OTA and HR base objects so that a single row presents a resource checklist line alongside its associated activity definition and version attributes.

Underlying Base Objects

The view is defined over a broad set of synonymed base tables, views, and packages. Core transactional sources include OTA_ACTIVITY_DEFINITIONS and OTA_ACTIVITY_DEFINITIONS_TL (the activity header and its translated columns), OTA_ACTIVITY_VERSIONS and OTA_ACTIVITY_VERSIONS_TL (version-level attributes such as capacity and duration), OTA_RESOURCE_USAGES (the resource requirement lines that drive the checklist), OTA_SUPPLIABLE_RESOURCES and OTA_SUPPLIABLE_RESOURCES_TL (resource master and translations), OTA_OFFERINGS, OTA_ACT_CAT_INCLUSIONS, and OTA_CATEGORY_USAGES/OTA_CATEGORY_USAGES_TL. Supporting descriptive data is joined from MTL_SYSTEM_ITEMS_B and ORG_ORGANIZATION_DEFINITIONS (inventory item and organization context), HR_ALL_ORGANIZATION_UNITS_TL, PER_ALL_PEOPLE_F, and PO_VENDORS for sponsor, manager, and supplier identification, plus FND_LANGUAGES/FND_LANGUAGES_TL for language. Package dependencies include HR_BIS, HR_GENERAL, HR_SECURITY (business group and row-level security), and OTA_GENERAL, which supply business-group filtering and utility logic.

Key Columns

The view returns identifiers and descriptive attributes for both checklist resources and their parent activities. Resource-level columns include RESOURCE_TYPE, RESOURCE_NAME, RESOURCE_QUANTITY, RESOURCE_REQUIRED, RESOURCE_USAGE, RESOURCE_ROLE, RESOURCE_START_DATE, RESOURCE_END_DATE, RESOURCE_USAGE_COMMENTS, and the keys RESOURCE_CHECK_LIST_ID, SUPPLIED_RESOURCE_ID, INVENTORY_ORGANIZATION_ID, and INVENTORY_ITEM_ID. Activity-level columns include ACTIVITY_NAME, ACTIVITY_DESCRIPTION, ACTIVITY_AUDIENCE, ACTIVITY_OBJECTIVES, ACTIVITY_LANGUAGE, ACTIVITY_STATUS, ACTIVITY_FROM, ACTIVITY_TO, NEXT_ACTIVITY, DURATION and DURATION_UNITS, ALLOW_EXPENSES, PROFESSIONAL_CREDITS_TYPE, PROFESSIONAL_CREDIT_AMOUNT, SUCCESS_CRITERIA, SPONSOR_BY, MANAGED_BY, and ACTIVITY_TYPE. Enrollment capacity is exposed through MINIMUM_STUDENTS, MAXIMUM_STUDENTS, and MAXIMUM_INTERNAL_STUDENTS, which is directly relevant to the search term. Security and context keys include BUSINESS_GROUP_NAME and BUSINESS_GROUP_ID, ACTIVITY_ID, ACTIVITY_VERSION_ID, RCO_ID, SPONSOR_ORGANIZATION_ID, MANAGED_BY_PERSON_ID, LANGUAGE_ID, and SUPERSESED_ACT_VERSION_ID, plus the _DF and _KF flexfield columns.

Common Use Cases and Queries

Typical uses include reporting on resource requirements per activity, verifying that scheduled resources and enrollment limits are consistent, and feeding integration extracts. A representative query to retrieve capacity and resource details for activities in a given business group is:

• SELECT activity_name, minimum_students, maximum_students, maximum_internal_students, resource_name, resource_quantity FROM apps.otfv_resource_checklist WHERE business_group_id = :p_bg_id AND activity_id = :p_activity_id;
• SELECT activity_name, resource_type, resource_role, resource_start_date, resource_end_date FROM apps.otfv_resource_checklist WHERE resource_required = 'Y' ORDER BY activity_name, resource_start_date;
• SELECT activity_name, maximum_students - maximum_internal_students AS external_capacity FROM apps.otfv_resource_checklist WHERE activity_status = 'ACTIVE';

Because the view enforces business-group security through HR_SECURITY and HR_GENERAL, queries should always constrain BUSINESS_GROUP_ID or rely on the session's security profile. The presence of both ID and translated name columns makes the view suitable for multi-language reporting, while the inclusion of version keys supports historical comparison of capacity and resource checklists across activity versions.