Example: Custom CDS View using predefined

Virtual Data Model and Extend View in

S/4HANA
23 28 48,679

Purpose of this blog:

This blog intends to encourage you to enjoy high productivity of custom object development
by using predefined Virtual Data Model (VDM) in S/4HANA by providing the sample of
Custom CDS Views based on predefined VDM enhanced with Extend View. By using
predefined VDM, you may not have to create custom CDS Views for all entities. It is always
the case that predefined content is totally reusable but it is necessary to add some fields,
which is possible with Extend View.

The example Consumption View in this blog is Analytic Query supposed to be used in Fiori
Multidimensional Reporting, SAC and BusinessObjects, but predefined VDM and custom CDS
View can be used for OData based Fiori app, ABAP program, data source to BW, etc.

But before considering Extend View, please check if the fields can be extended with Custom
Fields and Logic, which could add fields with graphical Fiori app.

The source code in this blog works on S/4HANA 1709.

2020/9/19 added:

It would take long time, e.g. 2 hours, to activate Extend VIew for the CDS View which is used
in many other view. In the case, firstly, it is expected to check if extension would be possible
with Custom Fields and Logic as explained later. Even if it is not possible, then it might be
better to create another new custom CDS view to add the fields. e.g. I have added a custom
field in EKKO (Purchase doc header table) and want to add it in the custom CDS view using
I_PurchaseOrder as a source. In the case, instead of creating Extend View for
I_PurchaseOrder, Join EKKO again in the Custom CDS VIew. In the case, the activation time
for the custom CDS view should be much shorter, and in the case, the join of EKKO would
not happen twice as internally select statement is optimized. (Self-join-optimization). (Use
the same definition for @ClientHandling.algorithm to make it work.).

This blog should help how to deal with long activation time.

2020/9/27

Use metadata data extension for the VDM which includes @Metadata.allowExtensions:true
to change UI, Consumption, EndUserText annotations.
2021/2/6

How to activate Extend View in Background

1. Choose System → Services → Table maintenance → Extended table maintenance.

The initial screen of the Extended Table Maintenance appears.
2. Enter table name TACOBand choose Maintain.
Specify the object to be activated in the next screen with the object type and object
name.
3. Enter the object types and object names.
o There is an input helpfor the Type field that displays the possible object types.
4. Save your entries and exit the Extended table maintenance.
With the mass activation program, now schedule a background job for activating the
entries in table TACOB (call report RADMASG0).

See help page:

https://help.sap.com/viewer/12a2d87e6c531014bec0e63ea0208c21/7.0.37/en-
US/cf21f232446011d189700000e8322d00.html

There is also a good blog about that: https://blogs.sap.com/2020/10/26/mass-activating-

multiple-objects-in-background/

2023/5/16

By adding the following annotation, activation time can be shortened as checks are skipped,
but it is not officially supported. For test purpose, it could be used.

My motivation to write the blog

Predefined VDM is one of the key in S/4HANA arechitecture, although it is not emphasized
as is the object underneath, but in my understanding, not so many customers enjoy it. I think
one of the main reason should be that how to use Predefined VDM might not be clear for
them, and some would think it be useless as they have custom fields in the table or want to
add the field from other table but it would be impossible to add field to Predefined VDM. To
overcome those concerns, I provide the example code to use Predefined VDM including
Extend View with which fields can be added to standard Predefined VDM.

Le VDM prédéfini est l'une des clés de l'architecture S/4HANA, bien qu'il ne soit pas souligné
comme l'objet en dessous, mais à ma connaissance, peu de clients l'apprécient. Je pense que
l'une des principales raisons devrait être que la façon d'utiliser Predefined VDM n'est peut-
être pas claire pour eux, et certains penseraient que c'est inutile car ils ont des champs
personnalisés dans la table ou veulent ajouter le champ d'une autre table mais ce serait
impossible d'ajouter un champ à Predefined VDM. Pour surmonter ces problèmes, je fournis
l'exemple de code pour utiliser Predefined VDM, y compris Extend View avec lequel des
champs peuvent être ajoutés à Predefined VDM standard.

Target audience:
This blog is for the ones who want to create report and analytical apps. It is not only for
analytics experts but for all functional experts as it is expected to create report based on
CDS View, instead of traditional functions like ALV or Report Painter, which has been used by
functional experts. See SAP Note 2579584 and 2349297.

It is also for developers as CDS View can be used not only for analytical apps, but it can be
used in normal ABAP program.

Summary:
• Concrete samples of the predefined VDMs are explained to understand what exactly
the predefined VDM is.
• Samples of custom CDS View using predefined VDMs and Extend View to add fields
to predefined VDM are provided, as the best way to understand is to see the source.
The predefined VDM of Billing Document Item is associated to Sales Order Item in
the sample.
o In the sample Extend View, a CDS Wiew is associated, and a field is added
from the view.
o Considerations to use Extend View and limitations are included.
o In the sample of Consumption View, some advanced settings are included
(hoping it would help creating sophisticated Analytic Query, although it is not
the main topic of this blog).
▪ Add value help to a parameter using association.
▪ Set start/end date as consumption filtering value automatically using
lookup entry used in Date Function.
▪ Exception aggregations are used to avoid value duplication when
joining sales order and billing document.
• How to deal with “Not released” predefined VDM is argued. “Not released” VDM is
subject to change after version up of the system. But in my personal view, it should
be better to use it than creating custom CDS Views for all business entities.

Predefined VDM and Extend View:

Predefined VDM:

Predefined VDM is the predefined CDS Views for business entities or for applications in
S/4HANA. There are mainly 3 types of predefined VDM in S/4HANA.

• Consumption View: The view consumed by application (Tech name: C_*). e.g.
Journal Entry Analyzer (C_GLLINEITEMSQ0001). It is created from Interface View in
general.
• Interface View: The view is the foundation of Consumption View (Tech name: I_*).
Interface View for business entities in S/4HANA is called Basic View, e.g. GL Account
Line Item (I_GLAccountLineItem), Profit Center (I_ProfitCenter). Interface view
created from Basic View is called Composite View, e.g. G/L Account Balance Cube
(I_GLAcctBalanceCube).
• Private View: The view used as a part to create Interface View or Consumption View
(Tech name: P_*). It is not mandatory to create.

See the document linked in this blog in detail about CDS View and VDM.

(In BW context, Consumption View is like BW Query and Interface View is like InfoProvider
or InfoObject.)

You can find the predefined VDMs in S/4HANA with Fiori View Browser.

Example of predefined VDM:

• Transaction Data View: Sales Order

 o Consumption View: C_SalesOrderItemQry （Analytic Query – executable as
BW Query）
o Interface View：I_SalesOrderItemCube
o Interface View: I_SalesDocumentItemAnalytics
o Interface View: I_SalesDocumentItem (Use table VBAK, VBAP, VBKD, VEDA as
sources)
• Master Data View:
o Interface View (Simple): I_CompanyCode
o Interface View (Complex): I_ProfitCenter

List of main predefined View:

Component Status CDS View Text

Analytics – Incoming Sales
SD Released I_SALESORDERITEMCUBE
Order Cube
SD Released I_BILLINGDOCUMENTITEMCUBE Analytics – Sales Volume Cube
MM Unreleased I_PURCHASEORDERITEM Purchase Order Item
MM Unreleased C_PURDOCLISTINVOICEDETAILS Invoice Details
MM Unreleased I_PURCHASEREQUISITIONITEM Purchase Requisition Item
MM Released I_MATERIALSTOCKTIMESERIES Material stock for periods
Analytical Cube for Goods
MM Released I_GOODSMOVEMENTCUBE
Movements
FI Released I_GLACCTBALANCECUBE G/L Account Balance Cube
FI Released I_GLACCOUNTLINEITEMCUBE G/L Line Items Cube
FI Released I_PROFITCENTER Profit Center
FI Released I_COSTCENTER Cost Center
G/L Account In Chart Of
FI Released I_GLACCOUNTINCHARTOFACCOUNTS
Accounts
LO Released I_CUSTOMER Customer
LO Released I_SUPPLIER Supplier
MM Released I_PLANT Plant
MM Released I_STORAGELOCATION Storage Location
MM Unreleased I_MATERIAL Material
BC Released I_CURRENCY Currency
BC Released I_UNITOFMEASURE Unit of Measure
CA Unreleased I_CALENDARDATE Date
FI Released I_FISCALCALENDARDATE Fiscal Calendar Date

• Release statuses is at S/4HANA 1709 FPS00.

Extend View:

Extend View is used to add fields to predefined VDM without changing predefined VDM
itself. It is possible to associate the view and add it in the source view, and it is also possible
to use the association for foreign key association on the added field. It is like APPEND for
table in ABAP Dictionary. See SAP Help , Wiki or blog in detail.

Consideration to use Extend View:

Enhancement by Extend View is in a sense like modification, so would cause the following
issues when upgrading the system.

• Conflict of the field name: conflict of the field name would happen if new fields are
added on the predefined VDM in the newer version but the field names has already
been used in the Extend View, e.g. Segment is added with Extend View to the source
predefined VDM, but in the newer version of the predefined VDM, Segment is added
by default. To avoid it, it is recommended to rename the fields added with Extend
View with ZZ~.
• Field name change of the source view: fields in the source (select ~ from <Source>)
can be added using Extend View. But if the source view is unreleased (see below), the
field name might be changed (or the filed would be deleted) in the newer version. In
this case, it cannot be avoided to adjust the Extend View and relevant CDS Views.

For those reasons, it is recommended to add fields using Key User Extensibility Tools
“Custom Fields and Logic” to add fields as much as possible.

Other limitations in Extend View:

• [ min .. *] cannot be used in Extend View. See the blog for [min..*] association.
• The field of the association cannot be added when path expression is used in ON
condition of the association, _FiscalYearCalenderDate.FiscalYear cannot be added
when _FiscalYearCalenderDate is associated in the Extend View and
SDIA._ControllingArea.FiscalYearVariant is used in the ON condition.
• It is not possible to set annotation only to existing field.
 o For doing that ANNOTATE VIEW is used. But it is available only for the
predefined VDM in which Metadata.allowExtensions is set to true.

Example of Custom CDS View using Predefined VDM and

Extend View
There are some ways to use predefined VDM as below.

In the example of this blog, Interface View of predefined VDM I_SalesOrderItemCube is

enhanced by Extend View, and Another Custom CDS View is created from it, and
Consumption View is created on top.

• The Interface View I_SalesOrderItemCube is enhanced by Extend View

ZE_SalesOrderItemCube to add FiscalYearVariant from I_ControllingArea associated
in I_SalesOrderItemCube.
• Custom Interface View is created on top of predefind VDM and I_ProfitCenter,
I_BillingDocumentItemBasic and I_FiscalCalendarDate are associated in it, and fields
and associations are added from those views.
• Consumption View ZC_Sales is created from I_SalesOrderItemCube.
Extend View: ZE_SalesOrderItemCube

@AbapCatalog.sqlViewAppendName: ‘ZESSOITMCB’

@EndUserText.label: ‘Extend SalesOrderItemCube’

extend view I_SalesOrderItemCube with ZE_SalesOrderItemCube

association [0..1] to I_FiscalYearVariant as _FiscalYearVariant

on $projection.ZZFiscalYearVariant = _FiscalYearVariant.FiscalYearVariant

@ObjectModel.foreignKey.association: ‘_FiscalYearVariant’

SDIA._ControllingArea.FiscalYearVariant as ZZFiscalYearVariant,

–expose

_FiscalYearVariant

Detail:
 • Add fields from associated Views: FiscalYearVariant is added from I_ControllingArea
associated in the source I_SalesOrderItemCube, and master view I_FiscalYearVariant
is associated and it is set as the foreign key association on the added field
FiscalYearVariant.
• Renamed as ZZ~: All fields added in the Extend View are renamed to ZZ~. it is to
avoid the possible conflict of the name when upgrading the system. Now
I_SalesOrderItemCube doesn’t have the field FiscalYearVariant so it is possible to add
the field named “FiscalYearVariant” with Extend View. However, if the field
FiscalYearVariant is added in the next version of I_SalesOrderItemCube, the conflict
would happen.
• Field and foreign key association added from associated View: The field Segment is
added from I_ProfitCenter, and _Segment (_ProfitCenter. _ProfitCenter) is also
added from I_ProfitCenter, and is used in the foreign key association on the field.
Although I_Segment has already been used in the foreign key association in
I_ProfitCenter, foreign key association setting is necessary again in the Extend View
(Transaction Interface View).
• Not possible to use Path Expression for ON condition for the association: I tried to
associate _FiscalCalendarDate.FiscalYear but found it is not possible. It is because
_ControllingArea. FiscalYearVariant cannot be used for ON condition for association
to add fields from the associated view, although it is possible to add association only,
e.g. _FiscalCalendarDate.FiscalYear cannot be added, but _FiscalCalendarDate can be
added. For doing that, the only way is to add only association in Extend View and add
the field from the associated view in custom CDS View created from the source view
extended by Extend View.

Interface View: ZI_SALESBILL:

@AbapCatalog.sqlViewName: ‘ZISALESBILL’

@AbapCatalog.compiler.compareFilter: true

@AccessControl.authorizationCheck: #CHECK

@EndUserText.label: ‘SalesOrder+BillingDoc’

@Analytics.dataCategory: #CUBE

@VDM.viewType: #COMPOSITE

@ClientHandling.algorithm: #SESSION_VARIABLE

define view ZI_SALESBILL

with parameters
P_ExchangeRateType : kurst,

P_DisplayCurrency : vdm_v_display_currency

as select from I_SalesOrderItemCube

( P_ExchangeRateType: $parameters.P_ExchangeRateType, P_DisplayCurrency:

$parameters.P_DisplayCurrency )

association [0..1] to I_ProfitCenter as _ProfitCenter

on $projection.ControllingArea = _ProfitCenter.ControllingArea

and $projection.ProfitCenter = _ProfitCenter.ProfitCenter

association [0..*] to I_BillingDocumentItemBasic as _BillingDocumentItemBasic

on $projection.SalesOrder = _BillingDocumentItemBasic.SalesDocument

and $projection.SalesOrderItem = _BillingDocumentItemBasic.SalesDocumentItem

association [0..1] to I_FiscalCalendarDate as _FiscalCalendarDate

on $projection.ZZFiscalYearVariant = _FiscalCalendarDate.FiscalYearVariant

and $projection.SalesOrderDate = _FiscalCalendarDate.CalendarDate

SalesOrder,

SalesOrderItem,

SalesOrderType,

SalesOrderDate,

SalesOrganization,
DistributionChannel,

OrganizationDivision,

ControllingArea,

SalesOrderDateYearMonth,

DisplayCurrency,

@ObjectModel.foreignKey.association: ‘_ProfitCenter’

ProfitCenter,

ZZFiscalYearVariant,

NetAmountInDisplayCurrency,

@ObjectModel.foreignKey.association: ‘_Segment’

_ProfitCenter.Segment,

_BillingDocumentItemBasic.BillingDocument,

_BillingDocumentItemBasic.BillingDocumentItem,

_FiscalCalendarDate.FiscalYear as ZZFiscalYear,

_FiscalCalendarDate.FiscalPeriod as ZZFiscalPeriod,

_FiscalCalendarDate.FiscalYearQuarter,

/* Associations */

//I_SalesOrderItemCube

_ControllingArea,
_DistributionChannel,

_FiscalYearVariant,

_OrganizationDivision,

_SalesOrder,

_SalesOrderType,

_SalesOrganization,

_ScheduleLine,

_ProfitCenter,

_ProfitCenter._Segment

Detail:

• Add fields from associated Views: In this Interface View, I_ProfitCenter are
associated and Segment are added from it, and this view is set as Foreign Key
association on ProfitCenter. BillingDocument and BillingDocumentItem are added
from associated I_BillingDocumentItemBasic, and FiscalYear, FiscalPeriod, and
FiscalQuarter are added from associated I_FiscalCalendarDate.

Most of them could be added with Extend View and it might be possible to go without
creating custom Interface View. However, it is created in this sample as it might be better to
avoid using Extend View too much because of the considerations and limitations as
mentioned above.

Consumption View: ZC_Sales

@AbapCatalog.sqlViewName: ‘ZCSALES’

@AbapCatalog.compiler.compareFilter: true

@AccessControl.authorizationCheck: #CHECK
@EndUserText.label: ‘Sample Sales’

@Analytics.query: true

define view ZC_Sales

with parameters

@AnalyticsDetails.query.variableSequence: 20

@Consumption.defaultValue: ‘EUR’

P_DisplayCurrency : vdm_v_display_currency,

@AnalyticsDetails.query.variableSequence: 30

@Consumption: { valueHelp: ‘_ExchangeRateType.ExchangeRateType’, defaultValue:

‘M’}

P_ExchangeRateType : kurst,

@Consumption.hidden: true

@Environment.systemField: #SYSTEM_DATE

P_KeyDate : sydate

as select from ZI_SALESBILL

( P_ExchangeRateType: $parameters.P_ExchangeRateType, P_DisplayCurrency:

$parameters.P_DisplayCurrency )

association [1] to I_ExchangeRateType as _ExchangeRateType on

_ExchangeRateType.ExchangeRateType <> ”

SalesOrder,

SalesOrderItem,

@AnalyticsDetails.query.totals: #SHOW

SalesOrderType,
@AnalyticsDetails.query.variableSequence : 10

@Consumption: {

filter: {selectionType: #INTERVAL},

derivation: {

lookupEntity: ‘C_SglGregorianCalDateFunction’,

resultElement: ‘DateFunctionStartDate’, binding: [

{ targetParameter: ‘P_DateFunction’, type: #CONSTANT, value : ‘YEARTODATE’ },

{ targetParameter : ‘P_Language’ , type : #SYSTEM_FIELD, value :

‘#SYSTEM_LANGUAGE’ } ],

resultElementHigh: ‘DateFunctionEndDate’ }

SalesOrderDate,

@AnalyticsDetails.query.axis: #ROWS

@AnalyticsDetails.query.display: #TEXT

@AnalyticsDetails.query.totals: #SHOW

SalesOrganization,

@AnalyticsDetails.query.display: #TEXT

@AnalyticsDetails.query.totals: #SHOW

DistributionChannel,

@AnalyticsDetails.query.display: #TEXT

@AnalyticsDetails.query.totals: #SHOW

OrganizationDivision,

@AnalyticsDetails.query.display: #TEXT
@AnalyticsDetails.query.totals: #SHOW

ControllingArea,

@EndUserText.label: ‘Calender YearMonth’

@AnalyticsDetails.query.axis: #COLUMNS

@AnalyticsDetails.query.totals: #SHOW

SalesOrderDateYearMonth,

DisplayCurrency,

ZZFiscalYearVariant,

BillingDocument,

@EndUserText.label: ‘Billing Document Item’

BillingDocumentItem,

@AnalyticsDetails.query.axis: #ROWS

@AnalyticsDetails.query.display: #TEXT

@AnalyticsDetails.query.totals: #SHOW

ProfitCenter,

@AnalyticsDetails.query.display: #TEXT

@AnalyticsDetails.query.totals: #SHOW

Segment,

ZZFiscalYear,

ZZFiscalPeriod,

FiscalYearQuarter,

@Consumption.hidden: true
@DefaultAggregation: #FORMULA

@AnalyticsDetails: {

exceptionAggregationSteps: [{ exceptionAggregationBehavior : #MAX,

exceptionAggregationElements: [‘BillingDocument’,’BillingDocumentItem’]

}]

@AnalyticsDetails.query.formula : ‘NetAmountInDisplayCurrency’

1 as SalesOrderAmtTmp,

@AnalyticsDetails.query.axis: #COLUMNS

@EndUserText.label: ‘SalesOdrAmt_D’

@DefaultAggregation: #FORMULA

@AnalyticsDetails: {

exceptionAggregationSteps: [{ exceptionAggregationBehavior : #SUM,

exceptionAggregationElements: [‘SalesOrder’,’SalesOrderItem’]

}],query.decimals: 0

@AnalyticsDetails.query.formula : ‘$projection.SalesOrderAmtTmp’

1 as SalesOrderAmt

Results of the Consumption View:

Detail:

• Analytic Query: This Consumption View is Analytic Query, which works as the source
of Fiori Multidimensional Reporting. It can be used with SAC and BusinessObjects.
• Value help for the parameter: I_ExchangeRateType is associated practically without
on condition (dummy association) to use it for the value help for the parameter
P_ExchangeRateType. See the blog in detail.
• Derive start and end date automatically using lookup entry for Date Function: The
start and end date are derived automatically from C_SglGregorianCalDateFunction as
Lookup entry. C_SglGregorianCalDateFunction is the CDS View used in Date Function.
As YEARTODATE is set as Date Function parameter Value, when running the view on
8/19/2018, 1/1/2018 is derived as start date and 8/19/2018 as end date.
• Exception Aggregation to avoid value duplicate value: The record of
I_SalesOrderItemCube would be duplicated when JOIN happens as relationship
between I_SalesOrderItemCube and I_BillingDocumentItemBasic is 1 : N. To avoid it,
2 calculated measures including Exception Aggregation are created
(SalesOrderAmtTmp and SalesOrderAmt). In SalesOrderAmtTmp, ZBillingDocument
and ZBillingDocumentItem are used as Exception Aggregation Element, and
Aggregation is set to MAX, so the aggregation of ZBillingDocument and
ZBillingDocumentItem is MAX, not SUM. In SalesOrderAmt, ZSalesOrder and
ZSalesOrderItem are used as Exception Aggregation Element, and Aggregation is set
to SUM, SalesOrderAmtTmp is aggregated with SUM. (For this reason, [0..*] in the
association to I_BillingDocumentItemBasic in Interface View (Extend View) is no
problem in this case).

When drilled down with Billing Document, SalesOdrAmt_D for Sales Order 388 is displayed
twice.

Even when Billing Document is removed and records are aggregated, SalesOdrAmt_D for
Sales Order 388 is displayed as expected without duplication.
As high granular attributes ZBillingDocument, ZBillingDocumentItem, and ZSalesOrder,
ZSalesOrderItem are used in Exception Aggregations, they have to be included in the select
list of internal SELECT statement. It would lead to longer runtime as larger amount of data
would have to be retrieved.

“Not released” predefined VDM:

Predefined VDM has the status of validity (Released/Not Released). In the unreleased
predefined VDM, the design is subject to change in the future release and current design is
not guaranteed by SAP, e.g. field name and the keys would be changed, fields would be
removed, the view would be removed. It is like unreleased Function Module. In addition,
Only the released CDS Views can be used for Key User Extensibility Tools Custom CDS View
and Custom Analytical Queries.

See the blog in detail.

Hope you enjoy high productivity by using predefined VDM and Extend View!

Assigned Tags

• ABAP Development
• ABAP Extensibility
• SAP S/4HANA
• SAP S/4HANA Cloud, private edition
• SAP S/4HANA Embedded Analytics
• ABAP CDS view
• embedded analytics

•
•
•
•
•

• How to deal with “Not released” predefined VDM in S/4HANA

By Masaaki AraiMay 23, 2019

 • Analytics in S/4HANA - real shape of embedded analytics and beyond embedded
analytics

By Masaaki AraiJun 08, 2019

• How to find a predefined Virtual Data Model in S/4HANA

By Masaaki AraiDec 05, 2018

• How to extend standard CDS view that expose a LCHR field

By Edoardo RotaJul 30, 2018

• CDS Entity not permitted in Custom CDS view

By V badhanApr 06, 2023

• CDS Virtual element - Query

By Maloy PalApr 19, 2021

23 Comments
You must be Logged on to comment or reply to a post.

vishwanath vedula
October 22, 2018 at 7:33 am

Great!

• Like 0
• Share

Joachim Rees
November 6, 2018 at 2:43 pm

Hi Masaaki,

thanks for sharing!

While your blog didn't help me with my specific question (see below), it still was a good
read.

I think CDS and the VDM are quite powerful!

Here's what I am onto:

I want to extend C_SalesContractWl_F1851 and thus also have to extend the underlying
views

I_SalesContract

I_SalesDocument

I_SalesDocumentBasic

So I need to create a total of 4 extend views (one for each SAP CDS-View).

My question is if there are any best practices on naming those extend-views?!

See also on Mastodon:

https://mastodon.technology/@Joachim_Rees/101024454603885620

Best

Joachim

• Like 0
• Share

Masaaki Arai
Blog Post Author
November 8, 2018 at 7:23 pm

Hello Joachim,

Interesting question.

If the field is new field in VBAK, I think you can add the field easily with Key User Tool,
Custom Fields and Logic.
If the field has already been there, one way it to add the field to all the views underneath.

The second way is to add the field in E_SalesDocumentBasic, which is associated

in C_SalesContractWl_F1851, using Extend View, and add the field
in C_SalesContractWl_F1851 using another Extend View.

In this case, you dont have to be concerned about the performance by joining large table
again, as internally self join optimization should happen, so it should be avoided to join VBAK
again internally.

But note that you have to avoid naming conflict to the fields added with Custom Fields and
Logic, e.g. if CFL uses ZZ1, you have to start the name of the field you add with ZY~.

And it is not supported, as E_* view is used for CFL internally.

Thanks, Masa

• Like 0
• Share

Tarow W
June 13, 2019 at 3:28 am

Hi Masaaki,

First of all, thank you so much for very great blog.

I am investigating how to VDM in Fiori using MultiDimensional (as suggested in one of your
blogs).

https://blogs.sap.com/2018/07/11/how-to-create-custom-fiori-multidimensional-reporting-
application-in-s4hana-on-premise/

I can create BW query on top of CDS view (as a Cube) and display it in RSRT perfectly.

However, when I consume this BW query in Fiori using MultiDimensional, the free
characteristics disappear.

More details are in the following question.

https://answers.sap.com/questions/12698306/no-free-dimensions-when-using-fiori-
multidimension.html
Not sure if there is any missing step.

Thank you so much.

• Like 0
• Share

Sreekanth Surampally
April 12, 2020 at 10:07 pm

Hi Masa, thank you for the blog. Quick question on the example you explained. When we are
creating ZI_SALESBILL custom cds view, we can make association from i_salesorderitemcube
to i_fiscalyearvariant to get the required column fiscal year variant, why do we need to
extend the i_salesorderitemcube standard cds view? am I missing something here in
understanding an extension?

Thanks, Sreekanth

• Like 0
• Share

Masaaki Arai
Blog Post Author
April 13, 2020 at 3:24 am

Hello Sreekanth,

I want to associate I_FiscalCalendarDate in ZI_SALESBILL so Fiscalyearvariant is needed in the

source view. so Fiscalyearvariant has to be added in i_salesorderitemcube.

Thanks, Masa

• Like 0
• Share

Sreekanth Surampally
April 13, 2020 at 4:45 am
Yes, but if I add fiscalyearvariant in ZI_SALESBILL and move the association target
i_fiscalcalendarDate to next level cds like ZI_SALESBILL1., should n't that be ok? I am just
trying to understand what is the benefit of extending i_salesorderitemcube ., please assist
me.

• Like 0
• Share

Masaaki Arai
Blog Post Author
April 13, 2020 at 9:54 am

Sorry, I cannot get the point. to associate i_fiscalcalendarDate , Fiscalyearvariant has to be

there in the source view, so I added it in the souce view.

• Like 0
• Share

Sreekanth Surampally
April 13, 2020 at 1:55 pm

Sorry for the confusion Masa, I will explain with below screen shot, If I can add the new
fields in a custom cds view which reads the standard cds view, what would be the need for
extending standard cds view generally?

• Like 0
• Share
Masaaki Arai
Blog Post Author
April 13, 2020 at 5:38 pm

Okay, I see.

Yes, another way to add fields is to create wrapping view on top of the standard View. In
this way, it might be that the time for activation should be shorter.

But in the case, you have to create custom Fiori app consuming the wrapping CDS View as
the source instead of the standard VDM, although in case of odata, it could be avoided by
redirection. but anyway, it is complex.

Thanks, Masa

• Like 1
• Share

Sreekanth Surampally
April 14, 2020 at 11:14 am

Thank you, I got it.

• Like 0
• Share

Gregorio Cybill
April 18, 2020 at 3:29 am

Hi Masa,

I like the approach you are explaining the CDS concept and example.
Would you be able to share another blog associating hierarchy with the custom CDS view?
For example, CDS GL hierarchy based on the S/4 GL FSV group.

Thank you.

• Like 0
• Share
Mayumi Lacerda Blak
May 14, 2020 at 1:29 pm

Hello Masaaki!

Great post! I've learned a lot with it!

Can you help me with an issue?

I'm trying to extend the P&L Plan/Actual Fiori app. So I mapped the flow:

Consumption view: C_ProfitAndLossPlanActQ2903)

Composite view: I_ActualPlanJrnlEntryItemCube.

Extend Views:

E_JournalEntryItem : ALIAS _Extension_acdoca

E_FinancialPlanningEntryItem: ALIAS _Extension_acdocp

My question is:

how can I have the fields extended for Plan and Actual? I cannot extend the composite view
with both of the extension views, because the fields get duplicated.

If I extend only from E_JournalEntryItem, the plan values are not read for the fields.

Can you help me with this issue?

Kind regards,

Mayumi

How can I have the fields being read by both Plan and Actual Extend views?

• Like 0
• Share

Masaaki Arai
Blog Post Author
May 14, 2020 at 5:45 pm

Hello Mayumi,

Could you check CFL?

https://blogs.sap.com/2020/02/01/adding-field-in-standard-fiori-apps-of-s-4hana-with-
custom-fields-and-logic/

regards, Masa

• Like 0
• Share

Mayumi Lacerda Blak

May 16, 2020 at 7:22 pm

Hello Masaaki,
I read your link but unfortunately according to sap note 2453614, COPA fields are not
extendable through app Custom Fields and Logic (not available in SCFD_EUI).

The only way is CDS view extensibility (Eclipse).

I did it sucessfully for CDS related to Actuals (P&L Actuals), that are based on
I_JournalEntryItem, but for Plan/Actual, I could't find the solution.

Kind regards

Mayumi

• Like 0
• Share

Masaaki Arai
Blog Post Author
May 18, 2020 at 8:27 am

Hello Mayumi,

I_ACTUALPLANJRNLENTRYITEMCUBE is available for Business Context FINS_CODING_BLOCK,

FINS_JOURNAL_ENTRY_ITEM.

Yes, If it is not possible with CFD, the remaining way is extend view.

https://blogs.sap.com/2018/08/22/sample-custom-cds-view-using-predefined-virtual-data-
model-and-extend-view-in-s4hana/

Thanks, Masa

• Like 1
• Share

Mayumi Lacerda Blak

May 26, 2020 at 11:33 pm

Hello Masa,

Do you have an example of how to extend CDS views with new fields + texts? I extended
COPA fields but only the key, the texts are not available on reports.

I tried with the tips from https://blogs.sap.com/2017/11/07/s4-hana-f4-help-values-key-

text-display-in-abap-cds-views-based-reports/

But i didn't have success...

Kind regards

Mayumi

• Like 0
• Share

Masaaki Arai
Blog Post Author
May 27, 2020 at 5:09 am

Hi Mayumi,

See ZE_SalesOrderItemCube in the blog https://blogs.sap.com/2018/08/22/sample-custom-

cds-view-using-predefined-virtual-data-model-and-extend-view-in-s4hana/

You can associate the master view via extend view. the master view should have the text
field and associated to the key field.

key and text can be displayed using @AnalyticsDetails.query.display: #KEY_TEXT in

consumption view by default.

see C_GLLineItemsQ0001 for example.

regards, Masa

• Like 0
• Share
Mayumi Lacerda Blak
May 28, 2020 at 10:27 pm

Hello Maza!

It worked for Key and text only with the annotation @AnalyticsDetails.query.display: #TEXT.
When I put @AnalyticsDetails.query.display: #KEY_TEXT, only the key was available.

Thanks a lot for your help! I'm not an Abaper so i'm struggling with CDS View extensions....

Kind Regards

Mayumi

• Like 0
• Share

Sreekanth Surampally
June 23, 2020 at 9:09 pm

Hi Masa, What is need of Private Views in Standard VDM content., I could not find more
explanation in sap help documentation and also in SAP forum. Why did SAP created some
private views in every business model, I mean what ever the code/logic inside private view
can be achieved with regular basic view or composite view. I posted a question in the forum
as well, but did not get any response.https://answers.sap.com/questions/13078306/what-
do-we-need-of-private-cds-views-s4-hana-vdm.html

• Like 0
• Share

Masaaki Arai
Blog Post Author
June 29, 2020 at 4:44 pm

Hello Sreekanth,
Private View is not mandatory, but importance is in Interface View and Consumption View.
Private View would have to be created for technical reasons, e.g. to create instead of sub-
query.

I personally think the differentiation among Consumption View, Interface View and Private
view is not so important. I think transaction view and master view should be differentiated.

see my blog below.

https://blogs.sap.com/2018/10/18/predefined-virtual-data-model-as-example/

Thanks, Masa

• Like 0
• Share

Joachim Rees
August 31, 2020 at 10:05 am

[Telling why and how this blog was helpful:]

I'm creating a report selection some stuff, and want "to do it right", using CDS-views.

I was not sure how interface- and consummations views work together, I wanted to read up
in the again. So I searched for "CDS VDM" and found this blog.

The section "Predefined VDM and Extend View" is just what I was looking for, and helps me
a lot!

As I need to join DD02L, TADIR and TDEVC, one of my questions was if I should:

- first create CDS-Views (Interface-Views) for each singel table, then do the join them
together in another (Interface-) view on top of them
or:
- do the join right away in the first (interface-) view I create.

This exmaple gives me the answer -> join right away:

Interface View: I_SalesDocumentItem (Use table VBAK, VBAP, VBKD, VEDA as sources)

Thanks for your blog!

Joachim

• Like 1
• Share
Sebastián Linares
November 25, 2020 at 12:52 pm

Hi Masa, great explanation!

one question.........If I want use the I_* views from a C_* view standard from SAC its not
necessary make anything, ok? I should create a custom C view when I want take it directly
(the I_* views)......ok?

Thanks