Welcome to the Learning Objekt Operational Analytics with Operational Data Providers. After the explanations of the entire ODP Architecture and the

Transcription

1 Welcome to the Learning Objekt Operational Analytics with Operational Data Providers. After the explanations of the entire ODP Architecture and the specifics of the TransientProvider layer this unit will focus on Operational Analytics in more detail concerning the usage of Analytic Queries based on Operational Data Providers. 1

2 The Objectives of this unit are to show a lot of details and specific benefits using Analytic Queries on ODPs. You will learn how: The consumption of ODP data is enabled any type of analytical user Interfaces and state of the art SAP Business Objects frontends Authorizations and Variables can be used for Analytc Queries on ODPs in the same way as it is supported for any other type of InfoProvider in the SAP Business Warehouse environment. BW Accelerator can help to optimize query performance for Operational Analytics in the Business Suite in the same way as it is used for the SAP Business Warehouse The Easy Query concept can help to build simple apps for particular purposes around Operational Analytics

3 Therefore the Agenda holds the following topics: Business Intelligence Frontend Perspective on ODP based TransientProviders Analytic Queries in Business Explorer Query Designer and Business Objects Analysis environments Creating individual analytic Queries Authorizations in the Analytic Query Using Variables in the Analytic Query Performance Optimization Using SAP NetWeaver BWA WebService Support for Operational Analytics using the Easy Query Functionality 3

4 For reporting and analysis on a TransientProvider derived from an operational data provider (ODP), you can either use an analytic query (query) as delivered for your operational analytics application or define a query of your own. The usage of Analytic Queries based on TransientProviders is transparent to the user compared to queries on top of BW-InfoProvider. Different frontend tools may give access to the data using different terms. To create or update Analytic queries on top of ODP the Business Explorer Query Designer is used. Available TransientProviders are displayed and logically grouped in InfoAreas and structured in InfoObjects. An InfoArea name is derived from the application component that is assigned using the package assignment to the underlying search and analysis model. The InfoArea description is also derived from the application component. For example the InfoArea name for models that are assigned to packages with application component CO-PC is 2O-CO-PC, the description is Product Cost Controlling. While editing in the BEx Query Designer, the InfoObjects belonging to the TransientProvider are displayed under InfoProviders. The InfoObjects are displayed here structured by key figures and the dimensions (Data Part, Key Part and Unit) for the characteristics. Due to this fact queries on top of ODPs can be edited in the same way as queries on other InfoProviders. For developing Queries on TransientProviders consider the Bex Query Designer Documentation. 4

5 This slide illustrates how Analytic Queries integrate into the entire Operational Data Provisioning architectural picture. As analytic queries typically read data from multiple DataSources the ODP layer defines relations between DataSources and exposes this very model the analytic query offering TransientProviders. 5

6 The ODP framework of the ERP system provides a TransientProvider Preview transaction to give an overview over the entire data model with all dimensions, key figures and related navigational attributes and texts up to refered hierarchies and authorizations. Exactly this picture has to be provided to the Analytic Query Layer by the particular BI tools. The following slides will give examples how TransientProviders can be found and consumed in different BI environments. 6

7 This example is showing the handling for ODP based TransientProviders in the Business Explorer Query Designer. For creating a new analytic query the designer offers the Create Query option which leads into an InfoProvider Selection dialog for the creation of a new query. InfoAreas represent different application components following the naming convention explained above. Per InfoArea finally TransientProviders are offered as the basic InfoProvider model for the query creation in the Bex Query Designer. The slide shows the example for a Customer Balances analysis in the Finance Accounts Receivable area. 7

8 Within BEx Query Designer queries are defined based on InfoProviders. InfoProviders offer a multidimensional model of an application component or a part of it. In our case the ODP based TransientProvider for Customer Balances in Financial Accounts Receivable appears as InfoProvider an offers the foundation for the query definition in decribing the entire multidimensional model for Customer Balances using InfoObjects for key figures and dimensions for characteristics, units and time relations. In this way TransientProviders are used to expose the ODP model to the BI user. 8

9 This slide explanes details of the text handling during query design. The screen shots show the properties of the InfoObject Company Code in the key part of the Dimensions. The option Value Display allows to choose between different options how to show textual information from the Company Code text tables that are also part of the underlying ODP model. 9

10 In this slide the hierarchy handling in the BEx Query Designer will be explained. The key field Reconciliation Account for Customer Balances supports hierarchies that are also reflected in the related ODP model. During designtime the Bex Query Designer allows to choose on of the available hierarchies Reconciliation Account for display and navigation purposes during query runtime. Beside that additional hierarchy parameters such as expanding level and position of lower level nodes can be defined in the properties for the dimension. 10

11 Authorzations are also reflected in Analytic Queries on ODP based TransienProviders. The screen shots document an example of an query run in the RSRT Query Monitor with active Authorization Check Log. The InfoProvider Check description shows again that the TransientProvider 2O0FIN_AR_T20 is seen here as an InfroProvider that is typical BW terminology. The consumption of information using this very Transientprovider is reflected by the activity 03 for which the user has to have the authorization finaly. Otherwise the query would have shown no results. 11

12 Numerous Business Suite Applications already provide huge Business Content for Operational Analytics. The screen shot shows an example for different predefined Operational Analytic Queries in Sales and Distribution and Accounts Receivable in a Business Client GUI. In this example the Customer Balance results are shown in the Chrystal Reports Viewer just another front end alternative out of the wide range of SAP Business Objects BI Tools. 12

13 In order to find all the details of an Operational Analytics Business Content Query beside the Business Content documentation you can use the Open Query option in the Bex Query Designer and navigate to a specific query again via InfoAreas. Standard queries follow the naming convention 0FIN (... In our case) whereby individual queries are in the Z-namespace. 13

14 The display behavior of the queries can be modified in various ways according to your needs. The sreen shots show examples for the Result Position per Rows and Columnes, Zero Supression behavior per row and/or column etc. 14

15 Another example for a Customer Balance Query result is shown here: It s the BEx Web result layout with different navigation options shown on the left side. The tabstrip Info provides details information about the query itself and the static filters or variable settings. A link to the Query documentation is also provided. 15

16 SAP Business Object Analysis Edition for Microsoft is SAPs most recent offering for an MS Excell based Analysis Add-In. Offering a modern and familiar Microsoft Office user experience it provides multidimensional analysis capabilities for SAP BW adressing the needs of an BI professional business user. SAP BO Analysis helps to build powerful Excel workbook BI applications and also supports BW-Integrated Planning. The connection to SAP BW backend systems uses the BI Consumer Services (BICS) interface. Therefore all BW Queries built with the BEx Query Designer are visible using the Select Data Sources dialog in Analysis and can be used as a data provider. Alternatively a TransientProvider can also be selected as data source. The system then generates a default query offering all dimensions and key figures of the underlying ODP. The structure of te ODP based Transientprovider is shown via InfoObjects in the well known way. 16

17 The grafic shows the conectivity options for BW backend systems in BO Analysis Edition for MS Office. This analytic interface is based on the BICS suite and therefore internal and generic using BEx Queries and TransientProviders. It allows to build complex frontend tools. 17

18 In this grafic the Select Data Source dialog is shown in detail. Data sources from BW are selectable per Role or InfoAreas. Existing BEx Queries are shown per Info Area and Application Component an can be directly consumed. Selecting an existing query leads into the Selection Prompt of the query and starts the particular analytical application. 18

19 The slide shows a query result and some background information of the query object itself, the involved components and the navigation options in the query result. 19

20 For Ad hoc reporting needs it is also possible to reference the TransientProvider level directly in SAP Business Objects Analysis, as shown in the grafic. In such a case the system will generate a default query in a similar way the BW Query Monitor (Transaction RSRT) does in the SAP Business Warehouse. 20

21 The result is based on all available information of the underlying ODP based TransientProvider. The technical name of the generated query follows the pattern TransientProvider name with the praefix!!a. 21

22 Amazingly Operational Data Provisioning also supports in memory indexing based on the BW Accelerator technology and frame work. Dedicated connectors allow to build up indexes and to store them in the BW Accelerator Appliance of the ERP system. The Connector Administration Cockpit supports all relevant process steps to bring Operational Analytics to the speed of thought that more and more businesses are asking for BW Accelerator guarantees optimal performance for Operational Analytics. The involvement of BWA indices can be controlled in the Run Time Statistics of the Query Monitor in BW 22

23 As the ODP concept is mainly based on the Data Provisioning layer for Search and Analytics the involvement of the TREX based BW Accelerator framework is possible and more than appreciated in Operational Analytics as well. 23

24 As shown in the graphic the Connector Administration Cockpit allows to administrate and monitor the BW Accelerator support for Operational Analytics in an ERP environment. Indexing schedules can be defined for the objects of an TransientProvider related connector and its dependent connectors. The Statistics Data for Query runtime finally shows that all data has been read using the BW Accelerator index which is shown here with the old terminology of Aggregate per InfoProvider. The name of the Aggregate is the name of the TransientProvider with the suffix $X. 24

25 Analytic Queries can be consumed in various ways from more or less sophisticated analytic applications on the frontend side. This example shows how the Easy Query tool of SAP BW (transaction eqmanager) can be used to generate a WebService that starts the query in an Web environment and is able to handover query results to mobile applications or gadgets. 25

26 The Easy Query concept allows to deliver an external interface for query data in SAP BW. This allows the early use of ABAP BICS in a well defined scenario. Nevertheless the ease of use comes with limitations. A static default view without drilldown is shown and no flexibility in formatting is available. 26

27 In summary you should now be able to consume ODP data using any type of analytical UI, to set authorizations in the Analytic Query, to use Variables in the Analytic Query, to optimize Query performance using the SAP NetWeaver BW Accelerator and to build Apps using Easy Query WebService Support for Analytic Queries

28 You can find further information on Using Analytic Queries for Operational Data Providers in the SAP Library for SAP NetWeaver 7.0 including Enhancement Package 3 under 28

29 29