BW 7.30: The New Planning Modeler. The new Planning Modeler With release 730 the new Planning Modeler is born!
You will see that it is not only new but also different from the old release. First of all, what is the Planning Modeler? It is the central tool for customizing Planning Applications within SAP BW Integrated Planning. The new release comes with all the central features you know in the old version. The real time InfoProviders as well as the filters and planning functions can be found under the corresponding Aggregation Level and be maintained there. The Planning Sequences have their own area in the Data Warehousing Workbench with a brand new feature: You can arrange your Planning Sequences now in InfoAreas which enables you to do an entire semantic grouping of your Planning Applications. By just double clicking on the sequence name you can display details of the sequence and execute it afterwards in the test framework. Moreover transaction RSPLAN gives you a standalone design time tool for your Planning Objects. 7.3 dataflow modeller: What do I need to know? The dataflow modeller is a brilliant new function available in the new release of SAP Business Warehouse.
It really helps with making your BW system easier to manage, develop and work in. Specifically, the functions it provides are... Top-down modelling of new dataflowsOrganization for existing dataflowsCreation of template dataflows using Best PracticeSAP delivered predefined dataflows That sounds easy! What are you going to tell me? Yeah, the above sounds straightforward. But due to the complexity of the topic in hand, and the flexibility of the system, there are quite a few things that can catch you out.
Here are some important things you need to know and understand. 1) Nodes within a dataflow are either “persistent” or “non-persistent” A “persistent node” references an object within the database, such as an InfoCube or DSO. 2) There are two types of dataflow: template and standard Standard: A standard dataflow contains nodes that reference objects existing in the database. Data Validations and Performance Improvements for Planning Applications. For all planning applications,it is vital that the planning data entered is consistent.Examples of this kind of consistency check are routines that prevent budgets from being exceeded or routines that convert amounts in local currencies (as entered by the planner) to the company currency.
The routines are usually implemented as planning functions/sequences and offered to the planners in the form of buttons in the applications. For obligatory constraints, the application designer normally offers a dedicated 'save' button where the corresponding functions/sequences precedes the native 'save'. This existing approach has some disadvantages:- The application modeler has to make sure that planners cannot save data other than using this dedicated button. It is clear that this gap needs to be filled. One question remains open. The assumption is this: Only changed (or related) data has to be processed. -Minimal data means maximum performance for planning functions. BW 7.30 hierarchy framework.
Introduction If you remember older releases of SAP NetWeaver BW hierarchies could only be loaded through the old 3.x data flow.
In this case you needed the so called direct update functionality of the corresponding InfoSource for uploading the hierarchy. This InfoSource 3.x was connected to an 3.x DataSource through update rules. Limitations of 3.x data flow for hierarchies This data flow has to be used in SAP NetWeaver BW 7.x, too, and could not be migrated to the new data flow. First, hierarchy DataSources were available only for flatfile and SAP source systems. The new BW 7.30 hierarchy framework With SAP NetWeaver BW 7.30 the hierarchy framework has been improved, you could now use the 7.x data flow with all its advantages. First you are able to use any BW object as source for a hierarchy, you are not limited to a DataSource for hierarchies.
New DataSource structure The hierarchy structure contained of the five fields NODEID, IOBJNM, NODENAME, LINK and PARENTID. Semantically Partitioned Objects. Abstract SAP NetWeaver BW 7.30 introduces the concept of semantic partitioning.
The following article explains how you can use semantically partitioned DataStores or InfoCubes to efficiently manage large data volumes and reduce the TCD/TCO. Motivation Enterprise Data Warehouses are the central source for BI applications and are faced with the challenge of efficiently managing constantly growing data volumes. A few years ago, Data Warehouse installations requiring terabytes of space were a rarity. In order to handle such large data quantities, we need to find modeling methods that guarantee the efficient delivery of data for reporting. Here is an example of a typical modeling scenario. If an error occurs (due to invalid master data) while the system is trying to activate one of the requests, the other requests cannot be activated either and are therefore initially not available for reporting.
Semantic partitioning provides a workaround here. Examples of semantically partitioned objects.