Search Results trainer_name

Overview

APPS.OTFV_EVENTS_WITH_TRAINER is a read-only reporting view in the Oracle E-Business Suite Training (OTF/OTA) schema. It presents a consolidated, denormalized projection of training events joined to the trainers booked against them, combining event descriptive attributes, trainer identity and role, and the resource booking record that links the two. Because it exposes resource booking status through a lookup decode, the view is directly relevant to the search term resource_booking_status: the column booking_status is generated by calling HR_BIS.BIS_DECODE_LOOKUP('RESOURCE_BOOKING_STATUS', trb.status), resolving the internal status code on OTA_RESOURCE_BOOKINGS into a meaningful, user-facing lookup value.

The view is defined with the WITH READ ONLY clause, confirming it is intended for query, reporting, and integration consumption rather than DML. It is scoped to a single business group via OTA_GENERAL.GET_BUSINESS_GROUP_ID, making it a natural source for concurrent programs and BI Publisher reports executed in a specific operating unit context.

Underlying Base Objects

The view is defined over five base objects plus two supporting packages:

• OTA_EVENTS (synonym, alias EVT) — the driving event record; joined on event_id and supplies event_id and parent_offering_id.
• OTA_EVENTS_TL (synonym, alias ETT) — the translated event title; joined on event_id and restricted to language = USERENV('LANG').
• OTA_RESOURCE_BOOKINGS (synonym, alias TRB) — the booking record linking an event to a supplied resource; joined on event_id.
• OTA_SUPPLIABLE_RESOURCES (synonym, alias TSR) — the pool of suppliable resources; joined on supplied_resource_id and filtered to resource_type = 'T' to isolate trainers.
• OTA_SUPPLIABLE_RESOURCES_TL (synonym, alias TST) — the translated resource (trainer) name; joined on supplied_resource_id and language-restricted.
• HR_BIS (package) — provides BIS_DECODE_LOOKUP to translate the booking status code.
• OTA_GENERAL (package) — provides GET_BUSINESS_GROUP_ID for business group security filtering.

Key Columns

• event_title — translated title of the training event (from OTA_EVENTS_TL).
• trainer_name — translated name of the booked trainer (from OTA_SUPPLIABLE_RESOURCES_TL).
• trainer_role — trb.role_to_play, the role the trainer plays on the event.
• date_of_booking — trb.date_booking_placed, when the booking was created.
• booking_status — decoded RESOURCE_BOOKING_STATUS lookup value, the key column for booking-state reporting.
• required_from / required_to — the required date range for the trainer booking.
• booking_comments, resource_booking_id, supplied_resource_id, event_id, offering_id — comments and surrogate keys for joining back to detail tables.

Common Use Cases and Queries

Typical use cases include trainer booking status reports, event-to-trainer assignment listings, and data extracts feeding scheduling analytics. A representative query filtered on the searched attribute:

• SELECT event_title, trainer_name, trainer_role, booking_status, required_from, required_to
• FROM apps.otfv_events_with_trainer
• WHERE booking_status = 'CONFIRMED'
• ORDER BY required_from;

To count bookings per status or per trainer, aggregate over booking_status and trainer_name. Because the view enforces business-group filtering and language translation automatically, it is well suited to localized, multi-organization ETRM reporting without additional joins.