Search Results csf_r_request_filters




Overview

CSF_R_REQUEST_FILTERS is a transactional configuration table in the CSF (Field Service) module of Oracle E-Business Suite, present identically in releases 12.1.1 and 12.2.2. It stores the filter settings associated with a scheduled service request. In the Field Service scheduling workflow, dispatchers and planners refine the population of service requests presented to them using saved filter criteria; each row in this table represents the enablement and association of a defined filter to a specific scheduling request context. The table therefore acts as the bridge between a reusable filter definition and the scheduling request to which it applies.

The ETRM metadata classifies this object, using a heuristic Data Vault analysis of its foreign key structure, as standalone. From a modeling standpoint this suggests the table behaves as an independent satellite-like structure carrying descriptive attributes (enablement flag, audit columns, version number) rather than a pure junction link. The classification is a modeling suggestion only; functionally the table contains two foreign keys and could equally be interpreted as a lightweight link between the filter definition and the scheduling request.

Key Information Stored

The table is documented with eleven columns in the ETRM 12.2.2 physical schema (owner CSF). The most significant are:

  • REQUEST_FILTER_ID — the surrogate primary key, enforced by the CSF_R_REQUEST_FILTERS_PK constraint. This is a system-generated identifier with no business meaning; it uniquely identifies each filter-setting row.
  • FILTER_ID — identifies the underlying filter definition being applied. This is the principal business-key candidate, since it links the row to the filter's semantic definition.
  • SCHED_REQUEST_ID — foreign key to CSF_R_SCHED_REQUESTS, tying the filter setting to a specific scheduling request.
  • ENABLED_FLAG — controls whether the filter is active for the associated request. This is the primary mutable attribute and the one most often reported on, typically valued Y/N.
  • SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, providing multi-tenant row-level security partitioning; only rows visible to the querying responsibility's security group are returned.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS audit who/when columns populated by the framework.
  • OBJECT_VERSION_NUMBER — the optimistic-locking version column used by the OA Framework to detect concurrent updates.

The combination of FILTER_ID and SCHED_REQUEST_ID is the natural business key candidate; no additional unique index beyond the primary key is documented in the ETRM metadata.

Common Use Cases and Queries

Typical scenarios include diagnosing why a dispatcher cannot see expected requests, auditing which filters are enabled for a scheduling request, and reporting on filter usage across the organisation.

  • List active filters for a given scheduling request:
    SELECT REQUEST_FILTER_ID, FILTER_ID, ENABLED_FLAG
    FROM   CSF.CSF_R_REQUEST_FILTERS
    WHERE  SCHED_REQUEST_ID = :sched_request_id
    AND    ENABLED_FLAG = 'Y';
  • Join to scheduling requests to enrich filter settings with request context:
    SELECT f.REQUEST_FILTER_ID, f.FILTER_ID, r.SCHED_REQUEST_ID
    FROM   CSF.CSF_R_REQUEST_FILTERS f,
           CSF.CSF_R_SCHED_REQUESTS r
    WHERE  f.SCHED_REQUEST_ID = r.SCHED_REQUEST_ID
    AND    f.SECURITY_GROUP_ID = :security_group_id;
  • Audit recently changed filter configuration using the audit columns (LAST_UPDATED_BY, LAST_UPDATE_DATE) for change-tracking reports.

All queries should bind SECURITY_GROUP_ID to respect the multi-org security model used throughout CSF.

Related Objects

  • CSF_R_SCHED_REQUESTS — referenced via SCHED_REQUEST_ID; the parent scheduling request record.
  • FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; governs row-level access.
  • The filter definition table implied by FILTER_ID (the CSF filter master), which supplies the criteria the setting enables.
  • Field Service concurrent programs and OA Framework dispatch pages that read ENABLED_FLAG when building the request list presented to planners.

The two documented foreign keys make CSF_R_SCHED_REQUESTS and FND_SECURITY_GROUPS the definitive related objects for joins and integrity checks.