In a InfoProvider CDS view, each key figure should be defined with @DefaultAggregation: #SUM, #MIN or #MAX, or @Aggregation.default: #NOP, #SUM, #MIN or #MAX (the new annotation as of Note 2381161).
Otherwise it is treated as characteristic. When the data type is not supported for a characteristic, the field is ignored and not included in the InfoProvider metadata before Note 2771186. After this note, the field gets a default NO2 aggregation and becomes a NO2 key figure..
Below is an example CDS that define a key figure with case statement:
In this CDS, key figure AAFlightPrice doesn't have default aggregation setting.
When activate the CDS, system gives error: Field AAFLIGHTPRICE ignored: Data type CURR not allowed for characteristic
In transaction RSRTS_ODP_DIS, display ODP ZGL_SFLIGHTV, field AAFlightPrice is not included: (before Note 2771186)
This means field AAFlightPrice can't be used in the CDS query defined on this InfoProvider.
If a CDS query is define as below:
When check syntax or activate, errors are displayed as above:
Could not resolve field yyy (ODP zzz) RSRTS_CDS028
Error while processing select entry number xx (at Line xx Column xx)
To solve the error, change the InfoProvider CDS and add @DefaultAggregation for field AAFlightPrice:
Here is an example of key figure with default aggregation NO2.
Define a simple CDS quey like this:
Run it in RSRT, key figure FirstClassSeats gets 'NOP' because there are more than one values to be aggregated.
Drill down connid, key figure FirstClassSeats gets a value since there is only one value to be aggregated.