Welcome to the session Operational Analytics with ODP TransientProvidersDerived from Operational Data Providers

1

This session is part of the Operational Analytics Learning map and will explain,what a TransientProvider derived from Operational Data Provider is, how theTransientProvider integrates into the Operational Analytics architecture, how theTransientProvider serves for Analytic Query Consumption and how to work withthe TransientProvider Preview and test a TransientProvider

The agenda topics of this session are the definition of the TransientProviderderived from Operational Data Provider, theTransientProvider and Operational Analytics Architecture, the TransientProvider asstructural element for Analytic Query Consumption, the TransientProvider Previewand testing the TransientProvider

3

The SAP NetWeaver BW Analytic Engine uses InfoProviders as a basis to defineanalytic queries. A TransientProvider derived from Operational Data Provider is aspecific InfoProvider type for Operational Analytics.

Such a TransientProvider is derived from the ODP metadata definitionautomatically (no additional modeling necessary) anddynamically (no separate metadata persistency)

Analytic queries on top of TransientProviders can be edited in the same way asqueries on other InfoProviders.TransientProvider names are derived from ODP names: Technical name of theTransientProvider = 2O <technical name of the ODP>and description of theTransientProvider = ODP Description

4

This slide illustrates how the TransientProvider derived from Operational DataProvider integrate into the Operational Data Provisioning architectural picture.For this purpose we have a closer look at the Data Provisioning part of the picture.(click animation)

As you have learned already, the analytic query typically reads data from multipleDataSources.

(click animation)In Operational Analytics scenarios, DataSource relations are defined within theODP layer and exposed to the analytic query by the TransientProvider.

5

6

On the following slides you will learn about the general structural elements for Analytic Query consumption and how theTransientProvider fits into the picture.

(click animation)The central structural elements of an analytic query engine deal with Transaction data / facts. This is the core data youwant to analyze - key figures in the context of characteristics. For example sales order items, quantity and net value ofproducts that were ordered by customers. Typical organizational characteristics would be the sales organization,distribution channels and divisions. You could directly report on this data, essentially a flat table of data records.But you need to know which field to handle as key figure and how to properly aggregate (e.g. sum or last).

(click animation)If you think of the customer or the product, these are typical master data entities. They might have a lot of attributes whichyou may want to include in your analysis. Other transaction data refer to the same entities. So it makes highly sense toshare such master data. This is why the master data is modeled separately and joined to the transaction data at query runtime.

(click animation)Another reasonable thing to do is to have an independent access to texts as they are typically language dependent andare added to the final result set only.

(click animation)The last structural element is the hierarchies that are always related to master data and that need to adhereto a distinct pattern themselves. Essentially these are different segments for header and hierarchy elementsthat refer to each other with the common parent child relationships.E.g. customer and product hierarchy, organizational unit hierarchy, financial statement hierarchy

(click animation)For the SAP NetWeaver Analytic Engine the InfoProvider plays the role of the central facts.

(click animation)In the InfoObject the other structural elements are modeled.

InfoProviders and InfoObjects are the basic elements for analytical query consumption.

7

(click animation)In the operational analytics picture each structural element you saw on theprevious slide is modeled as an ODP.For facts the ODP can either be an ODP for transaction or an ODP for masterdata.

(click animation)At runtime the entities that are known to the SAP NetWeaver Analytic Engine areinstantiated as transient objects, namely the TransientProvider and the transientInfoObject. They are presented to the query designer in pretty much the same wayas in the BW.

This picture shows an example for a TransientProvider from ODP Content forAccounts Receivable.

8

The TransientProvider has no metadata persistency. A preview functionenables you to display how the TransientProvider is derived from thedefinition of an Operational Data Provider.In order to display a preview for a TransientProvider call transactionRSRTS_ODP_DIS.You can find the TransientProvider based on• ODP selection or• Query selection (click animation)

You can choose between displaying the preview for• the active version• the version that is currently saved in the Search and Analytics Modeler

(modeled version)

Choose Execute to display the preview.

9

The preview displays the TransientProvider for the selected Operational DataProvider in a tree structure. To show how the TransientProvider can be used todefine an analytic query, the tree is built up in the same way as the InfoProviderdisplay in the SAP BEx Query Designer.

10

For each InfoObject the preview gives information on(click animation)• the InfoObject name• the name of the ODP field that the InfoObject is derived from• technical properties of the ODP field like data type and length• the InfoObject descriptionFor characteristics icons indicate whether the characteristic has master dataattributes, texts or hierarchies or whether it is authorization relevant.

Furthermore the preview provides you with reference information for certainInfoObjects:(click animation)For example, for a characteristic an icon indicates that the InfoObject is part of theTransientProvider because it has been defined as navigation attribute for the ODP.In addition the system provides the name of the ODP where the navigationattribute originates from.(click animation)For key figures the system displays the name of the associated unit.

11

For characteristics with master data attributes, texts or hierarchies, the nodes inthe tree structure can be expanded to display further information.(click animation)On the level below the characteristic, you can see the associated OperationalData Providers (ODP) with information on their underlying data source.For the ODP field list icons indicate if the fields of the associated ODP are used asattributes in the TransientProvider.

12

You can test the TransientProvider in the Query Monitor

Enter the default Query name for the TransientProvider and choose the buttonExecute.

When executing the Query in the debug mode with the debug optionDo not use BWA the use of all BWA indexes (transaction + master data) can beswitched off for that session

The default Query name is: 2O<ODP name>/!2O<ODP name>.The default Queryname for a Query with navigation attributes is: 2O<ODP name>/!!A2O<ODPname>.

13

In summary you should now be able to understand what a TransientProviderderived from Operational Data Provider is, how the TransientProvider integratesinto the Operational Analytics architecture, how the TransientProvider serves forAnalytic Query Consumption and you should be able to work with theTransientProvider Preview and test a TransientProvider.

You can find further information on TransientProviders Derived from OperationalData Providers in the SAP Library for SAP NetWeaver 7.0 including EnhancementPackage 3 under http://help.sap.com.

15

16