Search Results csf_selected_resources_v

Overview

CSF_SELECTED_RESOURCES_V is a dictionary view owned by the APPS schema in Oracle E-Business Suite, residing in the CSF (Field Service) product family. Its stated purpose is to hold the UI selected resources — that is, the set of resources currently selected within the Field Service application interface at any given point in a user session. Rather than persisting a materialized list, the view derives its content dynamically at query time by consulting the territory definition and the CSV_UTIL_PVT selection-checking API. In the R12.1.1 and 12.2.2 releases the object carries a VALID status, indicating that it compiles and executes correctly against the underlying territory schema, and it is documented in the ETRM repository as a read-only reporting and integration surface rather than a transactional entity. Consequently, its role is to expose a governed, normalized projection of selected resources for downstream reporting, concurrent processing, and service-oriented integration, while shielding callers from the complexity of territory membership evaluation.

Underlying Base Objects

The view is defined over the territory and territory-resource foundations of the Oracle CRM/JTF layer, with additional programmatic dependencies on CSF and JTF utility code. The documented base objects are:

• JTF_TERR_RSC_ALL (SYNONYM) — the territory-to-resource assignment table, supplying RESOURCE_TYPE and RESOURCE_ID.
• CSF_RESOURCE_PUB (PACKAGE) — the Field Service resource public API used in resource resolution logic.
• CSF_UTIL_PVT (PACKAGE) — supplies the selection predicate IS_TERR_SELECTED and the RESOURCE_NAME derivation function GET_OBJECT_NAME.
• JTF_NUMBER_TABLE (TYPE) — the numeric collection type used to pass territory identifier sets between the view logic and the utility package.

The view combines JTF_TERR_ALL (TA) and JTF_TERR_RSC_ALL (TR) on TA.TERR_ID = TR.TERR_ID, filtered by CSF_UTIL_PVT.IS_TERR_SELECTED(TA.TERR_ID) <> 0. Because the filter and the RESOURCE_NAME resolution are both function calls against package state, the view is not a simple join; it reflects the current territory selection context. DISTINCT eliminates duplicates arising from overlapping territory assignments, so a resource appearing in multiple selected territories is returned exactly once.

Key Columns

The view exposes three columns:

• RESOURCE_TYPE — the classification of the selected resource (for example, a party, employee, or organization category), used to determine which resolution logic applies when deriving a display name.
• RESOURCE_ID — the primary identifier of the selected resource within its resource type; together with RESOURCE_TYPE it forms the logical key of each returned row.
• RESOURCE_NAME — the human-readable name of the resource, computed at runtime by CSF_UTIL_PVT.GET_OBJECT_NAME using RESOURCE_TYPE and RESOURCE_ID.

Because RESOURCE_NAME is function-derived, it is not indexed and its value depends on the current definition of the referenced entity; changes to a resource's name or type are visible immediately on the next query.

Common Use Cases and Queries

Typical uses include populating LOVs and report parameters for Field Service scheduling, validating resource selection before dispatch operations, and feeding integration interfaces that require the active resource set. A minimal query is:

SELECT resource_type, resource_id, resource_name FROM apps.csf_selected_resources_v;

Because the underlying filter is driven by territory selection, callers should treat results as session- and context-sensitive; any query returning these rows must be executed under the appropriate Field Service responsibility, and results should not be cached across sessions. When joining to other tables, use RESOURCE_TYPE and RESOURCE_ID as the composite key. Note that Oracle recommends confining such queries to the supported APPS synonyms (for example JTF_TERR_RSC_ALL) rather than querying base tables directly, and that the function-based predicates can incur performance overhead on large territory populations.