Results for “internal_address”

2 results




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

Overview

The OTFV_RESOURCES_BOOKED view is an Oracle E-Business Suite 12.1.1 / 12.2.2 business view owned by the APPS schema and registered under the OTA – Learning Management (Oracle Training Administration) product. ETRM documentation describes it as a "business view template from which the flexfield view is generated," meaning it serves as the semantic layer that exposes descriptive, decoded column names over the underlying OTA transactional tables. This view is primarily consumed by Oracle Business Intelligence (OBIEE) and other reporting/integration tools that require user-friendly column labels rather than raw foreign keys and lookup codes.

The view consolidates resource booking activity — a critical component of training delivery logistics — with associated event, activity, supplier, finance, and resource master data. It answers operational questions such as which resources were booked for which event, at what cost, in which currency, and by whom. The invoice_currency concept the user sought is addressed via COST_CURRENCY and the currency columns derived from OTA_FINANCE_LINES (e.g., the decoded CURRENCY_CODE used with INVOICE_AMOUNT).

Underlying Base Objects

The view is defined across a broad set of OTA tables and supporting objects. Documented referenced base objects include:

Key Columns

Common Use Cases and Queries

Typical uses include resource utilization reporting, training cost analysis by currency, and supplier booking audits.

Example – bookings with invoice currency:

SELECT event_title,
       resource_name,
       supplier_name,
       invoice_amount,
       cost_currency
FROM   apps.otfv_resources_booked
WHERE  booking_status IS NOT NULL
ORDER BY event_title;

Example – resource cost by currency for an event:

SELECT event_title,
       cost_currency,
       SUM(cost_amount) total_cost
FROM   apps.otfv_resources_booked
GROUP BY event_title, cost_currency;

Because the view is a flexfield-enabled business view, it is best queried read-only for BI extract, discoverer, and custom concurrent program output rather than for transactional updates.