

In The elimination and adjustment rule ,detail table is configured as below: This article gives a more complicated example and explains how it affects calculation result. But some customers’ configuration is much more complicated than the simple example so it causes difficulty to customers to identify if the problem they have is exact the same problem. This has been documented in SAP KBA 2217212.On this KBA,it gives a simple example which causes problem. Indeed, reporting use the FC Cube Designer HANA views which have been specifically deployed by Cube Designer to be browsed by a BI tool, so everything is consistent and ready for reporting.īPC consolidation has a limitation: If there are two rule items, one item has 'periodic calc' selected and the other one doesn't and both rule items have the same destination data region (destination account+ destination flow), the result of both rule items will affect each other. We recommand to use EPM add in connectivity to report on Hana views. So, in order to generate exact same reporting value for all three measures (PERIODIC, QTD and YTD), customer need to build his own logic for above first 3 points mentioned.

What is used with MDX in BPC standard model Measure calculation: PERIODIC, QTD, YTD ( reporting relevant) YTD and sign flip calculation based on account type (reporting relevant) Member formula calculation (reporting relevant) So it means that reporting directly on HANA view by EPM Add in by using MDX connectivity on HANA, it’s bypassing these MDX calculations in BPC. Indeed, BPC standard model use case which is based on MDX syntax and MDX statements are generated by BPC consider the meta data, master data and hierarchy. We don't recommand to report directly to Hana views using EPM add in connectivity. Recommandations related to back end connectivity and support: After that, EPM add-in can connect to any analytic/ calculated view of HANA.

For XMLA, you can use the XMLA connection available in EPM Add-in.

For ODBO, HANA MDX provider have to be installed on local machine. Note: In any case no data entry is possible. EPM add in use MDX ( ODBO or XMLA) to connect to HANA views.
