Activating and Transporting Operational Analytics Scenarios
To keep the manual activities in a customer production system to a minimum and to support the enhancement concept, our recommendation for Operational Analytics is a 3 system landscape comprising development system, test system and production system.
In this system landscape, you activate and test an operational analytics scenario in your development system and then collect all objects required for the scenario in a transport request. Following the import to the follow-on system (test or production system), the scenario can be used without the need for further activities.
Note that the indexing activities with SAP HANA or SAP BW Accelerator (creating the connector or scheduling indexing, for example) have to be performed directly in the administration cockpit and cannot be transported.
Version Concept for Operational Data Providers
The version concept for operational data providers is based on the BW version concept: To be able to use an operational data provider (ODP) in an operational analytics scenario, an active version is required. For the active version, logical transport object (TLOGO object) ODPE is provided. Unlike other objects in the BW version concept however, there is no TLOGO objects for the delivery version. The delivery version of the ODP is simulated from the ODP metadata in the search repository.
The activation and transport of operational data providers is based on the technology for BI Content activation and the BW transport connection. For more information, see Transporting BW Objects and Creating, Delivering and Installing BI Content in the documentation for SAP NetWeaver Business Warehouse.
When activating and transporting objects for operational analytics, two different scenarios can apply:
Activating and transporting Business Content delivered by SAP
Transporting customer enhancements and customer-defined scenarios
Activating and Transporting Business Content Delivered by SAP (BI Content Activation Workbench)
The tool that you use to activate and transport Business Content delivered by SAP for operational data provisioning in the development system is the BI Content Activation Workbench (transaction BSANLY_BI_ACTIVATION). The BI Content Activation Workbench uses the technology from BI Content activation and BW transport connection.
Content is activated using the BI Content bundle. When one of these bundles is activated, the source system DataSources (object type OSOA), operational data providers (ODPs) and BW metadata objects (analytic queries, MultiProviders and the like) contained in it are all activated too.
If you perform the activation with transport, the objects in question are written to a transport request.
When an ODP is activated, a connector is created in the development system as well. This is not written to the transport request however.
In the standard setting in the BI Content Activation Workbench, existing active DataSources in the customer system are compared with the delivered version. There can be active DataSources for example if a BW system is already connected to the application, and the BW system in question uses this DataSource.
You can find out more about the BI Content Activation Workbench in the documentation for the SAP Business Suite, under BI Content Activation Workbench (CA-EPT-ACT).
If errors occur with certain objects when activating using the BI Content Activation Workbench, you can still activate these objects using the BI Content functional area in the Data Warehousing Workbench (transaction RSOR). More information: Activating and Transporting Customer-Defined Scenarios.
Transporting Customer Enhancements or Customer-Defined Scenarios (Functional Area Transport Connection - Transaction RSOR)
The tool that you use to transport customer enhancements of Business Content delivered by SAP or customer scenarios in the development system is the Transport Connection functional area in the Data Warehousing Workbench (transaction RSOR).
Transporting Customer Enhancements
Once you have activated the scenario using the BI Content Activation Workbench, you have performed the customer enhancement for the ODP. You have added the search and analysis model, created a connector (together with an active ODP version) in your customer-specific software component and have also created a query for the enhancement. More information: Enhancing Operational Data Providers.
To transport the customer enhancement, use the transport connection in the Data Warehousing Workbench (transaction RSOR). You can find information about the basic procedure in the documentation for SAP NetWeaver Business Warehouse, under Transporting BW Objects. Note the following features however:
To collect the objects, click Object Types in the Transport Connection pane in transaction RSOR.
You can collect the objects from the operational analytics scenario using object type Operational Data Provider, MultiProvider or Query.
To collect objects using object type Operational Data Provider, proceed as follows:
Open the Operational Data Provider node (technical name ODPE) under More Types in the All Objects According to Type pane.
To collect the ODPs, choose Select Objects. A screen now appears showing all active ODPs. Select the enhanced ODP/ODPs and apply your selection.
During collection, all ODPs belonging to a model are collected, together with the various ODP types (extraction, projection, join etc.). This is necessary because complete search and analysis models are activated with all the ODPs they contain when a connector is created.
When the collected objects are written to the transport request, the associated active source system DataSources (TLOGO object OSOA) are also written to the transport request.
When the transport request is released, the active versions of all collected objects are added to it.
Activating and Transporting Customer-Defined Scenarios
You activate customer-defined scenarios in the BI Content functional area in the Data Warehousing Workbench (transaction RSOR). You can find information about the basic procedure in the documentation for SAP NetWeaver Business Warehouse, under Copying BI Content to the Active Version. Note the following features however:
To collect the objects, choose Object Types in transaction RSOR.
You can collect the objects from the operational analytics scenario using object type Operational Data Provider, MultiProvider or Query.
To collect objects using object type Operational Data Provider, proceed as follows:
Open the Operational Data Provider node (technical name ODPE) under More Types in the All Objects According to Type pane.
To collect the ODPs, choose Select Objects. A screen now appears showing ODPs delivered by SAP and ODPs modeled locally in this system. Select the ODP/ODPs and apply your selection.
During collection, all ODPs belonging to a model are collected, together with the various ODP types (extraction, projection, join etc.). This is necessary because complete search and analysis models are activated with all the ODPs they contain when a connector is created.
NoteIf the time stamp for the last change in the software component for an ODP is higher than the time stamp for the most recent activation, the Apply and Compare (X) or Copy columns are selected.
When the collected objects are added to the active version, the associated active source system DataSources (TLOGO object OSOA) are activated too.
Note on Activation and Transport
When activating operational analytics scenarios, note the following:
ODPs are activated in the lowest possible software component. Note that models are moved to a higher software component if this is required by a connector.
When transporting operational analytics scenarios, note the following:
ODP metadata in the search repository (search metadata) is ignored when metadata from the operational analytics scenario (ODP metadata) is transported. The ODP metadata and the search metadata can be transported independently of one another.
Search metadata is not required for running queries in the direct access, as the ODP metadata already returns all information relevant for the direct access. When transporting operational analytics scenarios, we recommend always importing both transports: The ODP metadata transport and the search metadata transport.
No connectors are created in the target system when the transport request is imported.
If you use SAP HANA or SAP BW Accelerator for search and/or operational analytics, make sure that your system contains the search metadata. In a production system, a connector cannot be created so long as the ODP metadata in the search repository does not match the active ODP metadata. Every ODP field must therefore have a corresponding node attribute. This is relevant in the following cases:
Customer enhancement of Business Content delivered by SAP
Customer-defined search and analysis models
Business Content corrections delivered by SAP