SAP HANA Content for SAP Customer Activity Repository
SAP HANA Content for SAP Customer Activity Repository is a collection of views on the data stored in your SAP HANA database. Some of this data, for example sales documents, is accessed by SAP Customer Activity Repository from other source systems. Other data, for example, point-of-sale transactions, is created by the SAP Customer Activity Repository application.
SAP HANA Content for SAP Customer Activity Repository can be divided into two logical groups:
Analytics Content: A series of comprehensive analytical models (also referred to as virtual data models, or VDMs) allowing you to perform multichannel sales and inventory analysis.
Other Content: A collection of views, that are not necessarily interdependent and do not form a specific virtual data model, but that are used for integration:
With consuming applications (for example, optional integration with SAP Customer Engagement Intelligence).
Between the different software components within the repository. For example, integration between the Point of Sale Data Management software component (version RTLPOSDM 200) and the Demand Data Foundation software component (version RTLDDF 100).
SAP HANA Content for SAP Customer Activity Repository provides cohesive, unified access to master, transaction and analytical data from all consuming applications.
Query views included in SAP HANA Content for SAP Customer Activity Repository are provided as templates and are not intended for productive use in your business. The provided query views include extensive sets of characteristics, measures and master data to cover a wide spectrum of KPIs, which can render the performance of these views slower than is acceptable during productive use.
You can easily use the provided template query views as models to build smaller, targeted query views that consume the reuse views included in SAP HANA Content for SAP Customer Activity Repository.
Prior to being able to access data using SAP HANA Content for SAP Customer Activity Repository, there are several prerequisites that you must fulfill.
SAP HANA Studio Configuration
You view and manage SAP HANA Content for SAP Customer Activity Repository from the SAP HANA Studio. You must connect your SAP HANA Studio to your SAP Customer Activity Repository system, as described in the SAP Customer Activity Repository Installation Guide.
You should also have the required user account(s), roles and privileges to work with the SAP HANA Content for SAP Customer Activity Repository, as described in the SAP Customer Activity Repository Security Guide.
Installation of the SAP HANA Live for SAP ERP
SAP HANA Content for SAP Customer Activity Repository contains virtual data models and view groupings that include reuse views that are delivered as part of SAP HANA Live for SAP ERP. SAP HANA Live for SAP ERP must be installed on the same productive system as SAP Customer Activity Repository and all the views listed in the SAP Customer Activity Repository Installation Guide must be activated.
For more information on SAP HANA Live for SAP ERP, see http://help.sap.com/hba.
External Data Usage
All views of SAP HANA Live for SAP ERP and some views of SAP HANA Content for SAP Customer Activity Repository require that master and transactional data is accessed by the repository from a source SAP ERP system and, optionally, from a source SAP CRM system. SAP ERP data can be replicated to SAP Customer Activity Repository or, if SAP ERP and the repository are installed on the same SAP HANA database, accessed directly from the SAP ERP tables. SAP CRM data, if used, should be replicated to the repository.
For more information, see Usage of External Data by SAP Customer Activity Repository and the SAP Customer Activity Repository Installation Guide.
You can access technical details for every view in the auto documentation. To create the auto documentation, proceed as follows:
In the SAP HANA Studio Modeler perspective, start Auto Documentation from the central frame.
Choose the package and press Add.
Enter a target location path and press Finish.
One PDF document for each view is created in the given path using the view names as file names.