Results for “role_to_play”

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

Overview

OTA_RESOURCE_USAGES is a transactional table in the Oracle EBS Learning Management (OTA) module. It records the requirement that a specific activity version places on a resource, or on a resource type. In EBS terminology, a "resource usage" expresses what a training activity needs — an instructor, a room, a piece of equipment, or a class of resource — and how much of it is required. Each row therefore acts as the junction between an activity version and either a concrete suppliable resource or a broader resource type, carrying the scheduling and quantity attributes that govern how the requirement is satisfied.

Under the heuristic Data Vault classification derived from its foreign key structure, OTA_RESOURCE_USAGES is best modeled as a link table. Its role is associative: it resolves the many-to-many relationship between activity versions and suppliable resources, and it also participates in the offering context through OFFERING_ID. This classification is a modeling suggestion rather than a physical constraint; the table itself is a standard EBS 12.1.1 / 12.2.2 relational object owned by the OTA schema.

Key Information Stored

The table contains 39 documented columns. The most significant are:

• RESOURCE_USAGE_ID — the surrogate primary key, enforced by the unique index OTA_RESOURCE_USAGES_PK. This is the column most commonly used in application joins and API calls.
• SUPPLIED_RESOURCE_ID — foreign key to OTA_SUPPLIABLE_RESOURCES, identifying the specific resource reserved or required.
• ACTIVITY_VERSION_ID — foreign key to OTA_ACTIVITY_VERSIONS, tying the usage to a particular version of an activity.
• OFFERING_ID — foreign key to OTA_OFFERINGS, linking the usage to the offering under which the activity is delivered.
• RESOURCE_TYPE — indicates the category of resource when a generic (rather than specific) resource is required.
• REQUIRED_FLAG — flags whether the resource is mandatory for the activity.
• QUANTITY — the number of units of the resource required.
• ROLE_TO_PLAY — the role the resource fulfils, for example instructor or facilitator.
• USAGE_REASON — the business justification for the requirement.
• START_DATE and END_DATE — the effective window during which the resource is required.
• COMMENTS — free-text notes attached to the usage.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the OTA APIs.
• RUD_INFORMATION_CATEGORY and RUD_INFORMATION1 through RUD_INFORMATION20 — descriptive flexfield segments capturing customer-specific attributes.

Only RESOURCE_USAGE_ID is documented as a unique business-key candidate; the FK columns are non-unique by nature, since one activity version may require many resources.

Common Use Cases and Queries

Typical scenarios include reporting resource demand for scheduled classes, reconciling instructor assignments, auditing mandatory versus optional resource requirements, and extracting data for learning-management dashboards.

A common join pattern retrieves usages with their activity version and resource:

• SELECT ru.resource_usage_id, ru.activity_version_id, ru.supplied_resource_id, ru.quantity, ru.required_flag
• FROM ota_resource_usages ru
• WHERE ru.activity_version_id = :version_id
• ORDER BY ru.start_date;

To find mandatory resources for an offering, filter on OFFERING_ID and REQUIRED_FLAG, joining to OTA_SUPPLIABLE_RESOURCES for resource names. Because the table is version-aware, queries that compare requirements across activity versions should always constrain ACTIVITY_VERSION_ID. The START_DATE and END_DATE columns support effective-dated reporting, and the RUD flexfield segments support customer-specific filtering where descriptive flexfields have been configured.

Related Objects

• OTA_ACTIVITY_VERSIONS — joined on ACTIVITY_VERSION_ID; supplies the activity context for each usage.
• OTA_SUPPLIABLE_RESOURCES — joined on SUPPLIED_RESOURCE_ID; supplies the resource detail.
• OTA_OFFERINGS — joined on OFFERING_ID; supplies the offering under which the activity is delivered.
• OTA_RESOURCE_USAGES_PK — the primary key index on RESOURCE_USAGE_ID, used by constraint validation and lookups.
• OTA Resource Usage APIs — the Learning Management PL/SQL APIs that insert, update, and delete rows in this table, populating OBJECT_VERSION_NUMBER and the WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN).