Customer Activity Repository 2.

0 FP3
Feature Overview
June 2016
Summary

This document provides an overview of the new features that were

added to the Customer Activity Repository as part of the Customer
Activity Repository Application Bundle release SPS04. This
document also includes information related to the Unified Demand
Forecast (UDF) and Demand Data Foundation (DDF).

For detailed information for each of the features in this document,

please refer to the SAP Customer Activity Repository Application help:
http://help.sap.com/car

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 2
Agenda

1. Introduction and Overview

2. POS Data Transfer and Audit
3. Multichannel Sales Analytics
4. Inventory Visibility
5. Demand Data Foundation
6. Unified Demand Forecast
7. Omnichannel Promotion Pricing
8. Omnichannel Article Availability

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 3
SAP Customer Activity Repository

SAP Customer Activity Repository is a foundation that collects

granular sales data previously spread over multiple siloed
applications in diverse formats.

… as the basis for multi-channel transactions, SAP Customer

Activity Repository captures information on consumer sales activities
across all interaction channels enriched by master and transactional
data.

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 4
SAP Customer Activity Repository

The Repository stores data at the most granular level of detail,

allowing the embedded science layer to execute advanced statistical
algorithms and pattern predictions.

SAP HANA, the underlying in-memory technology of the Repository,

responds to analytical requests on huge amounts of data in real-
time. The Repository gives insight into sales performance and
consumer behavior across all channels enabling new processes and
interaction with all parties.

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 5
 SAP Customer Activity Repository – High Level View

Provides a harmonized view of Supports high volume

a consumers sales transactions Multichannel POS transactional data transfer and
across different channel Foundation sales audit

Gives real-time
insight into Drives multichannel
inventory quantities
Inventory Multichannel enabled analytics
and valuations for Visibility SAP Sales Analytics on transactional
the store channel
HANA consumer data

• Enables high
Drives ‘new’ real-time
performance demand
business scenarios Enable New Forecasting
forecasts for optimized
using analytics and Processes Capabilities promotions and
forecasting information
inventories

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 6
SAP Customer Activity Repository
Building Blocks and Addressed Roles

Promotion Category Store Supply Chain

Marketing
Management Management Management Management

Store Inventory /
Promotion Category Demand
Manager/ Replenishment
Planner Manager Planner
Employee Planner

POS Analysis MC Sales Analysis Inventory Visibility

Optional
VDM Hybris
POS Sales Multichannel Sales Inventory … Mkt

CRM IC

PIPE
SAP
(POS Inbound Processing Engine) Customer Activity Repository BW

Unified Demand Forecast Sales Frequency

q 0   p  v  Analysis
D4 NT Av1QTK F2CKN e 1Q 2 N 1QTK 2CN (known as OSA Algorithm
US  
)

 4 N (~z4 NT  1)  1
SLT
SAP HANA

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 7
SAP Customer Activity Repository – Modules

SAP SAP SAP * Optional

Partner Co-Deployment
New Features Promotion Assortment Merchandise
Applications
Management Planning Planning (SAP and Partners)

SAP IS Retail
SAP Customer Activity Repository (CAR) SAP Sales
Insights for
Master Data SAP HANA Live - Analytics Retail 3.0

SAP HANA (in-memory computing)

Sales
Documents
SAP Hybris
POS Data Unified Inventory
Transfer and Demand Visibility
Marketing*
Inventory
Audit Forecast

Point of Sale SAP

Business
Sales Demand Data On Shelf
Transactions
Multichannel Warehouse*
Transaction Foundation Availability
Data
SAP CRM Management
Other
Customer applications
Data *

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 8
Agenda

1. Introduction and Overview

2. POS Data Transfer and Audit
3. Multichannel Sales Analytics
4. Inventory Visibility
5. Demand Data Foundation
6. Unified Demand Forecast
7. Omnichannel Promotion Pricing
8. Omnichannel Article Availability

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 9
Enhancements in this release

POS Data SAP Customer Activity Repository now provides the

Transfer and ability to:
Audit
 Combine POS Sales Transactions stored in Hana (“hot”) with
data stored in an alternate storage location (SAP IQ or Hadoop)
for follow on analytics
 Associate POS Sales Transactions with customers stored in
Hybris Marketing based on different criteria
 Filter on reversed transactions from the POS DM Workbench
 Remove entries from the Unprocessed Sales and Goods
Movement table in order to preserve available memory

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 10
 Enhancements POS Data Transfer and Audit

Storage Optimization Enhancements

Feature Recap

Feature Released

Optimize the Storage of the TLOGF by removing record qualifiers FP01

not required for follow on analytics.

Optimized the Storage of Custom Extensions by introducing new FP01

column based table (TLOGF_X) and the ability to store report
critical extensions as additional columns in the TLOGF.

Optimized the Storage of the TLOGF by clearing the content of FP02

columns no longer needed for follow on analytics

Ability to age data into an alternate storage location such as SAP FP02
IQ or Hadoop.

Ability to read POS Sales Transaction data stored in Hana FP03

“hot” along with data stored in SAP IQ or Hadoop “cold”
through the use of new views.

Note: Dynamic Tiering “warm” storage is not supported yet.

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 11
 Enhancements POS Data Transfer and Audit

Alternate Storage of Transaction Logs

Use Case
Report on POS Sales Transactional data regardless on if the data is stored
in Hana (“Hot”) and/or in an alternate storage location (“Cold”) without the
necessity to know specifically where the data resides.

Solutions
• Provide a new set of Smart Hana Views which combine POS Sales
Transaction Data stored in Hana (“Hot”) with Data stored in SAP IQ or
Hadoop (“Cold”).
• The delivered Smart Views automatically know where the data to fulfil the
reporting requirements resides and extracts it from the appropriate
storage location.
• The following reuse views have been created in the sap.is.retail.car.nls
HANA content package:
• sap.is.retail.car.nls.TLOGF_ITEM_COM_NLS
• sap.is.retail.car.nls.POSSales_NLS
• sap.is.retail.car.nls.POSSalesPruning_NLS
• sap.is.retail.car.nls.MultiChannelSalesPruning_NLS

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 12
 Enhancements POS Data Transfer and Audit

Alternate Storage of Transaction Logs

High Level Architecture View

• The diagram shows the new “sap.is.retail.car.nls”

package’s contents and the dependencies of the
views that are in that package.

• When data is copied from SAP HANA using the

Table Content Aging report (transaction
/CAR/TABLE_AGING), information about the data
aging status is persisted to table
/CAR/DATA_AGING. This assists the views in this
grouping to harmonize both the aged data and the
data in SAP HANA

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 13
 Enhancements POS Data Transfer and Audit

Alternate Storage of Transaction Logs

Important Hadoop Installation Steps

Step 1 Step 2 Step 3 Step 4

Install Apache Hadoop: Install and set up: Create and partition Create a NFS mount
Hortonworks Distribution  Apache Hive ODBC tables in Apache Hive on SAP NetWeaver:
for Apache Hadoop: driver or Described in SAP Note The TLOG data and its
version 2.3 and higher, 2317597 extensions are copied
 SAP HANA Spark
supported on Intel-based from your SAP HANA
controller
hardware platforms only database to Hadoop
using the HDFS NFS
Gateway on your
Hadoop system.
To enable this you must
create a mount point on
your SAP NetWeaver
system for the data files
to be created directly in
the Hadoop File System
(HDFS).

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 14
 Enhancements POS Data Transfer and Audit

Enabling Customer Identification with SAP Hybris

Marketing

Use Case
Gain insight into the shopping habits of your customers through integration
between transactional data in SAP Customer Activity Repository and
customer data in SAP Hybris Marketing.

Solutions
• Provide the ability for CAR to perform customer identification for POS
Sales Transactions with SAP Hybris Marketing
• Extend the inbound customer identifier from Loyalty Card number to
other forms of identifiers given at the POS terminal that can be persisted
in the TLOGs when transactions are posted to CAR (email address,
phone number and Hybris Loyalty ID).
• New /POSDW/ANALYTIC_INB_CUSTCUAN BAdI implementation was
added to Customizing for SAP Customer Activity Repository under
POS Data Management  POS Inbound Processing  Multichannel
Enablement for POS Transactions  BAdI Implementations  BAdI: POS
Transaction Inbound Customer Determination Processing Enablement

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 15
 Enhancements POS Data Transfer and Audit

Enabling Customer Identification with SAP Hybris Marketing

Customizing:

SAP Customer Activity Repository General Settings  Client Mapping For External ABAP Systems

• This customizing option is to address the issue when both

CAR and Hybris Marketing are co-deployed via MCOD but
their respective ABAP components are on different client
numbers.
• This eliminates the need for any SLT Client Transformation

POS Data Management  POS Inbound Processing  Integration with Other SAP Components  SAP Hybris Marketing
 Map Transaction Field to Customer Identifier Code

• This customizing is used for mapping the Hybris Marketing

Facet origins to the relevant fields in TLOGF.

Design Considerations:
• The CUSTOMERNUMBER field in the TLOGF was extended
to 32 characters in length to accommodate the Hybris
Marketing facet key

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 16
 Enhancements POS Data Transfer and Audit

Filter Reversed Transactions

Use Case
Facilitate the usage of the POS Workbench for Sales
Auditor by providing the ability to filter on reversed
transactions.

Solutions
• Provide a checkbox to show reversed transactions
which will allow to filter the original transactions
which were post-voided after a certain period at the
POS Terminal.
Examples
Show Reversed Transactions checked Show Reversed Transactions unchecked

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 17
 Enhancements POS Data Transfer and Audit

Delete Unprocessed Sales and Goods Movement Report

Use Case
Maintain the size of the Unprocessed Sales and Goods
Movement table in order to help maintain sizing
requirements and optimum performance.

Solutions
• Provide the ability for administrators to delete entries
from the TLOGUS through a standard report.
• New report called (/POSDW/DELETE_TLOGUS)
• You can use any of the following input parameters to
select items to delete from the TLOGUS table:
• Store
• Store Group
• Posting Date
• Material Number
• Transaction Index
• Transaction Number

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 18
Agenda

1. Introduction and Overview

2. POS Data Transfer and Audit
3. Multichannel Sales Analytics
4. Inventory Visibility
5. Demand Data Foundation
6. Unified Demand Forecast
7. Omnichannel Promotion Pricing
8. Omnichannel Article Availability

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 19
Enhancements in this release

SAP Customer Activity Repository now provides the

Inventory
Visibility
ability to:
 Exclude articles from unprocessed sales and goods
movements
 Identify vendor consignment stock
 Improve the time gap between inventory updates from SAP
Customer Activity Repository to SAP ERP
 Provide service to return the inventory segmentation as
defined in the SAP Fashion Management System.

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 20
 Enhancements to Inventory Visibility

Exclusion of Articles from Unprocessed Sales and Goods Movements

Use Case
SAP Customer Activity Repository shall exclude articles from the unprocessed
sales based on their attributes like article type as defined in ERP, for which
values can be set at POSDTA customizing IMG node.

This would mean that certain articles will not be saved in the unprocessed sales
table (/POSDW/TLOGUS) when processing worklists.

Solutions
• SAP CAR will provide a generic framework that can be used to apply
additional processing to worklists such as filtering.

• New BAdI implementations have been added for BAdI definition

/POSDW/BADI_WORKLIST_EXCLUSION (interface
/POSDW/IF_BADI_WORKLIST_EXCL).

• The default implementation excludes articles based on article types from

unprocessed sales and from goods movements.

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 21
 Enhancements to Inventory Visibility

Exclusion of Articles from Unprocessed Sales and Goods Movements

Customizing:

The Define Parameters to Exclude Items in Worklist Customizing will define new parameters and their parameter values to be
used for filtering out articles from the unprocessed sales table.

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 22
 Enhancements to Inventory Visibility

Vendor Consignment Stock

Use Case
Identify other stock types available in store and DC and to be able to
be more flexible on the process side, when it comes to multi-channel
approaches.

Solutions

• Include the Unrestricted vendor consignment stock into the

existing CAR Inventory visibility views.

• The InventoryVisibility and InventoryVisibilityQuery SAP

HANA views have be updated in order for SAP Customer Activity
Repository to recognize vendor consignment stock quantities in
unprocessed sales stock.

• The CurrentStockWithVendorConsgmnt and VendorConsgmntUresUseStockQuantity fields were added into

each of the aforementioned views and incorporated into the following updated formula:

CurrentStockWithVendorConsgmnt =
UnresUseStockQuantity(normal stock) + UnresUseStockQuantity(vendor consignment stock) – unprocessedSalesQuantity

• The existing measure field “CurrentStock” was kept unchanged.

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 23
 Enhancements to Inventory Visibility

Vendor Consignment Stock POS CAR SAP Retail

Interfaces Do a sales transaction

 Data-sources for vendor consignment stock include: Outbound the sales

Inbound Sales Transaction to
TLOGF, change stock quantity in
transaction to CAR
TLOGUS

Inbound WPUUMS
Process Aggregation Task,
• Table MARD (Storage Location Data for Material). generate IDOC WPUUMS
IDOC, do stock
determination
• Table MOKL (Special Stocks from Vendor) with stock
indicator ‘K’. Reduce from Reduce from
normal stock Consignment stock

 Inbound POS Transactions: Get Stock information(MKOL, Update normal stock

Update vendor
consignment stock table
MARD etc.) through SLT replication table MARD etc.
MKOL, MARD

• Sell the goods and generate sales transactions. Inventory Visibility Views
• Return the goods sold from consignment stock and put it back
Stock information
to consignment stock. (MKOL, MARD etc.)

• Receive goods from DC or other store and put them into

consignment stock, and generate goods movement
transaction.
• Transfer goods from consignment stock to other stores and
generate goods movement transaction.

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 24
 Enhancements to Inventory Visibility

Reducing the Time Gap in Inventory

Use Case
Customers desiring near real-time inventory metrics
must consider the time gap caused by posting IDOCs
from SAP Customer Activity Repository to SAP ERP.

Solutions

• Unprocessed sales transactions should only be

deleted only when there is a confirmation for the
successful update in MARD table or IDoc processing.
This is achieved by:

1. Deactivating the existing

WPOSP_BADI_PROC_RESPONSE BADI
implementation and implementing the new BADI
using filter value WPUUMS.

2. In case there are multiple IDOCs to be processed and one of them fails, the RFC call to SAP Customer Activity Repository will
process (delete) the records of unprocessed sales related to the materials in a successfully processed IDOC.

3. The processing (deletion) of unprocessed sales is governed by the package numbers in which each IDOC is assigned a unique
package number.

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 25
 Enhancements to Inventory Visibility

Reducing the Time Gap in Inventory Updates

CAR Customizing:

POS Data Management  POS Inbound Processing  Tasks  Define Index/Worklist for POS Transactions

This would ensure that unprocessed sales data would get deleted after receiving the package confirmation.

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 26
 Enhancements to Inventory Visibility

Reducing the Time Gap in Inventory Updates

CAR Customizing:

POS Data Management  POS Inbound Processing  Tasks  Two-Step Processing  Define Aggregation Task (2001)

When this indicator is activated, the system adds POS

transaction indices to table /POSDW/AGGRTI while
building the aggregate.

You must select the Index Active checkbox to use one

of the following worklists (SAP Standard Profile):

• 0001 Index for Unprocessed Sales Transactions

• 0003 Index for un-processed Sales Trans for Inventory
visibility.

This worklist uses the POS transaction indices stored in

the /POSDW/AGGRTI table to determine which entries to
delete from the /POSDW/TLOGUS table.

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 27
 Enhancements to Inventory Visibility

Reducing the Time Gap In Inventory Updates

CAR Customizing:

POS Data Management  POS Inbound Processing  Tasks  Two-Step

Processing  Define Outbound Tasks (3001)

This indicator controls whether the target system has to

confirm the processing of aggregate packages.

If the indicator is selected, the processing status of an

aggregate package after processing is set to Confirmed only
once a confirmation has been received.

ERP Customizing:

IMG->Sales and Distribution->POS Interface->inbound->Maintain Profile for

POS Inbound.

The parameters with which processing of the data is controlled are

grouped together in profiles.

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 28
 Enhancements to Inventory Visibility

Reducing the Time Gap In Inventory Updates

ERP Customizing:

IMG->Sales and Distribution->POS Interface->inbound->Aggregated sales

control

This indicator controls whether to send confirmation for IDOC

processing related to POS inbound profile.

ERP Customizing:

IMG->Sales and Distribution->POS Interface->inbound->PIPE-Specific

Communication Settings.

This parameter is set to specify the RFC destination for target CAR
system for follow-on processing.

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 29
 Enhancements to Inventory Visibility

Reducing the Time Gap In Inventory Updates

ERP Customizing:

Maintain Plant Master (TCode: WB02)

In plant maintenance you can assign a profile to all plants for which you
wish to use the same parameters.

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 30
 Enhancements to Inventory Visibility

Inventory Segmentation

Use Case
Help determine default Fashion (FMS) segmentation value in the
purchase order creation from DC to store for set of articles.

Solutions
• Provide new Hana Calculation View “RequirementSegmentation”
which will expose the following information:
• Article – Material Number
• Supplying site (DC) - Supplying Plant
• Receiving site (Store) - Receiving Plant
• Purchase Order document type - Purchase document type
• Start date - Start date of default segmentation
• End date - End date of default segmentation
• Segmentation value - Default segmentation value
• This service will return all the valid stores and DC combination for
an article

Input for interface

• Purchase Order type
• Date

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 31
Agenda

1. Introduction and Overview

2. POS Data Transfer and Audit
3. Multichannel Sales Analytics
4. Inventory Visibility
5. Demand Data Foundation
6. Unified Demand Forecast
7. Omnichannel Promotion Pricing
8. Omnichannel Article Availability

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 32
Enhancements in this release

SAP Customer Activity Repository now provides the

Demand Data
Foundation ability to:
 Additional offer features supported PMR OPP

 Improvements for Merchandise Planning for Retail MPR

 Distribution Curves for use by multiple consumers AMR

 DDF offer integration with Hybris PMR yMKT

Key:
Promotion Management for Retail PMR

Omni-channel Promotion and Price Repository OPP

Merchandise Planning for Retail MPR

Allocation Management for Retail AMR
Hybris Marketing yMKT

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 33
 Enhancements Demand Data Foundation

Additional offer features supported

Use Case
With the addition of the new FIORI application, there were requests for additional
offer features to be added and supported through the platform module DDF.

Solution
PMR has a traditional UI that is licensed as a part of CARAB. With CARAB 1.0
FP3, a new FIORI application has been built to support some of the features of the
traditional UI, but also new features. In a future release, the FIORI application is
planned to replace the traditional UI.

Additional offer features added to the offer model include:

• Recurring and happy hour offers (future release of PMR)
• Product variation within a group
• Allow the quantity to be specified for a reward incentive
• Discount on fully priced items
• Offer on payment method
• Cheapest and most expensive item
• Additional support for incentives and minimum spend amount
• Detecting collisions >>> More details on the next slides
• Incentive redesign for greater flexibility >>> More details on the next slides

Customizing
The FIORI application can be used without a PMR license as a simple offer creation screen, or with a PMR license and full
functionality. This is managed by a BAdI /DMF/BAdI_FIORI_PMR_SW where the default (off) does not require a license. For more
information on this, please see the BAdI documentation.
© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 34
 Enhancements Demand Data Foundation

Additional offer features supported Overlapping Offer Concept

Detect Collisions during Offer Creation

Use Case
When creating a new offer, it is important to know if the current offer
has product, location and date overlaps with existing recommended or
approved offers.

Solution
A service is provided during offer creation that allows the user to
request the system to check for recommended and approved offers
that may overlap with the new offer. The user can then check the
listed offer to determine if the overlap was intended or if an
unintentional collision has been created.

Customizing
There is no customizing needed.

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 35
Enhancements Demand Data Foundation

Additional offer features supported Default Incentives

• Retailer coupon
New Offer Incentives
• Manufacturer coupon
• Retailer Rebate
Use Case • Manufacturer Rebate
• Instant Savings
Create a more flexible yet simplified model for incentives that is no longer
• Gift Card
tied to sales organizations and distribution channels.
• Points
• Retailer Coupon (Reward)
Solution • Manufacturer Coupon (Reward)
The DDF new incentives model simplifies the configuration, by condensing
four configuration tables into one, while allowing more incentive types to be
created. The incentive types can be used across sales organizations which
further simplifies the model by eliminating the requirement to associate
each incentive type to the sales organization and distribution channel.

Customizing
The redesigned incentives are delivered as part of CARAB 1.0 Feature
Pack 03 and will support all existing incentive types. After installation, the
report /DMF/INCENTIVE_ENHANCEMENTS needs to be run in order to
reseed the incentive default values prior to creating any new incentive
types.

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 36
Enhancements Demand Data Foundation

Improvements for Merchandise Planning for Retail

Use Case
Since its initial release, improvements for performance and usability have
been added to Merchandise Planning for Retail.

Solution
The list of improvements include:
• A report to load historical inventory information*
• Performance improvement to pre-load sales aggregations*
• Improvements for performance and currency handling

Customizing
There is no customizing needed.

Reports*
Historical Inventory Time Series (/DMF/BI_IF_INV_HIST)
• Import data from SAP BI systems to the time series in Demand Data
Foundation for inventory history Data during initial installation

Preload Sales Aggregations (/RAP/MPR_ECC_KPI_CALC )

• Run in the background to calculate the ECC KPIs from SLT replicated
tables weekly

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 37
 Enhancements Demand Data Foundation

Distribution Curves Engine

Use Case
FMS and AMR need the calculation of Distribution Curves based on historical
daily sales data in DDF spanned over the article’s color and sizes
considering historical and future season.
Call from FMS

Solution
For FMS the DCs are requested for a given group of articles and locations.
• The DCs are calculated based on the sales of the given prodlocs.
• FMS calls the DC Engine from an external system via RPC. Call from AMR

For AMR the DCs are requested for given generic products and locations.
• The CDs are calculated based on the sales of prodlocs identified based on the DC Configuration.
• Up to 2 filter attributes can be defined in the DC Configuration.
• AMR calls an AMDP within CARAB.

Result for AMR

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 38
 Enhancements Demand Data Foundation

DDF offer integration with Hybris Marketing

Use Case
When using Hybris for web promotions, it would be beneficial to also know
the offers that are being created in PMR. Basic integration would then be
able to show where there are conflicting or complementary promotions.

Solution
When an offer created in PMR that has a target group specified with a
marketing ID, the offer can be exported to an SAP Hybris Marketing system.
This standard integration is then a “closed loop” as the Hybris offer ID is sent
back to DDF as a cross-reference.

Customizing
Customizing is required for this feature.
BD54 >> Create logical system for SAP Hybris Marketing system
1) SPRO >>DDF >> Data maintenance >> Offer >>
• Implementation: Activate offer target group – activate the BAdI
• Enhancements using BAdIs >> BAdI: Target Group Data Access >> Check Active
• Enhancements using BAdIs >> BAdI: Offer Export Request>> Check Active
2) SPRO >>DDF >> Basic Settings >> Integration >> Sending system and master data
system coupling >> Add “Offer Export to SAP Hybris Marketing”
• sender: set to yMKT system For more information on this feature,
• Master: set to PMR system please see http://help.sap.com/car

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 39
Agenda

1. Introduction and Overview

2. POS Data Transfer and Audit
3. Multichannel Sales Analytics
4. Inventory Visibility
5. Demand Data Foundation
6. Unified Demand Forecast
7. Omnichannel Promotion Pricing
8. Omnichannel Article Availability

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 40
Enhancements in this release

SAP Customer Activity Repository now provides the

Unified Demand
Forecast ability to:
 Enhancements to the Analyze Forecast SAP FIORI App
 SAP HANA Views for Analyzing Price Elasticity and
Decomposition
 Forecast accuracy and performance improvements
 RDS support: Forecast accuracy

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 41
 Enhancements for Unified Demand Forecast

Analyze Forecast – Enhancements of the SAP Fiori App

Use Case
When you run the UDF module in SAP Customer Activity Repository, you get a forecast by product/location/sales organization/
distribution channel/order channel/promotion type/day for the time period requested. But what if you want to gain a deeper
understanding of the factors that went into determining the forecasted unit sales? How can you better analyze those demand
influencing factors, for both the past and the future?

Solution
Visualize the forecasts provided by UDF in an analytical SAP Fiori app
that gives you more insight into the demand influencing factors:
• Display forecasts by product, by location, or via a direct link (e.g. via another SAP Fiori app)
• Select multiple products and locations at the same time and view the aggregated forecasts
for your selection (e.g. one product in all locations in a particular city) [NEW]
• Display inputs, preprocessing results (e.g. outliers), historical sales, and forecasts
• Display decomposition view of modeling and forecasting results [NEW]
• Display additional statistical key figures [NEW]
• Display information by channel
• Share information on your analysis results via email, PDF, spreadsheet, …
• Covers the production forecast that is available in HANA, does not cover the what-if forecast that is returned to the calling application.

Customizing
There is no specific Customizing for «Analyze Forecast», beyond the Customizing activities for UDF (Cross-Application
Components > Demand Data Foundation > Modeling and Forecasting) and the configuration tasks described in the Common
Installation Guide (http://help.sap.com/car > <your release> > Installation and Upgrade Information > Installation Guide).

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 42
 Enhancements for Unified Demand Forecast

Analyze Forecast – New Decomposition View

Use Case
Demand models and forecasts are influenced by different factors,
such as promotions, seasonality, or calendar events. The
development of the modeling and forecasting values over time can
only be understood and interpreted correctly if the influencing
factors, and their impact on the demand, are known.

Solution
Break down the modeling and forecasting results by influencing
factors and display the results in a new decomposition view:
• Break down the total values into baseline demand and contributions of season, price
changes, and calendar events.
• Toggle time series view between days and weeks.
• Display decomposition values on different levels of aggregation (single or multiple
products and locations).

Prerequisite
Generation of decomposition results during modeling and
forecasting must have been activated in Customizing (transaction
SPRO). For details, see the documentation of the following activities:
Cross-Application Components > Demand Data Foundation >
Modeling and Forecasting > Define Modeling Control Settings and
Define Forecasting Control Settings.

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 43
 Enhancements for Unified Demand Forecast

Analyze Forecast – Data on Aggregated Levels

Use Case
Forecast-related questions often require analyzing multiple
products and/or locations at the same time. In these situations
it is helpful to be able to display modeling and forecasting
values for different levels of aggregation.
Also, when analyzing the forecast for a specific product
location, you will frequently want to compare this with a group
of similar product locations.

Solution
Select multiple products and locations at the same time and
display the aggregated values for your selection.
• Select multiple products and locations using attribute-based filtering in the input
help.
• Display aggregated time series values and KPIs:
• Total sales, forecasts, and decomposition values
• Average price
• Combination of calendar events and promotions

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 44
 Enhancements for Unified Demand Forecast

Analyze Forecast – Additional Statistical Key Figures

Use Case
Quickly check KPIs and identify potential issues when
analyzing the forecast for a specific product.

Solution
Display multiple key figures for the product:
• Percentage of outliers
• Percentage of out-of-stock days
• Standard deviation of the demand model
• Average sales
• Number of sales observations
• Standard deviation of the time series

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 45
Enhancements for Unified Demand Forecast

UDF Analytics provided by HANA Views

Use Case
UDF module of CAR has great analytic insights from the modeling and
forecasting output that goes beyond just unit sales. How can we leverage
these insights in a consumable way?

Solution
HANA views have been provided for several analytical use cases that
have been of interest to customers. By creating HANA views for this, you
can now easily access the analysis to use in any tool of your choice. This
could be excel, or other visualization tools.
• Affinity: Identify how a product drags along additional sales of another product
• sap.is.ddf.ddf.ProductAffinityQuery
• Decomposition: Views available to see the demand decomposition for the forecast
• sap.is.ddf.udf.viz.UDFModelAndForecastDecompositionQuery
• Elasticity: View to highlight the sensitivity for price
• sap.is.ddf.udf.viz.UDFPriceElasticityWeightedBySalesQuantityQuery
• Intra-day: Along with On shelf availability, determine day part unit sales projected for a day

Customizing
These views come with the standard installation of CAR. However you
must access them directly through HANA Studio or your tool of choice for
the output. For more information, please see the help portal here:

http://help.sap.com/car >> CAR 1.0 FP3>Additional Content>SAP HANA Content for SAP
Customer Activity Repository>Analytics Content.

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 46
Enhancements for Unified Demand Forecast

Sizing and Performance: Switch to control sizing of co

variance matrix
Full co –variance matrix as used
Use Case for FCI calculation
Generation of the Co-Variance Matrix in modeling is very time-consuming
Effect Tactic A Tactic B Tactic C
and the resulting table /DMF/UMD_PAR_COV can become large, requiring
more memory than planned. Tactic A 1.5 1,9 4,5
In customer sizing scenarios this table was responsible for up to 50% of
the total memory needed for UDF. Tactic B 1,9 1,6 3,6

Tactic C 1,7 2,5 2,5

Solution
The values of the Co-Variance Matrix are used for two purposes:
1. Calculation of Hierarchical Priors (HPR calculation module)
2. Calculation of the Forecast Confidence Index (Forecast module) Reduced co –variance as used
for HPR calculation
While for FCI calculation the full Co-Variance Matrix is required, the HPR
calculation uses only the diagonal elements. With only diagonal elements Effect Tactic A Tactic B Tactic C
(reduced Co-Variance Matrix) the table is much smaller.
FCI calculation is not required for all applications. It can be switched off in Tactic A 1,5
the forecast module. In those cases only the HPR calculation might be Tactic B 1,6
used and a reduced Co-Variance Matrix is sufficient.
Tactic C 2,5
Customizing
MOD_COV_HPR_ONLY in /DMF/UMD_PAR_COV can be changed to
indicate whether you want to generate the full (false) or the reduced (true)
Co-Variance Matrix as an output of modeling. The default value is false.

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 47
Enhancements for Unified Demand Forecast
Forecast Accuracy: Consideration of listing periods in the past
Use Case

Sometimes it is known that an product-location was not available at the Past Future

shelf, because it couldn’t be ordered and thus was de-listed for a

specific time. If there is no specific treatment for such situation the
Forecast
forecast will be too low, because the system assumes that the product- too low

location was available but not sold. Therefore it is necessary to

exclude such periods out of the modeling calculation, so it reflects the time
true demand situation in the past. Considered
as zero sales

Solution:
• ERP product/store listing information is considered which is
replicated via DFR out to DDF. Past Future
• Real-time listing:
/DMF/PRODLOC, the field LST_STATUS_CD is set to "1" if the
prod-loc is listed, to "0" otherwise.
• Time-dependent listing:
/DMF/PRODLOC, the field TD_LST_STATUS_CD is set to "X" and in
/DMF/PRODLOC_TD a record exists that defines the VALID_FR and
VALID_TO of the field "LST_STATUS_CD".
• Valid for all available data sources De-listed
time

• Delisting information is typically used for store purchase of the prod- period
excluded in
locs, thus a time-shift is given for real delisting modeling

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 48
Enhancements for Unified Demand Forecast

Forecast Accuracy: Exclude targeted offers from modeling and

forecasting.

Use Case

In CARAB 2.0 FP02 release, PMR/DDF made the data model changes for targeted offers. Although
UDF modeling and forecasting, do not support targeted offers, this has an adverse effect, since
targeted offers are only available to a fraction of customers and not to all the customers, as assumed
by UDF. Over the period, this has the effect of corrupting UDF models. It will then affect forecast
accuracy for regular (non-targeted) promotions. Therefore it is necessary ignore days in the past when
a targeted offer was set.

Solution

The system filters sales and offer data for a day in the past when targeted promotions were set.
Targeted promotions are defined as a new field in the offer data model that is populated from the user
interface.

This is a temporary solution until UDF can model and forecast offers to only a sub-segment of the total
customers.

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 49
Enhancements for Unified Demand Forecast

Forecast Accuracy as a part of the CAR RDS

Use Case
Forecasting is a tool that can be used to understand the future unit sales
for decisions you are making within your business. It is important to know
that the forecast is accurate enough to base these decisions on. How can
a customer accurately and easily assess the forecast compared to their
actual sales?

Solution
In partnership with the Rapid Deployment Solution (RDS) team, the
Forecast accuracy views have been built into a Lumira dashboard. This
allows for easy access to the data and a comparison point between actual
sales and the forecast.

Customizing
You can download the necessary configuration documentation, the
additional SAP HANA views and the pre-built SAP Lumira report at this
link:
https://service.sap.com/public/rds-car

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 50
Agenda

1. Introduction and Overview

2. POS Data Transfer and Audit
3. Multichannel Sales Analytics
4. Inventory Visibility
5. Demand Data Foundation
6. Unified Demand Forecast
7. Omnichannel Promotion Pricing
8. Omnichannel Article Availability

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 51
Enhancements in this release

Omnichannel SAP Customer Activity Repository now provides the

Promotion ability to:
Pricing
 Omnichannel promotion pricing provides a central price and
promotion repository that stores all relevant information for the
calculation of effective sales prices in all sales and
communication channels.
 The data can be replicated via IDocs to different sales channel
applications (outbound functionality). This replication
functionality is subject to a separate license. If you want to use it,
you must obtain a separate license. For more information, please
contact your account executive.

For additional information on the features available as a part of the omnichannel promotion pricing
functionality, please check out the SAP Help Portal.

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 52
Omnichannel Promotion Pricing

Use Case
• Today, the use of multiple price calculation functionalities in different sales applications and different repositories can result
in inconsistent prices across the sales channels. This also leads to massive development and test effort when introducing
new pricing rules. For your customers, this means that no seamless omnichannel buying experience is provided, which has
a profound effect on customers' satisfaction and loyalty.
• SAP’s vision is to ensure correct and consistent effective sales prices across all sales channels along with the ability to
introduce new pricing rule types with low implementation effort.
• The first step to achieve this is to provide a central price and promotion repository as part of omnichannel promotion pricing
(OPP). This repository is located within SAP Customer Activity Repository, an application that is based on SAP HANA. It
contains all regular prices and OPP promotions that are used to calculate the effective sales prices in the sales application.

Solution / Features
• Repository inbound via standard DDF interface to push regular prices and OPP promotions to the central price and
promotion repository
• Central price and promotion repository that contains all relevant information to determine effective sales prices for the end
customer
• Automatic and manual transformation of offers into OPP promotions
• Two new IDocs to replicate regular prices and OPP promotions from the central price and promotion repository to external
systems (manual replication, initial replication, delta replication)
• Support of simple offer types and complex offer types in all sales channels
• Extensibility concept (BAdIs and customer includes) to enhance existing offer types and introduce new offer types and OPP
promotion types

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 53
Agenda

1. Introduction and Overview

2. POS Data Transfer and Audit
3. Multichannel Sales Analytics
4. Inventory Visibility
5. Demand Data Foundation
6. Unified Demand Forecast
7. Omnichannel Promotion Pricing
8. Omnichannel Article Availability

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 54
Enhancements in this release

Omnichannel SAP Customer Activity Repository now provides the

Article ability to:
Availability
 Omnichannel Article Availability(OAA) provides accurate
availability information consistent over all sales channels
encompassing all the relevant sources (Stores, Distribution
Centers)*. The Omnichannel Article Availability comes together
with a central reservation mechanism as a customer service and
for accuracy reasons.
 Dynamic Order Sourcing allows to optimize the source of
supply determination for a given shopping basket according to
predefined sourcing strategies. This makes it possible to
implement certain business strategies (e.g. fast delivery, cost
reduction) and to support Omnichannel processes like “Click and
Collect” in the web shop.

* Vendor stock information is planned to be included in the Q4 2016 release

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 55
Omnichannel Article Availability (OAA)

Use Case
• Today availability information is spread over different systems with no common view on all availability information for all the
different sources. The source of supply determination is usually rather static not allowing for the kind of flexibility that is
required to support omnichannel processes like for example delivering to the customer’s home out of a store.
• SAP’s approach:
The Omnichannel Article availability(OAA) creates a common repository in CAR for availability information that is fed
from the CAR “Inventory Visibility View” for store and from ERP via ATP calculation for DC information *.
• Based on Omnichannel article availability involving all relevant sources a sources of supply determination (“Sourcing”) can
be made to determine the best source(s) to service an order according to predefined sourcing strategies.

Solution / Features
• Omnichannel Article Availability (OAA) as central availability hub in CAR taking into consideration store and DC information*
• Article Availability / Sourcing Request APIs in CAR to support buying process in the webshop
• Smart Update Logic: ATP Parallelization in ERP to improve performance of ATP runs in ERP.
Delta Update Mechanism to improve accuracy of ATP snapshot.
• ATP Time Series information available in CAR for the DCs.
• Strategy-based sourcing: Customer-defined sequence of strategies to determine the best source(s) of supply for a shopping
cart to reflect business requirements of a customer.
• Support for Click and Collect scenario
• Central cart reservation applicable for DCs and Stores (Click and Collect process)
• Rough Stock Indicator calculation in CAR

* Vendor stock information is planned to be included in the Q4 2016 release

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 56
Omnichannel Article Availability - Architecture
Architecture in Detail and Relevant Releases

SAP Retail Industry Addon 2.0 for Hybris Commerce 6.0

 Availability requests into CAR
 Dynamic Sourcing requests into CAR
 Temporary Reservation requests into CAR

CAR Retail Applications Bundle 1.0 FP03

(CAR RETAIL APPL BUNDLE 1.0)
 Omnichannel Availability Repository for DC and
store stock (but no vendor stock)
 Dynamic Sourcing Framework
 Temporary Reservation

SAP ERP / IS Retail with EhP7 SP11 or EhP8 SP01

 Parallel ATP run for DC stocked products

SAP ERP / IS Retail with EhP7 SP12 or EhP8 SP02

 "Delta" ATP run for those articles with stock
relevant changes since last ATP run

* Planned /
Subject to Change

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 57
 OAA - Architecture
Central Article Availability Hub * Planned /
Subject to Change

1) Central hub: Overall article availability information in CAR

-> Article availability request across DCs and stores

2) Foundation for article availability calculation

a) DC: ATP calculation run in ERP (time-series information): Snapshot
approach
b) Stores: Inventory Visibility in CAR (current stock information)
c) Temporary reservations are recognized to
o Ensure data consistency by using temporary reservation as
placeholder up to ERP order is created
1)
o Increase performance by using temporary reservation as placeholder
up to next ATP run for DCs

3) Smart update logic 2b)

a) DC article availability snapshot update by parallelized ATP run in ERP 3b) 2c) 2a)
Retail (full & delta)
b) Store article availability update by real/near-time POS & SD sales order
& ERP stock upload
3a)

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 58
 OAA - Architecture
Central Sourcing Hub * Planned /
Subject to Change

1) Sourcing steps
a) Get all feasible fulfillments locations for the articles in shopping cart
(based on the eligible sources defined by customer in CAR)
b) Check the article availability for all feasible article/location combinations
for shopping cart
c) Calculate the optimal source based on sourcing procedure

2) Concept of sourcing strategies 1c)

o Sourcing procedure is based on a prioritized sequence of sourcing 1a) 2)
strategies to find the best result
1b)
o Each sourcing strategy reflects an objective defined by the customer
o The sourcing strategy is based on the (time-series) article availability
information for all feasible article/location combinations
o The sourcing strategy can potentially take the cart information and
additional information of the back-end into account

o Delivery of sample sourcing strategies

o One Delivery Today: Calculates delivery of all articles in a cart on today’s
date in one consignment shipped from one source
o Delivery Today: Calculates delivery of all articles in a cart on today’s date,
while allowing several consignments shipped from different sources
o Delivery ASAP: Calculates delivery of all articles in a cart ASAP with focus
on less number of consignments shipped from different sources
o Assign your own sourcing strategy
o Sourcing strategies are highly custom individual

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 59
 OAA - Architecture
Article Availability & Sourcing Request APIs * Planned /
Subject to Change

1) Check article availability by synchronous call to CAR

o Check article availability for single (or list of) article/location combination
o Check article availability for aggregated online stock of single (or list of)
article/location combinations (based on the eligible sources defined by
customer in CAR)

3) 1) 2)
2) Check article availability and sourcing by synchronous call to
CAR
o Check article availability for all article/location combinations in shopping
cart (based on the eligible sources defined by customer in CAR)
o Do sourcing for all click & ship articles in the shopping cart
o Reserve the click & ship and click & collect articles of the shopping cart
with the determined sources

3) Check article availability against rough stock indicator (pushed

from CAR)
o Rough stock indicator is defined and calculated in CAR and pushed to
Hybris (full & delta)
o Rough stock indicator (traffic light) is defined by customer in CAR (BAdI
implementation, sample description on HRF)
o Article availability aggregation across the eligible sources and defined time-
series (-> aggregated online stock)
o Rough stock indicator is persisted in Hybris commerce (incl. quantity) and
catalog search engine

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 60
 OAA – Process Flow
Article Availability & Sourcing in Click & Ship Scenario

1) 1) 2) 3)

1) Catalog and product details

1)
o Article availability is checked by online rough stock indicator in Hybris commerce
 If online rough stock indicator is ‘low stock’: Article availability is checked by synchronous call
of aggregated online stock to CAR (not part of standard delivery; prepared only)
2) 3)

2) Shopping cart
o Article availability is checked by synchronous call of aggregated online stock to CAR
o Article availability check is triggered by add to cart and quantity change in shopping cart

3) Check-out
o Article availability is checked and source(s) for all articles in shopping cart are determined
o The articles in the shopping cart are reserved with the determined source(s) for the customer
o Article availability check, sourcing determination, and reservation is triggered when navigating
to check-out, determining address, selecting delivery method and placing the order

-> In customer implementation project the options can be reassigned / adjusted.

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 61
 OAA – Process Flow
Article Availability & Sourcing in Click & Collect Scenario

1) 2) 3) 4)

1) Catalog and product details

1)
o Article availability is checked by online rough stock indicator in Hybris commerce
 Catalog by filtering on store: Article availability is checked against store availability
information in Hybris search engine (yes/no) (update by synchronous call to CAR, not part
of standard delivery; prepared only) 2) 3) 4)

 If online rough stock indicator is ‘low stock’: Article availability is checked by synchronous
call of aggregated online stock to CAR (not part of standard delivery; prepared only)
2) Store finder
o Article availability is checked for single article in listed stores by synchronous call to CAR
3) Shopping cart
o Article availability is checked for single article in selected store by synchronous call to CAR
o Article availability check is triggered by add to cart and quantity change in shopping cart
4) Check-out
o Article availability is checked for single article in selected store by synchronous call to CAR
o The articles in the shopping cart are reserved with the selected source for the customer
-> In customer implementation project the options can be reassigned / adjusted.

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 62
 OAA – Process Flow
Transfer Hybris Order to Backend with Customer Promise

In Hybris order click & ship and click & collect items can be placed
2b)

1) Update temporary reservation in CAR

2c)
o Reservation status is changed from ‘cart’ to ‘order’ by asynchronous call to CAR

2) Transfer the Hybris order to ERP with customer promise

a) The Hybris order is transferred via data hub to ERP Retail, asynchronously
b) In ERP Retail one SD sales order will be created via IDoc
2a)
o The SD sales order can cover click & ship and click & collect items 1)
c) The SD sales order takes the availability date and source per article from Hybris order
(ERP VA03)
o Click&ship and click&collect in store is controlled by different shipping points

3) Transfer the SD sales order to CAR

2b) 3b)
a) The SD sales order is transferred via SLT to CAR 4)

b) The synchronization timestamp is set for the reservation 3a)

4) Relevance of temporary reservation

a) DC: synchronization timestamp is initial or synchronization timestamp > calculation
timestamp
b) Store: synchronization timestamp is initial

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 63
 OAA – Configure & Run
Configure Sourcing Determination
Sourcing is based on a prioritized sequence of sourcing strategies to find the best result
(CAR IMG: SAP Customer Activity Repository -> Omnichannel Article Availability (OAA) -> Define
Sourcing Procedures)

1)

1) Sequence of sourcing strategies

2) Sourcing strategies (CAR IMG: SAP Customer Activity Repository -> Omnichannel Article 1)
Availability (OAA) -> Define Sourcing Strategies) 2),3),4)

3a)
3c)
3b)

3) Delivery of sample sourcing strategies

a) One Delivery Today: Calculates delivery of all articles in a cart on today’s date in one
consignment shipped from one source
b) Delivery Today: Calculates delivery of all articles in a cart on today’s date, while allowing
several consignments shipped from different sources
c) Delivery ASAP: Calculates delivery of all articles in a cart ASAP with focus on less number of
consignments shipped from different sources

4) Assign your own sourcing strategy

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 64
 OAA – Configure & Run
Configure Omnichannel Article Availability Profile
An Omnichannel article availability profile contains the business and technical parameters
needed to calculate the omnichannel article availability (OAA)
(CAR IMG: SAP Customer Activity Repository -> Omnichannel Article Availability (OAA) -> Define
OAA Profiles)

1a) 2b) 1b) 1c)

2a)

1) Information to calculate the article availability in DC

2b)
a) ATP Parallelization profile in ERP (ERP IMG: Sales and Distribution -> Basic Functions -> 2a)
Availability Check and Transfer of Requirements -> Availability Check -> Availability Check
with ATP Logic or Against Planning -> Retail: ATP Parallelization -> Define ATP Parallelization
Profiles)
b) Site for Assortment in ERP
c) RFC Destination to ERP

2) Information to determine the sourcing

a) Eligible source 1)

b) Sourcing procedure (CAR IMG: SAP Customer Activity Repository -> Omnichannel Article
Availability (OAA) -> Define Sourcing Procedures)

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 65
 OAA – Configure & Run
Configure ATP Parallelization Profile
An ATP parallelization profile holds all the technical information needed to parallelize the ATP
run for the assortment of an online store.
(ERP IMG: Sales and Distribution -> Basic Functions -> Availability Check and Transfer of
Requirements -> Availability Check -> Availability Check with ATP Logic or Against Planning ->
Retail: ATP Parallelization -> Define ATP Parallelization Profiles)

1a) 1b) 1c) 1d)

1) Information to define the ATP Parallelization profile

a) RFC Destination: The RFC destination of the CAR system that is the target system of the
replication.
b) ServerName: Pre-defined server group which can be used to parallelize the ATP run.
Controlled by the batch job scheduler. 1)
c) Job Name Prefix: To identify the batch jobs, easily
d) Size: Number of article / site combination per batch job

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 66
 OAA – Configure & Run
Run ATP Calculation in ERP and Update Snapshot in CAR
Pre-condition:
- ATP Parallelization Profile is set
- Omnichannel article availability profile is set

1) Schedule background job in CAR to run the ATP calculation in ERP ( CAR SM36:
/OAA/ATP_CALL_PRECALC)

1a)
1d)

a) The ATP calculation run can be triggered for certain OAA Profile (controls the relevant articles,
DCs, ATP parallelization)
b) The relevant set of the article / DC combinations can be adjusted by BAdI (ERP IMG: Sales
and Distribution -> Basic Functions -> Availability Check and Transfer of Requirements ->
Availability Check -> Availability Check with ATP Logic or Against Planning -> Retail: ATP
Parallelization -> BAdI: Set of Article/DC Combinations for ATP Run) 2) 1)
c) The ATP calculation run can be triggered for entire set of the relevant article / DC combinations
d) The ATP calculation run can be triggered for the relevant combinations with ATP relevant
changes, only (delta ATP mode)

2) The result of the ATP calculation run is persisted in DC ATP snapshot (CAR SE16:
/OAA/ATP_DC_HDR; /OAA/ATP_DC_ITM)

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 67
 OAA – Configure & Run
Define Rough Stock Indicator in CAR
1) Define the Rough Stock Indicator in BAdI (CAR IMG: SAP Customer Activity Repository ->
Omnichannel Article Availability (OAA) -> Business Add-Ins (BAdIs) -> BAdI: Generation of
Rough Stock Indicators)

2) Sample BAdI implementation for Rough Stock Indicator based on hana-based rule
framework (HRF) (Development & Implementation Guide).

a) Vocabulary: The vocabulary describes the business representation of the relevant attributes
(e.g. article group, article) for rough stock indicator. (-> SAP HANA Studio)

Fiori launchpad to define the rule and the rule service for rough stock indicator
(http://<full_domain_name>:80<instance_number>/sap/hana/uis/clients/ushell-
app/shells/fiori/FioriLaunchpad.html?)
1)
b) Fiori App to define the rule: 2)

c) Fiori App to define the rule service:

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 68
 OAA – Configure & Run
Run Rough Stock Indicator Calculation in CAR
1) Schedule background job in CAR to run the ATP calculation in ERP ( CAR SM36:
/OAA/ATP_RSI_GENERATION)

1a)
1b)
1c)

1d)

1) 2) 4)

3)
4)

a) Rough Stock Indicator calculation run can be done for certain webshop (Consumer) (CAR
IMG: SAP Customer Activity Repository -> Omnichannel Article Availability (OAA) -> Define
Consumers)
b) Rough Stock Indicator calculation run is based on certain OAA Profile (CAR IMG: SAP
Customer Activity Repository -> Omnichannel Article Availability (OAA) -> Define OAA
Profiles)
c) End Date determines the period up to the available quantities are taken into account for Rough
Stock Indicator calculation
d) IDoc Parameters for sending the Rough Stock Indicator calculation result to Hybris commerce

2) Rough Stock Indicator calculation run is triggered for eligible source / article combinations
and defined time-series

3) Rough Stock Indicator calculation result is persisted in CAR (-> aggregated online rough
stock indicator and stock)
4) It can be controlled to send changed Rough Stock Indicator to Hybris commerce, only. For
that a comparision to current Rough Stock Indicator is done in CAR, before.

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 69
 OAA – Configure & Run
Send Rough Stock Indicator to Hybris Commerce
1) The Rough Stock Indicator calculation run result (Rough Stock Indicator and calculated
quantity) is sent via IDoc and datahub to Hybris commerce (CAR BD87)

2) The target is controlled by the Consumer ID defined in CAR customizing (CAR IMG: SAP
Customer Activity Repository -> Omnichannel Article Availability (OAA) -> Define Consumers)

4)
3)

1)

2)

3) The result of the Rough Stock Indicator calculation run is persisted in base store of Hybris
commerce
a) Warehouse for Rough Stock Indicator: (Hybris hMC: Base Commerce -> Base Store ->
Properties: Warehouse)
b) Quantity: (Hybris hMC: Base Commerce -> Warehouse -> Administration: Warehouse ->
Stock level -> Properties: Available Amount)
c) Rough stock indicator: (Hybris hMC: Base Commerce -> Warehouse -> Administration:
Warehouse -> Stock level -> Administration: Rough Stock Indicator)

4) Hybris search engine (Solr) index update (Hybris hMC: System -> Facet Search: Indexer
Operation Wizard)

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 70
 OAA – Configure & Run
Deletion of Outdated DC ATP Snapshot and Reserv. Data
1) Schedule background job in CAR to run
the deletion of outdated temporary
reservations (CAR SM36:
/OAA/ATP_RESV_DELETION)

Caution:
Deleting reservations too early may lead to a
situation where articles cannot be delivered
to online store customers although they
were displayed as being available.

Temporary reservations are persisted in

CAR (CAR SE16: /OAA/ATP_RESV_H;
/OAA/ATP_RESV_I)

2) Schedule background job in CAR to run

the deletion of outdated entries in ATP 1) 2)
Snapshot (CAR SM36:
/OAA/ATP_SNAPSHOT_DELETION)

Caution:
Deleting specific ATP snapshot entries may
lead to a situation where ordering these
articles in your online store is not possible
although the articles are available

DC ATP snapshot is persisted in CAR (CAR

SE16: /OAA/ATP_DC_HDR;
/OAA/ATP_DC_ITM)

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 71
 OAA – Configure & Run
Temporary Reservation Lifecycle (1/2)
Reason for temporary reservation: (A) DC: ATP snapshot situation before reservation

 Customer experience: Reserve shopping cart during check-out process

 Consistency reason: Placeholder up to ERP order is created
 Performance reason: Placeholder up to ATP update / Inventory Visibility update
(B) Store: Inventory Visibility situation before reservation

1) Creation of temporary reservation (standard delivery)

a) Directly when the sourcing procedure determines the sources for shopping cart first time
b) The sourcing procedure is triggered when customer navigates to check-out
c) In CAR a temporary reservation is created including the determined sources

2d)

2) Update of temporary reservation

a) Directly when the sourcing procedure updates the sources of the articles in shopping cart
b) The sourcing procedure is triggered by selecting ship-to address, delivery method, and place
order (B)
c) In CAR the temporary reservation is updated including the changed at timestamp 1) (A)

d) If the customer buys now:

The status of the temporary reservation is updated and the order ID is set, asynchronously (->
order)

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 72
 OAA – Configure & Run
Temporary Reservation Lifecycle (2/2)
3) Relevance of temporary reservation (standard delivery) (A) DC: ATP snapshot situation before reservation

If the customer buys now:

a) When the Hybris order is transferred to ERP -> CAR the synchronization (B) Store: Inventory Visibility situation before reservation
timestamp of the reservation is set by the SLT order transfer timestamp

b) Relevance check is based on timestamp comparision

Logic: Temporary reservation is relevant for the availability check, if

synchronization timestamp is initial or
synchronization timestamp > ATP calculation timestamp

Distribution Center:
Available quantity = quantity of ATP snapshot – relevant temporary
reservations
Store:
Available quantity = quantity of inventory visibility – relevant (B)
temporary reservations 3) (A)

Inventory Visibility situation after SLT order transfer to CAR (CAR SE11:
/OAA/STORE_AVAIL)

If the customer doesn‘t buy now:

Up to next temporary reservation deletion report run (CAR SM36:
/OAA/ATP_RESV_DELETION)

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 73
OAA
Additional Information

SAP Help for Omnichannel Article Availability

SAP Retail Omnichannel Commerce - Customer WIKI

Omnichannel Retail - The One Stop Shop

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 74
© 2016 SAP SE or an SAP affiliate company.
All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an
SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE
(or an SAP affiliate company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional
trademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind,
and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or
SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related
presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated
companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be
changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment,
promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties
that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking
statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

© 2016
2015 SAP SE or an SAP affiliate company. All rights reserved. Early Knowledge Transfer Customer 75