In order to ensure performant reporting based on SAP BW, it is necessary to avoid redundant requests. An important element in this context is the optimized master data request. This can be implemented particularly easily and effectively for hierarchy objects (especially menu hierarchies).
In this case, a menu hierarchy object in which the customers of an application can be selected will serve as example. If the customer element is drawn from the database window into the menu hierarchy object, the standard layer preferences are set. In this process, only the All node becomes visible. In the background, arcplan generates an MDX request in order to determine the menu content. Even though only master data is visible, this leads to a joining with the fact data within SAP BW and thus tends toward an expensive operation:
In order to avoid this joining with the facts, SAP provides special functional elements which directly request the dimension data. These functional elements can be used by arcplan by changing the layer settings for the menu hierarchy object. In this context, it must be noted that this way, the entire hierarchy is always (!) requested, so that this setting should only be used for smaller hierarchies (<1000 elements). For these, however, the request of all elements is generally markedly more performant than a joining with the facts.
If the layer settings are made as in illustration 2, arcplan will generate the activation of the functional element in the background. Now, the complete hierarchy is requested and initially presented in arcplan. Via the hierarchy formatting and the button “Set initial state” it is possible to adjust the initial presentation as required, so that the end user does not have to close the hierarchy:
Thus, on the surface, the menu looks absolutely identical to the end user.
In the background, however, the access via the functional element – which is markedly more performant for smaller hierarchies – is generated. The joining with the facts is thus avoided.
Do you want to replace the IoT core with a multi-cloud solution and utilise the benefits of other IoT services from Azure or Amazon Web Services? Then get in touch with us and we will support you in the implementation with our expertise and the b.telligent partner network.
Domain Lead Insights & Information Design
Exasol is a leading manufacturer of analytical database systems. Its core product is a high-performance, in-memory, parallel processing software specifically designed for the rapid analysis of data. It normally processes SQL statements sequentially in an SQL script. But how can you execute several statements simultaneously? Using the simple script contained in this blog post, we show you how.
Many companies with SAP source systems are familiar with this challenge: They want to integrate their data into an Azure data lake in order to process them there with data from other source systems and applications for reporting and advanced analytics. The new SAP notice on use of the SAP ODP framework has also raised questions among b.telligent's customers. This blog post presents three good approaches to data integration (into Microsoft's Azure cloud) which we recommend at b.telligent and which are supported by SAP.
First of all, let us summarize the customers' requirements. In most cases, enterprises want to integrate their SAP data into a data lake in order to process them further in big-data scenarios and for advanced analytics (usually also in combination with data from other source systems).
As part of their current modernization and digitization initiatives, many companies are deciding to move their data warehouse (DWH) or data platform to the cloud. This article discusses from a technical/organizational perspective which aspects areof particularly important for this and which strategies help to minimize anyrisks. Migration should not be seen as a purely technical exercise. "Soft" factors and business use-cases have a much higher impact.
No previous post
No next post
