This download file shows detailed view for all updates from BW 7.5 SP00 to SP05 released from SAP help portal.

Transcription

1 This download file shows detailed view for all updates from BW 7.5 SP00 to SP05 released from SAP help portal.

2 (1) InfoObject (New) As of BW backend version 7.5 SPS00, it is possible to model InfoObjects in the BW modeling tools. This provides you with all the functions that are available in the BW back end. The UI has been made clearer, and has been enriched with a number of extra functions: You can now model InfoObjects with attributes to referencing characteristics. You can create time characteristics with attributes. For key figures, you can now select the data type Integer 8. You can define characteristics in such a way that the initial value in the query is shown right at the start. It is still possible to model InfoObjects on the BW back end. If you use SAP HANA, we do however recommend creating all new InfoObjects in the BW modeling tools

3 (2) Open ODS View (Enhanced) The following enhancements have been made in connection with Open ODS views: As of BW back end version 7.4 SPS11 / 7.5 SPS00: You can swap the source object of an Open ODS view. You can generate a data flow for an Open ODS view. This allows you to create the following objects: o DataStore object (advanced) as persistence for an Open ODS view, comparable with a Persistent Staging Area (PSA) o A transformation, which you can use for example to perform data type conversions, assignments or string operations on source data As of BW back end version 7.4 SPS12 / 7.5 SPS00: You can create an Open ODS view by copying an existing one. You can then modify this copy to your liking.

4 (3) DataStore Object (advanced) (Enhanced) As of BW back end version 7.5 SPS00, you can now use the following new and enhanced modeling functions for DataStore objects (advanced): You can now create DataStore objects (advanced) for direct writing. As well as storing the inbound table as an extended table when working with a DataStore object (advanced), you can now also store all of the tables belonging to the DataStore object. You can activate navigation attributes for use in extraction. Non-cumulative key figures can now also be used in DataStore objects (advanced) with the properties Activate/Compress Data and Write Change Log. You can activate DataStore objects (advanced) for planning.

5 (4) Reusable Query Components (New) A reusable query component is an object that is not created within the scope of a query definition, but either for an InfoProvider or an InfoObject. You can then use it in all queries that are defined for this InfoProvider or with this InfoObject. When a reusable object is changed, the changes are applied everywhere that the object is used. This section describes functions, enhancements and changes that apply as of BW back end version 7.4 SPS13 / 7.5 SPS00. The following objects are reusable: Restricted key figure Calculated key figure Structure Filter Variable

6 (5) Creating a Query (Enhanced) The function Constant Selection has been enhanced. Several examples have been added to the documentation. This section describes functions, enhancements and changes that apply as of BW back end version 7.4 SPS13 / 7.5 SPS00. Constant Selection The Constant Selection property is available for selections in structural components, cells and restricted key figures in queries. If you go to the General tab and then go to the Constant Selection screen area and select total as constant, this means that this selection cannot be used at runtime for navigation and filtering. Therefore this selection can serve as a reference size.

7 You can also define components of selections - individual characteristics and their filter values - as constant. To do this, open the Edit Selection dialog box, go to the Edit Selection screen and choose Constant Selection from the context menu of the selection component. During navigation, the selection only remains unaffected by filters with relation to this characteristic. Local Calculations On the Calculations tab, you can configure local calculation settings for a formula or a selection. Several examples have been added to the documentation.

8 (6) SAP HANA Exit (New) Variable processing type SAP HANA Exit allows you to use an AMDP class implementation to determine default values for variables. This section describes functions, enhancements and changes that apply as of BW back end version 7.5 SPS00. We particularly recommend using the SAP HANA Exit in queries that you want to generate an external SAP HANA view for, and which special requirements apply for in terms of determining the variable values.

9 (7) Creating a Query (Enhanced) This chapter described functions, enhancements and changes that apply as of BW back end version 7.4 SPS12 / 7.5 SPS00. Creating a Query as a Copy You can use an existing query as a template for defining a new one. To do this, you first need to copy the existing query. You can then modify this copy to your liking. Tab Sheet Definition Characteristic: In the documentation in the General tab, information has been added about the Display Level screen area. Selection: On the Calculation screen, you can specify for a structure component which rules are used to recalculate result rows and/or single values, and in which direction the calculations are performed. The documentation about local calculations has been enhanced.

10 (8) Defining Cells in the Query (New) This chapter described functions, enhancements and changes that apply as of BW back end version 7.4 SPS12 / 7.5 SPS00. If you use two structures in a query, the system implicitly creates a generic cell definition at the intersection of two structural elements, thus defining the value to be presented in the cell. This implicit cell definition can be overwritten by an explicit definition. This defines an exception cell. You can add one or more help cells to an exception cell.

11 (9) Creating Input-Ready Queries (New) You can now use the BW Modeling tools in Eclipse to create and edit input-ready queries. This chapter described functions, enhancements and changes that apply as of BW back end version 7.4 SPS12 / 7.5 SPS00. You can use these queries for manual planning or to enter short texts in a query at runtime.

12 (10) Making Data Integrity Settings in the Query (New) This chapter described functions, enhancements and changes that apply as of BW back end version 7.4 SPS12 / 7.5 SPS00. Under Extended in the General tab (for the query as a whole), you can make data integrity settings. These are relevant if your back-end system supports this (request status, near-line storage). Under Extended, you can also find Document links.

13 (11) Defining Exception Cells and Help Cells in Queries (New) In queries with two structures, a cell arises from the intersection of two structural elements. You can overwrite this implicit cell definition with an explicit one. This chapter described functions, enhancements and changes that apply as of BW back end version 7.4 SPS12 / 7.5 SPS00. On the Cells tab, you can specify whether a cell is used as an exception cell or help cell. Note that using exception cells can have a negative impact on performance when you execute your query.

14 (12) Planning Function Formula (Enhanced) In BW Integrated Planning, planning function type Formula provides you with a simple programming language that you can use to manipulate transaction data. The following changes have been introduced in connection with this planning function type: There are cases where you would like to receive the selection for a characteristic, as it would otherwise be possible to read data without being authorized for example, and cases where you need more reference data. You can influence the selection of the reference data by using the KEEP and the ENHANCE statement. To better structure complex formulas, you can modularize them. You can use the INCLUDE statement to include formulas from various aggregation levels

15 (13) Implementing Business Logic for Planning Function Types on the SAP HANA Database (Enhanced) If you implement an SQLScript procedure, you can run a customer-specific planning function type optimized on the SAP HANA database. SQLScript procedures that you want to call using interface method if_rspls_sql_script -> execute_sql_script can now be implemented as AMDPs (ABAP managed database procedures). New parameters are also available.

16 (14) Aggregation: Exception Aggregations of Simple Linear Regression (New) The analytic manager supports the following exception aggregations based on the model of simple linear regression: Gradient: With exception aggregation SLS, the gradient of the regression line is displayed. Y Point of Intersection: With the exception aggregation SLI, the value of the point of intersection between the regression line and the Y axis (for x=0) is displayed. Empirical Correlation Coefficient: With exception aggregation SLS, the empirical correlation coefficient is displayed, which specifies how accurate the estimated regression line is (in other words, how far the points in the point set are from the straight line).

17 (15) Aggregation: Exception Aggregation Median (New) With exception aggregation Median, the central value of a set sorted in ascending order is displayed. (16) Aggregation: IF Operator (New) Conditional calculations can be performed by the IF operator with three operands. Prerequisite: You create queries with the BW Modeling Tools. BEx Query Designer does not support this operator. (17) Cache Parameters (Enhanced) On the Edit Cache Parameters screen, you can change the settings for the OLAP cache. The new option Automatic Limit has been added. If this parameter is set, the system compares the estimated search time with the estimated calculation time needed to recalculate the queried data while searching for a suitable cache object.

18 (18) Operations in SAP HANA / BWA (Modified) Enhancements have been made to the Exception Aggregation (Standard) (6) option. This is the standard option for optimized access to the SAP HANA DB. You can also calculate the exception aggregation in the BWA. Calculation of exception aggregation in the SAP HANA DB is now also possible for the following exception aggregations: First Value Last Value The restriction regarding characteristics with high cardinality as reference characteristic for exception aggregation no longer applies.

19 (19) Generating SAP HANA Views for Hierarchies (New) If you generate a SAP HANA view for an InfoObject that has hierarchies, a SAP HANA view is generated for the hierarchies too. (20) BW Workspaces: Local Hierarchies (Enhanced) You can now create local hierarchies in BW workspaces. (21) BW Workspaces: BW Workspace Query Designer (New) BW Workspace Designer enables casual users to easily create new BW Worskpace queries for data analysis or enhance existing queries. A BW Workspace query always refers to a BW Workspace. It has a subset of the functions of an analytic query. You can also enhance analytic queries in BW Workspace Query Designer. For every BW Workspace query, the system generates a BW query ID. This allows a Workspace query to be consumed like other analytic query from SAP BW.

20 (22) Pruning (New) When DataStore objects (advanced) are activated with nearline connection, CompositeProviders, MultiProviders and semantically partitioned objects, SAP HANA database pruning information is added to the column view of these objects in the BW schema.

21 (23) ODP Based Data Extraction via OData (New) For consistent and scalable (delta ) extraction of ODP data to external, non-abap recipients, such as cloud and mobile applications, you can use ODP-based data extraction via OData. ODP-based data extraction is available for all ODP contexts in the back end system for the extraction of available ODP contexts, such as SAP NetWeaver Business Warehouse (for InfoProviders of the BW system), DataSource / extractors or HANA infrormation layer (SAP HANA information models [calculation views]). With SAP Gateway Foundation and the generation of an OData service (with the SAP Gateway Service Builder) based on an Operational Data Providers (ODP), the data is made available for extraction. The service (URL) can then be called from an external application (OData client) via OData/HTTP.

22 (24) SAP HANA Dynamic Tiering for Using Extended Tables (Enhanced) The following enhancements have been introduced in connection with using extended tables for BW objects: You can use a program to define how DataSources and write-optimized DataStore objects should be treated with regard to multi-temperature data management with SAP HANA dynamic tiering. You can use this program in particular to define whether or not existing data in the objects should be moved. DataStore objects (advanced) are now supported with all of their tables.

23 (25) Transferring Demo Scenarios with SDATA (Enhanced) The following new and enhanced functions have been introduced in connection with transferring BW test and demo scenarios with SDATA: You can define filter conditions for DataStore objects (classic). You can modify the data for individual BW objects before transferal to the target system by manipulating the data or removing a certain percentage of the data. You can set an (existing) InfoArea as the target for BW objects to be transferred to a target system. You can display a history of the transfer logs and can delete logs.

24 InfoObjects from technical content (0*) can be transferred explicitly. For DataStore objects (advanced), you can now also transfer request data (in addition to metadata). The requests are written via request management here. This means that none of the restrictions that applied for DataStore objects (classic) apply anymore. If access is not made to a local client, you can perform the SDATA transfer in the background, with large amounts of data for example. If the transfer target is in a local database, you can write the data to a transport request and use the transport system to transfer it to a connected system.

25 (26) Request Housekeeping (New) (27) Exchanging Data Between BW Systems Using the ODP Source System (Enhanced) The data mart scenario using an ODP source system now also supports full extraction of CompositeProviders (object type HCPR). (28) Process Chains: Process Chain Type for Deleting Data from DataStore Objects (advanced) (new) To delete data from the DataStore object (advanced), you can use process chain type Deleting Data from DataStore Objects (advanced).

26 (29) Process Chains for Data Archiving (Enhanced) When a process chain is used for archiving, the process steps for the copy phase, the verification phase and the deletion phase can be processed in parallel. (30) Open ODS View Maintenance in the SAP GUI (Deactivated) In previous releases, it was possible to create and edit Open ODS views in the Data Warehousing Workbench (SAP GUI): Modeling of Open ODS views is now only possible in the BW modeling tools in Eclipse. Open ODS views are still displayed in the Data Warehousing Workbench. In places that it was previously possible to access the maintenance screen for Open ODS views from, information is displayed to this effect, and a restricted display opens.

27 (31) BW Workspace Query Designer (enhanced) This section describes enhancements made to BW Workspace Query Designer in 7.5 SP01. Simplified URLs for Calling BW Workspace Query Designer The syntax of the URLs in the web browser has been simplified: <Web Server Host> : <Web Server Port> /sap/bw/wqd/index.html <Web Server Host> : <Web Server Port> /sap/bw/wqd/index.html Loading Additional Data and Facts In the context of planning (and only then in case you have not added any dimensions yet) the following new option is now available: Add New Input-Ready Measure.

28 (32) Process Type for Creating Database Statistics for Virtual Tables (New) Database statistics for virtual tables are used by the system to optimize query performance for InfoProviders that use SAP HANA Smart Data Access. You can use a process type to integrate the creation of database statistics for the virtual table for an InfoProvider that uses SAP HANA Smart Data Access into a process chain.

29 (33) Locale Favorites (Deleted) The Local Favorites node has been removed from the Project Explorer view. The associated functions in the context menu have also been removed together with this node. The Back End Favorites node, which stores cross-project favorites in the BW back end system, has been renamed as Favorites. The Add to Favorites functions in the context menus and create wizards for the objects now relate to the cross-project favorites stored in the BW back end system. If you want to add objects created in the local favorites to the cross-project favorites stored in the BW back end system, open the context menu for the Favorites node in your BW project and choose Import from Local Favorites.

30 (34) CompositeProvider (Changed) In the default setting, only navigation attributes that are already assigned are displayed in the CompositeProvider editor. You can choose to display all navigation attributes of a participating InfoProvider however. (35) Where-Used List for SAP HANA Views in CompositeProviders (New) You can use the BW object search n the BW modeling tools to run a where-used list for SAP HANA views in CompositeProviders. This function is available as of BW back end versions 7.4 SPS14 and 7.5 SPS02.

31 (36) BW Workspace Query Designer (enhanced) This section describes the enhancements made to BW Workspace Query Designer in 7.5 SP02. Create InfoProviders from Local Data New Data Type: You can use data type InfoObject Assignment to select a different InfoObject as the basis of the data type. If there is a local dimension for a dimension, this can also be selected. Assignment of Units and Currencies: If a measure in the neighboring column is positioned before the associated unit or currency, the system recognizes this and automatically proposes the corresponding assignment. If the unit or currency column is not positioned immediately after the associated measure column, or relates to multiple measure columns, you have to make the assignment yourself. Key Field: The setting Key Field is set by default for dimensions. In other words, these are key fields of the local provider.

32 Create InfoProviders from Local Data and BW Data In the dimension properties, you can change the name of the dimension and specify whether you want to use the local dimension (if provided). This change cannot be made once plannable key figures have been added to the CompositeProvider. Load Additional Data You can view the objects of the InfoProviders in a sorted view. Instead of displaying the additional data in the Additional Data directory, the system then assigns it to the relevant categories (dimensions, measures or data records). Besides selecting a local file, you can now also select a local provider from the current workspace as the source (from which the new object or the new data records are loaded).

33 The user interface helps you to assign metadata or data in the preview and input table; simply hover over the status symbols in the mapping row to view details of the current status. Once you are satisfied with the assignment, and there are no errors, choose Transfer in order to transfer the data to the entry table. If this already contains data, and you want to replace this data, choose Replace. If this already contains data, and you want to replace this data, choose Replace. The function keys below the entry table allow you to perform the following functions: Add Generated Rows, Download. You can include additional dimensions or key figures.

34 BW Workspace Query You can copy a structure element by using the relevant function in the context menu. You can save a local copy of a BW Workspace query under a different name by choosing Save As. The function for executing a query has been enhanced. It is now possible to use various reporting tools for the preview. These include SAP BusinessObjects Design Studio and SAP BusinessObjects Analysis, edition for Microsoft Office. The selection options are specified in the SAP Customizing Implementation Guide.

35 (37) Partitioning (Enhanced) InfoCubes containing time characteristic Calendar Week (0CALWEEK) can now also be partitioned by calendar week. (38) Open Hub Destination (Enhanced) It is now also possible to change data records for open hub destinations with DB Table as their target. (39) ODP-Based Data Extraction via OData (Changed) For entity sets that can fetch data from the source in delta mode, it is now possible to display a history of existing delta links. If errors occur, it is also possible to restore data changed by a delta link since a given date.

36 (40) Data Archiving Process for DataStore Objects (Advanced) - (Enhanced) You can archive data from DataStore objects (advanced). Only archiving into near-line storage is supported here. Data from DataStore objects (advanced) that contain noncumulative key figures or consist solely of an inbound table (if no modeling properties are selected) cannot be archived at present.

37 (41) Creating an Aggregation Level (New) You can create aggregation levels in the BW Modeling Tools. This function is available in BW back end version 7.5 SPS04 and higher. To plan data manually or to change it using planning functions, you need a planning-specific InfoProvider known as the aggregation level. You use the aggregation level to set the granularity of planning by only adding characteristics and key figures of the underlying InfoProvider for planning. Aggregation levels that you create in the BW Modeling tools are also available in Planning Modeler. You can also model other planning-specific metadata objects (characteristic relationships, data slices, planning function and planning sequence) in Planning Modeler.

38 (42) InfoSource (New) You can create InfoSources in the BW Modeling Tools. You need authorization object S_RS_TRCS for these InfoSources. Authorization object S_RS_ISNEW is still checked for all InfoSources created in Data Warehousing Workbench. This function is available in BW back end version 7.5 SPS04 and higher.

39 (43) DataSources (new) You can create and edit DataSources in the BW Modeling tools. For certain source system types, you can create DataSources using a wizard in a native Eclipse editor (ODP and SAP HANA). For other source system types, you create DataSources either by replication in the BW Modeling tools or by calling the Data Warehousing Workbench creation transaction embedded in the BW Modeling tools. For certain source system types, you can edit DataSources in the native Eclipse editor (ODP, SAP HANA, SAP and BW). For other source system types, you edit DataSources by calling the Data Warehousing Workbench editing transaction embedded in the BW Modeling tools.

40 For the source system types SAP HANA and ODP, you can run a comparison of the metadata and update the DataSource in the native Eclipse editor. For replicating source systems, you can replicate the DataSource in the Data Sources tree in the BW Modeling tools. These functions are available in BW back end version 7.5 SPS04 and higher.

41 (44) InfoObject (Enhanced) When editing characteristics, you can switch on transitive attributes. This function is available in BW back end version 7.5 SPS04 and higher (45) DataStore Object (advanced) (Enhanced) The following new functions are available for the DataStore object (advanced): In the modeling properties, you can use the Snapshot Support function to make DataSources update deltas, even if they only allow full update. Selective deletion from a DataStore object (advanced) can be passed on to other connected InfoProviders. These functions are available in BW back end version 7.5 SPS04 and higher.

42 (46) CompositeProvider (Enhanced) The following enhancements have been introduced for CompositeProviders: You can use temporal joins in a CompositeProvider. You can save a CompositeProvider under a different name in order to create a copy of it. You can make settings for the query properties of an InfoProvider participating in a query. These functions are available in BW back end version 7.5 SPS04 and higher. (47) Open Hub Destination (New) You can create open hub destinations in den BW Modeling Tools. This function is available in BW back end version 7.5 SPS04 and higher.

43 (48) Editing Hierarchies (New) Editing of hierarchies in Web Dynpro ABAP is integrated in the BW Modeling Tools can be called from the InfoObject editing screen. This function is available in BW back end version 7.5 SPS04 and higher. (49) Semantic Groups (New) You can create semantic groups in the BW Modeling tools. This function is available in BW back end version 7.5 SPS04 and higher.

44 (50) Routines in Transformations (Changed) You can now also create routines (start, field or end routines) as ABAP managed database procedures (ADMP). If execution of a transformation in ABAP and SAP HANA is supported, you can create either an ABAP routine or an ABAP managed database procedure (ADMP). This function is available in BW back end version 7.5 SPS04 and higher.

45 (50) Routines in Transformations (Changed) You can now also create routines (start, field or end routines) as ABAP managed database procedures (ADMP). If execution of a transformation in ABAP and SAP HANA is supported, you can create either an ABAP routine or an ABAP managed database procedure (ADMP). This function is available in BW back end version 7.5 SPS04 and higher.

46 (51) Open ODS View (Enhanced) The following enhancements have been made to the Open ODS view in BW back end version 7.5 SPS04: For the source types Database Table or View and Virtual table using SAP HANA Smart Data Access : If you want to create a source system for the connection to the source when creating an Open ODS view, a SAP HANA source system is now created. Previously a DB connect source system was created. If you generate a data flow, a SAP HANA DataSource is now created. Previously a DB connect DataSource was created. With Open ODS views, you can directly access the source object of a SAP HANA source system.

47 SAP HANA source systems use SAP HANA Smart Data Integration to support real-time replication. You can use Open ODS views to directly access the data in the DataSource (target table for a remote subscription of type UPSERT). The wizard for creating Open ODS views has been made more user-friendly. The functions for adding semantics, for swapping the source and for creating the data flow now also use the wizard. A proposal for automatic assignment of the source fields to the field categories of the Open ODS view was previously always made during creation of the Open ODS view. In the wizard for creating the Open ODS view, you can now control the automatic assignment with the Create with Proposal flag. In the default setting, automatic assignment is carried out. You can use navigation attributes for InfoObjects with virtual master data.

48 (52) InfoArea (New) You can now create and delete InfoAreas in the BW Modeling tools, and move objects and InfoAreas in the InfoArea hierarchy. This function is available in BW back end version 7.5 SPS04 and higher. (53) General Functions (Enhanced) The following general functions in the BW Modeling tools are either new or have been changed: Sorting in the Project Explorer view: The Toggle Sorting pushbutton has been replaced by Alphabetical Order for BW Objects in the context menu of BW projects. You can open a BW object in another project. With this function, you can navigate rapidly between two versions of the same BW object in two different projects.

49 You can create a hyperlink to another BW object in the BW Modeling tools. This allows you to share the object by or a document of your choosing. The recipient can use this hyperlink to open the referenced BW object in another installation of the BW Modeling tools in the corresponding BW project. From the editor, you can save a copy of InfoObjects, CompositeProviders and queries, and save the copy under a new name. This function is available in BW back end version 7.5 SPS04 and higher. With a native Eclipse editor, you can move BW objects in the Project Explorer view in the InfoArea hierarchy. This function is available in BW back end version 7.5 SPS04 and higher. The following context menu entries in the Project Explorer view have been renamed:

50 (54) Data Sources Tree in the Project Explorer View (New) The Project Explorer view in the BW Modeling tools now contains a Data Sources node, which displays the source systems of the connected BW system with its application component hierarchies and DataSources. This function is available in BW back end version 7.5 SPS04 and higher. (55) Favorites (Enhanced) The following new functions have been added for managing favorites in the BW Modeling tools: You can now use a search dialog to copy objects from the Favorites tree to the favorites. Previously it was only possible to add to the favorites via the BW Repository tree. You can remove all objects from the favorites at once. This function is available in BW back end version 7.5 SPS04 and higher.

51 (56) Data Warehousing: Data Warehouse Management This section describes all the new functions, enhancements and changes for Data Warehouse Management in SAP Business Warehouse (BW). (57) Process Types (Changed) There are different new, changed and deleted process types. For the administration of DataStore objects (advanced) there are a number of new process types, while others have been changed or deleted: o The process type Activating Requests from the DataStore Object has been changed to Activating Requests from the DataStore Object (Classic). You can now only activate requests in DataStore objects (classic) and not in DataStore objects (advanced). If you are already using this process type in your process chains for DataStore objects (advanced) however, these process chains will continue to function in the same way.

52 o The process data type Activating Requests from the DataStore Object (advanced) is new. You can use this to activate requests from the DataStore object (advanced). o The process data type Cleaning up Old Requests in the DataStore Object (advanced) is new. You can use this to remove requests from the DataStore object (advanced) or to compress them. o The process data type Deleting Requests from the DataStore Object (advanced) has been deleted. If you are using this process type in your process chains, they will continue to function in the same way. You cannot create any new process chains with this process type however. There is a new process type - Start SAP HANA Remote Subscription - for the delta initialization of real-time replication with a SAP HANA source system.

53 (58) Authorizations (New) New authorization objects in object class RS: S_RS_IOBJA: Authorizations for working with InfoObjects that are structured using InfoAreas S_RS_TRCS: Authorizations for working with InfoSources (InfoAreas) for BW systems that are using a SAP HANA database. (59) Process Chains for Streaming (new) In a BW system running on the SAP HANA database, you can set the Streaming Mode attribute for a process chain. A process chain for streaming can be started and executed very frequently, and makes it possible to update data in real-time to DataStore objects (advanced). The architecture of SAP BW on SAP HANA is also simplified by the provision of a holistic solution for periodic and very frequent scheduling and for streaming.

54 (60) Analytic Manager This section describes all the new functions, enhancements and changes for the Analytic Manager in SAP Business Warehouse (BW). (61) BW Workspaces (Enhanced) The following enhancements have been made BW workspaces: You can load data from local providers to central BW providers. You can now switch on navigation attributes for local CompositeProviders. RSL_WORKSPACE_SUBMISSION_BADI: You can also create additional checks for transferring data from local providers to central providers.

55 (62) Processing Effective Local Filters (FEMS) (Modified) Effective local filters in queries on InfoCubes in SAP HANA are processed by default in the database. Effective local filters (FEMS > 0) can now also be processed on other database platforms directly in the database. This reduces the consumption of resources on the application server, as less data is transferred from the database to the application server. This is supported by Microsoft SQL Server and DB2 (Linux, Unix, Windows, z/os and i/os).

56 (63) Query Property Operations in SAP HANA / SAP NetWeaver BW Accelerator (enhanced) In the query runtime properties, you can specify which operations should be performed in the SAP HANA or SAP NetWeaver BW Accelerator. Exception Aggregation (Standard) (6): Calculation of exception aggregation in the SAP HANA or SAP NetWeaver BW Accelerator is possible for the following exception aggregations: No aggregation if there is more than one record [NO1] No aggregation if there is more than one value [NO2] Standard Deviation [STD] Variance [VAR]

57 Formulas calculated in the SAP HANA (7): In SAP HANA 1.0 SP11 and higher, numerous exception aggregations are supported, especially for calculating formula exception aggregations. A formula with exception aggregation can only be calculated in SAP HANA if the formula result does not have a currency or a unit, or the currency or unit of the formula result is taken over from another individual operand. (64) Entries in the IMG (New) There is a new activity in the IMG: SAP Customizing Implementation Guide > SAP NetWeaver > Business Warehouse > General Settings > Prerequisites for Hierarchy Maintenance