Best Practices for leveraging CAR Calculation views as a Data Source in SAP BW/4HANA
SAP Customer Activity Repository (CAR) is a foundation that collects transactional data that was previously spread over multiple independent applications in diverse formats. The repository provides a common foundation and a harmonized multichannel transaction data model for all consuming applications. SAP CAR consists of POSDM, Demand Data Foundation, Unified Demand Data, Forecasting, Promotion Management, Loyalty and much more. SAP CAR offers real time insights into Inventory, On-shelf availability, Omnichannel sales across all channels,and the list goes on.
CAR Architecture is below:
CAR Architecture (Source SAP.COM)
SAP CAR and SAP BW Standalone System Architecture.
Let’s understand the architecture of CAR and BW when they are 2 separate standalone systems.
As you see from picture 1.0 SAP CAR and SAP BW are on 2 separate systems.
Main Points to note from the Picture 1.0 are:
1. CAR has POSDM/DDF/UDF/Real Time Inventory /PMR/Multi Channel Sales Query and much more.
2. CAR sits on a separate HANA Data Base where as BW has its own HANA Data base
3.BW Uses POS Standard SAP Data source- 0RT_PA_TRAN_CNTL which gets replicated from CAR into BW.
4. BW extracts Inventory/Purchasing/Billing/FI GL and other SA data from ECC using regular standard extractors.
Pros and Cons of standalone system Architecture
Limitation of Standard SAP BW Content with respect to CAR:
Customers who are not on SAP BW/4HANA can use Retail Content, provided they have a Retail POSDM add on in BW. With this, customers can get Std DSO’s, Cubes, Info objects, Queries etc out of the box.
When a customer is on BW/4HANA(assuming CAR and BW are separate systems), there is no Retail specific content available from SAP.
In this case, a customer can replicate the data sources from CAR into BW, but the data flow upwards is not available. ( i.e no Std SAP ADSO’s, Composite Providers, queries). This leaves the customer with below options:
a. Transport the Cubes/DSO’s/Transformations from lower BW version to BW/4HANA and migrate them. Note- There’s a risk as not all objects/methods/classes are supported now in BW/4HANA.
b. Leverage on SAP CAR’s calculation views which I will discuss in detail below.
How to best leverage on CAR Calculation Views as a Data source to BW by using agile development and consume in BW for reporting.
- When you want to leverage on a CAR Calculation view as a data source to BW
- When there’s no Std SAP data source available in CAR for BW
- When you want to do a quick agile development
Logon to BW Eclipse
Go to data sources tree and create a new Data source on ODP_HANA Source system. In my case its called NS2HBDSCHE.
Activate the data source and you refresh your data source tree to see the newly created data source:
Create a ADSO and use the above data source ( POSSALESV2) as the source. Create transformations and activate the objects:
When to use which system for reporting:
Source: /N SPRO