How to add Cost Center Hierarchy into CDS View selection screen

In SAP Delivered CDS View for Cost Centers – Actuals/ Cost Centers – Plan/Actual, or even your own custom created CDS View, you might need to have Cost Center Hierarchy and Cost Center Node on the selection screen within WebDynpro version of the app. You can select Cost Center Hierarchy as an additional filter, but it will not be visible among other variables.

In order to be able to see Cost Center Hierarchy on selection screen, you will need to create your own CDS View, as you cannot modify SAP Delivered one. You can create copy of the CDS View C_COSTCENTERQ2001, which has the Cost Center Hierarchy already in the code, but it is commented out by default.

You will find this code under the Rows characteristic:

@AnalyticsDetails.query.axis: #ROWS  
IsStatisticalCostCenter,  
 
@AnalyticsDetails.query.variableSequence: 50
@Consumption.filter: { selectionType: #INTERVAL, multipleSelections: true, mandatory: false }
@AnalyticsDetails.query.totals: #SHOW
@AnalyticsDetails.query.axis: #ROWS
@AnalyticsDetails.query.display: #KEY_TEXT
CostCenter,
 
//@AnalyticsDetails.query.variableSequence: 81
//@Consumption.filter: {  selectionType: #HIERARCHY_NODE, multipleSelections: true, mandatory: false,
//                        hierarchyBinding : [    {type: #USER_INPUT, value: 'CostCenterHierarchy', variableSequence: 80 } ] }
//@AnalyticsDetails.query.displayHierarchy: #FILTER
//@AnalyticsDetails.query.totals: #SHOW
//@AnalyticsDetails.query.axis: #ROWS
//@AnalyticsDetails.query.display: #KEY_TEXT
//CostCenter as CostCenterChildNode,
//_CostCenter[1:ValidityEndDate   >= $parameters.P_KeyDate and 
//                    ValidityStartDate <= $parameters.P_KeyDate]._Text[1:Language = $parameters.P_Language].CostCenterName as CostCenterChildNodeName,
 
 
@AnalyticsDetails.query.variableSequence: 86
@Consumption.filter: {  selectionType: #HIERARCHY_NODE, multipleSelections: true, mandatory: false,
                                      hierarchyBinding : [  { type: #USER_INPUT, value: 'GLAccountHierarchy', variableSequence: 85 } ] }
@AnalyticsDetails.query.displayHierarchy: #FILTER
@AnalyticsDetails.query.axis: #ROWS
@AnalyticsDetails.query.totals: #SHOW
GLAccount,
_GLAccountInChartOfAccounts._Text[1:Language = $parameters.P_Language].GLAccountName,

When you create a copy of this view, or you will use your own, you will need to replace this part of the code for this one:

@AnalyticsDetails.query.axis: #ROWS  
IsStatisticalCostCenter,  
 
 
@AnalyticsDetails.query.variableSequence: 86
@Consumption.filter: {  selectionType: #HIERARCHY_NODE, multipleSelections: true, mandatory: false,
                        hierarchyBinding : [    {type : #PARAMETER, value : 'P_ControllingArea'}, {type: #USER_INPUT, value: 'CostCenterHierarchy', variableSequence: 85 }
                                            ] }
@AnalyticsDetails.query.displayHierarchy: #FILTER
//@Consumption.filter: { selectionType: #INTERVAL, multipleSelections: true, mandatory: false }
@AnalyticsDetails.query.totals: #SHOW
@AnalyticsDetails.query.axis: #ROWS
CostCenter,
_CostCenter[1:ValidityEndDate   >= $parameters.P_KeyDate and 
                    ValidityStartDate <= $parameters.P_KeyDate]._Text[1:Language = $parameters.P_Language].CostCenterName,
 
@AnalyticsDetails.query.variableSequence: 96
@Consumption.filter: {  selectionType: #HIERARCHY_NODE, multipleSelections: true, mandatory: false,
                                      hierarchyBinding : [  { type: #USER_INPUT, value: 'GLAccountHierarchy', variableSequence: 95 } ] }
@AnalyticsDetails.query.displayHierarchy: #FILTER
//@Consumption.filter: { selectionType: #INTERVAL, multipleSelections: true, mandatory: false }
@AnalyticsDetails.query.axis: #ROWS
@AnalyticsDetails.query.totals: #SHOW
GLAccount,
_GLAccountInChartOfAccounts._Text[1:Language = $parameters.P_Language].GLAccountName,

As you can see in the changed code, the part with single Cost Center was removed completely and  Cost Center Hierarchy with Cost Center Node took its place. In Cost Center Hierarchy and GL Account Hierarchy is a line:

//@Consumption.filter: { selectionType: #INTERVAL, multipleSelections: true, mandatory: false }

This line is there in case, you would like to select it not as a Hierarchy and Node, but just a single selection of Cost Center or GL Account. If you would like to have a single GL Account for selection, you need to uncomment this line and comment these two lines in the code for GL Account:

@Consumption.filter: {  selectionType: #HIERARCHY_NODE, multipleSelections: true, mandatory: false,
                                      hierarchyBinding : [  { type: #USER_INPUT, value: 'GLAccountHierarchy', variableSequence: 95 } ] }
@AnalyticsDetails.query.displayHierarchy: #FILTER

These two lines for Cost Center:

@Consumption.filter: {  selectionType: #HIERARCHY_NODE, multipleSelections: true, mandatory: false,
                        hierarchyBinding : [    {type : #PARAMETER, value : 'P_ControllingArea'}, {type: #USER_INPUT, value: 'CostCenterHierarchy', variableSequence: 85 }
                                            ] }
@AnalyticsDetails.query.displayHierarchy: #FILTER

At the end, you will need to create your own Fiori Tile with this CDS View in it, to be able to run it in Fiori Launchpad.

The result will look like this in Fiori.

Cost Centers – Actuals with Hierarchy

Please share your feedback or thoughts in the comment section.

Follow me for more tips about BW or BPC in general, so I can create more post about these topics.

You can also follow BW Planning, post and answer questions (https://answers.sap.com/tags/369280904654660339247670897548678), and read other posts on the topic (https://blogs.sap.com/tags/369280904654660339247670897548678/) for more content.

You might suggest some topic, you would like to know more about in my DMs as well, so I know on which topics should I focus.