Search Results rt_look

Overview

APPS.OTA_SUPPLIABLE_RESOURCES_V is a reporting and integration view within the Oracle E-Business Suite Training Administration (OTA) module. It exposes supplier-provided resources recorded in the OTA_SUPPLIABLE_RESOURCES entity, enriching the base record with translated names, vendor details, lookup meanings, and resource-definition context. The view consolidates data spanning the OTA schema (suppliable resources, resource definitions) and reference data owned by Oracle Purchasing (PO_VENDORS) and Oracle Human Resources (HR_LOOKUPS).

In the context of Oracle EBS 12.1.1 and 12.2.2, this view is commonly consumed by reports, concurrent programs, and custom integrations that need a denormalized, single-row-per-resource representation of external or cost-bearing training resources. It abstracts away the multi-table joins required to resolve vendor names, yes/no consumable flags, and resource type meanings, making it suitable for read-only reporting surfaces rather than transactional processing.

Underlying Base Objects

The view is defined over several documented base objects, joined through outer and inner relationships:

• OTA_SUPPLIABLE_RESOURCES (SYNONYM) — the primary driving table, aliased as TSR, holding the supplier resource records.
• OTA_SUPPLIABLE_RESOURCES_TL (SYNONYM) — the translated table, aliased SRT, supplying the language-specific resource name via a join on SUPPLIED_RESOURCE_ID filtered by USERENV('LANG').
• OTA_RESOURCE_DEFINITIONS (SYNONYM) — aliased RES, joined on RESOURCE_DEFINITION_ID to supply the ID_FLEX_NUM.
• PO_VENDORS (VIEW) — aliased VEN, outer-joined on VENDOR_ID to retrieve VENDOR_NAME.
• HR_LOOKUPS (VIEW) — joined twice, once as CF_LOOK for the 'YES_NO' consumable flag and once as RT_LOOK for the 'RESOURCE_TYPE' lookup, resolving code values to their MEANING.
• OTA_GENERAL (PACKAGE) — invoked as ota_general.fnd_currency_name to translate the currency code.
• HR_API (PACKAGE) — documented as a referenced base object, typically used for currency or localization utilities.

Key Columns

• SUPPLIED_RESOURCE_ID — primary identifier of the suppliable resource.
• NAME — language-specific resource name from the TL table.
• VENDOR_ID / VENDOR_NAME — supplier linkage and resolved vendor name.
• RESOURCE_DEFINITION_ID / ID_FLEX_NUM — reference to the resource definition and its key flex number.
• CONSUMABLE_FLAG / CF_LOOK.MEANING — consumable indicator and its yes/no meaning.
• RESOURCE_TYPE / RT_LOOK.MEANING — resource type code and lookup meaning (the value the "rt_look" alias resolves to).
• COST, COST_UNIT, CURRENCY_CODE — pricing attributes, with currency translated via ota_general.
• START_DATE, END_DATE, LEAD_TIME — availability and scheduling attributes.
• TRAINING_CENTER_ID, LOCATION_ID, TRAINER_ID — delivery-location and trainer references.
• TSR_INFORMATION1 through TSR_INFORMATION20 — the descriptive flexfield (DFF) context and attribute columns.
• OBJECT_VERSION_NUMBER and audit columns — concurrency control and standard WHO audit trail.

Common Use Cases and Queries

The view is typically used to report on active suppliable resources with resolved vendor, resource type, and consumable meanings. A representative query returning resources with their meanings and vendor:

• SELECT SUPPLIED_RESOURCE_ID, NAME, VENDOR_NAME, RESOURCE_TYPE, MEANING FROM APPS.OTA_SUPPLIABLE_RESOURCES_V; — but note the view exposes two MEANING columns, so aliasing via a wrapper is required.
• Reporting consumable versus non-consumable resources by vendor: SELECT VENDOR_NAME, CONSUMABLE_FLAG, MEANING, COUNT(*) FROM APPS.OTA_SUPPLIABLE_RESOURCES_V GROUP BY VENDOR_NAME, CONSUMABLE_FLAG, MEANING;
• Filtering by validity window: SELECT * FROM APPS.OTA_SUPPLIABLE_RESOURCES_V WHERE SYSDATE BETWEEN START_DATE AND END_DATE;
• Extracting DFF attributes for a specific training center: SELECT SUPPLIED_RESOURCE_ID, TSR_INFORMATION1, TSR_INFORMATION_CATEGORY FROM APPS.OTA_SUPPLIABLE_RESOURCES_V WHERE TRAINING_CENTER_ID = :p_center;

Because the underlying joins rely on HR_LOOKUPS and USERENV('LANG'), queries should run under a language-configured session. As a read-only view over standard OTA and dependent reference tables, it is safe for reporting and integration extracts, but should not be treated as an update surface.