The arcplan library is a very useful tool for coordinating the layout of reports. All objects which are extracted from a library behave equally on the reports with regard to the selection of the subsequently described properties.
Table of Contents
The library can be opened with the following button:
Setting up Library Objects
In order to move an object into the library, a library must first be set up and saved. Then, this object can simply be dragged into the library window by way of drag & drop. (Alternative via the menu list: objects / move to library)
Note: Hierarchical objects cannot be managed in the library.
As soon as this is done, a pop-up opens where the properties of the object can be defined:
In this context, it must be noted that the property “With management functions“ is only active if the object receives an entry under one of the management events such as “After updating” or “After entry”.
Tip:
In order to activate the management function in the library it is sufficient to simply insert an empty string ““ into one of the formulas. It is merely important that the management function is active (has a * as in case of computation). If the management function is not supposed to be consciously different in the instances of the library object, then it can be recommended in most cases to include it directly, as a subsequent inclusion of the management function is no longer possible.
After this change has been made, “With management function” may now be selected.
The property “As reference object” should be used cautiously. Generally, objects which have been moved to the library may well be deleted. They remain in the library and on each report on which they have been rolled out, regardless, and may be retrieved at any time.
If an object has been marked as reference object, all other objects which are connected to this object via the library are also deleted upon deletion of the former. In addition, all changes to the library objects must be managed via this (original) object. An adjustment to just any object is then no longer possible.
The properties can be further limited via the button “Setting global properties”. Thus, e.g. only the breadth can be set as global property and the height may deviate from report to report.
Via the “Info” button in the library window, it can be checked at any time what the settings for the selected library object are. Further, the name can be changed here.
Modifying and Deleting Library Objects
As the global properties of library objects in the report merely constitute a reference to the library, the library must be saved if these properties are modified.
Example:
Breadth = global property
Height = local property (box unticked)
If the breadth of the object is modified, it is imperative that the library be saved. In case of a modification of the height, it suffices to save the report.
If a library object is supposed to be deleted, all documents must be closed first. Then, the library may be opened separately and the object may be deleted.
Who is b.telligent?
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.
With the new function REPLACEEXPRESSION, arcplan 7 affords the possibility to influence the automatically generated SQL and MDX statement. This has the benefit that a design can continue to be made with “arrows” and that one is not limited to formulas. Currently, only simple adjustments of the query are possible with this tool; however, there is a large impact on the resulting possibilities.
With the Q2 2023 updated titled "New optimized story experience - unified strories and applications", SAP analytics cloud offers users new ways to develop reports and dashboards even more flexibly and easily in an integrated design enviroment. We'll showyou which new features theupdate provides and how it supports you in creating reports,
As a business intelligence package, SAP BW provides many opportunities for efficient reporting – but also contains numerous barriers which significantly slow down performance. Using the example of report filters available in the application, this article shows how the smallest adaptations impair SAP BW performance, and how efficient settings for filtering options can improve results.