Search Results csr_resources_v

Overview

CSR_RESOURCES_V is a scheduler-module database view in Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2, owned by the CSR (Scheduler / Field Service Scheduler) product. As documented in the ETRM metadata, its stated purpose is to present "a view of resources used by Oracle Resources." In practice, the view consolidates resource master data from the Resource Manager schema with the party-site and location (geography) data that the Scheduler engine requires to place resources on a map or dispatch grid. It therefore acts as a reporting and integration surface for anything that needs to know, for a given schedulable resource, where that resource is located and how its geometry was resolved.

The view is documented as "Not implemented in this database" in the ETRM excerpt, meaning it is a shipped, dictionary-defined object that may only be instantiated where the Scheduler component is installed. Consumers must verify its existence against their specific instance before relying on it in custom reporting.

Underlying Base Objects

The view text is defined over three base tables joined through the resource-address chain:

• JTF_RS_RESOURCE_EXTNS (aliased RES) — the Resource Manager extension table holding the resource identifier, category, time zone, and address reference.
• HZ_PARTY_SITES (aliased SIT) — the party-site assignment linking a party (or resource) to a physical location.
• HZ_LOCATIONS (aliased LOC) — the TCA location record containing the geometry used for spatial resolution.

The join is RES.ADDRESS_ID = SIT.PARTY_SITE_ID AND SIT.LOCATION_ID = LOC.LOCATION_ID. Significant derivation logic is delegated to the CSR_SCHEDULER_PVT package, which supplies the locus segment, side, spot, latitude, longitude, and the location finder indicator via GET_LOCUS_SEGMENTID, GET_LOCUS_SIDE, GET_LOCUS_SPOT, LOCATION_FINDER_USED, GET_LOCUS_LAT, and GET_LOCUS_LON. Although the ETRM metadata lists "none documented" for referenced base objects, the view text itself documents these three tables explicitly.

Key Columns

• RESOURCE_ID — Primary identifier of the schedulable resource.
• RESOURCE_TYPE — Derived from RES.CATEGORY via DECODE; maps EMPLOYEE, PARTNER, SUPPLIER_CONTACT, PARTY, and OTHER to internal type codes RS_EMPLOYEE, RS_PARTNER, RS_SUPPLIER, RS_PARTY, and RS_OTHER respectively. This normalizes disparate resource categories into Scheduler-recognized types.
• TIME_ZONE — Resource's scheduling time zone, essential for correct appointment rendering.
• LOCATION_FINDER_USED — The value returned by CSR_SCHEDULER_PVT.LOCATION_FINDER_USED(LOC.GEOMETRY); it records which location-finding mechanism resolved the geometry, a key audit field for geocoding quality.
• LOCUS_SEGMENTID, LOCUS_SIDE, LOCUS_SPOT — Parsed locus components derived from the geometry, used for map placement and route sequencing.
• LOCATION_ID — TCA location identifier, the foreign key back to HZ_LOCATIONS.
• LOCUS_LAT, LOCUS_LON — Latitude and longitude extracted from the geometry, used directly by mapping and proximity calculations.

Common Use Cases and Queries

Typical uses include resource-map reporting, geocoding audit (identifying resources whose location was resolved by a fallback finder), and integration feeds into dispatch or mobile applications. A representative query listing resources with resolved coordinates is:

• SELECT RESOURCE_ID, RESOURCE_TYPE, TIME_ZONE, LOCATION_FINDER_USED, LOCUS_LAT, LOCUS_LON FROM CSR_RESOURCES_V WHERE LOCUS_LAT IS NOT NULL;
• SELECT RESOURCE_TYPE, LOCATION_FINDER_USED, COUNT(*) FROM CSR_RESOURCES_V GROUP BY RESOURCE_TYPE, LOCATION_FINDER_USED;
• SELECT RESOURCE_ID FROM CSR_RESOURCES_V WHERE LOCATION_FINDER_USED <> 'PRIMARY'; (adjust to your configured finder values)

Because the geometry parsing is performed by the CSR_SCHEDULER_PVT package at query time, these statements can be costlier than queries against flat tables; restricting by LOCATION_ID or RESOURCE_ID is advisable in production reporting.