Hierarchy

⤷

⤷

IMG Activity
ID | RODPS_NOTES | Overview Information |
Transaction Code | S_BY3_13000020 | (empty) |
Created on | 20110404 | |
Customizing Attributes | RODPS_NOTES | Overview Information |
Customizing Activity |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | RODPS_NOTES |
Use
Operational Data Provisioning makes data available to an application for analysis purposes. There can be two different application scenarios here:
- Operational Analytics
Operational Analytics makes it possible to perform reporting and analysis based on an application data model without the need to replicat the data in a Data Warehouse. Unlike strategic analysis, it mainly supports decision making in operative business processes. Operational Analytics is available to a broad spectrum of users in the company, has low latencyz, high granularity of data and a high level of availability. If you use Operational Data Provisioning for Operational Analytics, the data can be used by direct access from analytic queries (query) and can also be replicated to the SAP NetWeaver BWA.
- Data Extraction and Replication
Operational Data Provisioning supports extraction and replication scenarios for various consumers and thereby supports delta mechanisms. Operational Data Provisioning therefore supports replication of data to SAP NetWeaver BWA. Operational Data Provisioning's service for extraction, transformation and loading (ETL) still makes it possible to transfer data to SAP BusinessObjects Data Services, for example.
The data extraction and data replication abilities therefore make it possible to index data for Operational Analytics in the BWA and, if the data analysis requirements become complex, to make the data available to other consumers.
If you want to use Operational Data Provisioning, make sure that you have made the following Customzing settings for Search and Operational Analytics:
1. Joint Settings for Operational Analytics and Embedded Search:
- Settings for joint use of the modeling environment and administration environment for Suche and Operational Analytics:
- Setting for accessing data for Operational Analytics without using SAP NetWeaver BWA:
- Defining the TREX Destination
- Note:
Even if are not using a SAP NetWeaver BWA, you need to specify a TREX destination. Operational Data Providers can only be activated if you enter "NO TREX" under RFC Destination of TREX. - Settings for using SAP NetWeaver BWA (Optional):
- Define TREX Destination
- Note:
If you use the SAP NetWeaver BWA, specify the actual RFC connectoin between the ABAP system and the BWA as RFC Destination of TREX. - Define Server Group for Indexing Jobs
- Configure Extraction Users for Indexing
2. Basic Configuration for Operational Analytics
3. Specify Client for Modeling
4. BAdI: Process DataSource Enhancements (optional)
Requirements
Standard settings
Activities
Example
Business Attributes
ASAP Roadmap ID | 899 | not to be assigned |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | RODPS_NOTES | 0 | BYI3000065 | Operational Data Provisioning (ODP) in Search&Analytics |
Maintenance Objects
Maintenance object type |
History
Last changed by/on | SAP | 20110725 |
SAP Release Created in | 731 |