SAP Customer Activity Repository (NEW)

Use
As of SAP Customer Activity Repository 1.0, you have access to a platform that unifies point-of-sale
(POS) transactions and SAP ERP sales documents in a single, multichannel transaction data repository.

The SAP Customer Activity Repository includes the Point of Sale Data Management software component
(version RTLPOSDM 200) for the acquisition and processing of POS transactions. SAP ERP sales
documents are replicated to SAP Customer Activity Repository using the SAP LT Replication Server.

The repository includes order channel management capabilities, allowing you achieve a unified view of
customers' transactional activities across multiple channels.

The repository also includes the SAP HANA Content for SAP Customer Activity Repository, which is a
series of SAP HANA virtual data models and view groupings that provide a convenient and fast access to
the data stored in the repository. The four major virtual data models included in SAP HANA Content for
SAP Customer Activity Repository are:

 Inventory Visibility Analysis

 POS Transaction Sales Analysis

 Sales Analysis Based on Billing Documents

 Multichannel Sales Analysis

SAP HANA Content for SAP Customer Activity Repository enables you to integrate the repository with
other applications. For example, customers can create their own front-end applications that consume data
from views of the SAP HANA Content for SAP Customer Activity Repository. Furthermore, customers can
use SAP BusinessObjects Analysis tools to run near real-time analytical business reports on the virtual
data models included in SAP HANA Content for SAP Customer Activity Repository.

SAP Customer Activity Repository is integrated with the Demand Data Foundation, making it the future
platform for SAP applications with predictive capabilities.

See also
Master Data Reading/Checking Using SAP HANA VDMs

SAP Workforce Management Integration

Customer Harmonization

Order Channel Definition

Assignment of Order Channels to Profiles and Sales Item Types

Determination of Order Channels for Sales Documents

Deleted SAP POS DM Enterprise Services

POS Transaction Data Migration

Extending POS Transaction Data Model

Master Data Reading/Checking Using SAP HANA
VDMs (Changed)
Use
As of SAP Customer Activity Repository 1.0, master data is replicated to the repository from a source
SAP ERP system and is read and verified using Virtual Data Models (VDMs) included in:

 SAP HANA Live for SAP ERP

 SAP HANA Content for SAP Customer Activity Repository

There are several BAdIs, listed in the Effects on Customizing section, that have standard SAP
implementations that access master data using VDMs. To change the master data access, you can use
the enhancement framework to provide your own implementations of these BAdIs.

Effects on Customizing
The table containing the definitions of the units of measure is replicated directly to SAP Customer Activity
Repository from a source SAP ERP system. Manual maintenance of the units of measure through the
SAP NetWeaver > General Settings > Check Units of Measurement Customizing activity is not required.

In the Customizing for SAP Customer Activity Repository, the majority of BAdIs included under POS Data
Management > POS Inbound Processing > Customer-Specific Enhancements and BAdI Implementations
> Enhancement of Implementation of Access Methods > Access to Master Data have a default
implementation that reads master data from VDMs.

The implementations of the following check profile BAdIs have been updated to read master data from
VDMs:

 BAdI: Check POS Transactions Using Check Profiles

 BAdI: Check Store Data Using Check Profiles

Futhermore, the new following BAdIs also access data from VDMs:

 BAdI: Read Loyalty Card Data

 BAdI: Master Data Reader of Store's Own Customer ID

 BAdI: Distribution Channel Reader for Search Help

 BAdI: International Article Number (EAN) Reader

 BAdI: Article Identifier for Search Help

 BAdI: Master Data Reader for Material

 BAdI: Material Group Reader for Search Help

  BAdI: Sales Organization Reader for Search Help

 BAdI: Unit of Measure Reader for Search Help

In the Customizing for SAP Customer Activity Repository, the BAdIs included under POS Data
Management > POS Inbound Processing > Integration with Other SAP Components > SAP Workforce
Management > BAdI Implementations have a default implementation that reads master data from VDMs.

 BAdI: Implementation of Determination of Category

In the Customizing for SAP Customer Activity Repository, a BAdI included under POS Data Management
> POS Inbound Processing > Multichannel Enablement for POS Transactions > BAdI Implementations
has a default implementation that reads master data from VDMs.

 BAdI: POS Transaction Inbound Customer Determination Processing Enablement

In the Customizing for SAP Customer Activity Repository, BAdIs included under Multichannel Enablement
for Sales Documents > BAdI Implementations have a default implementation that reads master data from
VDMs.

 BAdI: Implementation to Access Condition Type Data

 BAdI: Implementation to Access Distribution Chain Data

 BAdI: Implementation to Access Sales Document Category Data

 BAdI: Implementation to Access Sales Document Type Data

In the Customizing for SAP Customer Activity Repository, the BAdI included under POS Data
Management > POS Inbound Processing > Integration with Other SAP Components > DMF-Based
Applications has a default implementation that reads master data from VDMs

 BAdI: Implementation for Offer ID Determination from Receipt

SAP Workforce Management Integration (New)
Use
As of SAP Customer Activity Repository 1.0, you can send POS transaction summaries to SAP Workforce
Management (WFM) using iDocs of type WFAFCA01 (WFAFC_A01 in SAP WFM). SAP WFM can use the
information received from the SAP Customer Activity Repository to maintain data for volume indicators
defined in SAP WFM, which in turn are used to drive the definition of workloads.

Effects on Data Transfer

Transaction totals are transferred to SAP WFM using iDocs of type WFAFCA01 (WFAFC_A01 in SAP
WFM).

Effects on Customizing
The Define Tasks Customizing activity standard values have been enhanced to include the following new
task:

 Task 0099 Generate IDoc WFAFCA01 - this task sends POS transaction summaries to SAP
Workforce Management (WFM) using iDocs of type WFAFCA01 (WFAFC_A01 in SAP WFM).

Furthermore, the following Customizing activity and BAdIs have been added:

 Define SAP WFM General Settings - Contains settings for sending information to SAP WFM.

 BAdI: Implementation of Determination of Organization ID - Allows you to create your own

implementations to map SAP Customer Activity Repository store identifiers to the identifiers of
SAP WFM organizations.

 BAdI: Implementation of Determination of Category - Allows you to define your own

categories for counting the total number of line items sold for a particular category. This BAdI also
contains the default implementations to group line items by material group or material hierarchy.

See also
For more information on using the new Task 0099 Generate IDoc WFAFCA01 (SAP Standard Profile),
see SAP Help Portal at http://help.sap.com/car --> Application Help --> SAP Customer Activity Repository
--> POS Transaction Management --> Task Processing --> Tasks for Sending Data to Follow-On
Applications--> Sending Data to SAP WFM.
Customer Harmonization (New)
Use
As of SAP Customer Activity Repository 1.0, you can obtain a harmonized view on a customer and the
transactional activities that the customer performs across all channels. Sales documents replicated into
the repository from SAP ERP already have a customer number associated to them. Customer
harmonization is primarily achieved by associating a customer number to all POS transactions stored in
the repository. When customer information is available for each multichannel transaction data record, you
can use SAP HANA Content for SAP Customer Activity Repository views for activities such as:

 Identification of customers who shop across multiple channels (for example, on-line and store)

 Identification of purchases that a particular customer has made using each order channel

Effects on Data Transfer

The customer number and the Customer Qualifier are stored in dedicated fields of the /POSDW/TLOGF
table and are consumed directly by the views of the SAP HANA Content for SAP Customer Activity
Repository.

Effects on Customizing
The Define Tasks Customizing activity standard values have been enhanced to include the following new
task:

 Task 8004 Determine Customer ID in Transactions - this task associates a customer number
to POS transactions.

Furthermore, the following BAdIs have been added:

 BAdI: POS Transaction Inbound Customer Determination Processing - Assigns a customer

number to POS transaction.

 BAdI: Read Loyalty Card Data - Reads underlying customer master data based on the loyalty
card number contained in a POS transaction record.

See also
For more information on using the new task 8004 Determine Customer ID in Transactions (SAP
Standard Profile), see SAP Help Portal at http://help.sap.com/car --> Application Help --> SAP Customer
Activity Repository --> POS Transaction Management --> Task Processing --> Tasks for Enhancing
Transactions --> Enhancing POS Transaction Data with Customer Numbers.
Order Channel Definition (New)
Use
As of SAP Customer Activity Repository 1.0, you can obtain a holistic view of the multichannel transaction
data in one, unified platform. SAP Customer Activity Repository contains a set of default order channel
definitions. You can use the default definitions, or, create new definitions that better suit the order
channels used in your business.

Effects on Customizing

The Define Order Channels Customizing activity allows you to create all the order channel
identifiers required for your business.

See also
For more information on defining order channels, see SAP Help Portal at http://help.sap.com/car -->
Application Help --> SAP Customer Activity Repository --> Multichannel Transaction Data Management --
> Order Channel Management.
Assignment of Order Channels to Profiles and Sales
Item Types (New)
Use
As of SAP Customer Activity Repository 1.0, you can obtain a holistic view of the multichannel transaction
data in one, unified platform. To achieve this, SAP Customer Activity Repository contains the rules for
associating order channels to POS transactions.

Effects on Customizing
The order channel is assigned to POS transaction line items based on the settings of one the following
Customizing activities:

 Assign Order Channels to Sales Item Type

 Assign Order Channels to Profile (if order channel settings are not defined in the Assign
Order Channels to Sales Item Type Customizing activity)

BAdI: Implementation of Determination of Order Channel has been added to allow you to
create custom rules for assigning order channels to line items.

Furthermore, the Define Tasks Customizing activity standard values have been enhanced to include
the following new tasks:

 Task 0200 Update Order Channel in Transactions - this task processes all POS transactions
stored in the /POSDW/TLOGF table to change the order channel assigned to each line item based
on updated Customizing settings.

 Task 0201 Insert Missing Order Channel in Transactions - this task processes all POS
transactions stored in the /POSDW/TLOGF table and assigns order channels to those line items
that do not have an order channel assigned.

See also
For more information on assigning order channels to POS transactions, see SAP Help Portal at
http://help.sap.com/car --> Application Help --> SAP Customer Activity Repository --> Multichannel
Transaction Data Management --> Order Channel Management.
Determination of Order Channels for Sales Documents
(New)
Use
As of SAP Customer Activity Repository 1.0, you obtain a holistic view of the multichannel transaction
data in one, unified platform. To achieve this, SAP Customer Activity Repository contains the derivation
rules that allow the identification of the order channel for sales documents replicated to the repository
from SAP ERP. These rules are used by views of the SAP HANA Content for SAP Customer Activity
Repository to associate a sales document with its order channel.

Effects on Data Transfer

Order channel derivation rules specified in the Define Sales Document Order Channel
Derivation Customizing activity are stored in table /CAR/SALESDOCOC and are consumed directly by
the views of the SAP HANA Content for SAP Customer Activity Repository.

Effects on Customizing

The Define Sales Document Order Channel Derivation Customizing activity allows you to
define the rules for associating an order channel to a sales document.

See also
For more information on associating sales orders with their order channels, see SAP Help Portal at
http://help.sap.com/car --> Application Help --> SAP Customer Activity Repository --> Multichannel
Transaction Data Management --> Order Channel Management.
Deleted SAP POS DM Enterprise Services (Changed)
Use
As of SAP Customer Activity Repository 1.0, several enterprise services that were available in the BI
Content software component SAP NW 7.XX BI CONT ADDON 7.X6 and lower have been deleted. BI
Content software component SAP NW 7.XX BI CONT ADDON 7.X6 and lower are out of maintenance,
and therefore, associated enterprise services are also no longer supported.

Therefore, if you were using one of the following POS Data Management enterprise services:

 Namespace: http://sap.com/xi/BICONTENT/Global2

o PointOfSaleTransactionERPBulkCreateRequest_In

o LoyaltyMembershipActivityJournalCRMBulkRequest_Out

 Namespace: http://sap.com/xi/BICONTENT/Global2/Testing

o PointOfSaleTransactionERPBulkCreateRequest_Out

you should be aware that these enterprise services have been deleted from the Enterprise Service
Repository (ESR) for Process Component Point Of Sale Transaction Processing.

If you are using enterprise services in your implementation of SAP Customer Activity Repository, use the
following enterprise services:

 Namespace: http://sap.com/xi/RTLPOSDM/Global2

o PointOfSaleTransactionERPBulkCreateRequest_In

o LoyaltyMembershipActivityJournalCRMBulkRequest_Out_V1

 Namespace: http://sap.com/xi/RTLPOSDM/Global2/Testing

o PointOfSaleTransactionERPBulkCreateRequest_Out

See also
For more information, see SAP Help Portal at http://help.sap.com/car --> Application Help --> SAP
Customer Activity Repository --> Enterprise Services.
POS Transaction Data Migration (New)
Use

As of SAP Customer Activity Repository 1.0, you can use the POS Transaction Data Migration
Report to migrate POS transaction data from SAP POS DM 1.0 to SAP Customer Activity Repository.

Effects on Data Transfer

The POS Transaction Data Migration Report, executed using transaction /POSDW/MIGR, allows you to
migrate POS transaction data using one of the following migration paths:

1. SAP POS DM 1.0 on SAP NetWeaver BW powered by SAP HANA -> SAP Customer Activity
Repository 1.0

2. SAP POS DM 1.0 on RDBMS -> SAP Customer Activity Repository 1.0

See also
For more information on POS transaction data migration, refer to the documentation accompanying the
report.
Extending POS Transaction Data Model (New)
Use
As of SAP Customer Activity Repository 1.0, you can control how POS transaction extension segments
are stored in the database. Furthermore, you can create implementations for two new BAdIs that allow
mapping between custom fields in the /POSDW/TLOGF table and the internal TLOG structure
(/POSDW/TRANSACTION_INT).

Effects on Existing Data

You can use the Transfer POS Transaction Extension Segments report (transaction /POSDW/REFE) to
change the database storage location of the extension segments of existing POS transaction records.

Effects on Customizing
The Store Extensions in Separate Table option has been added to the Define General Settings
Customizing activity, allowing you to specify which database table to store POS transaction extensions
segments.

Also, two BAdIs ( BAdI: POS Transaction Log Write Enhancements and BAdI: POS Transaction Log
Read Enhancements) have been added under POS Inbound Processing --> Customer-Specific
Enhancements and BAdI Implementations --> Enhancements for In-Memory Analytics. These
BAdIs allow you to implement a mapping between custom fields of the /POSDW/TLOGF table and custom
components of the internal TLOG structure (/POSDW/TRANSACTION_INT).
Demand Data Foundation (New)
Use
As of Demand Data Foundation (DDF) 1.0, you have access to a reusable software layer that supports
the planning, analysis, and forecasting required by retail business processes. DDF acts as a liaison
between the planning applications consuming it and the forecasting and data analysis components within
it.

The foundation handles exception management for planning applications, as well as data creation and
the import and export of data to and from external master data systems. Additionally, DDF supports the
mass maintenance of its objects.

Within the SAP Customer Activity Repository, DDF manages master data such as products, locations,
product hierarchies, location hierarchies, offers, and prices. Master data can be imported from SAP ERP.
DDF also manages time series data such as sales.

Release Note Remarks

Software Component RTLDDF100 has a dependency on the SAP HANA database. Due to this
dependency, a patch (revision) of the Hana DB might require patching (note, SP) of the RTLDDF
software component. In addition a patch of the RTLDDF software component might require a patch of the
SAP HANA database.

In case such a situation occurs, requiring either the NetWeaver or the SAP HANA database patch, this
information would be made available in the section below. A problem statement, as well as the SAP note
number would be provided here.
Unified Demand Forecast (New)
Use
As of Demand Data Foundation (DDF) 1.0, Unified Demand Forecast (UDF) provides a new generation of
forecasting for SAP retail applications. Multiple applications can reuse UDF to predict demand for a
requested duration. UDF depends on DDF to manage the data for modeling and forecasting.

Modeling
Taking historical inputs, the demand modeling process determines the factors and how much impact each
factor has that contributed to the total unit sales, which occurred within the available history. We
recommend that you use 2 years of history. These factors can determine the impact of price changes,
seasonality, promotions, and promotion tactics.

Forecasting
Once the demand modeling process quantifies the factors, forecasting uses them to predict future
demand. Given inputs (such as price and planned promotions), the unit sales forecasts are generated for
a specified product in a location for the time period requested. The impact of each factor that contributed
to the total forecast is detailed for the user to review through the decomposition. The forecast values are
provided to the consuming application as requested (on demand what-if forecasting) or saved in the
database (scheduled production forecasting).

The following features are supported in the support package 00 (SP00):

 Demand data types
o Point of sale (POS)
o Consumption
o POS from TLOG as Virtual Data Model (VDM)
o Sales order as VDM
 Technical framework
o Application Programming Interface (API) for ABAP modeling and forecasting
o ABAP controller and dispatcher
 Modeling and forecasting
o Diagnostic mode
o Lift factors for the following:
 Baseline
 Day of week effect
 Price effect
 Seasonality effects
 Trend effect
o Offer features
 Tactics and time-dependent tactics
 Simple offer types
 Optional and Enforced multibuy offer types
 Buy X Get X
 Incentives (as supported in PMR)
o Multichannel enabled by sales organization, distribution channel, and order channel.