Professional Documents
Culture Documents
The Customer Activity Repository is a foundation that collects data that was previously
spread over multiple applications in diverse formats.
The Customer Activity Repository is a repository that captures information on consumer
activities across all interaction channels enriched by master and transactional data.
Retailers can use SAP Customer Activity Repository to gradually transform their system
landscapes from traditional database technology to the revolutionary, in-memory
database technology(HANA).
HANA calculation views can take data from both ERP and CAR at same time. Therefore
most up to date data will available in HANA Views. This data can be used then in any
application to produce useful information.
SAP CAR can be integrated with SAP ERP (IS Retail, FMS, S/4 HANA), Hybris, ARIBA etc. It
can also integrate with third party ERP solution as well. CAR comes as part of CARAB (CAR
application bundle) which also includes application like Assortment Planning, PMR etc.
CAR can only run on HANA.
Difference between SAP CAR and POSDM:
SAP Customer Activity Repository is designed to function both receiving and consuming applications.
A receiving application is one that receives data sent from the repository using outbound tasks.
SAP Customer Activity Repository integrates with the following receiving applications:
•SAP Business Warehouse (BW)
•SAP ERP for Retail
•SAP Demand Management Foundation (DMF)
•SAP Forecasting and Replenishment (F&R)
•SAP Workforce Management (WFM)
A consuming application is one that makes use of, or consumes, data stored in the repository
using SAP HANA .
SAP Customer Activity Repository integrates with the following consuming applications:
•SAP Promotion Management for Retail (PMR)
•SAP Customer Engagement Intelligence, in particular, the Audience Discovery and Targeting work set
POSDM Detail Diagram
Detail Design of SAP CAR
• In the above Design all master data, Sales order, Inventory data are
coming from SAP ERP into SAP CAR . POS data also coming into SAP
CAR system. CAR provide data for consuming retail applications
(promotion management, assortment planning, merchandise
planning). CAR serve as a data provider for central analytical or
transactional applications (like SAP Business Warehouse or SAP Hybris
Marketing). SAP CAR data will be also use for SAP Fiori as per
customer requirement.
• The following SAP Fiori apps are available in SAP CAR
Gross Margin
Number of Transactions
Average Items per Transaction
Average Transaction Value
We can also make Fiori apps as per customer requirement.
Features of SAP CAR:
The Customer Activity Repository captures sales transactions across multiple channels by introducing a
new multichannel data model and provides a harmonized view of the customer across all channels.
This enables retailers to get a 360° view of the customer and offers SAP CEI(customer engagement
initiative) and SAP 360° Customer access to cross channel transactional data.
Inventory Visibility
The Customer Activity Repository offers real time visibility into current stock situation in the stores by
taking ERP stock in unrestricted use and unprocessed sales into account.
Solution Scope
• Inventory information is replicated from ERP into CAR via SAP ERP Customer Activity Repository
SLT (SAP Landscape Transformation)
Inventory VDM
• This inventory information in CAR is combined with
unprocessed sales transactions from POS DM to derive
current stock in stores
Calculation: Unrestricted Use – unprocessed sales
• Intra company code stock in transit is displayed to inform
the user about deliveries on their way to the store Unrestricted Display: Intra company code stock in transit
Use
• Additionally inventory valuation at both, cost and retail Intra company Calculation: Valuation actual stock at cost
sales are calculated stock in transit
All the inventory data from ERP, replicated into HANA views and unprocessed sales which
were posted into sap car from POS system also stored in HANA views. So we can easily find
out real time inventory detail from HANA views.
We can create inventory visibility report using SAP Lumira and HANA views
On shelf availability algorithms
The on-shelf availability algorithms can be used to detect and visualize out-of shelf/out of stoke
situations in the stores when they happen in real time and take immediate actions to prevent further lost
sales.
Solution Scope
View weekly statistics for products with on-shelf availability issues by department
Drill down to daily and hourly views
Drill down to view details of how store associates using the SAP On-Shelf Availability Store
Associate mobile app resolved each of the on-shelf availability issues
Gain insight on how vendors, poor store processes, and employee performance may be affecting
product on-shelf availability in the store
Sort and filter on-shelf availability alerts to prioritize critical items
Flag products for follow-on activities, such as entering damaged quantities and reporting products as
out-of-stock
The OSA algorithm considers the sales of a product at a specific store. This algorithm extracts the
sales transactions from transactional information stored by POS Data Transfer and Audit. Then, the
algorithm analyses the length of each sales interval between two subsequent sales of that product.
Typically, long intervals indicate potential on-shelf availability issues.
Demand Data Foundation
The Demand Data Foundation (DDF) is the platform and data model defined to support SAP Retail applications. DDF provides
flexibility to integration with SAP Suite or any other master data system. SAP Hana is utilized to manage, aggregate, and filter data
in a faster way than previously possible.
Solution Scope
UDF Delivery
(reused in CAR)
• A flexible time series framework allows for fast access to pricing, and Query Views
MultiChannelSalesQuery MultiChannelSalesVsForecastQuery
BillingDocumentItemQuery POSSalesQuery
• DDF provide the technical mechanisms for easy data access through
Attributes/ Attributes/
Measures Measures
BillingDocumentItem POSSales
HANA Views
Plant Material OrderChannel RetailPromotion MaterialGroup Date FiscalDate POSLogItem
Type
Private Views
TLOGF_ITEM_COM
• Forecasting with the Unified Demand Forecast is called through DDF. T001W
Plant
MAKT MARA
Material
/DSMFD/
ORDERC
/DSMFD/
ORDERCT
Order Channel
WAKH WAKT
Retail
Promotion
TWAA TWAAT
Retail
PromotionType
T023 T023T _SYS_BLM_TIME
_DIMENSION
Fiscal Calendar
/POSDW/
TLOGF
Transaction Log
Flat Table
Solution Scope
• UDF models causal based factors to understand true customer
demand and then use this understanding to forecast future unit sales
• Bayesian and hierarchical priors aggregate data to fill the gaps of the
understanding in demand history
• Forecasts are generated at product, location, channel, day with a
flexible multichannel data model
• UDF supports what-if scenarios or long-term forecasts
• Through HANA views, the decomposed unit sales can be used for
advanced analytics.
• Forecast Demand for Lifecycle Products
Provide Demand Forecasts to External System
Key features:
DDF is a cross-industry reusable data layer in SAP Customer Activity Repository. It includes, for
example, the data model, data import infrastructure, reuse frameworks (such as the exception
handling or process controller), as well as reuse tools and user interfaces for data maintenance. DDF
also stores master data and it supports UDF.
UDF provides the demand modeling and demand forecasting services. It includes an application
function library (UDF AFL) and runs in the SAP HANA database.
Both DDF and UDF are components in SAP Customer Activity Repository and provide their functions
and data through the respective consuming application.
DDF supports the mass maintenance of data and stores master data. It handles the creation, import,
and export of data to and from external master data systems (such as SAP ERP). It also manages the
exceptions for the consuming application.
DDF can receive data from and send data to an SAP ERP system or a legacy system. Note that DDF
can receive data from more than one system.