Search Results consumable_flag

Overview

APPS.OTA_SUPPLIABLE_RESOURCES_VL is a Learning Management (OTA) view that lists information about suppliable resources within Oracle E-Business Suite 12.1.1 and 12.2.2. Suppliable resources represent the reusable assets, venues, trainers, equipment, and vendor-supplied materials that can be attached to a training offering or event. The view exposes these resources in a translatable, language-stripped form so that reports, concurrent programs, and integration interfaces can retrieve resource attributes without joining the translation table manually.

The object is registered in ETRM with a status of VALID in the APPS schema, but the documentation explicitly notes that it is scheduled for a future release. This is an important caveat for implementers: while the view compiles and returns data, Oracle does not position it as a supported, committed interface in the current release. Consumers should therefore treat it as an internal or interim object and verify against their own patch level before depending on it in production customizations. The _VL suffix follows the standard EBS convention for "view with language," combining the base table with its translation table to return a single row per resource in the session's language.

Underlying Base Objects

The view is defined over two documented base objects:

• OTA_SUPPLIABLE_RESOURCES (SYNONYM) — the primary table holding the non-translatable resource attributes such as identifiers, cost, capacity, dates, and the CONSUMABLE_FLAG.
• OTA_SUPPLIABLE_RESOURCES_TL (SYNONYM) — the translation table holding language-dependent columns such as NAME and SPECIAL_INSTRUCTION.

The join is performed on SUPPLIED_RESOURCE_ID, with the translation row filtered by SRL.LANGUAGE = USERENV('LANG'). This ensures each query returns exactly one translated row matching the runtime session language rather than the full translation set. The base table alias is TSR and the translation alias is SRL in the documented view text. Both underlying objects are exposed to APPS through synonyms, so the view reads them directly without schema qualification.

Key Columns

The view projects the full column list from the base resource table plus the two translated columns. Notable columns include:

• SUPPLIED_RESOURCE_ID — primary identifier and the join key to the translation table.
• CONSUMABLE_FLAG — the column the user searched for. It indicates whether a suppliable resource is consumable, typically distinguishing one-time/replenishable items (such as printed course materials) from persistent resources (such as a trainer or a room).
• RESOURCE_DEFINITION_ID, RESOURCE_TYPE, BUSINESS_GROUP_ID — classify and scope the resource within the business group.
• VENDOR_ID, SUPPLIER_REFERENCE — identify the external supplier of the resource.
• CAPACITY, COST, COST_UNIT, CURRENCY_CODE — quantity and pricing characteristics.
• START_DATE, END_DATE, LEAD_TIME — availability and scheduling windows.
• TRAINING_CENTER_ID, LOCATION_ID, TRAINER_ID — physical and personnel associations.
• NAME, SPECIAL_INSTRUCTION — the translated columns sourced from the TL table.
• TSR_INFORMATION_CATEGORY and TSR_INFORMATION1 through TSR_INFORMATION20 — a standard flexible descriptive flexfield block.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER.

Common Use Cases and Queries

The view is most useful for reporting on resource inventory and for identifying consumable versus non-consumable resources. A representative query filtering on the searched column is:

• SELECT supplied_resource_id, name, resource_type, consumable_flag FROM apps.ota_suppliable_resources_vl WHERE consumable_flag = 'Y';
• SELECT supplied_resource_id, name, cost, currency_code, vendor_id FROM apps.ota_suppliable_resources_vl WHERE resource_definition_id = :p_resource_definition_id;
• SELECT supplied_resource_id, name, consumable_flag, capacity, cost_unit FROM apps.ota_suppliable_resources_vl WHERE business_group_id = :p_bg_id AND consumable_flag = 'N';

Typical scenarios include cost roll-up reporting for training events, supplier reconciliation by vendor, and integration extraction into external scheduling or inventory systems. Because the view is documented as pending a future release, all such usage should be validated against the target patch level, and custom code should avoid hard dependencies on the object remaining stable across upgrades.