Search Results csf_r_scenario_values_pk




Overview

CSF_R_SCENARIO_VALUES is a transaction-level configuration table in the CSF (Field Service) product family of Oracle E-Business Suite, valid in release 12.1.1 and 12.2.2. It stores the filter parameter values that are associated with a given scenario. In the ETRM scheduling and assignment engine, a scenario defines a reusable set of filtering conditions, and each individual condition is expressed as a parameter together with the value it must satisfy. CSF_R_SCENARIO_VALUES is the child table that materializes those parameter-value pairings, allowing a single scenario to carry multiple simultaneous filter criteria.

From a dimensional modeling perspective, the mined foreign-key structure classifies this object heuristically as standalone. No formal Data Vault classification was supplied in the documentation, so the object is best treated as a descriptive detail table rather than an enforced hub, link, or satellite. Where such a classification is required, the table would most naturally behave as a satellite attached to the scenario and filter-parameter keys, capturing the value attributes in context.

Key Information Stored

The table is owned by the CSF schema and contains eleven documented columns in the 12.2.2 physical schema. The most significant columns are:

The surrogate SCENARIO_VALUE_ID is distinct from the business-key combination of SCENARIO_ID and FILTER_PARAM_ID, which is the meaningful identifier from an application standpoint.

Common Use Cases and Queries

Developers and analysts use this table to reconstruct the complete set of filter conditions defined for a scenario, to audit scenario configuration, and to diagnose assignment or scheduling behavior driven by scenario filters. A typical pattern resolves the human-readable parameter name through the parent parameter table:

  • List all values for a scenario: SELECT sv.scenario_value_id, sv.filter_param_id, sv.param_value FROM csf.csf_r_scenario_values sv WHERE sv.scenario_id = :scenario_id;
  • Join to parameter definitions: SELECT sv.scenario_id, fp.parameter_name, sv.param_value FROM csf.csf_r_scenario_values sv, csf.csf_r_filter_params_b fp WHERE sv.filter_param_id = fp.filter_param_id AND sv.scenario_id = :scenario_id;
  • Security-scoped reporting: filter rows by SECURITY_GROUP_ID to respect responsibility-level data access.
  • Audit and change tracking: order by LAST_UPDATE_DATE to identify recently reconfigured scenarios.

Because the table is narrow and value-oriented, it is well suited to configuration migration scripts, scenario comparison reports, and validation routines that confirm each scenario has the expected parameter coverage.

Related Objects

  • CSF_R_FILTER_PARAMS_B — parent table referenced by FILTER_PARAM_ID; supplies the parameter definition (name, type) for each value row.
  • FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID; governs row-level security access.
  • CSF_R_SCENARIOS (or equivalent scenario header) — the logical parent identified by SCENARIO_ID, which anchors each value row to its owning scenario.
  • CSF_R_SCENARIO_VALUES_PK — the primary key constraint enforcing uniqueness of SCENARIO_VALUE_ID.
  • FND_OBJECTS / AOL audit views — standard EBS metadata that expose the created-by and last-updated-by relationships for reporting.

When joining, use SCENARIO_VALUE_ID for direct row retrieval, FILTER_PARAM_ID to reach parameter attributes, and SECURITY_GROUP_ID to enforce or verify access control.