C_DfsScenClfnObjectCharcVal

DDL: C_DFSSCENCLFNOBJECTCHARCVAL SQL: CDFSSCNCLFNVAL Type: view CONSUMPTION

Consumption View for Scenario Classification values

C_DfsScenClfnObjectCharcVal is a Consumption CDS View that provides data about "Consumption View for Scenario Classification values" in SAP S/4HANA. It reads from 2 data sources (I_ClfnCharcDescForKeyDate, I_ClfnObjectCharcValForKeyDate) and exposes 14 fields with key fields ClfnObjectID, ClfnObjectTable, CharcInternalID, ClassType, CharcValue. It is exposed through 1 OData service (UI_DFS_SCENARIO). It is used in 1 Fiori application: Manage Planning Scenarios.

Data Sources (2)

SourceAliasJoin Type
I_ClfnCharcDescForKeyDate I_ClfnCharcDescForKeyDate inner
I_ClfnObjectCharcValForKeyDate I_ClfnObjectCharcValForKeyDate from

Annotations (11)

NameValueLevelField
AbapCatalog.sqlViewName CDFSSCNCLFNVAL view
Metadata.allowExtensions true view
AbapCatalog.compiler.compareFilter true view
AbapCatalog.preserveKey true view
EndUserText.label Consumption View for Scenario Classification values view
AccessControl.authorizationCheck #CHECK view
ClientHandling.algorithm #SESSION_VARIABLE view
VDM.viewType #CONSUMPTION view
ObjectModel.usageType.dataClass #TRANSACTIONAL view
ObjectModel.usageType.serviceQuality #B view
ObjectModel.usageType.sizeCategory #L view

OData Services (1)

ServiceBindingVersionContractRelease
UI_DFS_SCENARIO UI_DFS_SCENARIO V2 C1 NOT_RELEASED

Fiori Apps (1)

App IDApp NameTypeDescription
F4697 Manage Planning Scenarios Transactional A scenario consists of one or more possible alternatives. Alternatives can be alternative response options to a threat or natural disaster. Each alternative includes a set of objects related to a capability code, and they are combined with active force elements at alternative task level. A scenario is used in capability-based planning and development processes. It collects different objects related to the capability and actual active force elements (or reference force elements) and allows the user to compare the scenario alternative requirement defined by the capabilities assigned to it with active force elements that could possibly fulfil the requirements. A planner can view the crucial personnel, material and training requirements (job, FMPO, METL) linked to each required capability code in a scenario alternative task. This allows the planner to evaluate whether the identified unit is now ready and prepared to perform the operation at hand. This scenario master data set is also used as the basis for any tailored and complex readiness and preparedness evaluations, reporting or simulations. Two types of scenarios are available: 1. Preparedness monitoring scenario 2. Capability development scenario The Preparedness monitoring scenario is a scenario that is monitored periodically. The aim is to identify shortcomings in capabilities and provide input for different downstream processes, such as material replenishments or any human resources management activities. The capability development scenario relates to the introduction of new or upgraded capabilities in defense.

Manage Planning Scenarios

Business Role: Organizational Planner - Capabilities

A scenario consists of one or more possible alternatives. Alternatives can be alternative response options to a threat or natural disaster. Each alternative includes a set of objects related to a capability code, and they are combined with active force elements at alternative task level.

Fields (14)

KeyFieldSource TableSource FieldDescription
KEY ClfnObjectID _ClfnObjectCharcVal ClfnObjectID
KEY ClfnObjectTable _ClfnObjectCharcVal ClfnObjectTable
KEY CharcInternalID _ClfnObjectCharcVal CharcInternalID Characteristic Internal ID
KEY ClassType _ClfnObjectCharcVal ClassType X Flag
KEY CharcValue _ClfnObjectCharcVal CharcValue Char. Value
CharcValuePositionNumber _ClfnCharcValue CharcValuePositionNumber
CharcDescription _ClfnCharcDesc CharcDescription
CharcValueDescription _ClfnCharcValueDesc CharcValueDescription
CharcFromNumericValue _ClfnObjectCharcVal CharcFromNumericValue Value from
CharcFromNumericValueUnit _ClfnObjectCharcVal CharcFromNumericValueUnit Internal UoM
CharcToNumericValue _ClfnObjectCharcVal CharcToNumericValue Value to
CharcToNumericValueUnit _ClfnObjectCharcVal CharcToNumericValueUnit Internal UoM
_Characteristic _ClfnObjectCharcVal _Characteristic
DfsScenarioCharacteristicValue

Derived SQL interpretation, reconstructed from the parsed view metadata (data sources, associations, and field mappings). SAP annotations are omitted and the structure is reformulated as SQL — this is a functional approximation, not the verbatim SAP source.

-- Derived SQL interpretation of CDS view C_DfsScenClfnObjectCharcVal.
-- Reconstructed from parsed metadata (data sources, associations, fields).
-- SAP annotations are omitted and the structure is reformulated as SQL;
-- this is a functional approximation, not the verbatim SAP source. Some join
-- conditions may be unavailable and a few CDS constructs are kept as-is.
-- SQL view name: CDFSSCNCLFNVAL

CREATE VIEW C_DfsScenClfnObjectCharcVal AS
SELECT
  _ClfnObjectCharcVal.ClfnObjectID AS ClfnObjectID,
  _ClfnObjectCharcVal.ClfnObjectTable AS ClfnObjectTable,
  _ClfnObjectCharcVal.CharcInternalID AS CharcInternalID,
  _ClfnObjectCharcVal.ClassType AS ClassType,
  _ClfnObjectCharcVal.CharcValue AS CharcValue,
  _ClfnCharcValue.CharcValuePositionNumber AS CharcValuePositionNumber,
  _ClfnCharcDesc.CharcDescription AS CharcDescription,
  _ClfnCharcValueDesc.CharcValueDescription AS CharcValueDescription,
  _ClfnObjectCharcVal.CharcFromNumericValue AS CharcFromNumericValue,
  _ClfnObjectCharcVal.CharcFromNumericValueUnit AS CharcFromNumericValueUnit,
  _ClfnObjectCharcVal.CharcToNumericValue AS CharcToNumericValue,
  _ClfnObjectCharcVal.CharcToNumericValueUnit AS CharcToNumericValueUnit,
  _ClfnObjectCharcVal._Characteristic AS _Characteristic,
  cast( '' as abap.char(70) ) AS DfsScenarioCharacteristicValue
FROM I_ClfnObjectCharcValForKeyDate
INNER JOIN I_ClfnCharcDescForKeyDate ON /* join condition not captured in parsed metadata */
;