Upgrade Guide | PUBLIC

Document Version: 1.0 – 2020-12-04

Common Upgrade Guide for SAP Customer

Activity Repository applications bundle 5.0
© 2020 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

1 How to Use this Common Upgrade Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.1 Naming Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2 Information Available on SAP Help Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2 Plan your System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.1 System Landscape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2 Deployment Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.3 Integration with Source Master Data Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3 Upgrade the Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

4 Prepare the Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

4.1 Implement SAP Notes for the Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.2 Verify Correct Schema Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
4.3 Verify SAP HANA Users and Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
4.4 Configure AFL Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Enable Usage of PAL Functions (SAP Assortment Planning). . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Check the OFL Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
4.5 Configure the Zero Downtime Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Map Schemas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Get Database User Authorization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Activate and Deploy Logical HDI Containers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Select a Mode for HDI Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
4.6 Migrate to New Default Table for Sales Pricing Data (/DMF/PRC). . . . . . . . . . . . . . . . . . . . . . . . . . 64

5 Upgrade the Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

5.1 Verify Prerequisites and SAP Notes (Pre-Upgrade). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
5.2 Download and Install SAP RTL AFL FOR SAP HANA (Mandatory). . . . . . . . . . . . . . . . . . . . . . . . . 67
5.3 Download and Install SAP XRP AFL (Only for SAP Replenishment Planning). . . . . . . . . . . . . . . . . . . 71
5.4 Upgrade SAP CARAB Back-End Product Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
5.5 Verify SAP Client Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
5.6 Upgrade SAP FIORI FOR SAP CARAB Front-End Product Version. . . . . . . . . . . . . . . . . . . . . . . . . 77
5.7 Verify SAP Notes and RINs (Post-Upgrade). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

6 Set Up the Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

6.1 SAP Customer Activity Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Core (Mandatory for All Applications). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Advanced (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
2 PUBLIC Content
 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

6.2 SAP Merchandise Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Verify SAP HANA Content for SAP Merchandise Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Activate Application BI Content Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Verify Time Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216

6.3 SAP Assortment Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

4.0/4.0 FPS01/FPS02/FPS03/SPS05 to 5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

2.0 SP6/SP7/SP8 to 5.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244

6.4 SAP Promotion Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .272

6.5 SAP Allocation Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

1.5 (CARAB 2.0 SPS0) to 4.0, 4.0 FPS02, 4.0 FPS03, 4.0 SPS04, 4.0 SPS05, or 5.0. . . . . . . . . . 274

2.0 FP1 to 4.0, 4.0 FPS02, 4.0 FPS03, 4.0 SPS04, 4.0 SPS05, or 5.0. . . . . . . . . . . . . . . . . . . . . 276

2.0 FP2 and FP3 to 4.0, 4.0 FPS02, 4.0 FPS03, 4.0 SPS04, 4.0 SPS05, or 5.0. . . . . . . . . . . . . . 278

Activate SAP HANA Content for SAP Allocation Management . . . . . . . . . . . . . . . . . . . . . . . . . 279

Check Procedure Associated with Function GENIOS_SOLVE Is Active. . . . . . . . . . . . . . . . . . . . 283

Implement BAdI for Real-Time Inventory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

Troubleshooting for SAP Allocation Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

6.6 SAP Replenishment Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

Perform Core Steps for SAP Customer Activity Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . .285

Implement SAP Notes for the Integration of SAP Replenishment Planning with SAP ERP or
SAP S/4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .285

Specify RFC Destinations for Source Master Data Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . 286

Enable the Use of Scheduling Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .286

Set Up SAP Fiori Apps for SAP Replenishment Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .287

Set Up Database Roles and Authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .309

Set Up Back-End Roles and Authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310

Set Up Authorizations for Transfer of Order Plan Items to Source Master Data System. . . . . . . . 315

Perform Configuration Steps in SAP Customer Activity Repository. . . . . . . . . . . . . . . . . . . . . . 316

Configure SAP Replenishment Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

Define the Parameterization Profiles and the Assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . .319

Configure Exception Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .320

Verify Real-Time Inventory Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

6.7 Configure Access to Documentation Provided on SAP Help Portal (Optional for All Applications)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

6.8 Enable In-App Help (Web Assistant). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

Install and Configure SAP Web Dispatcher. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326

Set Up the In-App Help (Web Assistant) Plugin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Content PUBLIC 3
1 How to Use this Common Upgrade Guide

This guide describes how to upgrade and set up the applications included in SAP Customer Activity Repository
applications bundle 5.0. Learn what applications are included in this release, and get an overview of the main
upgrade steps.

Applications in this Release (Functional View)

 Caution

If you do not have an existing installation of any of these applications, you must perform a new installation
rather than an upgrade. In this case, see the Common Installation Guide at https://help.sap.com/viewer/p/
CARAB.

Functionally, SAP Customer Activity Repository applications bundle 5.0 includes the following applications:

● SAP Customer Activity Repository 5.0

● SAP Merchandise Planning 5.0
● SAP Assortment Planning 5.0
● SAP Promotion Management 5.0
● SAP Allocation Management 5.0
● SAP Replenishment Planning 5.0

Product Documentation

You can find this guide and all product documentation for these applications on SAP Help Portal for SAP
Customer Activity Repository applications bundle at https://help.sap.com/viewer/p/CARAB.

 Note

You can set up your back-end system to consume documentation directly from SAP Help Portal. For more
information, see Configure Access to Documentation Provided on SAP Help Portal (Optional for All
Applications) [page 323].

What to Upgrade (Technical View)

Technically, SAP Customer Activity Repository applications bundle 5.0 is delivered in the form of two installable
product versions, one for the back-end and one for the front-end.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
4 PUBLIC How to Use this Common Upgrade Guide
 Product Versions for this Release Purpose

SAP CARAB 5.0 Back-end product version

Contains several software components that provide the ABAP

back-end functionality and the business content for all the appli­
cations in SAP Customer Activity Repository applications bundle
5.0. For example, this includes SAP HANA views and SQLScript
procedures, local BI Content, application function libraries, and
workbooks, where applicable.

SAP FIORI FOR SAP CARAB 5.0 Front-end product version

Contains one software component that includes the SAP Fiori

apps for the applications in SAP Customer Activity Repository
applications bundle 5.0. This product version is also referred to as
the product-specific SAP Fiori UI component.

Upgrade at a Glance

This guide leads you through the following main activities:

1. First you prepare the upgrade. Here you ensure that the technical prerequisites are installed. You also
implement mandatory corrections, verify authorizations, and do other preparatory tasks. These steps are
described in section Upgrade the Prerequisites [page 18] and section Prepare the Upgrade [page 29].
2. Then you upgrade the back-end product version and the front-end product version. These steps are
described in section Upgrade the Software [page 66]. You must do these steps regardless of the
application that you want to set up later on.
3. Now you can set up the desired applications. These steps are described in section Set Up the Applications
[page 81]. First you must do the general setup steps in section Core (Mandatory for All Applications)
[page 81]. You must do these core steps regardless of the application that you want to set up. After the
core steps, you only need to do the steps that are required for your application. You do not need to read
sections that do not apply to your application.

 Tip

Get Notified of SAP Note Updates

This guide references several SAP Notes that are regularly updated with new information. If a note is
particularly relevant for your scenario and you want to be informed of updates, you can easily set up email
notifications. See SAP Note 2478289 (How to get notifications for SAP Notes or KBAs).

 Tip

Get SAP Universal ID for Easy Login

With an SAP Universal ID, you get a single user login and profile. You are able to log in once to gain access to
all of your authorized SAP platforms and applications.

SAP Universal ID is a free service offered by SAP which requires no software installation. For more
information, see https://discover.sap.com/universalid/en-us/about.html .

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
How to Use this Common Upgrade Guide PUBLIC 5
1.1 Naming Conventions

This section explains important terms used in this guide. It also explains the meaning of important variables
(for example, SAPHANADB). Additionally, you get an overview of naming differences that exist between the
consuming applications.

Important Terms

Term Definition

Common Installation Guide These two common guides are your entry points for all the applications and scenarios in­
cluded in SAP Customer Activity Repository applications bundle. Use the Common Installa­
Common Upgrade Guide
tion Guide if you wish to do a completely new installation. Use the Common Upgrade Guide
if you wish to upgrade from a lower release.

You can find both guides on SAP Help Portal at https://help.sap.com/viewer/p/CARAB un­
der Implement.

consuming application An application consuming data from SAP Customer Activity Repository.

Examples:

● SAP Allocation Management

● SAP Assortment Planning
● SAP Merchandise Planning
● SAP Promotion Management
● SAP Replenishment Planning

back-end server / back-end The SAP NetWeaver-based ABAP back-end server

system
Depending on your deployment scenario, this is where you might install the SAP CARAB
back-end product version of SAP Customer Activity Repository applications bundle..

front-end server / front-end The SAP NetWeaver-based ABAP front-end server

system
Depending on your deployment scenario, this is where you might install SAP Gateway, the
central SAP Fiori UI component (including SAP Fiori launchpad), and the SAP FIORI FOR
SAP CARAB front-end product version of SAP Customer Activity Repository applications
bundle.

logical schema A term used in the Display Mappings of Database Schemas transaction in SAP Customer
Activity Repository.

The term is synonymous with the authoring schema concept in SAP HANA studio.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
6 PUBLIC How to Use this Common Upgrade Guide
 Term Definition

source master data system SAP Customer Activity Repository applications bundle must be deployed alongside an SAP
ERP (SAP Retail, SAP Fashion Management) or SAP S/4HANA (SAP S/4HANA Retail) cen­
tral component as the single source of truth for all master data.

Whenever this guide refers to a source master data system, it refers to the SAP ERP or SAP
S/4HANA central component that you choose for your implementation.

For more information, see Integration with Source Master Data Systems [page 16].

SAP ERP Unless otherwise specified, references in this guide to SAP ERP are comprehensive. That is,
they apply to SAP Retail and SAP Fashion Management.

SAP S/4HANA Unless otherwise specified, references in this guide to SAP S/4HANA are comprehensive.
That is, they apply to SAP S/4HANA Retail for merchandise management and to SAP S/
4HANA for fashion and vertical business.

Important Variables

 Note

Variables are placeholders for objects that have different names in your customer system landscape or are
user-defined.

When you come across a variable in this guide, replace it with your customer-specific name of the
respective object.

 Example

An instruction states to map the authoring schema to the SAPHANADB physical schema in your ABAP back-
end system.

● In your customer system landscape, this physical schema is called ABC01.

● You therefore replace the SAPHANADB variable with ABC01. That is, you map the authoring schema to
the ABC01 physical schema.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
How to Use this Common Upgrade Guide PUBLIC 7
Variable Description

Depending on the documentation and user Stands for the name of the ABAP back-end system, database schema, or da­
interface, you might come across any of the tabase user in your customer system landscape.
following variables. They all mean the
same:  Tip
● SAPHANADB If you don't know what the name is in your customer system landscape,
● SAPABAP<num> there are two easy ways to find it:

● SAP<id> ● Log on to your ABAP back-end system using SAP Logon. Choose

System Status . In the section titled Database data, see the

name for Schema.
● In SAP HANA studio, the schema name is listed under Catalog.

For more information, see SAP Note 2535951 (FAQ: SAP HANA Users and
Schemas).

<DBSID> Database ID in uppercase letters

<dbsid> Database ID in lowercase letters

<INSTDIR> Installation directory for the SAP system

<DVD_DIR> Directory on which a DVD is mounted

<OS> Operating system name within a path

Naming Differences

Due to naming differences between the underlying technical objects, the following terms are used
interchangeably in this guide:

SAP Customer Activity Unified Demand Forecast SAP Retail and SAP S/
Repository (all modules ex­ (UDF) and Demand Data 4HANA
cept for UDF and DDF) Foundation (DDF)

SAP Merchandise Planning

SAP Assortment Planning

SAP Promotion
Management

SAP Replenishment SAP Allocation

Planning Management

article product product article

material

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
8 PUBLIC How to Use this Common Upgrade Guide
 SAP Customer Activity Unified Demand Forecast SAP Retail and SAP S/
Repository (all modules ex­ (UDF) and Demand Data 4HANA
cept for UDF and DDF) Foundation (DDF)

SAP Merchandise Planning

SAP Assortment Planning

SAP Promotion
Management

SAP Replenishment SAP Allocation

Planning Management

article variant product variant product variant or product/ article variant

color/size

store location (used as an umbrella store store

term for stores, distribution
site
centers, etc.)

1.2 Information Available on SAP Help Portal

Information on prerequisite platforms, applications, and other components as well as quick links to SAP sites

Information on Prerequisite Platforms, Applications, Other Components

Information On Path Title

Installing SAP HANA http://help.sap.com/viewer/p/ SAP HANA Server Installation and Up­
SAP_HANA_PLATFORM date Guide

<Version> Installation and

Upgrade SAP HANA Server

Installation and Update Guide

Installing SAP HANA database clients http://help.sap.com/viewer/p/ SAP HANA Client Installation and Up­
SAP_HANA_PLATFORM date Guide

<Version> Installation and

Upgrade SAP HANA Client

Installation and Update Guide

Installing SAP HANA studio http://help.sap.com/viewer/p/ SAP HANA Studio Installation and Up­
SAP_HANA_PLATFORM date Guide

<Version> Installation and

Upgrade SAP HANA Studio

Installation and Update Guide

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
How to Use this Common Upgrade Guide PUBLIC 9
Information On Path Title

Installing SAP LT (Landscape Transfor­ http://help.sap.com/viewer/p/ Installation Guide

mation) Replication Server for SAP SAP_HANA_REAL_TIME_REPLICATION
HANA <Version> Installation and

Upgrade

Managing major operational aspects of http://help.sap.com/viewer/p/ Versions up to 3.0 SP04: Application

the SAP LT (Landscape Transforma­ SAP_HANA_REAL_TIME_REPLICATION Operations Guide
tion) Replication Server for SAP HANA <Version> Versions 3.0 SP04 and higher: Applica­
tion Help

Using SAP HANA http://help.sap.com/viewer/p/ SAP HANA Administration Guide for

SAP_HANA_PLATFORM SAP HANA Platform

<Version> Administration SAP

HANA Administration Guide

Using the SAP HANA development http://help.sap.com/viewer/p/ SAP HANA Developer Guide
tools to create comprehensive analyti­ SAP_HANA_PLATFORM
cal models and to build applications
<Version> Development SAP
with SAP HANA interfaces and inte­
HANA Developer Guide (For SAP HANA
grated development
Studio)
(for developers)

Defining data models for use in SAP http://help.sap.com/viewer/p/ SAP HANA Modeling Guide for HANA
HANA SAP_HANA_PLATFORM Studio

(for modelers, business analysts) <Version> Development SAP

HANA Modeling Guide (For SAP HANA

Studio)

Installing Foundation on SAP NetWea­ https://help.sap.com/viewer/p/ Master Guide

ver AS for ABAP 7.52, version for SAP SAP_NETWEAVER_AS_ABAP_752
HANA <Version> Installation and

Upgrade Master Guide

Installing SAP ERP 6.0 http://help.sap.com/viewer/p/ Installation Guide

SAP_ERP <Version> Installation

and Upgrade Installation Guide

Installing SAP S/4HANA http://help.sap.com/viewer/p/ Installation Guide

SAP_S4HANA_ON-PREMISE

<Version> Implement

Installation Guide

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
10 PUBLIC How to Use this Common Upgrade Guide
General Quick Links

SAP Site Path

SAP Help Portal http://help.sap.com

Knowledge Base Articles and SAP Notes https://support.sap.com/en/index.html

Product Availability Matrix (PAM) http://support.sap.com/pam

Maintenance and release strategy https://support.sap.com/en/release-upgrade-maintenance.html

SAP Software Download Center http://support.sap.com/swdc

SAP Solution Manager http://support.sap.com/solutionmanager

SAP Security Optimization Services Portfolio https://support.sap.com/en/offerings-programs/support-services/

security-optimization-services-portfolio.html

Data Protection and Privacy 2590321 Upgrade recommendations to support GDPR compliance

Support information (quick access via SAP ONE https://launchpad.support.sap.com/#/productsearch

Support Launchpad; requires login)

Support package stacks, latest versions, patch http://support.sap.com/patches

level requirements

System sizing http://www.sap.com/sizing

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
How to Use this Common Upgrade Guide PUBLIC 11
2 Plan your System

Plan your customer landscape so that it best serves your business scenario. Choose the best deployment
option, and see from which source master data systems you can replicate data to your SAP Customer Activity
Repository applications bundle system.

System Landscape [page 13]

Find out what a typical system landscape for SAP Customer Activity Repository applications bundle
looks like. You can see the main layers in the diagram (database, back-end, front-end).

Deployment Options [page 15]

Learn about the two deployment options for your SAP Customer Activity Repository applications
bundle solution.

Integration with Source Master Data Systems [page 16]

Get an overview of the source master data systems from which you can replicate master data and
transactional data to SAP Customer Activity Repository applications bundle.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
12 PUBLIC Plan your System
2.1 System Landscape

Find out what a typical system landscape for SAP Customer Activity Repository applications bundle looks like.
You can see the main layers in the diagram (database, back-end, front-end).

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Plan your System PUBLIC 13
System Landscape Example

The applications included in SAP Customer Activity Repository applications bundle require a layered system
landscape, as shown in the following example:

System Landscape Example

 Tip

Planning Help

● For more information on possible deployment scenarios, see Deployment Options [page 15].
● For the minimum versions required for this release, see Upgrade the Prerequisites [page 18].

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
14 PUBLIC Plan your System
2.2 Deployment Options

Learn about the two deployment options for your SAP Customer Activity Repository applications bundle
solution.

To help you decide on the best deployment option for your scenario, please see SAP Note 2997851 (SAP
Customer Activity Repository applications bundle 5.0: Front-end deployment options).

What is Central Hub Deployment?

With central hub deployment, you install the back-end product version (SAP CARAB) in your ABAP back-end
system, while you install the front-end product version (SAP FIORI FOR SAP CARAB) and the SAP Fiori front-
end server in a separate front-end system.

As a result, the SAP Fiori apps are deployed in separate systems (UIs in the front-end system, related OData
services in the back-end system).

What is Embedded Deployment?

With the embedded deployment option, you install the SAP Fiori front-end server in the same system as your
ABAP back-end server. For your SAP Customer Activity Repository applications bundle solution, this means
that you install the back-end product version (SAP CARAB) and the front-end product version (SAP FIORI
FOR SAP CARAB) in the same system (that is, your SAP S/4HANA FOUNDATION back-end system).

 Caution

If you wish to use or are already using an embedded deployment scenario for SAP Customer Activity
Repository applications bundle in the same system as the SAPS/4HANA source master data system,
carefully read SAP Note 2948396 (Deployment options for SAP Customer Activity Repository
applications bundle and SAP S/4HANA source master data system).

The note contains important deployment information for the following scenario:

● Your current source master data system is SAP S/4HANA 1709 or 1809.
● You want to install or upgrade to SAP S/4HANA 1909 or higher.
● You are using your source master data system in an embedded deployment scenario. That is, you are
also using it as your front-end system for SAP Customer Activity Repository applications bundle. In
other words, you have installed the front-end product version SAP FIORI FOR SAP CARAB
(containing the software component UICAR001 with the SAP Fiori apps) on your SAP S/4HANA
system.
The advantage of this option is that you do not require a separate front-end system.
● Be aware that such an embedded scenario is no longer possible as of SAP S/4HANA 1909. For more
information and for supported deployment alternatives, please see SAP Note 2948396 .

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Plan your System PUBLIC 15
More Information

 Tip

To help you decide on the best deployment option for your scenario, see SAP Note 2997851 (SAP
Customer Activity Repository applications bundle 5.0: Front-end deployment options).

For more information on deployment options for SAP Fiori, see the following:

● For a system landscape overview showing the ABAP back-end server and the ABAP front-end server, see
https://help.sap.com/viewer/p/FIORI_IMPLEMENTATION and choose Implement Installation and
Upgrade SAP Fiori: Setup and Configuration Setup of SAP Fiori System Landscape .

2.3 Integration with Source Master Data Systems

Get an overview of the source master data systems from which you can replicate master data and transactional
data to SAP Customer Activity Repository applications bundle.

Overview

You can deploy your scenario of SAP Customer Activity Repository applications bundle in parallel with one of
the following source master data systems:

Source Master Data System Flavor

SAP ERP SAP Retail (add-on to SAP ERP)

SAP Fashion Management (add-on to SAP Retail)

SAP S/4HANA SAP S/4HANA Retail for merchandise management

SAP S/4HANA for fashion and vertical business

 Note

Unless otherwise specified, references in this guide to SAP ERP are comprehensive. That is, they apply to
SAP Retail and SAP Fashion Management.

The same is true for references to SAP S/4HANA. That is, they apply to SAP S/4HANA Retail for
merchandise management and to SAP S/4HANA for fashion and vertical business.

For more information on these and other important terms used in this guide, see Naming Conventions
[page 6].

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
16 PUBLIC Plan your System
Prerequisites

For information on what versions of the source master data systems are required for this release, see Upgrade
the Prerequisites [page 18].

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Plan your System PUBLIC 17
3 Upgrade the Prerequisites

This section lists all the prerequisite platforms, applications, and components that must be installed and
configured to prepare the system landscape for an upgrade from a previous release.

 Note

If you are performing a new installation of this release, the information in this Common Upgrade Guide is
not relevant for you. Instead, proceed with the Common Installation Guide available at https://
help.sap.com/viewer/p/CARAB on the Implement tab.

The prerequisites are grouped in two categories:

● Common Prerequisites, which must be installed regardless of the business scenario you are planning to
implement
● Application-Specific Prerequisites, which are only relevant for specific applications under specific
conditions

 Caution

The prerequisites should be installed and configured by an experienced SAP Basis administrator.

 Tip

This guide references several SAP Notes that are updated regularly. If you want to be informed of such
updates because a note is particularly relevant for your scenario, you can easily set up email notifications
for it. For instructions, see SAP Note 2478289 (How to get notifications for SAP Notes or KBAs).

Common Prerequisites

 Tip

For the latest support information and technology updates, always see SAP Note 2957259 (Latest news
on SAP Customer Activity Repository applications bundle 5.0). If there are updates concerning the
prerequisites described in this guide, you can find this information in the note.

You can also find the note on SAP Help Portal at https://help.sap.com/viewer/p/CARAB under
Implement Important SAP Notes .

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
18 PUBLIC Upgrade the Prerequisites
SAP S/4HANA FOUNDATION
The minimum requirement for this release is as follows, regardless of the business scenario you are planning to
implement:

Foundation Com­
ponent Minimum Requirement Installation Information

SAP S/4HANA ● SAP S/4HANA FOUNDATION ● SAP Note 2750164 (SAP S/4HANA FOUNDATION 1909:
FOUNDATION 1909 — FPS02 (05/2020) Release Information Note)
(SAP S/4HANA Foundation) ● Guide Finder (list of guides with installation and migration
information on SAP S/4HANA FOUNDATION)

 Note

If the required version of SAP S/4HANA FOUNDATION is not yet installed in your back-end system, it will be
installed automatically when you upgrade to the SAP CARAB 5.0 back-end product version. This guide
leads you through the correct steps.

 Caution

Before installing or upgrading the foundation component in your system landscape, check for the latest
support information. See SAP Note 2957259 (Latest news on SAP Customer Activity Repository
applications bundle 5.0).

SAP HANA Platform 2.0

● SAP HANA database component:
The minimum requirement for this release is as follows, regardless of the business scenario you are
planning to implement:
○ SAP HANA database 2.0 SPS05 revision 50.00
○ Before installing a revision, check for the latest support information. See SAP Note 2818378 (Which
releases of SAP HANA Platform are supported for which releases of SAP Customer Activity Repository
applications bundle (SAP CARAB)?).

 Caution

Guidance for Selecting a Higher Revision than the Minimum Revision

If you wish to use a higher revision, we recommend that you select one of the “maintenance revisions”.
See SAP Note 2378962 (SAP HANA 2.0 Revision and Maintenance Strategy) and consult the
information under Last Released Revision or Maintenance Revision.

Also use this same strategy if the minimum revision is no longer available for download from the
Software Download Center. This situation might occur depending on when you perform the actual
installation and how long ago the revision was released.

If you wish to use the latest SAP HANA support package stack, be aware that there are no
maintenance revisions for it. In this case, we recommend the following:
1. To avoid incompatibilities, first consult SAP Note 2818378 (Which releases of SAP HANA
Platform are supported for which releases of SAP Customer Activity Repository applications bundle
(SAP CARAB)?).

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Upgrade the Prerequisites PUBLIC 19
 Select a supported combination of releases. This applies not only during a new installation or an
upgrade, but is equally relevant if you decide to upgrade your SAP HANA Platform to a higher
revision or even support package stack later on.
2. Install the latest SAP HANA support package stack in your test system. Test it carefully to evaluate
its impact on your customer system landscape. Only roll it out to your production system when you
are sure that it integrates well with your day-to-day business processes.

● SAP HANA AFL component:

The minimum requirement for this release is the SAP HANA AFL revision that is compatible with the
selected SAP HANA database revision.

For installation information, see the following:

● SAP Note 2818378 (Which releases of SAP HANA Platform are supported for which releases of SAP
Customer Activity Repository applications bundle (SAP CARAB)?)
● SAP Note 2378962 (SAP HANA 2.0 Revision and Maintenance Strategy, lists the available maintenance
revisions)
● SAP Note 2115815 (FAQ: SAP HANA Database Patches and Upgrades, helpful information on database
upgrades, downgrades, downtimes, patch levels, and more)
● SAP HANA 2.0 Revision Strategy (what are revisions, what are support package stacks, what is the SAP
HANA product availability and maintenance strategy)
● SAP Note 2844322 (SAP HANA Platform 2.0 SPS 05 Release Note)
● SAP HANA Server Installation and Update Guide for your SAP HANA Platform version at https://
help.sap.com/viewer/p/SAP_HANA_PLATFORM
● Overview and download of SAP HANA Platform 2.0: http://support.sap.com Software Downloads
By Alphabetical Index (A-Z) H SAP HANA PLATFORM EDITION SAP HANA PLATFORM EDITION 2.0
INFO
● SAP Note 2339267 (HANA Client version and installation manifest file doesn't match currently available
HANA server version information)

If you are planning to upgrade from SAP HANA Platform 1.0 to SAP HANA Platform 2.0, also see the following:

● SAP Note 1948334 (SAP HANA Database Update Paths for SAP HANA Maintenance Revisions)
● SAP Note 2372809 (Mandatory Preparation Steps for Upgrading a SAP HANA 1 System to SAP HANA 2)
● SAP Note 2422421 (Guideline for upgrading a SAP HANA system with extended application services,
advanced model)

SAP RTL AFL FOR SAP HANA

 Note

SAP RTL AFL FOR SAP HANA is a back-end software component of SAP Customer Activity Repository
applications bundle. However, you must always upgrade this component together with the SAP HANA
Platform. You must do this before upgrading the SAP CARAB back-end product version. This guide leads
you through the correct steps.

The minimum revision for SAP RTL AFL FOR SAP HANA applies regardless of the business scenario you are
planning to implement. There is a minimum AFL revision for each SAP HANA database revision. Whichever AFL
revision you choose, it must be compatible with the SAP HANA database revision.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
20 PUBLIC Upgrade the Prerequisites
Compatible Minimum Revisions
Minimum Revision of SAP RTL AFL FOR SAP HANA Compatible With This Revision of SAP HANA Database

AFL revision 50.1 (patch 1 of revision 50) SAP HANA database 2.0 revision 50

AFL revision 51.1 (patch 1 of revision 51) SAP HANA database 2.0 revision 51

AFL revision 52.1 (patch 1 of revision 52) SAP HANA database 2.0 revision 52

AFL revision 53.0 (patch 0 of revision 53) SAP HANA database 2.0 revision 53

 Note

For information on higher revisions, see SAP Note 2818378 (Which releases of SAP HANA Platform are
supported for which releases of SAP Customer Activity Repository applications bundle (SAP CARAB)?).

 Caution

No matter which AFL revision you choose, always install the highest patch available for download.

Be aware that patches for different revisions can occur at different points in time.

 Example

The AFL patch 51.1 was released later than the AFL patch 52.0.

If you decide to install a higher revision of SAP RTL AFL FOR SAP HANA, it must again be compatible
with the SAP HANA database revision.

When you download an AFL revision from the SAP Support Portal, the compatible SAP HANA database
revision is always indicated.

 Note

SAP RTL AFL FOR SAP HANA contains back-end functionality for two modules of SAP Customer Activity
Repository: Unified Demand Forecast (UDF) and On-Shelf Availability (OSA). You must always install the
component, regardless of the scenario you are planning to implement. You only need to configure UDF
and/or OSA if you wish to use the functionality in your scenario.

SAP Landscape Transformation Replication Server

The minimum requirement for this release is SAP Landscape Transformation Replication Server 2.0 for SAP
HANA, regardless of the business scenario you are planning to implement.

 Caution

If your source master data system is SAP S/4HANA 1909 or higher, be aware that the SAP LT Replication
Server is no longer available as a standalone component. For more information, see the Source Master Data
Systems section below.

For installation information and possible dependencies to other components, see the following:

● Installation Guide (Replicating Data to SAP HANA) at https://help.sap.com/viewer/p/

SAP_LANDSCAPE_TRANSFORMATION_REPLICATION_SERVER

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Upgrade the Prerequisites PUBLIC 21
● SAP Note 1605140 (SAP Landscape Transformation Replication Server (SLT)): This is the central note
for enabling trigger-based data replication (functional overview, download, installation, upgrade,
corrections, implementation).
● SAP Note 2014562 (FAQ: SAP HANA LT Replication Server (SLT))
● SAP Note 2707835 (SLT Licensing, licensing and deployment overview by source master data system)
● SAP Note 2572945 (DMIS compatibility with S/4HANA, integration of DMIS component into S4CORE
layer, release overview and guidance for SAP S/4HANA source master data systems)

SAP Fiori

SAP Fiori front-end server is an add-on product version. It contains the front-end software components
required to run SAP Fiori apps and the SAP Fiori launchpad.

The minimum requirement for this release is SAP FIORI FRONT-END SERVER 6.0 SPS02 (05/2020),
regardless of the business scenario you are planning to implement. The accompanying SAP_UI version is 7.54
SPS01. The accompanying SAPUI5 version is 1.65.xx.

For more information, see the following:

● Planning:
○ Overview of SAP Fiori front-end server components and versions
○ SAP Fiori Deployment Options and System Landscape Recommendations (regularly updated,
includes helpful landscape diagrams)
○ For planning information and a helpful version overview (front-end server, application server ABAP,
SAP Gateway, SAPUI5), see SAP Note 2217489 (Maintenance and Update Strategy for SAP Fiori
Front-End Server).
○ SAP Note 2825540 (Release of Fiori Product Versions for SAP Fiori front-end server 6.0)
○ SAP Note 2977715 (Release of Fiori Product Versions for SAP Fiori front-end server 2020 for SAP S/
4HANA)
● Installation and implementation:
○ SAP Fiori Implementation Information (select your front-end server version at the top)
○ SAP Note 2590653 (SAP Fiori front-end server deployment for SAP S/4HANA)
○ SAP Note 2775163 (SAP-Fiori-Frontend-Server 6.0 - General Information)
○ SAP Note 2919182 (SAP Fiori front-end server 2020 for SAP S/4HANA)

 Tip

If you wish to check what SAPUI5 version is currently installed, there is an easy way to do this. See SAP
Note 2282103 (How to check the version of SAPUI5 you have installed).

Source Master Data Systems

● Either SAP ERP or SAP S/4HANA must be installed.

 Note

Unless otherwise specified, references in this guide to SAP ERP are comprehensive. That is, they apply
to SAP Retail and SAP Fashion Management.

The same is true for references to SAP S/4HANA. That is, they apply to SAP S/4HANA Retail for
merchandise management and to SAP S/4HANA for fashion and vertical business.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
22 PUBLIC Upgrade the Prerequisites
 For more information on these and other important terms used in this guide, see Naming Conventions
[page 6].

● The minimum requirements for this release are as follows, regardless of the business scenario you are
planning to implement:

Source Master Data Sys­

tem Minimum Requirement Installation Information

SAP ERP ○ SAP ERP 6.0 Enhancement Package 7 SP16 Installation Guide at https://
or higher help.sap.com/viewer/p/SAP_ERP
○ SAP ERP 6.0 Enhancement Package 8 SP09
or higher

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Upgrade the Prerequisites PUBLIC 23
 Source Master Data Sys­
tem Minimum Requirement Installation Information

SAP S/4HANA ○ SAP S/4HANA 1709 FPS2 or higher ○ Installation Guide at https://
○ SAP S/4HANA 1809 Initial Shipment Stack help.sap.com/viewer/p/
or higher SAP_S4HANA_ON-PREMISE
○ SAP S/4HANA 1909 Initial Shipment Stack ○ SAP Note 2482453 (SAP S/
or higher 4HANA 1709: Release Information
○ SAP S/4HANA 2020 Initial Shipment Stack Note)
or higher ○ SAP Note 2625407 (SAP S/
4HANA 1809: Release Informa­
 Caution tion Note)
If you wish to use or are already using an em­ ○ SAP Note 2769531 (SAP S/
bedded deployment scenario for SAP 4HANA 1909: Release Informa­
Customer Activity Repository applications tion Note)
bundle in the same system as the SAPS/ ○ SAP Note 2884313 (SAP S/
4HANA source master data system, care­ 4HANA 2020: Release Informa­
fully read SAP Note 2948396 (Deploy­ tion)
ment options for SAP Customer Activity Re­
pository applications bundle and SAP S/  Note
4HANA source master data system).
If your source master data sys­
The note contains important deployment in­ tem is SAP S/4HANA 1909 or
formation for the following scenario: higher, be aware that the SAP LT
Replication Server is no longer
○ Your current source master data system
available as a standalone compo­
is SAP S/4HANA 1709 or 1809.
nent. Instead, an embedded SAP
○ You want to install or upgrade to SAP S/
LT Replication Server is included
4HANA 1909 or higher.
in SAP S/4HANA by default.
○ You are using your source master data
system in an embedded deployment To set up the data replication
scenario. That is, you are also using it as from SAP S/4HANA 1909 or
your front-end system for SAP higher, you need to do some pre­
Customer Activity Repository paratory steps. This guide leads
applications bundle. In other words, you you through the correct proce­
have installed the front-end product ver­ dure in the data replication sec­
sion SAP FIORI FOR SAP CARAB tion (Create/Replicate Source
(containing the software component Master Data System Tables [page
UICAR001 with the SAP Fiori apps) on 88]). The preparatory steps

your SAP S/4HANA system. have the added advantage that

The advantage of this option is that you they give you the option to still

do not require a separate front-end sys­ use a standalone SAP LT Replica­

tem. tion Server.

○ Be aware that such an embedded sce­

nario is no longer possible as of SAP S/
4HANA 1909. For more information and
for supported deployment alternatives,
please see SAP Note 2948396 .

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
24 PUBLIC Upgrade the Prerequisites
  Tip

If you are planning to convert from SAP ERP to SAP S/4HANA, you can use the SAP Readiness Check
to check the readiness of your SAP ERP system. For more information, see SAP Note 2758146 (SAP
Readiness Check 2.0 & Next Generation SAP Business Scenario Recommendation).

Application-Specific Prerequisites

SAP Customer Activity Repository

Prerequisites for SAP Customer Activity Repository

Prerequisite Minimum Requirement Mandatory/Optional Installation Information

SAP Customer Relationship The minimum requirement Optional, depending on Installation Guide at https://
Management (SAP CRM) for this release is one of the whether or not you choose to help.sap.com/viewer/p/
following: implement customer deter­ SAP_CUSTOMER_RELA­
mination with SAP CRM. TIONSHIP_MANAGEMENT
● SAP Enhancement
Package 2 for SAP CRM
7.0
● SAP Enhancement
Package 2 for SAP CRM
7.0, Version for SAP
HANA or higher

SAP Smart Business SAP Smart Business founda­ Optional, depending on SAP Note 2018360 (Re­
tion component 1.0, most re­ whether or not you choose to lease Information Note for
cent SPS implement the SAP Smart SAP SMART BUSINESS)
Business for Multichannel
Sales Analytics dashboard
within SAP Customer Activity
Repository.

SAP Marketing solution (SAP SAP Marketing 1.10 or higher Optional, depending on ● For SAP Marketing, see
Marketing or SAP Marketing whether or not you choose to the Installation and Con­
Cloud) implement customer deter­ figuration Guide at
mination with your SAP Mar­ https://help.sap.com/
keting solution. viewer/p/
SAP_HYBRIS_MARKET­
ING.
● For SAP Marketing
Cloud, see https://
help.sap.com/viewer/p/
SAP_MARKET­
ING_CLOUD.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Upgrade the Prerequisites PUBLIC 25
Prerequisite Minimum Requirement Mandatory/Optional Installation Information

SAP Commerce SAP Commerce 1811 or Optional, depending on https://help.sap.com/

higher (in particular, the Ac­ whether or not you choose to viewer/p/SAP_COMMERCE/
celerator, the Data Hub, and implement Omnichannel Ar­
SAP Asynchronous Order ticle Availability and Sourc­
Management) ing (OAA) or Omnichannel
Promotion Pricing (OPP)
within SAP Customer Activity
Repository.

SAP Commerce, integration SAP Commerce, integration Optional, depending on See the Administration Guide
package for SAP for Retail package for SAP for Retail whether or not you choose to delivered with the software
1811 or higher implement Omnichannel Ar­ package or from https://
ticle Availability and Sourc­ help.sap.com/viewer/p/IPR.
ing (OAA) or Omnichannel
Promotion Pricing (OPP)
within SAP Customer Activity
Repository.

SAP Analytics Cloud Content Innovation 12 Optional, depending on System Requirements and
whether or not you choose to Technical Prerequisites
implement Omnichannel Ar­
ticle Availability and Sourc­
ing (OAA) within SAP
Customer Activity
Repository.

You only need to run and

connect this application if
you want to use the set of
OAA analyses that has been
predefined in SAP Analytics
Cloud and that is part of the
standard delivery of SAP An­
alytics Cloud. If you are using
a different analytics tool, or if
you do not run analytics at
all, you do not need this ap­
plication.

SAP IQ SAP IQ 16.0, SP8 or higher Optional, depending on https://help.sap.com/

whether or not you choose to viewer/product/SAP_IQ/
use the Table Content Aging 16.1.latest/en-US?task=im­
report to move data from plement_task
SAP Customer Activity
Repository to SAP IQ.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
26 PUBLIC Upgrade the Prerequisites
 Prerequisite Minimum Requirement Mandatory/Optional Installation Information

SAP HANA Dynamic Tiering SAP HANA Dynamic Tiering Optional, depending on SAP HANA Dynamic Tiering:
is delivered with the SAP whether or not you choose to Installation and Update Guide
HANA Platform. See the use the Table Content Aging at https://help.sap.com/
Common Prerequisites sec­ report to move data from viewer/p/
tion above. SAP Customer Activity SAP_HANA_DYNAMIC_TIER­
Repository to extended stor­ ING
age using SAP HANA Dy­
namic Tiering.

SAP HANA extended applica­ SAP HANA XSA, version Optional, depending on SAP HANA Server Installation
tion services, advanced 1.0.88 or higher whether or not you choose to and Update Guide at https://
model (XSA) use Omnichannel Promo­ help.sap.com/viewer/p/
We recommend that you use
tion Pricing (OPP) within SAP_HANA_PLATFORM,
the highest version available.
SAP Customer Activity search for section Installing
Repository. XS Advanced Runtime

SAP Merchandise Planning

Prerequisites for SAP Merchandise Planning

Prerequisite Minimum Requirement Mandatory/Optional Installation Information

SAP Analysis SAP Analysis for Microsoft Mandatory Administrator Guide at

Office 2.8 SP02 https://help.sap.com/
viewer/p/SAP_BUSINES­
SOBJECTS_ANALYSIS_OF­
FICE

SAP Assortment Planning

Prerequisites for SAP Assortment Planning

Prerequisite Minimum Requirement Mandatory/Optional Installation Information

SAP Analysis SAP Analysis for Microsoft Mandatory Administrator Guide at

Office 2.8 SP02 https://help.sap.com/
viewer/p/SAP_BUSINES­
SOBJECTS_ANALYSIS_OF­
FICE

SAP Promotion Management

SAP Promotion Management requires only the common prerequisites.

SAP Allocation Management

SAP Allocation Management requires the common prerequisites.

In addition, the bar chart used to display the purchase order quantity by status requires the SAPUI5 library
version 1.71.14 or higher. In lower library versions, additional color is shown in the bar chart even if the
purchase order quantity is zero. This affects SAP Fiori apps (My Allocation Workload - Promotional Push, My

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Upgrade the Prerequisites PUBLIC 27
Order Workload - Promotional Buy, and My Allocation Plans for buy plans) in the business scenarios for
promotional push and promotional buy.

SAP Replenishment Planning

SAP Replenishment Planning requires the SAP XRP AFL.

 Note

SAP XRP AFL is a back-end software component of SAP Customer Activity Repository applications
bundle. You must install this component before using SAP Replenishment Planning for the first time but
you can do it after installing or upgrading the SAP CARAB back-end product version. This guide leads you
through the correct steps.

The minimum revision for SAP XRP AFL applies regardless of the business scenario you are planning to
implement. There is a minimum AFL revision for each SAP HANA database revision. Whichever AFL revision
you choose, it must be compatible with the SAP HANA database revision.

Compatible Minimum Revisions

Minimum Revision of SAP XRP AFL Compatible With This Revision of SAP HANA Database

AFL revision 50.1 (patch 1 of revision 50) SAP HANA database 2.0 revision 50

AFL revision 51.1 (patch 1 of revision 51) SAP HANA database 2.0 revision 51

AFL revision 52.1 (patch 1 of revision 52) SAP HANA database 2.0 revision 52

AFL revision 53.0 (patch 0 of revision 53) SAP HANA database 2.0 revision 53

AFL revision 53.0 (patch 0 of revision 53) SAP HANA database 2.0 revision 53

 Caution

No matter which AFL revision you choose, always install the highest patch available for download.

Be aware that patches for different revisions can occur at different points in time.

 Example

The AFL patch 51.1 was released later than the AFL patch 52.0.

If you decide to install a higher revision of SAP XRP AFL, it must again be compatible with the SAP HANA
database revision.

When you download an AFL revision from the SAP Support Portal, the compatible SAP HANA database
revision is always indicated.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
28 PUBLIC Upgrade the Prerequisites
4 Prepare the Upgrade

Before you start with the actual upgrade of SAP Customer Activity Repository applications bundle 5.0, you
must first perform several preparatory tasks.

1. Implement SAP Notes for the Upgrade [page 29]

This section lists SAP Notes (corrections) that you must read and — when appropriate — implement at
different points in the upgrade process. The section also points you to the release information notes
(RINs) for this release. There you can find the back-end and front-end corrections that have become
available since the software was released. The RINs complement the SAP Notes listed in this chapter.
2. Verify Correct Schema Mapping [page 48]
In SAP HANA studio, verify that the authoring schemas delivered by SAP are mapped to the correct
physical schemas of your customer landscape. First do an n:1 mapping (all authoring schemas of SAP
Customer Activity Repository applications bundle to the same SAPHANADB physical schema). Then do
a 1:1 mapping (the authoring schema of each source master data system to the corresponding physical
schema). If necessary, create any mappings that are missing. This procedure is mandatory for all the
applications.
3. Verify SAP HANA Users and Privileges [page 51]
SAP Customer Activity Repository applications bundle requires a multi-level system landscape: Level 1
is the SAP HANA database. Level 2 is the ABAP back-end server. Level 3 is the ABAP front-end server
with SAP Gateway and the SAP Fiori apps. Each level requires specific users with specific privileges. In
this procedure, you set up the authorizations for the SAP HANA database (level 1).
4. Configure AFL Usage [page 56]
Perform configuration tasks to enable the usage of application function libraries (such as the PAL and
the OFL) for the applications SAP Assortment Planning and SAP Allocation Management.
5. Configure the Zero Downtime Option [page 59]
Use the zero downtime option (ZDO) to continue regular operations during system upgrades and
maintenance procedures.
6. Migrate to New Default Table for Sales Pricing Data (/DMF/PRC) [page 64]
Make sure that /DMF/PRC is the default table for sales pricing data in your customer system. This
procedure is mostly relevant for upgrade scenarios but might also apply to some new installation
scenarios.

4.1 Implement SAP Notes for the Upgrade

This section lists SAP Notes (corrections) that you must read and — when appropriate — implement at
different points in the upgrade process. The section also points you to the release information notes (RINs)
for this release. There you can find the back-end and front-end corrections that have become available since
the software was released. The RINs complement the SAP Notes listed in this chapter.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Prepare the Upgrade PUBLIC 29
Prerequisites

● Make sure that you have the latest version of Note Assistant (transaction SNOTE) installed. This is required
so that notes can be implemented correctly. For more information, see the following:
○ Versions of Note Assistant: See https://support.sap.com/en/my-support/knowledge-base/note-
assistant.html#section_2043200365 .
○ Mandatory corrections for Note Assistant: See SAP Note 1668882 (Note Assistant: Important notes
for SAP_BASIS 730,731,740,750,751,752,753,754).
● Make sure that you have the up-to-date version of each SAP Note, which you can always find on the SAP
Support Portal at http://support.sap.com/notes .

Release Information Notes (RINs) with Latest Corrections for all

Applications

After the publication of this guide, additional corrections might become available. You can find these
additional corrections in the RINs for this release:

● For the latest back-end corrections, see SAP Note 2924956 .

● For the latest front-end corrections, see SAP Note 2924957 .

The RINs are regularly updated if new corrections become available.

 Tip

If a note is particularly relevant for your scenario and you want to be informed of updates, you can easily set
up email notifications. See SAP Note 2478289 (How to get notifications for SAP Notes or KBAs).

 Caution

Always consult the SAP Notes for SAP Customer Activity Repository, regardless of your scenario. Notes
listed here are often common corrections, applicable to all applications.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
30 PUBLIC Prepare the Upgrade
SAP Notes for SAP Customer Activity Repository

SAP Notes for SAP Customer Activity Repository

Implement Area SAP Note Description

After the upgrade Front-end 2998753 Mandatory if you are using SAP Fiori front-end server 2020 for
SAP S/4HANA.
List of SAP
Notes required The note collects all the required SAP Notes for configuring and
to use Multi­ querying Multichannel Sales Analytics apps in SAP Customer Ac­
channel Sales tivity Repository when using SAP Fiori front-end server 2020 for
Analytics apps SAP S/4HANA.
in SAP Cus­
tomer Activity
Repository
with SAP Fiori
front-end
server 2020
for SAP S/
4HANA

After the upgrade Back-end Mandatory correction if you are using omnichannel promotion
2961153
pricing (OPP).
Parallel proc­
essing became
mandatory
though the flag
Parallel proc­
essing is not
active in
DRFOUT

After the upgrade Back-end Mandatory correction if you are using omnichannel promotion
2986824
pricing (OPP).
Performance
Optimization
price lookup
central PPS

After the upgrade Back-end Mandatory correction if you are using omnichannel promotion
2967391
pricing (OPP).
OPP: DRFOUT
dump with out­
bound imple­
mentation
ROP_PRO_ST

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Prepare the Upgrade PUBLIC 31
Implement Area SAP Note Description

Prior to the upgrade Back-end 2548843 Only relevant if your source master data system is ABAP FND
1709 ON HANA (foundation 1709 on SAP NetWeaver AS for ABAP
DD: data ele­
7.52, version for SAP HANA):
ment changes
from DEC to If so, this is a mandatory correction for all the applications of SAP
CURR, error for Customer Activity Repository applications bundle.
dependent
views

During the upgrade Back-end 2330184 If you get error messages during the upgrade, consult this note for
possible solutions.
Appearance of
Non-Exis­ The note provides troubleshooting information for errors that
tence/Activa­ might occur during ...RSDB02CK... phases in transaction SUM.
tion Errors of
Example error messages:
Views/DDL
Sources within ● 2EETG002 View "/AMR/C_P_A_L_C" does not exist in the da­
installation of tabase
CARAB 1.0 ● 2EETG002 View "/AMR/V_APITSLOC" does not exist in the
FP03 and database
CARAB 2.0

After the upgrade Back-end 2623953 Mandatory if you are using omnichannel article availability and
sourcing (OAA) and using the functionality in sales channel mode.
SADL GW: Ex­
Not required for functions other than OAA. Not required if you are
posure for An­
using OAA in OAA profile mode.
notations on
Entity Con­
tainer with
namespace

After the upgrade Back-end 2625428 Mandatory if you are using omnichannel article availability and
sourcing (OAA) and using the functionality in sales channel mode.
SADL GW: Ex­
Not required for functions other than OAA. Not required if you are
posure for An­
using OAA in OAA profile mode.
notations on
Entity Con­
tainer with
namespace

After the upgrade SAP S/4HANA 2835297 Only required if your source master data system is SAP S/4HANA
1909 back-end 1909.
Missing OAA
ATP Change Mandatory if you are using omnichannel article availability and
Indicator en­ sourcing (OAA), for both sales channel mode and OAA profile
tries for S/ mode. Not required for functions other than OAA and source mas­
4HANA 1909 ter data systems other than SAP S/4HANA 1909.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
32 PUBLIC Prepare the Upgrade
 Implement Area SAP Note Description

After the upgrade Back-end Troubleshooting information for errors that might occur if the ma­
2576497
terial number is longer than 18 characters.
SQL Error
Code 274: in­
serted value
too large for
column

After the upgrade Back-end 2857334 Mandatory correction if your source master data system is SAP
S/4HANA 1909. In that case, the note is required for all the appli­
Unsupported
cations of SAP Customer Activity Repository applications bundle.
data type DEC­
FLOAT34 /
D34N when
replicating
from an SAP
S/4HANA
1909 on prem­
ise system

After the upgrade Back-end 2991316 Mandatory note containing several corrections for the Analyze
Forecast app
"Analyze Fore­
cast" app: fix
for overlapping
forecast cor­
rections, per­
formance im­
provements
(SAP CARAB
5.0)

After the upgrade Back-end 2994197 Mandatory performance correction for the Analyze Forecast app

"Analyze Fore­
cast" app: Per­
formance im­
provements for
time series
data (SAP
CARAB 5.0)

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Prepare the Upgrade PUBLIC 33
Implement Area SAP Note Description

After the upgrade Front-end 3000380 Mandatory correction for the Adjust Forecast app

"Adjust Fore­
cast" app: App
freezes on
closing the
chart personal­
ization dialog
(SAP CARAB
5.0)

After the upgrade Front-end 2986835 Mandatory note containing several corrections for the Manage
Demand Influencing Factors app
"Manage De­
mand Influenc-
ing Factors"
app: Input
fields not edit­
able for new
DIF assign­
ment (SAP
CARAB 5.0)

After the upgrade Front-end 3000602 Mandatory correction for the Manage Demand Influencing Factors
app
"Manage De­
mand Influenc-
ing Factors"
app: App
freezes on cre­
ating new DIF
assignment
(SAP CARAB
5.0)

After the upgrade Back-end 2990476 Mandatory note for two related services of Demand Data Founda­
tion (DDF):
RFC Authoriza­
tions for Simi­ ● similar products search (function module /DMF/PROD­
lar Products UCT_SIMILARITY_FM)
Search and ● price binning (function module /DMF/GENER­
Price Binning ATE_PRICE_BINS)

After the upgrade Back-end 2996880 Highly recommended enhancement for Unified Demand Forecast
(UDF). The note extends the existing service Calculate
Calculate hier­
Hierarchical Priors with a new option. With this option, you can run
archical priors
the service in delta mode, where the hierarchical priors (HPRs)
(delta run)
are only calculated for newly listed product locations.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
34 PUBLIC Prepare the Upgrade
 Implement Area SAP Note Description

After the upgrade Back-end 2948474 Mandatory note for Unified Demand Forecast (UDF). This note
prevents a potential key violation which can occur within the serv­
"Double en­
ice Calculate Hierarchical Priors.
tries (key viola­
tion) in /DMF/
UMD_PRI"

After the upgrade Back-end 2988891 Mandatory note for Demand Data Foundation (DDF). This note
prevents multiple entries from being created for the same factory
Timestream
calendar I.D. when importing locations.
data may be­
come corrupt
after location
import

SAP Notes for SAP Merchandise Planning

 Note

Always consult the table for SAP Customer Activity Repository, regardless of your scenario. Notes listed
there are often common corrections, applicable to all consuming applications.

SAP Notes for SAP Merchandise Planning

Implement Area SAP Note Description

After the upgrade Back-end 1919631 Embedded BW-IP features explicitly needs the NW BPC10.1 li­
cense along with the PAK.
Activating the
BPC imbedded
is necessary

After the upgrade Back-end 2906856 This note provides troubleshooting information for errors in sys­
System error in tem CL_RSR_RRI2_LRECH and form AGGRE­
program GATE_NO_UNITS-01-.
CL_RSR_RRI2_
LRECH and
form AGGRE­
GATE_NO_UNI
TS-01-

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Prepare the Upgrade PUBLIC 35
Implement Area SAP Note Description

After the upgrade Back-end 2913238 If you receive an error when variables are submitted, consult this
Error transfer­ note for possible solutions.
ring single key
value from var­
iable to SID

After the upgrade Back-end 2925634 Mandatory note if filter values are not taken into account for com­
Input help: Ex­ pound characteristics.
clusion of
characteristic
values is not
taken into ac­
count

After the upgrade Back-end 2927392 Mandatory correction if a BW query including a current member
Current Mem­ variable, shows unexpected values.
ber and selec­
tion for Partial
Time Charac­
teristic

After the upgrade Back-end 2932787 Mandatory note includes correction to runtime improvements.
Minor perform­
ance improve­
ments
(BICS,BOLAP)

After the upgrade Back-end 2935854 Mandatory correction if you receive query message Unique value
Current Mem­ for fiscal variant needed in global filter" (BRAIN 073) although
ber: Unique there exists a filter for the fiscal variant.
value for fiscal
variant needed
in global filter

After the upgrade Back-end 2938084 Mandatory correction if a figure or structure element isn’t calcu­
Current mem­ lated correctly.
ber and char­
acteristics ref­
erencing to
0FISC*

After the upgrade Back-end 2950567 Mandatory correction if a planning sequence uses a mandatory
BRAIN 629 variable without default value or error Specify a value for variable
when Save a (BRAIN 629) is received.
Planning Se­
quence

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
36 PUBLIC Prepare the Upgrade
 Implement Area SAP Note Description

After the upgrade Back-end 2925895 This note includes correction related to the value help returning
Current mem­ too many values or wrong (not shifted) values.
ber: value help
for characteris­
tic

After the upgrade Back-end 2926663 Mandatory correction when query aborts with error message
Current mem­ BRAIN 299.
ber variable
with operator
and reference
to fiscal in­
foObject

After the upgrade Back-end 2929997 Mandatory note that provides corrections for error messages:
Current Mem­ ● System error in program CL_RS_TIME_SERVICE and form
ber: fiscal year CALCULATE_REL_FUNC_GEN-1-
variant not set ● System error in program LCL_CM_TIME_BUFFER and form
in fix filter DERIVE_TIMES_AND_APPEND-1-

After the upgrade Back-end 2935804 Mandatory correction if you have implemented a correction from
Current Mem­ note 2927392 but query result still shows unexpected values.
ber and selec­
tion for Partial
Time Charac­
teristic (2)

After the upgrade Back-end 2938717 Mandatory correction if a value for a key figure using a current
Key figure us­ member variable is unexpectedly empty (NULL).
ing Current
Member varia­
ble empty

After the upgrade Back-end 2941202 Mandatory correction if a global filter is deleted during query run­
Not required time.
part provider
access for cur­
rent member
query

After the upgrade Back-end 2946337 Mandatory correction if a query shows incorrect data.
Wrong data in
current mem­
ber query

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Prepare the Upgrade PUBLIC 37
SAP Notes for SAP Assortment Planning

 Note

Always consult the table for SAP Customer Activity Repository, regardless of your scenario. Notes listed
there are often common corrections, applicable to all consuming applications.

SAP Notes for SAP Assortment Planning

Implement Area SAP Note Description

After the upgrade Back-End 2983914 This mandatory note includes corrections to improve perform­
ance when copying assortment lists.
APR 5.0 - Opti­
mize copy as­
sortment lIst

After the upgrade Back-End 2987562 This mandatory correction improves performance in the Build As­
sortment screen.
APR 5.0 - Opti­
mize Option
Defining Attrib­
utes retrieval in
Build Assort­
ment

After the upgrade Back-end 2906856 This note provides troubleshooting information for errors in sys­
System error in tem CL_RSR_RRI2_LRECH and form AGGRE­
program GATE_NO_UNITS-01-.
CL_RSR_RRI2_
LRECH and
form AGGRE­
GATE_NO_UNI
TS-01-

After the upgrade Back-end 2913238 If you receive an error when variables are submitted, consult this
Error transfer­ note for possible solutions.
ring single key
value from var­
iable to SID

After the upgrade Back-end 2925895 This note includes correction related to the value help returning
Current mem­ too many values or wrong (not shifted) values.
ber: value help
for characteris­
tic

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
38 PUBLIC Prepare the Upgrade
 Implement Area SAP Note Description

After the upgrade Back-end 2926663 Mandatory correction when query aborts with error message
Current mem­ BRAIN 299.
ber variable
with operator
and reference
to fiscal in­
foObject

After the upgrade Back-end 2929997 Mandatory note that provides corrections for error messages:
Current Mem­ ● System error in program CL_RS_TIME_SERVICE and form
ber: fiscal year CALCULATE_REL_FUNC_GEN-1-
variant not set ● System error in program LCL_CM_TIME_BUFFER and form
in fix filter DERIVE_TIMES_AND_APPEND-1-

After the upgrade Back-end 2935804 Mandatory correction if you have implemented a correction from
Current Mem­ note 2927392 but query result still shows unexpected values.
ber and selec­
tion for Partial
Time Charac­
teristic (2)

After the upgrade Back-end 2938084 Mandatory correction if a figure or structure element isn’t calcu­
Current mem­ lated correctly.
ber and char­
acteristics ref­
erencing to
0FISC*

After the upgrade Back-end 2938717 Mandatory correction if a value for a key figure using a current
Key figure us­ member variable is unexpectedly empty (NULL).
ing Current
Member varia­
ble empty

After the upgrade Back-end 2941202 Mandatory correction if a global filter is deleted during query run­
Not required time.
part provider
access for cur­
rent member
query

After the upgrade Back-end 2946337 Mandatory correction if a query shows incorrect data.
Wrong data in
current mem­
ber query

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Prepare the Upgrade PUBLIC 39
Implement Area SAP Note Description

After the upgrade Back-end 2927392 Mandatory correction if a BW query including a current member
Current Mem­ variable, shows unexpected values.
ber and selec­
tion for Partial
Time Charac­
teristic

After the upgrade Back-end 2935854 Mandatory correction if you receive query message Unique value
Current Mem­ for fiscal variant needed in global filter" (BRAIN 073) although
ber: Unique there exists a filter for the fiscal variant.
value for fiscal
variant needed
in global filter

After the upgrade Back-end 2950567 Mandatory correction if a planning sequence uses a mandatory
BRAIN 629 variable without default value or error Specify a value for variable
when Save a (BRAIN 629)” is received.
Planning Se­
quence

After the upgrade Back-end 2925634 Mandatory note if filter values are not taken into account for com­
Input help: Ex­ pound characteristics.
clusion of
characteristic
values is not
taken into ac­
count

After the upgrade Back-end 2932787 Mandatory note includes correction to runtime improvements.
Minor perform­
ance improve­
ments
(BICS,BOLAP)

After the upgrade Back-end 2983526 This mandatory note improves performance in the Select
APR 5.0 - As­ Products for Planning Area screen of the Manage Assortment Lists
sortment List app: If there is nothing related to option-defining attribute values
Select Prod­ displayed or filtered, the values assigned to products are not re­
ucts for Plan­ trieved.
ning Area Op­
tion Defining
Attributes re­
trieval

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
40 PUBLIC Prepare the Upgrade
 Implement Area SAP Note Description

After the upgrade Back-end 2978543 This note improves performance in the Manage Assortment Lists
APR 5.0 - As­ app. It is mandatory after an upgrade to SAP HANA 2.0 database
sortment List revision 46 or higher.
Performance
improvement

After the upgrade Front-end This mandatory note fixes bugs and improves layouts.
2995920

APR5.0 Re­
useV2 – Bug
Fixes

After the upgrade Back-end This correction is mandatory if SAP Merchandise Planning is not
3001133
installed..
APR 5.0 - Op­
tion Planning
Capacity de­
fault extractor

SAP Notes for SAP Promotion Management

 Note

Always consult the table for SAP Customer Activity Repository, regardless of your scenario. Notes listed
there are often common corrections, applicable to all consuming applications.

SAP Notes for SAP Promotion Management

Implement Area SAP Note Description

After the upgrade Back-End 2844653 Transfer offer from PMR to ERP including product promotion cost
price currency
PMR Offer
Transfer - in­
clude product
promo cost
price currency

After the upgrade Back-End 2847080 Correction for BAPI_PROMO_CREATE to accept purchase price
currency at item level
BAPI_PROMO_
CREATE not
accepting
product pur­
chase price
currency

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Prepare the Upgrade PUBLIC 41
Implement Area SAP Note Description

After the upgrade Back-End 2952618 Mandatory: SAP NWVC ABAP Runtime Patch 73

After the upgrade Front-End 2984146 This note contains corrections to error visibility while editing the
Manage Promotional Offers Attributes table.
PMROFFERS -
Automatic
Maint Upload

After the upgrade Front-End 2985671 This note contains corrections to error visibility while editing the
Manage Product Groups Attributes table.
Manage Prod­
uct Groups -
Attributes Ta­
ble Missing an
Error State

SAP Notes for SAP Allocation Management

 Note

Always consult the SAP Notes for SAP Customer Activity Repository, regardless of your scenario. Notes
listed there are common corrections, applicable to all consuming applications.

 Note

Some SAP Notes must be implemented before activation of SAP HANA content. If this is the case, this is
indicated in the description of the note. Otherwise, the note must be implemented after activation of SAP
HANA content.

SAP Notes for SAP Allocation Management

Implement Area SAP Note Description

After the upgrade Back-end 2995707 This note provides a missing SLT table name.

AMR 5.0 - Pre­ Please ensure that you implement this SAP Note before you
wave Note be­ activate SAP HANA content for SAP Allocation Management.
fore HANA
Content Acti­
vation

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
42 PUBLIC Prepare the Upgrade
 Implement Area SAP Note Description

After the upgrade Back-end 2986172 This note comprises all back-end corrections of SAP Allocation
Management up to the RTC date of SAP Customer Activity
SAP Allocation
Repository applications bundle 5.0.
Management
5.0 - Collective
Note with All
Corrections
until RTC

After the upgrade Front-end 2986856 This note comprises all front-end corrections of SAP Allocation
Management up to the RTC date of SAP Customer Activity
SAP Allocation
Repository applications bundle 5.0.
Management
5.0 - Collective
Note with All
Corrections
until RTC for
Front End

After the upgrade Back-end 2982741 Starting with SAP Allocation Management 5.0, a BAdI implemen­
tation is required for retrieving real-time inventory. This SAP Note
SAP Allocation
provides steps for implementing the standard BAdI logic.
Management -
BAdI Imple­
mentation for
Real-Time In­
ventory View

After the upgrade Back-end 2994341 Corrects an issue for the loading of SAP Allocation Management
apps if the SAP Customer Activity Repository system is running
AM 5.0 - NW
on SAP NetWeaver AS for ABAP 7.55.
ABAP 7.55 Cor­
rections

After the upgrade Back-end 2951092 Provides an RFC function module for handling allocation tables in
the business scenarios for promotional push and promotional
RFC function
buy.
module to cre­
ate allocation
table for SAP
Allocation
Management
in source sys­
tem (Allocation
Management
5.0)

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Prepare the Upgrade PUBLIC 43
Implement Area SAP Note Description

After the upgrade Back-end 2777415 This note can be implemented if activation fails for CDS views for
SAP Allocation Management.
SAP Allocation
Management:
Activating /AM
R/* views ends
in Error

After the upgrade Back-end 2631613 Follow the instructions to create a valid business scenario ID.

SAP Allocation
Management -
Customizing -
Define Busi­
ness Scenarios

After the upgrade SAP S/4HANA 2522603 This note can be implemented for calling ATP (available-to-prom­
Retail for mer­ ise) for multiple products in the target SAP S/4HANA or ECC sys­
Wrapper RFC
chandise man­ tem. This note is intended to increase the performance of the ATP
for ATP via
agement call to the target system
Controller

After the upgrade Back-end 2474287 This note resolves inconsistent maintenance of units of measure
between SAP ECC and SAP Customer Activity Repository.
Handling of
units of meas­
ure inside SAP
Allocation
Management

After the upgrade Back-end 2441184 The manual instructions in the note must be implemented for the
successful activation of SAP Allocation Management applications.
Static ABAP
generation er­ This note is mandatory.
ror of
classes /AMR/
CL... when in­
stalling CARAB
1.0 FP03,
CARAB 2.0,
CARAB 4.0,
CARAB 5.0

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
44 PUBLIC Prepare the Upgrade
SAP Notes for SAP Replenishment Planning

 Note

Always consult the table for SAP Customer Activity Repository, regardless of your scenario. Notes listed
there are often common corrections, applicable to all consuming applications.

SAP Notes for SAP Replenishment Planning

Implement Area SAP Note Description

After the upgrade Back-end 2991913 This note can be implemented to cleanup location dumps when
trying to find dependent order plan items in the Where Used
WUF Purge
Framework for Purging.
Agent dumps
for location in
non-cascade
mode

After the upgrade Back-end 2991638 This note can be implemented to activate a check on replenish­
ment types that was removed as MRP type.
Consistency
check in re­
plenishment
type main­
tennce

After the upgrade Back-end 2987852 Mandatory note that corrects errors in the DDF tools reports that
occurred during the export of output lists into a Word or Excel
DDF Tools Re­
document.
ports: ALV ex­
port in Excel
and Word not
working

After the upgrade Back-end 2985918 Mandatory note that corrects errors in the SAP Replenishment
tools reports that occurred during the export of output lists into a
XRP Tools Re­
Word or Excel document.
ports: ALV ex­
port in Excel
and Word not
working

After the upgrade Back-end 2985737 Mandatory note that corrects the field help of the data element
Last Change Time in the Purging of Order Plan Items report.
Wrong Data El­
ement for Last
Change Time
in Order Plan
Purge Report

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Prepare the Upgrade PUBLIC 45
Implement Area SAP Note Description

After the upgrade Back-end 2980033 This note can be implemented to avoid duplicate entries for order
plan outbound processing in the order plan item change history.
Separate con­
trol option for
change history
of "Transfer in
Progress" up­
date

After the upgrade Back-end 2996488 Entries delivered by SAP for Change Reasons for Order Plan Items
(/DMF/V_OPI_R4C) and Order Plan Change History Operation
Content of ta­
(/DMF/V_OP_CHOPR) are only available in language english.
bles /DMF/
C_OPI_R4CT The changes will automatically be available with support pack
and /DMF/ SP01.
C_OP_CHOPR
T not trans­
lated

After the upgrade Back-end 2982552 Mandatory note that corrects the error that is displayed when
Real-Time Inventory Status is selected as a validation point for Ge­
Real-Time In­
neric or Specific assignments.
ventory Status
not considered
as an assign­
ment field for
the validation
of Generic or
Specific as­
signments in
Manage Con­
figuration As­
signment Fiori
Application

After the upgrade Back-end 2985025 This note can be implemented to avoid replenishment engine ter­
mination during execution due to missing client handling annota­
Replenishment
tion in configuration profiles core data services.
Engine Termi­
nates Due to This note is applicable for Manage Cost Profiles, Manage
Missing Client Constraint Profiles, Manage Shelf Cost profiles, Manage
Handling An­ Procurement Schedules, Manage Configuration Assignments.
notation in
Configuration
Profile Core
Data Service

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
46 PUBLIC Prepare the Upgrade
 Implement Area SAP Note Description

After the upgrade Back-end 2994441 Mandatory note containing corrections for issues related to DDIC
Enhancements in CARAB 5.0.
Manage Alerts
Fiori Applica­
tion related
DDIC Enhance­
ments for
CARAB 5.0 re­
lease

After the upgrade Back-end 2986095 Mandatory note containing certain corrections for the Generate
Alerts report.
Corrections to
Replenishment
Alert Genera­
tion
Report /DMF/
GENER­
ATE_ALERTS

After the upgrade Back-end 2994442 Mandatory note containing corrections and performance im­
provements for the Manage Alerts app.
Corrections
and Perform­
ance Improve­
ments in Man­
age Alerts Fiori
Application

After the upgrade Back-end 2982245 Mandatory note for correcting errors that occur while reading the
demand forecasts.
Replenishment
Calculation:
Weekday proc­
essing leads to
insufficient de­
mand records

After the upgrade Back-end 2986859 Mandatory note containing several corrections for the Review
Order Plan Items app (back-end)
Corrections for
Review Order
Plan Items app
(Backend)

After the upgrade Back-end 2997009 Mandatory note that corrects a few issues related to the Purge
Alerts report (back-end) and also improves its performance.
Corrections for
Purge Alerts
report

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Prepare the Upgrade PUBLIC 47
Implement Area SAP Note Description

After the upgrade Back-end 2996815 Mandatory note that contains a fix for the global search function­
ality in the Manage Configuration Assignments app (back-end).
Fix for global
search func­
tionality in
Manage Con­
figuration As­
signments app

After the upgrade Front-end 2997222 Mandatory note containing several corrections for the errors dis­
played while trying to navigate to the Review Order Plan Items or
Corrections in
Adjust Forecast app from the Manage Alerts app.
UI for Manage
Alerts Fiori Ap­
plication

After the upgrade Front-end 2982687 Mandatory note containing several corrections for the Review
Order Plan Items app (front-end)
Corrections in
Review Order
Plan Items app

Parent topic: Prepare the Upgrade [page 29]

Next: Verify Correct Schema Mapping [page 48]

4.2 Verify Correct Schema Mapping

In SAP HANA studio, verify that the authoring schemas delivered by SAP are mapped to the correct physical
schemas of your customer landscape. First do an n:1 mapping (all authoring schemas of SAP Customer
Activity Repository applications bundle to the same SAPHANADB physical schema). Then do a 1:1 mapping (the
authoring schema of each source master data system to the corresponding physical schema). If necessary,
create any mappings that are missing. This procedure is mandatory for all the applications.

Context

Why Schema Mapping?

Schema mapping is required if the source system and the target system have different physical schemas.

● Schema mapping allows you to transport SAP HANA objects from the source system to the target system.
For example, from the SAP delivery system to your test system, and from your test system to your
production system. After schema mapping, you can access and deploy the transported objects.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
48 PUBLIC Prepare the Upgrade
 ● Schema mapping is a prerequisite to activate the SAP HANA content.
● Schema mapping is a prerequisite to replicate the required SLT tables from the source master data system
to the target system (your SAP Customer Activity Repository back-end system).

What are Authoring Schemas and Physical Schemas?

The SAP HANA content of SAP Customer Activity Repository applications bundle is delivered with several
authoring schemas (for different scenarios and different source master data systems).

● The authoring schema is the logical database schema with which the SAP HANA objects were originally
created in the SAP source system. The authoring schema is listed in each object's properties in SAP HANA
studio. Different objects can have different authoring schemas.
● The physical schema is the logical database schema of your customer back-end system (referred to as
SAPHANADB, sometimes also as SAPHANADB).

In the procedure below, you must map the authoring schemas to the physical schemas of your customer back-
end system.

Prerequisites

● You have set up the authorizations as described in Verify SAP HANA Users and Privileges [page 51].
● You know what the name of the SAPHANADB database schema is in your customer back-end system. This is
the physical schema name that you will need to enter in the mapping procedure below.

 Note

In this guide, SAPHANADB is used as a variable. Replace it with the name of the database user or
database schema in your ABAP back-end system. You might also come across documentation or user
interfaces that use SAPHANADB. Both variables mean the same.

For more information and an example, see the Important Variables in section Naming Conventions
[page 6].

For more information about database users and schemas, see SAP Note 2535951 (FAQ: SAP HANA
Users and Schemas).

 Tip

If you don't know the SAPHANADB of your system, there are two easy ways to find it:

○ Log on to your ABAP back-end system using SAP Logon. Choose System Status . In the
section titled Database data, see the name for Schema.
○ In SAP HANA studio, the schema name is listed under Catalog.

Authoring Schemas

The following tables show the two sets of authoring schemas that are relevant for this release. In the procedure
below, you map these authoring schemas to the physical schemas of your customer system landscape.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Prepare the Upgrade PUBLIC 49
Table 1: Authoring Schemas for SAP Customer Activity Repository applications bundle

Schema Name Required For

SAP_CAR SAP HANA objects for SAP Customer Activity Repository

SAP_DDF SAP HANA objects for Demand Data Foundation and Unified
Demand Forecast

SAPOSA SAP HANA objects for On-Shelf Availability

SAP_RAP SAP HANA objects for consuming applications (for example,

SAP Assortment Planning, SAP Merchandise Planning, or
SAP Promotion Management)

SAP_RTLRAP_AMR SAP HANA objects for SAP Allocation Management

Table 2: Authoring Schemas for Source Master Data Systems

Schema Name Required For

SAP_CRM SAP Customer Relationship Management

SAP_CUAN SAP Marketing Cloud

SAP_ECC SAP ERP (SAP Retail)

SAP_S4H SAP S/4HANA Retail

Procedure

 Note

If you encounter issues during the steps below, see the SAP HANA Modeling Guide (SAP HANA Studio) at
https://help.sap.com/viewer/p/SAP_HANA_PLATFORM. Select your version at the top. Search for section
Map Authoring Schema to Physical Schema and also consult the subsections.

1. In SAP HANA studio, log on to your back-end system.

2. Choose Window Perspective Open Perspective SAP HANA Modeler .
3. Choose Help Quick View Schema Mapping .
4. Select the system and choose Add.
5. Enter the authoring schemas and physical schemas that you want to map:

 Caution

Make sure that you enter the names correctly.

Make sure there are no leading or trailing spaces before or after a name. Space characters cause issues
with schema mapping.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
50 PUBLIC Prepare the Upgrade
 1. Map all authoring schemas from Table 1 to the same physical schema (SAPHANADB) of your customer
system. This is the n:1 mapping step. If necessary, add new mappings.
2. Map each authoring schema from Table 2 to the physical schema for the respective source master
data system in your customer system. This is the 1:1 mapping step. If necessary, add new mappings.
6. Choose OK.

 Note

If you are using an SAP HANA system with multiple isolated tenant databases to perform cross-
database access between tenants, you must provide the authoring database name and the physical
database name in the schema mapping definition.

You maintain schema mapping definitions in the SYS_BI.M_DATABASE_SCHEMA_MAPPING table.

Parent topic: Prepare the Upgrade [page 29]

Previous: Implement SAP Notes for the Upgrade [page 29]

Next: Verify SAP HANA Users and Privileges [page 51]

4.3 Verify SAP HANA Users and Privileges

SAP Customer Activity Repository applications bundle requires a multi-level system landscape: Level 1 is the
SAP HANA database. Level 2 is the ABAP back-end server. Level 3 is the ABAP front-end server with SAP
Gateway and the SAP Fiori apps. Each level requires specific users with specific privileges. In this procedure,
you set up the authorizations for the SAP HANA database (level 1).

Overview

In the following diagram, you can see an overview of the three levels and the required authorizations:

 Note

Depending on your deployment scenario, the concrete implementation in your customer system landscape
can vary. For example, if you have an embedded deployment scenario, you are using the ABAP back-end
server also as your front-end system, and have no separate ABAP front-end server.

For more information, see Deployment Options [page 15]. For an overview diagram, see System Landscape
[page 13].

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Prepare the Upgrade PUBLIC 51
 Authorization Levels for SAP Customer Activity Repository applications bundle

 Caution

Level 1: You must always set up the SAP HANA users and privileges first, that is, before upgrading SAP
Customer Activity Repository applications bundle on the ABAP back-end server and the ABAP front-end
server. This procedure is described below.

 Note

Level 2 and Level 3: You can only set up these authorizations after the actual upgrade. In most cases, you
only need to do this if you are doing a new installation. If you are doing an upgrade from a lower support
package stack or feature package stack, the authorizations should already be available.

● Level 2: This procedure is described in the Common Installation Guide in section Verify Back-End Users
and Roles.
● Level 3: The required authorizations depend on the consuming application and SAP Fiori apps that you
wish to use. For example, the procedures are described in the following sections in the Common
Installation Guide:
SAP Customer Activity Repository: Set Up SAP Fiori Apps for SAP Customer Activity Repository; SAP
Assortment Planning: Assign Roles, Catalogs, and Groups in SAP Fiori Launchpad; SAP Allocation
Management: Assign Roles, Catalogs, and Groups in SAP Fiori Launchpad; SAP Replenishment
Planning: Set Up SAP Fiori Apps for SAP Replenishment Planning

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
52 PUBLIC Prepare the Upgrade
Prerequisites

● You are authorized to maintain users and assign privileges in the SAP HANA system.

 Note

For more information or if you encounter any issues during the procedure below, see the SAP HANA
Administration Guide for SAP HANA Platform at https://help.sap.com/viewer/p/
SAP_HANA_PLATFORM. Select your version at the top. Search for section Managing SAP HANA Users
and section User Authorization.

● You know what the source master data system is (for example, SAP S/4HANA or SAP Retail).
● You know what the name of the SAPHANADB ABAP database schema is in your customer system
landscape.

 Note

In this guide, SAPHANADB is used as a variable. Replace it with the name of the database user or
database schema in your ABAP back-end system. You might also come across documentation or user
interfaces that use SAPHANADB. Both variables mean the same.

For more information and an example, see the Important Variables in section Naming Conventions
[page 6].

For more information about database users and schemas, see SAP Note 2535951 (FAQ: SAP HANA
Users and Schemas).

 Tip

If you don't know the SAPHANADB of your system, there are two easy ways to find it:

○ Log on to your ABAP back-end system using SAP Logon. Choose System Status . In the
section titled Database data, see the name for Schema.
○ In SAP HANA studio, the schema name is listed under Catalog.

Procedure

To set up the authorizations, follow these steps:

1. Open SAP HANA studio and log on to your back-end system.

2. Choose Window Perspective Open Perspective SAP HANA Administration Console .
3. In the Systems view, choose Security Users to display the list of database users.
4. Verify that the following users exist and that they have the required privileges and roles. If necessary,
assign any missing privileges and roles.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Prepare the Upgrade PUBLIC 53
  Caution

Users marked * must be identical on all three levels. Make sure these users have the same name on
the SAP HANA database level, on the ABAP back-end server, and on the ABAP front-end server.

Users Privileges / Roles

SAPHANADB ○ Privilege REPO.IMPORT

○ Privilege ROLE ADMIN
This is the generic database user
○ Privilege STRUCTUREDPRIVILEGE ADMIN
that you need for the connection
from the ABAP back-end server to ○ Privilege EXECUTE on procedure TRUNCATE_PROCEDURE_OBJECTS
the SAP HANA database. ○ Privilege EXECUTE on procedure GET_PROCEDURE_OBJECTS
○ Privilege SELECT on schema SAP_ECC (required if your source master
data system is SAP Retail)
○ Privilege SELECT on schema SAP_S4H (required if your source master
data system is SAP S/4HANA)
○ Role CONTENT_ADMIN
○ Role AFLPM_CREATOR_ERASER_EXECUTE
This role enables the user to execute functions of the PAL library (required
by SAP Assortment Planning, for example).
For more information, see Enable Usage of PAL Functions [page 57] and
SAP Note 2046767 .
○ Role AFL__SYS_AFL_OFL_AREA_EXECUTE
○ Additionally, grant the following privileges, with option Grantable to others,
on these schemas:
On schema _SYS_BIC:
○ Privilege CREATE ANY
○ Privilege ALTER
On schema <your SAP S/4HANA or SAP Retail schema name>:
○ Privilege SELECT

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
54 PUBLIC Prepare the Upgrade
 Users Privileges / Roles

_SYS_REPO ○ Privilege SELECT, with option Grantable to others, on the following physical
database schemas:
○ Physical database schema of your back-end system (referred to as
SAPHANADB in this guide)
○ Physical database schema that contains the SAP S/4HANA or SAP
Retail tables
○ Physical database schema that contains the SAP CRM tables
○ Physical database schema that contains the SAP Marketing Cloud ta­
bles
○ Authoring schema SAP_S4H (required if your source master data sys­
tem is SAP S/4HANA)
○ Authoring schema SAP_ECC (required if your source master data sys­
tem is SAP Retail)

 Tip
You can use the following example SQL statement to grant the privi­
lege:

GRANT SELECT ON SCHEMA <Your schema name> TO

_SYS_REPO WITH GRANT OPTION;

○ Role UDF_DEPLOY_SYS_REPO.
For information about the privileges automatically assigned with this role,
see the Set Up Authorizations for Unified Demand Forecast (UDF) section
in the Common Installation Guide.
○ For SAP Allocation Management, grant the following additional privileges:
○ Privilege CREATE SCHEMA
This privilege enables the user to create a schema in the SAP HANA
database.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Prepare the Upgrade PUBLIC 55
 Users Privileges / Roles

<Your User Name> * ○ Privilege SELECT on schema _SYS_BI

○ Privilege SELECT on schema SAPHANADB
○ Privilege EXECUTE on procedure REPOSITORY_REST
○ Privilege SELECT on schema SAP_S4H (if your source master data system
is SAP S/4HANA)
○ Privilege SELECT on schema SAP_ECC (if your source master data system
is SAP Retail)
○ Set the Session Client of this database user to the correct back-end sys­
tem client.
This step is required to enable the SAP Assortment Planning planning
framework, where SAP Analysis for Microsoft Office workbooks obtain
data from SAP HANA views.

 Note
If you encounter issues with the steps below, see the Assign Default
Client section in the SAP HANA Modeling Guide at https://
help.sap.com/viewer/p/SAP_HANA_PLATFORM.

1. Still under Security Users , select the user.

2. On the User tab, set the Session Client to the client number created in
the Set Up SAP Client section in the Common Installation Guide.

5. Save your changes.

Result

You have successfully set up the users and privileges in the SAP HANA back-end system. Continue with the
next section.

Parent topic: Prepare the Upgrade [page 29]

Previous: Verify Correct Schema Mapping [page 48]

Next: Configure AFL Usage [page 56]

4.4 Configure AFL Usage

Perform configuration tasks to enable the usage of application function libraries (such as the PAL and the OFL)
for the applications SAP Assortment Planning and SAP Allocation Management.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
56 PUBLIC Prepare the Upgrade
 1. Enable Usage of PAL Functions (SAP Assortment Planning) [page 57]
To enable the usage of the PAL algorithm for SAP Assortment Planning, perform the required setup
steps.
2. Check the OFL Installation [page 58]
Confirm that the OFL algorithm was installed successfully as prerequisite for SAP Assortment Planning
and SAP Allocation Management.

Parent topic: Prepare the Upgrade [page 29]

Previous: Verify SAP HANA Users and Privileges [page 51]

Next: Configure the Zero Downtime Option [page 59]

4.4.1 Enable Usage of PAL Functions (SAP Assortment

Planning)
To enable the usage of the PAL algorithm for SAP Assortment Planning, perform the required setup steps.

Use

The installation of SAP HANA Platform includes the installation of the PAL algorithm, a prerequisite for SAP
Assortment Planning.

To enable the usage of the PAL algorithm, as required by SAP Assortment Planning, perform the following
procedure.

 Note

You do not need to create the AFL_WRAPPER_GENERATOR or AFL_WRAPPER_ERASER procedures, nor do

you need to generate any special PAL procedures; this is done automatically.

Procedure

1. To confirm that the PAL functions were installed successfully, you can run SELECT statements in the three
relevant public views as follows:
○ SELECT * FROM SYS.AFL_AREAS WHERE AREA_NAME = 'AFLPAL';
In the case of a successful installation, the statement should return 1 row.
○ SELECT * FROM SYS.AFL_PACKAGES WHERE AREA_NAME = 'AFLPAL';
In the case of a successful installation, the statement should return 1 row.
○ SELECT * FROM SYS.AFL_FUNCTIONS WHERE AREA_NAME = 'AFLPAL';
In the case of a successful installation, the statement should return many rows. Verify that the function
KMEANS is part of the list.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Prepare the Upgrade PUBLIC 57
More Information

● Section Upgrade the Prerequisites [page 18] Common Prerequisites SAP HANA Platform
● http://help.sap.com/hana_platform <Version> Reference SAP HANA Predictive Analysis Library
(PAL)

Parent topic: Configure AFL Usage [page 56]

Next: Check the OFL Installation [page 58]

4.4.2 Check the OFL Installation

Confirm that the OFL algorithm was installed successfully as prerequisite for SAP Assortment Planning and
SAP Allocation Management.

Use

The installation of SAP HANA Platform includes the installation of the OFL algorithm, a prerequisite for SAP
Assortment Planning.

Procedure

1. To confirm that the OFL was installed successfully, you can run SELECT statements in the three relevant
public views as follows:
○ SELECT * FROM SYS.AFL_AREAS WHERE AREA_NAME = 'OFL_AREA';
In the case of a successful installation, the statement should return 1 row.
○ SELECT * FROM SYS.AFL_PACKAGES WHERE AREA_NAME = 'OFL_AREA';
In the case of a successful installation, the statement should return 1 row.
○ SELECT * FROM SYS.AFL_FUNCTIONS WHERE AREA_NAME = 'OFL_AREA';
In the case of a successful installation, the statement should return 4 rows. Verify that the function
GENIOS_SOLVE is part of the list.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
58 PUBLIC Prepare the Upgrade
Parent topic: Configure AFL Usage [page 56]

Previous: Enable Usage of PAL Functions (SAP Assortment Planning) [page 57]

4.5 Configure the Zero Downtime Option

Use the zero downtime option (ZDO) to continue regular operations during system upgrades and maintenance
procedures.

Use

ZDO is available for the following modules in SAP Customer Activity Repository:

● Omnichannel Article Availability

● Inventory Visibility
● POS Data Transfer and Audit

 Note

During upgrades with ZDO, SAP HANA content is not accessible with SAP HANA studio.

To use ZDO, you perform several procedures that result in SAP Customer Activity Repository being able to
consume SAP HANA Deployment Infrastructure (HDI) views. The steps you perform depend on whether you're
using SAP ERP (SAP Retail) or SAP S/4HANA Retail as your source master data system, and whether your
system landscape also includes SAP CRM or an SAP Marketing system (either SAP Marketing Cloud or SAP
Marketing on-premise).

In all procedures, settings for your main master data system, either SAP ERP (SAP Retail) or SAP S/4HANA
Retail, are mandatory.

1. Map Schemas [page 60]

Start configuring the zero downtime option (ZDO) by mapping physical schemas for your master data
systems to corresponding logical (authoring) schemas.
2. Get Database User Authorization [page 62]
Use the SQL console in SAP HANA studio to assign the required privileges to the database user.
Authorization for SAP ERP (SAP Retail) or SAP S/4HANA Retail is mandatory; authorization for
scenarios using SAP CRM or an SAP Marketing system are optional.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Prepare the Upgrade PUBLIC 59
3. Activate and Deploy Logical HDI Containers [page 63]
To use views from SAP HANA Deployment Infrastructure (HDI) with the zero downtime option (ZDO),
you must first activate the HDI containers in which to deploy the views.
4. Select a Mode for HDI Views [page 64]
Configure SAP Customer Activity Repository to use views from SAP HANA Deployment Infrastructure
(HDI) during upgrades instead of SAP HANA views.

Parent topic: Prepare the Upgrade [page 29]

Previous: Configure AFL Usage [page 56]

Next: Migrate to New Default Table for Sales Pricing Data (/DMF/PRC) [page 64]

4.5.1 Map Schemas

Start configuring the zero downtime option (ZDO) by mapping physical schemas for your master data systems
to corresponding logical (authoring) schemas.

Prerequisites

You have implemented the steps described in SAP Note 2981564 .

Context

You can create a logical database schema as a repository object. This enables you to access data outside the
default ABAP database schema whenever the name of the database schema in question varies within the
system landscape. For more information, see Creating a Logical Database Schema and Mapping It to a Physical
Database Schema in the SAP - ABAP for SAP HANA Development User Guide.

 Note

SAP HANA studio refers to authoring schemas, whereas the Display/Edit Mappings for Logical Schemas
transaction in SAP Customer Activity Repository refers to logical schemas. They are the same thing.

Procedure

1. In SAP Customer Activity Repository, run Display/Edit Mappings for Logical Schemas (transaction
DB_SCHEMA_MAP).

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
60 PUBLIC Prepare the Upgrade
 2. If using SAP ERP (SAP Retail), map physical schemas to logical (authoring) schemas as described in the
following table. For each physical schema, map to the actual logical schema or the relevant dummy
schema that you created when implementing SAP Note 2981564 .

Physical Schema Logical Schema

SAP ERP /POSDW/SAP_ECC

If SAP ERP (SAP Retail) isn't part of your system land­

scape, then map the SAP_ERP_DUMMY schema.

SAP CRM /POSDW/SAP_ECC_CRM

If SAP CRM isn't part of your system landscape, then

map the SAP_CRM_DUMMY schema.

SAP Marketing Cloud /POSDW/SAP_ECC_CUAN

If SAP Marketing Cloud isn't part of your system land­

scape, then map the SAP_CUAN_DUMMY schema.

3. If using SAP S/4HANA Retail, map physical schemas to authoring (logical) schemas as described in the
following table. For each physical schema, map to the actual logical schema or the relevant dummy
schema that you created when implementing SAP Note 2981564 .

Physical Schema Logical Schema

SAP S/4HANA /POSDW/SAP_S4H

If SAP S/4HANA Retail isn't part of your system land­

scape, then map the SAP_ERP_DUMMY schema.

SAP CRM /POSDW/SAP_S4H_CRM

If SAP CRM isn't part of your system landscape, then

map the SAP_CRM_DUMMY schema.

SAP Marketing Cloud /POSDW/SAP_S4H_CUAN

If SAP Marketing Cloud isn't part of your system land­

scape, then map the SAP_CUAN_DUMMY schema.

Task overview: Configure the Zero Downtime Option [page 59]

Next task: Get Database User Authorization [page 62]

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Prepare the Upgrade PUBLIC 61
4.5.2 Get Database User Authorization

Use the SQL console in SAP HANA studio to assign the required privileges to the database user. Authorization
for SAP ERP (SAP Retail) or SAP S/4HANA Retail is mandatory; authorization for scenarios using SAP CRM or
an SAP Marketing system are optional.

Procedure

1. Open SAP HANA studio and log on to your SAP HANA database system.

2. Choose Window Perspective Open Perspective SAP HANA Modeler .

3. Open the SQL console.
4. For each of the following master data systems in your landscape, add the following privileges to the
database user:

Physical Schema Privileges

SAP ERP (SAP Retail) grant select on schema <ECC-PHYSICAL-

SCHEMA> TO <DBUSER>

WITH GRANT OPTION

SAP S/4HANA Retail grant select on schema <S4H-PHYSICAL-

SCHEMA> TO <DBUSER>

WITH GRANT OPTION

SAP CRM (optional) grant select on schema <CRM-PHYSICAL-

SCHEMA> TO <DBUSER>

WITH GRANT OPTION

SAP Marketing system (optional) grant select on schema <CUAN-PHYSICAL-

SCHEMA> TO <DBUSER>

WITH GRANT OPTION

Task overview: Configure the Zero Downtime Option [page 59]

Previous task: Map Schemas [page 60]

Next task: Activate and Deploy Logical HDI Containers [page 63]

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
62 PUBLIC Prepare the Upgrade
4.5.3 Activate and Deploy Logical HDI Containers

To use views from SAP HANA Deployment Infrastructure (HDI) with the zero downtime option (ZDO), you must
first activate the HDI containers in which to deploy the views.

Procedure

1. In SAP Customer Activity Repository, run ABAP-Managed HDI Containers (transaction SCTS_AMHC).
2. Display and activate each of the following, in the order provided:

○ /POSDW/SAP_CAR_DATA
○ /POSDW/SAP_CAR_ECC_HDI
○ /POSDW/SAP_CAR_S4H_HDI
○ /POSDW/SAP_CRM_ECC_HDI
○ /POSDW/SAP_CRM_S4H_HDI
○ /POSDW/SAP_CUAN_ECC_HDI
○ /POSDW/SAP_CUAN_S4H_HDI
○ /POSDW/SAP_FMS_ECC_HDI
○ /POSDW/SAP_FMS_S4H_HDI
○ /POSDW/SAP_OAA_ECC_HDI
○ /POSDW/SAP_OAA_S4H_HDI
3. Run HTA for HDI (Deployment) (transaction SCTS_HDI_DEPLOY).
4. Enter each of the following in the Transport Object Name field, choose Execute, and then select and deploy
all instances of sap.is.retail:

○ SAP.IS.RETAIL//POSDW/SAP_CAR_DATA
○ SAP.IS.RETAIL//POSDW/SAP_CAR_ECC_HDI
○ SAP.IS.RETAIL//POSDW/SAP_CAR_S4H_HDI
○ SAP.IS.RETAIL//POSDW/SAP_CRM_ECC_HDI
○ SAP.IS.RETAIL//POSDW/SAP_CRM_S4H_HDI
○ SAP.IS.RETAIL//POSDW/SAP_CUAN_ECC_HDI
○ SAP.IS.RETAIL//POSDW/SAP_CUAN_S4H_HDI
○ SAP.IS.RETAIL//POSDW/SAP_FMS_ECC_HDI
○ SAP.IS.RETAIL//POSDW/SAP_FMS_S4H_HDI
○ SAP.IS.RETAIL//POSDW/SAP_OAA_ECC_HDI
○ SAP.IS.RETAIL//POSDW/SAP_OAA_S4H_HDI

Task overview: Configure the Zero Downtime Option [page 59]

Previous task: Get Database User Authorization [page 62]

Next task: Select a Mode for HDI Views [page 64]

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Prepare the Upgrade PUBLIC 63
4.5.4 Select a Mode for HDI Views

Configure SAP Customer Activity Repository to use views from SAP HANA Deployment Infrastructure (HDI)
during upgrades instead of SAP HANA views.

Procedure

1. In Customizing for SAP Customer Activity Repository, go to POS Data Management POS Inbound
Processing General Settings Define General Settings .
2. Under Further Settings, choose an option from the Activate HDI dropdown list:

○ If using SAP ERP (SAP Retail), choose 1 Active for HDI ECC release
○ If using SAP S/4HANA Retail, choose 2 Active for HDI S4H release

Task overview: Configure the Zero Downtime Option [page 59]

Previous task: Activate and Deploy Logical HDI Containers [page 63]

4.6 Migrate to New Default Table for Sales Pricing Data

(/DMF/PRC)

Make sure that /DMF/PRC is the default table for sales pricing data in your customer system. This procedure is
mostly relevant for upgrade scenarios but might also apply to some new installation scenarios.

Context

As of SAP Customer Activity Repository applications bundle 5.0, the default table for sales pricing data has
changed:

● New default table: /DMF/PRC (Product Pricing Data)

● Old default table: /DMF/PRODLOC_PRC (Product Location Price Data)

If you are upgrading from a lower release, you need to migrate to the new table for replicating sales pricing
data.

 Tip

You can already perform this procedure now, prior to the actual upgrade. This enables you to schedule the
migration at a time that is convenient for you.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
64 PUBLIC Prepare the Upgrade
  Note

The table /DMF/PRODLOC_PRC is still used when replicating purchase pricing data (moving average price).
This is not affected by the migration described here. Applications requiring knowledge of the moving
average price, such as SAP Replenishment Planning, continue to use the data from this table.

Procedure

1. Migrate the sales pricing data to the new table. Follow the instructions in the Enable Extended Sales Pricing
Data section of the SAP Customer Activity Repository Administration Guide.
2. Check your data replication settings. Make sure that the sales pricing data from the source master data
system is replicated to the new table. For replication instructions, see the Configure Data Replication from
SAP ERP and SAP S/4HANA to DDF section of the SAP Customer Activity Repository Administration Guide.

Parent topic: Prepare the Upgrade [page 29]

Previous: Configure the Zero Downtime Option [page 59]

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Prepare the Upgrade PUBLIC 65
5 Upgrade the Software

For a correct upgrade, you must first upgrade the required prerequisites and implement the pre-upgrade SAP
Notes. Then you install the SAP RTL AFL FOR SAP HANA component in your SAP HANA Platform. Next you
upgrade the back-end components, verify the SAP Client setup, and upgrade the front-end components.
Finally, you implement the SAP Notes that can only be applied after the upgrade.

 Tip

If you encounter issues during these procedures, see the Troubleshooting [page 190] section for possible
solutions.

1. Verify Prerequisites and SAP Notes (Pre-Upgrade) [page 67]

Before upgrading to the current release of SAP Customer Activity Repository applications bundle 5.0,
ensure that your system landscape is fully prepared. In this procedure, you verify that all the
prerequisites for your scenario are installed and that all the preparatory SAP Notes have been
implemented.
2. Download and Install SAP RTL AFL FOR SAP HANA (Mandatory) [page 67]
Install compatible revisions of the SAP HANA database and the application function library
components (SAP HANA AFL and SAP RTL AFL FOR SAP HANA). You must do this before you
upgrade the SAP CARAB back-end product version of SAP Customer Activity Repository applications
bundle. This procedure is mandatory for all the scenarios.
3. Download and Install SAP XRP AFL (Only for SAP Replenishment Planning) [page 71]
This procedure is only required if you want to use SAP Replenishment Planning. Download a revision of
the SAP XRP AFL component that is compatible with the revision of your SAP HANA database and
install it in your SAP HANA system.
4. Upgrade SAP CARAB Back-End Product Version [page 74]
Upgrade your back-end system to the SAP CARAB 5.0 back-end product version of SAP Customer
Activity Repository applications bundle 5.0. First create a stack XML file with Maintenance Planner.
Then install this file with Software Update Manager (SUM).
5. Verify SAP Client Setup [page 76]
In most upgrade scenarios, you do not need to set up an SAP client in your back-end system because
you already did this during the initial installation. However, if you are not only upgrading your system to
the current release but also adding a new scenario, you must check whether the current SAP client
setup is still sufficient. For example, you might need to add SLT transformation rules for the client
mapping between your source master data system(s) and your ABAP back-end system.
6. Upgrade SAP FIORI FOR SAP CARAB Front-End Product Version [page 77]
Upgrade your front-end system to the SAP FIORI FOR SAP CARAB 5.0 front-end product version of
SAP Customer Activity Repository applications bundle 5.0. The product version contains the SAP Fiori
apps for this release. First create a stack XML file with Maintenance Planner. Then install this file with
Software Update Manager (SUM).
7. Verify SAP Notes and RINs (Post-Upgrade) [page 80]
There are SAP Notes (corrections) that can only be implemented after you have upgraded the back-
end product version and the front-end product version. You must therefore do this additional check and
implement the required notes, before you move on to the setup steps for the applications.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
66 PUBLIC Upgrade the Software
5.1 Verify Prerequisites and SAP Notes (Pre-Upgrade)

Before upgrading to the current release of SAP Customer Activity Repository applications bundle 5.0, ensure
that your system landscape is fully prepared. In this procedure, you verify that all the prerequisites for your
scenario are installed and that all the preparatory SAP Notes have been implemented.

Procedure

 Note

Make sure that you have the up-to-date version of each SAP Note, which you can always find on the SAP
Support Portal at http://support.sap.com/notes .

1. Verify that you have installed and configured the Common Prerequisites and the Application-Specific
Prerequisites, as described in Upgrade the Prerequisites [page 18].
2. Verify that you have implemented all SAP Notes listed in Implement SAP Notes for the Upgrade [page 29]
that are required for your application and that must be implemented before the upgrade.
1. Always see the table for SAP Customer Activity Repository in that section. SAP Notes listed there are
often common corrections, applicable to all the applications.
2. Then see the table for your application.

Parent topic: Upgrade the Software [page 66]

Next: Download and Install SAP RTL AFL FOR SAP HANA (Mandatory) [page 67]

5.2 Download and Install SAP RTL AFL FOR SAP HANA
(Mandatory)

Install compatible revisions of the SAP HANA database and the application function library components (SAP
HANA AFL and SAP RTL AFL FOR SAP HANA). You must do this before you upgrade the SAP CARAB back-

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Upgrade the Software PUBLIC 67
end product version of SAP Customer Activity Repository applications bundle. This procedure is mandatory for
all the scenarios.

Overview

There is one software component in SAP Customer Activity Repository applications bundle that you must
always install (or upgrade) first:

● SAP RTL AFL FOR SAP HANA

You must install (upgrade) this component together with the following components of SAP HANA Platform:

● SAP HANA AFL

● SAP HANA DATABASE

The revision of each AFL component must be compatible with the revision of the SAP HANA database. Be
aware of the following dependencies.

Dependencies Between AFL Components and the SAP HANA Database

The AFL components (SAP HANA AFL, SAP RTL AFL FOR SAP HANA) run directly in the SAP HANA
database. Because of this, they are released in sync with the SAP HANA database.

The releases are called “revisions”. Whenever a new revision of the SAP HANA database is released, a new
revision of each AFL component is released. As a result, there are always several revisions of each component
available for download.

 Caution

Compatible Revisions

For each revision of an AFL component, there is only one compatible revision of the SAP HANA database.
Whenever you upgrade the AFL components to a new revision, you must also upgrade the database.
Whenever you upgrade the database to a new revision, you must also upgrade the AFL components.

This applies not only during a new installation or an upgrade, but is equally relevant during normal
business operations.

Patches for Same Revision

Patches are the sole exception to this rule. Within the same revision, you can and should upgrade the AFL
components to the highest available patch. Here is an example:

● Your current revision is:

SAP RTL AFL FOR SAP HANA revision 50.1 for SAP HANA database 2.0 SPS05 revision 50
● A higher patch might be:
SAP RTL AFL FOR SAP HANA revision 50.2 for SAP HANA database 2.0 SPS05 revision 50

In this case, you should install the higher patch of the AFL. You do not need to update the database.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
68 PUBLIC Upgrade the Software
  Tip

You can easily check which revision is currently installed:

1. Execute transaction DB02 to open the Diagnostics: Missing Tables and Indexes screen.
2. Choose Current Status Overview to open the SAP HANA database overview.
3. Under Installed Plug-Ins , choose RTL to open the table with the plug-in details.
4. Search for SAP RTL AFL and see the values for rev-number and rev-patchlevel.

Download and Install SAP RTL AFL FOR SAP HANA

 Tip

When you download AFL components from the SAP Support Portal, the compatible revision of the SAP
HANA database is always indicated.

1. Determine which revision of the SAP HANA database and the AFL components you need.
To select the best revision for your scenario, see the Common Prerequisites in section Upgrade the
Prerequisites [page 18]. Carefully read the information under SAP HANA Platform 2.0 and SAP RTL AFL
FOR SAP HANA:
○ Note the minimum revision of the SAP HANA database and the AFL components. You need at least
this revision for the current release.
○ Read the Caution to know what to do if you wish to select a higher revision than the minimum
revision.
Once you have selected a revision, this gives you the compatible revisions of the other components.
2. Download the compatible revisions from the SAP Support Portal at http://support.sap.com under
Software Downloads :

 Tip

Alternatively, you can log in to the SAP ONE Support Launchpad at https://
launchpad.support.sap.com/#/softwarecenter/ and follow the navigation from there.

○ SAP RTL AFL FOR SAP HANA:

The component is included in the SAP CARAB back-end product version. To download one of the
available revisions, choose By Alphabetical Index (A-Z) C CAR RETAIL APPLICATIONS BUNDLE
SAP CARAB 5.0 Support Packages and Patches DOWNLOADS COMPRISED SOFTWARE
COMPONENT VERSIONS SAP RTL AFL FOR SAP HANA 200 .

 Caution

Always select the highest available patch of a revision.

○ SAP HANA AFL and SAP HANA DATABASE:

These components are part of SAP HANA Platform. To download one of the available revisions, choose
By Alphabetical Index (A-Z) H SAP HANA PLATFORM EDITION SAP HANA PLATFORM

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Upgrade the Software PUBLIC 69
 EDITION 2.0 Support Packages and Patches DOWNLOADS SAP HANA AFL 2.0 and SAP HANA
DATABASE 2.0.
3. Upgrade your back-end system to the selected revisions of SAP RTL AFL FOR SAP HANA, SAP HANA
AFL, and SAP HANA DATABASE. See the following table for guidance.

Overview of Upgrade Scenarios

You wish to upgrade from a release of... What you do is...

SAP Customer Activity Repository applications bundle 1.0 You replace the AFL revisions UDFAFL_INST 100 and
POSAFL_INST 100 of the lower release with the SAP RTL
AFL FOR SAP HANA revision that you have selected for
the current release.

As described above, you also upgrade the SAP HANA AFL

and SAP HANA DATABASE components to the compatible
revisions.

SAP Customer Activity Repository applications bundle 2.0 You replace the existing revision of SAP RTL AFL FOR
SAP HANA with the revision that you have selected for the
current release.

As described above, you also upgrade the SAP HANA AFL

and SAP HANA DATABASE components to the compatible
revisions.

SAP Customer Activity Repository applications bundle 4.0 You replace the existing revision of SAP RTL AFL FOR
SAP HANA with the revision that you have selected for the
current release.

As described above, you also upgrade the SAP HANA AFL

and SAP HANA DATABASE components to the compatible
revisions.

See SAP Note 2377894 and carefully follow the steps for the upgrade scenario.

 Tip

If you encounter issues, see the Troubleshooting [page 190] section for possible solutions.

 Tip

For installation and upgrade information for SAP HANA Platform, see the following sections of the SAP
HANA Server Installation and Update Guide (select your release at the top):

○ Installing an SAP HANA System

○ Updating the SAP HANA System

Result

You have successfully upgraded the SAP RTL AFL FOR SAP HANA component.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
70 PUBLIC Upgrade the Software
  Remember

For future updates of your system landscape, remember that the dependencies between the AFL
components and the SAP HANA database still apply:

● For example, should you decide to upgrade your SAP Customer Activity Repository applications bundle
scenario to a higher release requiring a higher AFL revision, you will also need to upgrade the database.
● Likewise, should you decide to upgrade your SAP HANA database to a higher revision (for example, to
use new features in SAP HANA), you will also need to upgrade the AFL components.

Parent topic: Upgrade the Software [page 66]

Previous: Verify Prerequisites and SAP Notes (Pre-Upgrade) [page 67]

Next: Download and Install SAP XRP AFL (Only for SAP Replenishment Planning) [page 71]

5.3 Download and Install SAP XRP AFL (Only for SAP
Replenishment Planning)

This procedure is only required if you want to use SAP Replenishment Planning. Download a revision of the SAP
XRP AFL component that is compatible with the revision of your SAP HANA database and install it in your SAP
HANA system.

Context

 Note

SAP XRP AFL is only required if you use SAP Replenishment Planning.

SAP XRP AFL is the application function library (AFL) component for SAP Replenishment Planning. Basically,
it is the calculation engine for your replenishment-related processes.

It is delivered as a component in the SAP CARAB 5.0 back-end product version of SAP Customer Activity
Repository applications bundle.

SAP XRP AFL runs in the database layer of your system landscape. Because of technical dependencies, the
component follows the release cycle of the SAP HANA database. The releases are called “revisions”.

This section describes where to download the correct revision of SAP XRP AFL and how to install it.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Upgrade the Software PUBLIC 71
Prerequisites

● You are aware of the SAP HANA Platform prerequisites for this release of SAP Customer Activity
Repository applications bundle.
See section Upgrade the Prerequisites [page 18] and consult the information under Common
Prerequisites SAP HANA Platform 2.0 . The information about minimum revisions and maintenance
revisions also applies to SAP XRP AFL.
● You know that the SAP XRP AFL revision must always be compatible with the SAP HANA DATABASE
revision.
See section Download and Install SAP RTL AFL FOR SAP HANA (Mandatory) [page 67] and consult the
information under Dependencies Between AFLs and the SAP HANA Database.
● You have already installed compatible revisions of the following components in your SAP HANA system:
○ Components of SAP HANA Platform: SAP HANA DATABASE and SAP HANA AFL
○ Component of SAP Customer Activity Repository applications bundle: SAP RTL AFL FOR SAP HANA

Procedure

To install SAP XRP AFL, follow these steps:

1. Select a revision:
Select the SAP XRP AFL revision that is compatible with your SAP HANA database revision.
2. Download the revision:
1. Navigate to the SAP Support Portal at http://support.sap.com and choose the Download Software
icon.
Alternatively, you can log in to the SAP ONE Support Launchpad at https://
launchpad.support.sap.com/#/softwarecenter/ and follow the navigation from there.
2. Choose By Alphabetical Index (A-Z) C CAR RETAIL APPLICATIONS BUNDLE SAP CARAB 5.0
Support Packages and Patches DOWNLOADS COMPRISED SOFTWARE COMPONENT VERSIONS
SAP XRP AFL 1.0 .
3. Download the selected revision (*.sar file).

 Note

The compatible SAP HANA database revision is always indicated.

3. Install the revision:

 Note

Your tool for this step is the SAP HANA database lifecycle manager (HDBLCM).

You have several options for installing or upgrading components with the HDBLCM. For more
information, see the SAP HANA Server Installation and Update Guide for your SAP HANA Platform
version at https://help.sap.com/viewer/p/SAP_HANA_PLATFORM under Installation and Upgrade.

In particular, consult the following sections:

○ Choosing the Correct SAP HANA HDBLCM for Your Task

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
72 PUBLIC Upgrade the Software
 ○ Installing or Updating SAP HANA Components
○ Parameter Reference

If you encounter issues using the HDBLCM, see SAP Notes 2078425 (Troubleshooting note for SAP
HANA platform lifecycle management tool hdblcm) and 2082466 (Known Issues in SAP HANA
Platform Lifecycle Management (HDBLCM)) for possible solutions.

1. Log in as user root.

2. Load the SAP XRP AFL revision into your directory (<download path>).
3. Change to the SAP HANA resident directory where the HDBLCM is located:
cd /<sapmnt>/<SID>/hdblcm

 Note

<SID> is your customer-defined database system ID.

4. Call the resident HDBLCM tool at command line level with the following option as user root:
./hdblcm --action=update_components --component_dirs=/<download path>/
SAP_XRP_AFL
5. Follow the on-screen instructions.
6. Check that the script server for the SAP HANA database is active. If it isn't, activate it as described in
SAP Note 1650957 (SAP HANA Database: Starting the Script Server).
7. Check that the SAP XRP AFL component is now installed and active in your SAP HANA database:
○ Follow the instructions in SAP Note 2188129 (Application Function Library (AFL): Check what
AFLs are installed and active in a SAP HANA Database).
○ You should get the message “registration was successful” (for PLUGIN_NAME = 'xrp' and
PLUGIN_NAME = 'afl' in view M_PLUGIN_STATUS).
○ If you get the message “registration failed”, repeat the installation steps above.
Then restart the server and the SAP HANA database.
○ If you encounter other issues, see section Troubleshooting [page 190] for possible solutions.

Result
You have successfully installed the SAP XRP AFL component. Continue with the next step.

 Remember

For future updates of your system landscape, remember that the dependency between the AFL and the
SAP HANA database still applies.

For example, should you later decide to upgrade your SAP Replenishment Planning and SAP Customer
Activity Repository system to a higher release requiring a higher AFL revision, you will also need to upgrade
the revision of the SAP HANA database.

Vice versa, should you decide to upgrade your SAP HANA database to a higher revision (for example, to use
new features in SAP HANA), you will also need to upgrade the AFL to the compatible revision.

Parent topic: Upgrade the Software [page 66]

Previous: Download and Install SAP RTL AFL FOR SAP HANA (Mandatory) [page 67]

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Upgrade the Software PUBLIC 73
Next: Upgrade SAP CARAB Back-End Product Version [page 74]

5.4 Upgrade SAP CARAB Back-End Product Version

Upgrade your back-end system to the SAP CARAB 5.0 back-end product version of SAP Customer Activity
Repository applications bundle 5.0. First create a stack XML file with Maintenance Planner. Then install this file
with Software Update Manager (SUM).

Prerequisites

● A valid start release (add-on product version) must already be installed in your system landscape. It serves
as the basis for the upgrade.
● You know how to use SAP Solution Manager to perform uploads into Maintenance Planner on the SAP
Support Portal. If you need more information, see the Maintenance Planner - User Guide at https://
help.sap.com/viewer/product/MAINTENANCE_PLANNER/latest/en-US. Search for section Uploading
Landscape Data Into SAP Support Portal.
● You have completed all of the previous procedures in this guide. In particular, see section Prepare the
Upgrade [page 29].
● You have installed compatible revisions of the SAP HANA database and the mandatory AFL components
(SAP HANA AFL and SAP RTL AFL FOR SAP HANA). For information on the minimum revisions for this
release, see the Common Prerequisites in section Upgrade the Prerequisites [page 18].

Overview

In the procedures below you do the following:

Use this tool... To do this...

Maintenance Planner Create a stack XML file based on the required product ver­
sions.
More information: https://help.sap.com/viewer/p/MAINTE­
NANCE_PLANNER

Software Update Manager (SUM) Install or upgrade components using the stack XML file.

More information: https://support.sap.com/en/tools/soft­

ware-logistics-tools/software-update-manager.html

 Note

It may be possible to install or upgrade components using the SAP Add-On Installation Tool (transaction
SAINT) or the Support Package Manager (transaction SPAM). However, these alternative procedures are

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
74 PUBLIC Upgrade the Software
 not described in this guide. For information on whether they are supported for your implementation
scenario and on how to proceed in this case, see SAP Note 1803986 .

Create Stack XML File With Maintenance Planner

 Note

If you encounter issues with Maintenance Planner, see the following sources for possible solutions:

● Maintenance Planner Troubleshooting Guide on the SAP Community Wiki

● SAP Note 2535751 : Can not select the higher release for Netweaver in Maintenance Planner
● SAP Note 2314463 : Required file K-XXXxxxxxxxx.SAR is not visible for your user Sxxxxxxx

1. Navigate to the SAP Support Portal at https://support.sap.com/en/alm/solution-manager/processes-72/

maintenance-planner.html .
2. Upload the current system state of your installed ABAP back-end server (with a valid add-on product
version installed for the upgrade) into Maintenance Planner.
3. Choose Access Maintenance Planner.
4. Choose Plan.
5. Determine whether you need to update your target software level for the current release of SAP Customer
Activity Repository applications bundle.

 Note

This can vary, depending on your upgrade scenario, the stack currently installed on your back-end
server, and the minimum version required for this release.

For information on minimum versions, see Upgrade the Prerequisites [page 18].

Depending on your decision, select either the update option or the maintenance option.
6. Select a product version and a support package stack.
7. Select a product version instance.
8. Choose Confirm Selection.
9. Choose Install or Maintain an Add-On.
10. As target software, select the back-end product version SAP CARAB 5.0 and the support package stack
Initial Shipment Stack (12/2020).

 Note

If the required version of SAP S/4HANA FOUNDATION is not yet installed in your back-end system, it
will be installed automatically during the upgrade, together with the SAP CARAB 5.0 back-end
product version. For more information on the required version, see Upgrade the Prerequisites [page 18]
and consult the Common Prerequisites.

11. Choose Confirm Selection.

12. Choose Next.
13. Select the operating system and database for your scenario.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Upgrade the Software PUBLIC 75
14. Choose Confirm Selection.
15. Review the details of your stack dependent and stack independent files. If everything is OK, choose Next.
16. Choose Download Stack XML.
You have now created the stack XML file.

Install Stack XML File With Software Update Manager (SUM)

1. Download and install the SUM tool:

1. Navigate to the SAP Support Portal at https://support.sap.com/en/tools/software-logistics-tools/
software-update-manager.html .
2. Consult the information for SUM 2.0 SP xx and follow the instructions.
2. In SUM, install your add-on product using the stack XML file that you have created in the first procedure.

Result

You have successfully upgraded the back-end product version.

 Note

With this upgrade, several SAP HANA content packages have already been activated automatically. This
saves you manual activation steps later on.

Continue with the next section.

Parent topic: Upgrade the Software [page 66]

Previous: Download and Install SAP XRP AFL (Only for SAP Replenishment Planning) [page 71]

Next: Verify SAP Client Setup [page 76]

5.5 Verify SAP Client Setup

In most upgrade scenarios, you do not need to set up an SAP client in your back-end system because you
already did this during the initial installation. However, if you are not only upgrading your system to the current
release but also adding a new scenario, you must check whether the current SAP client setup is still sufficient.
For example, you might need to add SLT transformation rules for the client mapping between your source
master data system(s) and your ABAP back-end system.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
76 PUBLIC Upgrade the Software
Example

Let's assume you are currently using one of the following scenarios of SAP Customer Activity Repository
applications bundle:

● Unified Demand Forecast (UDF) module of SAP Customer Activity Repository

● Omnichannel Promotion Pricing (OPP) module of SAP Customer Activity Repository
● SAP Allocation Management
● SAP Assortment Planning
● SAP Merchandise Planning
● SAP Promotion Management
● SAP Replenishment Planning

With this upgrade, you now want to add one of the following modules of SAP Customer Activity Repository to
your overall implementation:

● POS Data Transfer and Audit

● Multichannel Transaction Data Management
● Inventory Visibility (including Omnichannel Article Availability and Sourcing, OAA)
● On-Shelf Availability

Procedure

Whenever you wish to add a scenario or module, you must verify the current SAP client setup in your back-end
system.

1. See the Set Up SAP Client section in the Common Installation Guide. It describes the setup for different
scenarios.
2. Carefully read the information for the scenario that you wish to add. Check whether your current setup of
the SAP client is sufficient. If not, follow the instructions.

Parent topic: Upgrade the Software [page 66]

Previous: Upgrade SAP CARAB Back-End Product Version [page 74]

Next: Upgrade SAP FIORI FOR SAP CARAB Front-End Product Version [page 77]

5.6 Upgrade SAP FIORI FOR SAP CARAB Front-End

Product Version
Upgrade your front-end system to the SAP FIORI FOR SAP CARAB 5.0 front-end product version of SAP
Customer Activity Repository applications bundle 5.0. The product version contains the SAP Fiori apps for this
release. First create a stack XML file with Maintenance Planner. Then install this file with Software Update
Manager (SUM).

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Upgrade the Software PUBLIC 77
Prerequisites

● A valid start release (add-on product version) is already installed in your system landscape. It serves as the
basis for the upgrade.
● You have completed the previous procedures in this guide.
● You know how to use SAP Solution Manager to perform uploads into Maintenance Planner on the SAP
Support Portal. If you need more information, see the Maintenance Planner – User Guide at https://
help.sap.com/viewer/product/MAINTENANCE_PLANNER/latest/en-US. Search for section Uploading
Landscape Data Into SAP Support Portal.

Overview

In the procedures below you do the following:

Use this tool... To do this...

Maintenance Planner Plan your system landscape and create a stack

XML file based on the required product versions.
More information: https://help.sap.com/viewer/p/MAINTE­
NANCE_PLANNER

Software Update Manager (SUM) Install or upgrade components using the stack
XML file.
More information: https://support.sap.com/en/tools/software-logis­
tics-tools/software-update-manager.html

 Note

It may be possible to install or upgrade components using the SAP Add-On Installation Tool (transaction
SAINT) or the Support Package Manager (transaction SPAM). However, these alternative procedures are
not described in this guide. For information on whether they are supported for your implementation
scenario and on how to proceed in this case, see SAP Note 1803986 .

Create Stack XML Using Maintenance Planner

 Note

If you encounter issues with Maintenance Planner, see the following sources for possible solutions:

● Maintenance Planner Troubleshooting Guide on the SAP Community Wiki

● SAP Note 2535751 : Can not select the higher release for Netweaver in Maintenance Planner
● SAP Note 2314463 : Required file K-XXXxxxxxxxx.SAR is not visible for your user Sxxxxxxx

1. Navigate to the SAP Support Portal at https://support.sap.com/en/alm/solution-manager/processes-72/

maintenance-planner.html .

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
78 PUBLIC Upgrade the Software
 2. Upload the current system state of your installed front-end server (with a valid add-on product version
installed for the upgrade) into Maintenance Planner.
3. Choose Access Maintenance Planner.
4. Choose Plan.
5. Determine whether you need to update your target software level for the current release of SAP Customer
Activity Repository applications bundle.

 Note

This can vary, depending on your upgrade scenario, the stack currently installed on your back-end
server, and the minimum version required for this release.

For information on minimum versions, see Upgrade the Prerequisites [page 18] under SAP Fiori.

Depending on your decision, select either the update option or the maintenance option.
6. Select a product version and a support package stack.
7. Select a product version instance.
8. Choose Confirm Selection.
9. Choose Install or Maintain an Add-On.
10. Select the front-end product version SAP FIORI FOR SAP CARAB 5.0 and the support package stack
Initial Shipment Stack (12/2020).
11. Select an instance of SAP Fiori front-end server.
12. Choose Confirm Selection.
13. Choose Next.
14. Select the operating system and database for your scenario.
15. Choose Confirm Selection.
16. Review the details of your stack dependent and stack independent files. If everything is OK, choose Next.
17. Choose Download Stack XML.
You have now created the stack XML file.

Install Stack XML File Using Software Update Manager (SUM)

1. Download and install the SUM tool:

1. Navigate to the SAP Support Portal at https://support.sap.com/en/tools/software-logistics-tools/
software-update-manager.html .
2. Consult the information for SUM 2.0 SP xx and follow the instructions.
2. In SUM, install your add-on product using the stack XML file that you have created in the first procedure.

Result

You have successfully upgraded to the front-end product version for this release.

Continue with the next section.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Upgrade the Software PUBLIC 79
Parent topic: Upgrade the Software [page 66]

Previous: Verify SAP Client Setup [page 76]

Next task: Verify SAP Notes and RINs (Post-Upgrade) [page 80]

5.7 Verify SAP Notes and RINs (Post-Upgrade)

There are SAP Notes (corrections) that can only be implemented after you have upgraded the back-end
product version and the front-end product version. You must therefore do this additional check and implement
the required notes, before you move on to the setup steps for the applications.

Prerequisites

Make sure that you have the up-to-date version of each SAP Note, which you can always find on the SAP
Support Portal at http://support.sap.com/notes .

Procedure

Check whether there are SAP Notes that can only be implemented after the upgrade. See section Implement
SAP Notes for the Upgrade [page 29] and do the following:
a. Always check the release information notes (RINs) indicated there. The RINs list the installation- and
upgrade-relevant corrections that have become available since this guide was published and the software
was released. Implement any corrections from the RINs that are required for your scenario.
b. Always check the table for SAP Customer Activity Repository. SAP Notes listed there are often common
corrections, applicable to all consuming applications.
c. Then check the SAP Notes for your consuming application. Implement any corrections required for your
scenario.

Task overview: Upgrade the Software [page 66]

Previous: Upgrade SAP FIORI FOR SAP CARAB Front-End Product Version [page 77]

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
80 PUBLIC Upgrade the Software
6 Set Up the Applications

You have upgraded the back-end components and front-end components of SAP Customer Activity Repository
applications bundle. Now you must first do the setup steps under SAP Customer Activity Repository Core
(Mandatory for All Applications) . These steps are required for all the applications. Then you either continue
with the setup steps under SAP Customer Activity Repository Advanced (Optional) or do the setup steps
for your application.

For SAP Allocation Management, first consult the information in section SAP Allocation Management [page
274]. Then do the setup steps under SAP Customer Activity Repository Core (Mandatory for All
Applications) .

6.1 SAP Customer Activity Repository

Set up SAP Customer Activity Repository after the upgrade. The Core steps are always mandatory. You must
do them for any application or scenario of SAP Customer Activity Repository applications bundle.

Core (Mandatory for All Applications) [page 81]

Perform the core steps to set up SAP Customer Activity Repository as the common platform. The core
steps are mandatory for SAP Customer Activity Repository and for all the consuming applications.

Advanced (Optional) [page 110]

After you have completed the core steps, perform the advanced steps that are relevant to your
scenario. The advanced steps are optional. They enable specific functionality in SAP Customer Activity
Repository.

Troubleshooting [page 190]

Diagnose and resolve issues that may arise when you install, upgrade, and set up your scenario. If you
need to report a customer incident, see the information at the end of this section.

6.1.1 Core (Mandatory for All Applications)

Perform the core steps to set up SAP Customer Activity Repository as the common platform. The core steps
are mandatory for SAP Customer Activity Repository and for all the consuming applications.

 Caution

Always do the core steps first. Then you can continue with the Advanced (Optional) steps for SAP
Customer Activity Repository or with the setup steps for your application.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 81
1. Verify Authorizations for On-Shelf Availability (OSA) [page 82]
In SAP HANA studio, verify that the AFL__SYS_AFL_POSDM_AREA_EXECUTE role has been granted to
the SAPHANADB user in your back-end system. If it hasn´t, grant the role as described below. This short
procedure is mandatory for all the applications, because it is required for the successful activation of
the SAP HANA content later on.
2. Verify Authorizations for Unified Demand Forecast (UDF) [page 84]
In an upgrade scenario, the authorizations should already be available in your back-end system.
Perform this check in SAP HANA studio to verify that the roles for UDF exist, that they have the
required privileges, and that they are assigned to the required users. If any authorizations are missing,
set them up as described here. This procedure is mandatory for all the applications because the
authorizations are needed for the successful activation of the SAP HANA content later on.
3. Create/Replicate Source Master Data System Tables [page 88]
Create the tables in SAP Customer Activity Repository that are required for replicating data from your
source master data system. Then perform the actual replication of the data. You need SAP HANA
studio and the SAP Landscape Transformation Replication Server (SLT) for this procedure. For
reference, you can download a spreadsheet that lists the required tables for each source master data
system (SAP Retail, SAP S/4HANA).
4. Activate SAP HANA Content [page 92]
Activate the SAP HANA content for your scenario by running the /CAR/ACTIVATE_HTA report in the
back-end system. You can run this report as many times as required. For example, if you choose to
extend your scenario at a later point in time, simply run the report again to activate the SAP HANA
content for the added options.
5. Activate SAP HANA Content for Demand Data Foundation (DDF) [page 95]
If your scenario includes the calculation of Demand Data Foundation (DDF), do the additional steps
described here to activate the required SAP HANA content. All steps are mandatory.
6. Verify that SAP HANA Script Server Is Active [page 98]
Verify that the script server for the SAP HANA database is still active. If necessary, restart it manually.
This step is mandatory for all the applications.
7. Configure SAP Gateway [page 98]
Perform several configuration steps for SAP Gateway and activate the OData services for the SAP Fiori
apps. The steps to follow depend on the SAP NetWeaver version on your front-end server.

6.1.1.1 Verify Authorizations for On-Shelf Availability

(OSA)

In SAP HANA studio, verify that the AFL__SYS_AFL_POSDM_AREA_EXECUTE role has been granted to the
SAPHANADB user in your back-end system. If it hasn´t, grant the role as described below. This short procedure
is mandatory for all the applications, because it is required for the successful activation of the SAP HANA
content later on.

Context

The AFL__SYS_AFL_POSDM_AREA_EXECUTE role enables the SAPHANADB user to call the OSA application
function library (part of the SAP RTL AFL FOR SAP HANA component) in the SAP HANA database.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
82 PUBLIC Set Up the Applications
Prerequisites

● You have mapped authoring schemas to physical schemas as described in Verify Correct Schema Mapping
[page 48].
● You have installed the SAP RTL AFL FOR SAP HANA component as described in Download and Install
SAP RTL AFL FOR SAP HANA (Mandatory) [page 67].
● You have database administrator rights so that you can grant roles to users.
● You have an SAPHANADB user and an SAPHANADB physical schema in your SAP HANA database. The
names must be identical.

 Note

The name SAPHANADB is used as a variable. Replace it with the name of the database user or database
schema in your ABAP back-end system. Instead of SAPHANADB, you might also come across
documentation or user interfaces that mention SAPHANADB. Both variables mean the same.

For more information and an example, see the Important Variables in Naming Conventions [page 6].

If you need more information on database users and schemas, see section Verify Correct Schema
Mapping [page 48].

Procedure

 Tip

● If you encounter issues related to authorization or authentication, see section Security-Related Issues
of the SAP HANA Troubleshooting and Performance Analysis Guide, which you can find at https://
help.sap.com/viewer/p/SAP_HANA_PLATFORM for your SAP HANA Platform version.
● We have provided an example SQL statement below that you can adapt as needed for your system
landscape.

1. In SAP HANA studio, access your back-end system and open the SAP HANA Administration Console.
2. Choose Security Users .
3. Select your SAPHANADB user and open the user details (or double-click the user).
4. On the Granted Roles tab, choose the plus icon and select AFL__SYS_AFL_POSDM_AREA_EXECUTE as the
role name.

 Example

SQL example: grant AFL__SYS_AFL_POSDM_AREA_EXECUTE to SAPHANADB;

5. Save your changes by choosing the Deploy (F8) icon at the top right.

Result

You have successfully set up the authorizations for OSA. Continue with the next section.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 83
Parent topic: Core (Mandatory for All Applications) [page 81]

Next: Verify Authorizations for Unified Demand Forecast (UDF) [page 84]

6.1.1.2 Verify Authorizations for Unified Demand Forecast

(UDF)

In an upgrade scenario, the authorizations should already be available in your back-end system. Perform this
check in SAP HANA studio to verify that the roles for UDF exist, that they have the required privileges, and that
they are assigned to the required users. If any authorizations are missing, set them up as described here. This
procedure is mandatory for all the applications because the authorizations are needed for the successful
activation of the SAP HANA content later on.

Context

The three roles for UDF have the following purpose:

Role Purpose

UDF_EXECUTE Required to execute UDF. Enables the SAP<SID> user to call the UDF applica­
tion function library (AFL) in the SAP HANA database.

UDF_DEPLOY Required to activate the SAP HANA content for UDF. Enables the SAP<SID>
user to deploy the SAP HANA content for UDF.

UDF_DEPLOY_SYS_REPO Required to activate the SAP HANA content. Defines additional privileges for
the _SYS_REPO standard user.

 Note

If you require more information on standard users (such as _SYS_REPO), see the following guides for your
SAP HANA Platform version at https://help.sap.com/viewer/p/SAP_HANA_PLATFORM:

● SAP HANA Security Guide: Search for section SAP HANA User Management.
● SAP HANA Security Checklists and Recommendations: Search for section Recommendations for
Database Users, Roles, and Privileges.

Prerequisites

● You have mapped the authoring schemas to the physical schemas as described in Verify Correct Schema
Mapping [page 48].

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
84 PUBLIC Set Up the Applications
 ● You have installed the SAP RTL AFL FOR SAP HANA component as described in Download and Install
SAP RTL AFL FOR SAP HANA (Mandatory) [page 67].
● You have database administrator rights so that you can grant roles to users.
● You have an SAP<SID> user and an SAP<SID> physical schema in your SAP HANA database. The names
must be identical.

 Note

The name SAP<SID> is used as a variable. Replace it with the name of the database user or database
schema in your ABAP back-end system. Instead of SAP<SID>, you might also come across
documentation or user interfaces that mention SAPHANADB. Both variables mean the same.

For more information and an example, see the Important Variables in Naming Conventions [page 6].

If you need more information on database users and schemas, see Verify Correct Schema Mapping
[page 48].

Procedure

 Tip

● If you encounter issues related to authorization or authentication, see the Security-Related Issues
section of the SAP HANA Troubleshooting and Performance Analysis Guide for your SAP HANA
Platform version at https://help.sap.com/viewer/p/SAP_HANA_PLATFORM.
● We have provided example SQL statements below that you can adapt as needed for your system
landscape.

1. In SAP HANA studio, log on to your back-end system and open the SAP HANA Administration Console.
2. Navigate to Security Roles and select New Role from the context menu.
3. In the Role Name field, enter UDF_EXECUTE.

 Example

SQL example: create role UDF_EXECUTE;

4. Make the following settings for this role:

○ On the Granted Roles tab: Choose the plus icon and select the
AFL__SYS_AFL_UDFCORE_AREA_EXECUTE role from the list.

 Example

SQL example: grant AFL__SYS_AFL_UDFCORE_AREA_EXECUTE to UDF_EXECUTE;

○ On the Object Privileges tab: Add the following catalog objects and grant them the following privileges:
○ Catalog object (schema name) SAP<SID>: privileges SELECT, INSERT, UPDATE, DELETE

 Example

SQL example: grant SELECT, INSERT, UPDATE, DELETE on schema SAP<SID> to

UDF_EXECUTE;

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 85
 ○ Catalog object (schema name) _SYS_BIC: privileges SELECT, EXECUTE

 Example

SQL example: grant SELECT, EXECUTE on schema _SYS_BIC to UDF_EXECUTE;

○ On the Analytic Privileges tab: Add the _SYS_BI_CP_ALL privilege.

 Example

SQL example: call

GRANT_ACTIVATED_ANALYTICAL_PRIVILEGE('_SYS_BI_CP_ALL','UDF_EXECUTE');

5. Save your changes by choosing the Deploy (F8) icon at the top right.
6. Navigate to Security Users .
7. Select the SAP<SID> user from the list and open the details screen (or double-click the user).
8. On the Granted Roles tab, add the UDF_EXECUTE role.

 Example

SQL example: grant UDF_EXECUTE to SAP<SID>

9. Save your changes by choosing the Deploy (F8) icon at the top right.

 Note

You have created the first role with the required privileges and granted the role to the SAP<SID> user.

10. Now create the second role. Navigate again to Security Roles and select New Role from the context
menu.
11. In the Role Name field, enter UDF_DEPLOY.

 Example

SQL example: create role UDF_DEPLOY;

12. Make the following settings for this role:

○ On the Granted Roles tab: Choose the plus icon and select the CONTENT_ADMIN role from the list.

 Example

SQL example: grant CONTENT_ADMIN to UDF_DEPLOY;

○ On the System Privileges tab: Add the CATALOG READ privilege.

 Example

SQL example: grant CATALOG READ to UDF DEPLOY;

13. Save your changes by choosing the Deploy (F8) icon at the top right.
14. Navigate again to Security Users .
15. Select the SAP<SID> user from the list and open the details screen (or double-click the user).
16. On the Granted Roles tab, add the UDF_DEPLOY role.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
86 PUBLIC Set Up the Applications
  Example

SQL example: grant UDF_DEPLOY to SAP<SID>;

17. Save your changes by choosing the Deploy (F8) icon at the top right.

 Note

You have created the second role and granted the role to the SAP<SID> user.

18. Now create the third role. Navigate again to Security Roles and select New Role from the context
menu.
19. In the Role Name field, enter UDF_DEPLOY_SYS_REPO.

 Example

SQL example: create role UDF_DEPLOY_SYS_REPO;

20.On the Object Privileges tab, make these settings:

Add the catalog object (schema name) SAP<SID> and grant the privileges SELECT, INSERT, UPDATE, and
DELETE.

 Example

SQL example: grant SELECT, INSERT, UPDATE, DELETE on schema SAP<SID> to

UDF_DEPLOY_SYS_REPO;

21. Save your changes by choosing the Deploy (F8) icon at the top right.
22. Navigate again to Security Users .
23. Select the _SYS_REPO user from the list and open the details screen (or double-click the user).
24. On the Granted Roles tab, add the UDF_DEPLOY_SYS_REPO role.

 Example

SQL example: grant UDF_DEPLOY_SYS_REPO to _SYS_REPO;

25. Save your changes by choosing the Deploy (F8) icon at the top right.

 Note

You have created the third role with the required privileges and granted the role to the _SYS_REPO user.

Result

You have successfully set up the authorizations for UDF.

Parent topic: Core (Mandatory for All Applications) [page 81]

Previous: Verify Authorizations for On-Shelf Availability (OSA) [page 82]

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 87
Next task: Create/Replicate Source Master Data System Tables [page 88]

6.1.1.3 Create/Replicate Source Master Data System

Tables

Create the tables in SAP Customer Activity Repository that are required for replicating data from your source
master data system. Then perform the actual replication of the data. You need SAP HANA studio and the SAP
Landscape Transformation Replication Server (SLT) for this procedure. For reference, you can download a
spreadsheet that lists the required tables for each source master data system (SAP Retail, SAP S/4HANA).

Prerequisites

● You have completed the previous procedures in this guide.

● You have installed the SAP Landscape Transformation Replication Server. For the minimum version
required, installation and implementation information, see Upgrade the Prerequisites [page 18] and
consult the Common Prerequisites.
● If your source master data system is SAP S/4HANA 1909 or higher, be aware that as of that release, the
SAP LT Replication Server is no longer available as a standalone component. Instead, as of SAP S/4HANA
1909, an embedded SAP LT Replication Server is included by default.

 Caution

To be able to replicate the data from an SAP S/4HANA 1909 (or higher) system, you first need to
prepare the replication. This preparation has the added advantage that it gives you the option to still
use a standalone SAP LT Replication Server. Follow the steps in SAP S/4HANA 1909 or Higher: Prepare
Data Replication with SAP Landscape Transformation Replication Server [page 91]. Then return to
this procedure here.

Context

The applications in SAP Customer Activity Repository applications bundle can use data originating from a
single or multiple source master data systems.

The list of tables to create and replicate depends on your leading source master data system:

● SAP Retail: for installations based on the SAP_ECC schema

● SAP S/4HANA Retail: for installations based on the SAP_S4H schema

In this procedure, you first create and then replicate the required tables.

 Note

It is possible to combine the steps create and replicate.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
88 PUBLIC Set Up the Applications
Procedure

1. Download the spreadsheet with the SLT tables for your version of SAP Customer Activity Repository
applications bundle:
a. Navigate to SAP Help Portal at https://help.sap.com/viewer/p/CARAB and select your version at the
top.
b. Choose Implement Implementation Help SLT Tables for SAP Customer Activity Repository
applications bundle 5.0 and download the archive.
c. Extract the spreadsheet and see the tables listed for your source master data system.

2.  Caution

You must always create and replicate all the tables listed for your source master data system in the
spreadsheet. This is necessary not only for the data replication itself but also for the successful
activation of the SAP HANA content later on.

Create all the tables listed for your source master data system.
a. Configure access from the SAP Landscape Transformation Replication Server to the source SAP Retail
or SAP S/4HANA Retail system (RFC connection), and from the SAP Landscape Transformation
Replication Server to the target SAP HANA database of your SAP Customer Activity Repository back-
end system.

For more information, see the Installation Guide at https://help.sap.com/viewer/p/

SAP_LANDSCAPE_TRANSFORMATION_REPLICATION_SERVER. If necessary, select a different
version at the top.
b. Ensure that your SAP Customer Activity Repository back-end system is connected to SAP HANA
studio.

If necessary, set the connection as follows:

1. Log on to SAP HANA studio.
2. Right-click in the Navigator pane and select Add System.
3. In the Specify System dialog, enter the Host Name, Instance Number, and Description.
4. In the Connection Properties dialog, enter your system User Name and Password.
5. Save your changes.
c. Ensure that the database schemas are created on the SAP HANA database of your back-end system.
These are the schemas on your SAP HANA database to which the SAP Retail and/or SAP S/4HANA
data will be replicated.

 Note

For more information, see the Create a Schema section of the SAP HANA Developer Guide.

d. Create all the tables for your source master data system.
1. Log on to the SAP Landscape Transformation Replication Server.
2. Execute transaction LTRC (SAP LT Replication Server Cockpit)).
3. Define and select your replication configuration.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 89
  Note

For more information, see SAP Library at https://help.sap.com/viewer/p/

SAP_LANDSCAPE_TRANSFORMATION_REPLICATION_SERVER. Search for section Creating a
Configuration.

4. Choose Execute (F8) . A screen opens that shows the details of this replication configuration.
5. Select the table overview tab. You can now see the data provisioning function.
6. Execute the table overview function. On the subsequent pop-up, select the function for table
creation.
7. Choose the multiple selection push-button next to the table name field.
8. In the next screen, you can either enter the table names manually or upload a text file with the
table names (recommended):
Create this text file from the spreadsheet that you downloaded before. Make sure that the text file
contains only the table names and no other data. Then upload the text file.
9. Choose Copy (F8) to return to the previous screen.
10. Choose Execute (F8) to trigger the creation of the tables.

You have successfully created the tables in your SAP Customer Activity Repository back-end system.
3. Replicate all the tables listed for your source master data system.

 Note

If your SAP Retail or SAP S/4HANA Retail system and your back-end SAP Customer Activity
Repository system are co-deployed on the same SAP HANA database, you do not need to replicate the
tables.

a. Save a CSV file of the required tables. You will later load the tables from this file.
b. In SAP HANA studio, choose Window Perspective Open Perspective SAP HANA Modeler .
c. In the Quick View panel, choose Data Provisioning to open the Data Provisioning Editor for your system.

If the Quick View panel is not displayed, choose Help Quick View .
d. In the Data Provisioning Editor, make any necessary adjustments: remove or add tables, select the
appropriate source system, and select the target schema for the replication.
e. Choose Replicate to open the Replicate Request screen.
f. Choose Load from file, browse to the location where you saved the CSV file, and select it.
g. The tables in the file are added to the Selected column on the right-hand side. Choose Finish.

 Note

In the Data Provisioning Editor, you can monitor the action status of the tables using Data Load
Management.

Results

You have successfully replicated the tables from your source master data system into your SAP Customer
Activity Repository back-end system. Continue with the next section.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
90 PUBLIC Set Up the Applications
Task overview: Core (Mandatory for All Applications) [page 81]

Previous: Verify Authorizations for Unified Demand Forecast (UDF) [page 84]

Next task: Activate SAP HANA Content [page 92]

6.1.1.3.1 SAP S/4HANA 1909 or Higher: Prepare Data

Replication with SAP Landscape Transformation
Replication Server

Only perform this procedure if your source master data system is SAP S/4HANA 1909 or higher. If so, you must
do the steps described here before doing the actual replication.

Context

If your source master data system is SAP S/4HANA 1909 or higher, be aware that the SAP LT Replication
Server is no longer available as a standalone component. Instead, an embedded SAP LT Replication Server is
included in SAP S/4HANA by default.

To be able to replicate data from your SAP S/4HANA system into SAP Customer Activity Repository, you first
need to prepare the replication as described below.

This preparation has the added advantage that it gives you the option to still use a standalone SAP LT
Replication Server.

 Note

You do not need to perform this procedure if you are using SAP S/4HANA FOUNDATION 2020. This is
because the foundation provides a standalone SAP LT Replication Server by default. For more information,
see https://help.sap.com/viewer/product/
SAP_LANDSCAPE_TRANSFORMATION_REPLICATION_SERVER_FOR_SAP_S4HANA/latest/en-US?
task=implement_task, open the Installation Guide, and consult section SAP Landscape Transformation
Replication Server for SAP S/4HANA 1.0.

Procedure

Prepare data replication from SAP S/4HANA 1909 or higher to SAP Customer Activity Repository, using an
embedded or a standalone SAP LT Transformation Server:

1. Pause your current SLT replication routine with the SAP LT Replication Server.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 91
2. Upgrade your source master data system to SAP S/4HANA 1909 or higher as described in the
corresponding product documentation. For more information, see SAP Help Portal for SAP S/4HANA
1909. Consult the Upgrade Guide and, if applicable, also the Conversion Guide.
If necessary, select a different version at the top.
3. Implement SAP Note 2857334 (Unsupported data type DECFLOAT34 / D34N when replicating from a
S/4 HANA OP1909 system) in your SAP S/4HANA system.
4. Adjust your SLT configuration as described in the note.
5. Now you can resume the data replication. Return to section Create/Replicate Source Master Data System
Tables [page 88] and follow the instructions.

6.1.1.4 Activate SAP HANA Content

Activate the SAP HANA content for your scenario by running the /CAR/ACTIVATE_HTA report in the back-end
system. You can run this report as many times as required. For example, if you choose to extend your scenario
at a later point in time, simply run the report again to activate the SAP HANA content for the added options.

Prerequisites

You have successfully completed all the previous procedures in this guide.

Context

The /CAR/ACTIVATE_HTA report activates the SAP HANA Transport for ABAP (HTA) objects for your scenario.
For more information on the report, see the accompanying system documentation.

 Tip

If you encounter issues during the activation, see the Troubleshooting [page 190] section for possible
solutions.

Procedure

1. Start transaction SE38.

2. Enter /CAR/ACTIVATE_HTA as the program (report) and choose Execute ( F8 ).
3. On the Activate SAP HANA Content for SAP CARAB screen, select all the options for which you wish to
activate the SAP HANA content. Use the following table for reference:

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
92 PUBLIC Set Up the Applications
  Caution

Always activate the SAP HANA content for SAP Customer Activity Repository first. This content
must be active before you can activate the content for additional options.

 Tip

If the SAP HANA content is already active for an option, you can see this directly on the screen.

To activate the SAP HANA content for... Select at least these options...

SAP Customer Activity Repository ○ ECC Mode: Select your source master data system.
○ Business Scenarios Activation: Select SAP Customer Activity
Repository.
○ Optional: If your system landscape includes more than one SAP ERP
or SAP S/4HANA master data system, select either Multiple SAP ERP
or Multiple S/4HANA under the scenario options.

SAP Allocation Management Follow the instructions in Activate SAP HANA Content for SAP Allocation
Management [page 279].

Calculation of Demand Data Foundation Follow the instructions in Activate SAP HANA Content for Demand Data
(DDF) (without SAP Allocation Foundation (DDF) [page 95].
Management)

SAP Assortment Planning No action required.

The SAP HANA content was already activated automatically during the up­
grade of the back-end product version.

Unified Demand Forecast (UDF) and SAP No action required.

Fiori apps for demand forecasting
The SAP HANA content was already activated automatically during the up­
grade of the back-end product version.

On-Shelf Availability ○ ECC Mode: Select your source master data system.
○ Business Scenarios Activation: Select On-Shelf Availability and
Customer Activity Repository.

Omnichannel Article Availability and ○ ECC Mode: Select your source master data system.

Sourcing (OAA) ○ Business Scenarios Activation: Select Omnichannel Article Availability.

SAP Merchandise Planning No action required.

The SAP HANA content was already activated automatically during the up­
grade of the back-end product version.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 93
 To activate the SAP HANA content for... Select at least these options...

SAP Replenishment Planning There is no specific SAP HANA content for SAP Replenishment Planning.
However, if you use the real-time inventory, select at least these options:
○ ECC Mode: Select your source master data system.
○ Business Scenarios Activation: Select Customer Activity Repository
and Demand Data Foundation.
○ Optional: If your system landscape includes more than one SAP ERP
or SAP S/4HANA master data system, select either Multiple SAP ERP
or Multiple S/4HANA under the scenario options.

SAP Promotion Management No action required.

4. Do a test run to verify your selections:

a. Select Perform Prerequisite Check and choose Execute ( F8 ).
b. Read the system log and first resolve any issues found during the check. See the Troubleshooting
[page 190] section for possible solutions.
5. Activate the SAP HANA content for real:
a. Deselect Perform Prerequisite Check.
b. Choose Execute ( F8 ) again.
6. Verify that the activation was successful. There are three ways how you can do this:
a. Simply rerun the report. You can see all the options that are now active.
b. Or: Start transaction SCTS_HTA_DEPLOY. Specify an SAP HANA content package (for example,
sap.is.retail), select Include subpackages, and choose Execute ( F8 ). You can see all the packages
and objects including their status.
c. Or: Navigate to the same package in SAP HANA studio or SAP Web IDE and check whether all its views
are active.

Results

You have successfully activated the SAP HANA content for your scenario. Continue with the next section.

Task overview: Core (Mandatory for All Applications) [page 81]

Previous task: Create/Replicate Source Master Data System Tables [page 88]

Next: Activate SAP HANA Content for Demand Data Foundation (DDF) [page 95]

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
94 PUBLIC Set Up the Applications
6.1.1.5 Activate SAP HANA Content for Demand Data
Foundation (DDF)

If your scenario includes the calculation of Demand Data Foundation (DDF), do the additional steps described
here to activate the required SAP HANA content. All steps are mandatory.

 Caution

If you wish to calculate distribution curves for SAP Allocation Management (that is, for the “distribution
curve analysis”), skip the steps below and follow the instructions in Activate SAP HANA Content for SAP
Allocation Management [page 279].

Run the Report for Creating the Dummy Schema and Dummy Tables

The /DMF/CREATE_SLT_TABLES (Create SLT Tables) report checks for a missing physical schema and, if
necessary, creates this as a dummy schema together with the corresponding dummy tables.

Prerequisites

You have an SAP HANA database user in the ABAP back-end system with the authorization to create the
dummy schema (privilege CREATE SCHEMA). This should already be the case if the authorizations were set up
as described in section Verify SAP HANA Users and Privileges [page 51].

Procedure

1. Run the report /DMF/INSERT_SLT_TABLES_TO_DB (Insert SLT Table Entries to Database in insert mode
(by deselecting the simulation setting).
2. In your ABAP back-end system, start transaction SE38. Enter /DMF/CREATE_SLT_TABLES as the program
and choose Execute.
3. Select your source master data system. For SAP S/4HANA, also select the version.
4. For the Physical Source Schema, enter the name of the physical schema into which your SLT tables should
be replicated.

 Note

If the physical source schema already exists in the SAP HANA database, only the dummy tables in this
schema are created when you execute the report.

5. For the Physical Dummy Schema, enter the name of the schema to be created.
6. Select the simulation mode for a test run and execute the report. Check for errors in the application log
and resolve them.
7. Run the report again, this time without simulation mode.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 95
Maintain Schema Mapping

Check the name of your physical schema:

1. If it is one of the default names below, no further action is required:

○ SAP_S4H, for SAP S/4HANA
○ SAP_ECC, for SAP Retail and SAP Fashion Management
2. If your physical schema has a different name, do the following:
In SAP HANA studio, create a schema mapping where your customer-specific name is used as authoring
schema for the physical schema. For instructions, see Verify Correct Schema Mapping [page 48].

Set PREWORK_DONE Indicator for DDF Packages

Demand Data Foundation (DDF) has a number of SAP HANA content packages that are relevant:

● sap.is.ddf.ecc
● sap.is.ddf.fms
● sap.is.ddf.fms_s4h
● sap.is.ddf.cross.ecc
● sap.is.ddf.cross.fms
● sap.is.ddf.cross.fms_s4h
● sap.is.ddf.cross

These packages have the activation mode P (Package and its objects deployed only after prework done). In this
procedure, you confirm that the prework has been done. You do this by setting the PREWORK_DONE indicator in
the CTS_HOT_PREWORK table to X for all the packages above.

Procedure
1. Start transaction SE16, enter CTS_HOT_PREWORK as the table, and choose Execute.
2. Enter sap.is.ddf.* as ABAP_HANA_PACKAGE_ID and choose Execute.
3. You now see a list that includes the DDF packages above. Switch to change mode to edit the entries.
4. Check whether all of the DDF packages above have the PREWORK_DONE indicator set to X.
5. If the setting is still missing for one of the DDF packages above, double-click the entry and set
PREWORK_DONE to X.
6. Save your changes.

 Note

Here is how you can always check the current settings and display details for each package:

1. Start transaction SE16, enter CTS_HOT_PACKAGE as the table, and choose Execute.
2. Enter sap.is.ddf.* as ABAP_HANA_PACKAGE_ID and choose Execute.
3. You now see a list that includes the DDF packages above. For each of the DDF packages above, double-
click the entry to display the package details.
4. For each package, verify the current setting in field HOT ACTIVATION MODE (set to P).

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
96 PUBLIC Set Up the Applications
Check and Activate the SAP HANA Content for Demand Data Foundation
(DDF)

Depending on your scenario, there might still be inactive DDF packages even though you have already activated
the content as described in the previous section (Activate SAP HANA Content [page 92]).

Now you make sure that those packages are activated as well.

Procedure
1. Execute transaction SCTS_HTA_DEPLOY (SAP HANA Transport for ABAP - Deployment).
2. Deploy each of the following packages in exactly the same order as listed below. One by one, enter the
package ID in SAP HANA Repository Package and choose Execute.

 Caution

Do not select the Include subpackages option.

1. sap.is.ddf.ecc
2. sap.is.ddf.fms
3. sap.is.ddf.fms_s4h
4. sap.is.ddf.cross.ecc
5. sap.is.ddf.cross.fms
6. sap.is.ddf.cross.fms_s4h
7. sap.is.ddf.cross

Result

You have successfully activated the SAP HANA content for calculating Demand Data Foundation.

Parent topic: Core (Mandatory for All Applications) [page 81]

Previous task: Activate SAP HANA Content [page 92]

Next task: Verify that SAP HANA Script Server Is Active [page 98]

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 97
6.1.1.6 Verify that SAP HANA Script Server Is Active

Verify that the script server for the SAP HANA database is still active. If necessary, restart it manually. This step
is mandatory for all the applications.

Context

The script server is an auxiliary SAP HANA server that is required to execute application function libraries
(AFLs). For example, this applies to the SAP HANA AFL component (which includes the SAP HANA Predictive
Analysis Library (PAL) and other libraries) and to the SAP RTL AFL FOR SAP HANA component (which
includes the libraries for Unified Demand Forecast and On-Shelf Availability).

 Note

● The service name is scriptserver.

● The operating system process is hdbscriptserver.
● The operating system process can be started while the SAP HANA database is already running.

Procedure

1. In SAP HANA studio, verify that the script server is active.

2. If the script server is not active, restart it manually as described in SAP Note 1650957 (SAP HANA
Database: Starting the Script Server).

Task overview: Core (Mandatory for All Applications) [page 81]

Previous: Activate SAP HANA Content for Demand Data Foundation (DDF) [page 95]

Next: Configure SAP Gateway [page 98]

6.1.1.7 Configure SAP Gateway

Perform several configuration steps for SAP Gateway and activate the OData services for the SAP Fiori apps.
The steps to follow depend on the SAP NetWeaver version on your front-end server.

 Note

If you have an upgrade scenario where you hadn't configured SAP Gateway before and now want to use
SAP Fiori apps for the first time, you must do a full configuration of SAP Gateway. See the Common
Installation Guide for this release and search for the Configure SAP Gateway section. Do all the procedures
listed there.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
98 PUBLIC Set Up the Applications
Parent topic: Core (Mandatory for All Applications) [page 81]

Previous task: Verify that SAP HANA Script Server Is Active [page 98]

6.1.1.7.1 Connect SAP Gateway to Your Back-End System

Set up the connection between SAP Gateway on your front-end server and your back-end system. In other
words, set up the OData Channel (ODC).

Use

The steps are not specific to this guide and are described in the product documentation for your SAP
NetWeaver version.

 Note

As of SAP NetWeaver 7.40, the major components of SAP Gateway have been integrated into the SAP
NetWeaver system as SAP Gateway Foundation (SAP_GWFND). SAP Gateway Foundation has since been an
integral part of SAP NetWeaver.

Procedure

1. Determine the SAP NetWeaver version on your front-end server.

2. Set up the OData Channel as described in the SAP Gateway Foundation Configuration Guide for your SAP
NetWeaver version.
Use SAP Help Portal for SAP NetWeaver as your entry point and navigate to the guide for your version.
Here are two examples:

 Example

For SAP Gateway on Foundation for ABAP Platform, see the SAP Gateway Foundation Configuration
Guide.

If required, select a different version at the top.

Search for section Connection Settings for the SAP Gateway Hub System and follow the instructions.

 Example

For SAP Gateway for SAP NetWeaver 7.52, see https://help.sap.com/viewer/p/

SAP_NETWEAVER_AS_ABAP_752.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 99
 Select your version at the top and choose Application Help SAP Gateway Foundation
(SAP_GWFND) SAP Gateway Foundation Configuration Guide SAP Gateway Configuration User,
Developer, and Administrator Roles and Connection Settings for the SAP Gateway Hub System.

3. Set up the required roles on the front-end server and assign your user to these roles.
4. Specify the connection settings on the SAP Gateway hub system:
○ Connection from SAP Gateway to consumer systems
These settings allow you to connect the SAP Gateway host to the consumer systems (clients from
which you access the SAP Fiori apps).
○ Connection from SAP Gateway to SAP back-end system
These settings allow you to connect SAP Gateway to your back-end system. They include the following
steps:
○ Creating a type 3 connection from the SAP Gateway host to your back-end system
○ Defining a trust relationship between your back-end system and the SAP Gateway host
○ Configuring your back-end system to accept SAP assertion tickets from the SAP Gateway host
○ Configuring your SAP Gateway host to accept SAP assertion tickets from your back-end system
○ Configuring the necessary system aliases

6.1.1.7.2 Activate SAP Gateway

Before you can use SAP Gateway, you must activate it globally on your front-end server.

Use

The steps are not specific to this guide and are described in the product documentation for your SAP
NetWeaver version.

 Note

As of SAP NetWeaver 7.40, the major components of SAP Gateway have been integrated into the SAP
NetWeaver system as SAP Gateway Foundation (SAP_GWFND). SAP Gateway Foundation has since been an
integral part of SAP NetWeaver.

Procedure

1. Determine the SAP NetWeaver version on your front-end server.

2. Follow the steps in the Activating SAP Gateway section of the SAP Gateway Foundation Configuration Guide
for your SAP NetWeaver version.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
100 PUBLIC Set Up the Applications
 Use SAP Help Portal for SAP NetWeaver as your entry point and navigate to the guide for your version.
Here are two examples:

 Example

For SAP Gateway on Foundation for ABAP Platform, see the SAP Gateway Foundation Configuration
Guide.

If required, select a different version at the top.

Search for section Activating SAP Gateway and follow the instructions.

 Example

For SAP Gateway for SAP NetWeaver 7.52, see https://help.sap.com/viewer/p/

SAP_NETWEAVER_AS_ABAP_752.

Select your version at the top and choose Application Help SAP Gateway Foundation
(SAP_GWFND) SAP Gateway Foundation Configuration Guide SAP Gateway Configuration
Activating SAP Gateway .

6.1.1.7.3 Verify that OData Services are Active

First verify that all the common OData services for SAP Fiori are active. Then verify that the OData services for
your specific application and SAP Fiori apps are active as well.

Context

For security reasons, the OData services are delivered in an inactive state:

● The common OData services are delivered as part of the SAP Fiori front-end server. They are required for
the SAP Fiori launchpad and you must always activate them.
● The application-specific OData services are delivered with SAP Customer Activity Repository
applications bundle. You only need to activate the services that are relevant for your application and
scenario.

Procedures

Mandatory: Verify that Common OData Services for SAP Fiori are Active
1. Log on to your front-end server (your SAP Gateway system).
2. In transaction SPRO, navigate to SAP Reference IMG SAP NetWeaver SAP Gateway OData Channel
Administration General Settings Activate and Maintain Services and execute the Customizing
activity.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 101
  Tip

As a shortcut to the same screen, use transaction /n/IWFND/MAINT_SERVICE.

The Service Catalog shows you all the services that are currently active in your SAP Gateway system.
3. Verify that all the common OData services for SAP Fiori are active:

Common OData Services for SAP Fiori

/UI2/PAGE_BUILDER_CONF

/UI2/PAGE_BUILDER_CUST

/UI2/PAGE_BUILDER_PERS

/UI2/TRANSPORT

/UI2/INTEROP

4. If a service is not active, activate it as follows:

1. Choose Add Service.
The Add Selected Services screen is displayed.
1. In System Alias, select the alias of your local back-end system.
This is the alias that you have created in Connect SAP Gateway to your Back-End System [page 99].
For example, LOCAL.
2. In Technical Service Name, specify /UI2*.
3. Choose Get Services (or press ENTER ).
4. Choose Add Selected Services and follow the instructions.

Result

The common OData services are now active in your SAP Gateway system.

Verify that Application-Specific OData Services for SAP Customer Activity Repository
applications bundle are Active
1. Log on to your front-end server (your SAP Gateway system).
2. In transaction SPRO, navigate to SAP Reference IMG SAP NetWeaver SAP Gateway OData Channel
Administration General Settings Activate and Maintain Services and execute the Customizing
activity.

 Tip

As a shortcut to the same screen, use transaction /n/IWFND/MAINT_SERVICE.

The Service Catalog shows you all the services that are currently active in your SAP Gateway.
3. Activate the services that are required for your application:
1. Choose Add Service.
The Add Selected Services screen is displayed.
2. In System Alias, select the alias of your back-end system.
3. Choose Get Services (or press ENTER ).

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
102 PUBLIC Set Up the Applications
 The available services are displayed.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 103
 4. Use the following table for reference and verify that the services for your application are active:

For this Application... Activate These OData Services...

SAP Customer Activity ○ For POS Data Transfer and Audit: No OData services for SAP Gateway

Repository ○ For Multichannel Transaction Data Management: No OData services for SAP Gate­
way
○ For Unified Demand Forecast and the apps for demand forecasting (Analyze
Forecast, Adjust Forecast, Manage Demand Influencing Factors, Manage Alerts):
○ /DMF/ANALYZEFORECAST_SRV
○ /DMF/OD_FC_TIME_SERIES_VIZ_SRV
○ /DMF/DEMAND_PLAN_UTILITIES_SRV
○ /DPL/OD_ADJUST_FORECAST_SRV
○ /DPL/OD_DEMAND_PLANNING_SRV
○ /DMF/MANAGE_RTLPLNG_ALERTS_SRV
○ APS_CHANGE_DOCUMENTS_SRV
○ For Demand Data Foundation (optional, alternative to the DRF data replication
framework for importing master data):
○ /DMF/API_DOCUMENT
○ /DMF/API_GENERIC_TIME_SERIES
○ /DMF/API_INVENTORY
○ /DMF/API_LOCATION
○ /DMF/API_LOCATION_HIERARCHY
○ /DMF/API_PRODUCT
○ /DMF/API_PRODUCT_HIERARCHY
○ /DMF/API_PRODUCT_LOCATION
○ /DMF/API_SALES_HISTORY
○ /DMF/API_TRANSPORTATION_LANE
○ /DMF/API_ATTRIBUTES
○ /DMF/API_IMAGES
○ /DMF/API_MERCHANDISE_PLAN_KPI
○ /DMF/API_PHPS
○ For the Manage Product Attributes app:
○ /DMF/API_ATTRIBUTES_SRV (optional, to import external attributes for inte­
gration scenarios with a non-SAP source master data system)
○ For Omnichannel Promotion Pricing: none
○ For Omnichannel Article Availability and Sourcing (part of Inventory Visibility):
○ With SAP S/4HANA back-end:
/OAA/F3391_MSN_SRV (SAP Customer Activity Repository)
/OAA/F2586_MSS_SRV
/OAA/F2659_MSC_SRV
/OAA/F3392_MS_SRV (SAP Customer Activity Repository)
○ With SAP Retail back-end:
/OAA/F2530_MSN_SRV
/OAA/F2586_MSS_SRV

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
104 PUBLIC Set Up the Applications
 For this Application... Activate These OData Services...

/OAA/F2659_MSC_SRV
/OAA/F3003_MS_SRV
○ For On-Shelf Availability:
○ /OSA/ON_SHELF_AVAILABILITY
○ For SAP Smart Business for Multichannel Sales Analytics: none

Distribution Curves For the Configure Distribution Curves app and the calculation of distribution curves:

○ /DMF/DIST_CURVE

SAP Allocation ○ /AMR/OD_ALLOCATIONPLAN_SRV

Management ○ /AMR/OD_COMMON_SRV
○ /AMR/OD_MARKETUNIT_SRV
○ /AMR/OD_PARAM_SRV
○ /AMR/OD_WORKLOAD_SRV
○ /AMR/OD_PRODUCT_FLOW_SRV
○ /AMR/OD_KPI_CONFIG_SRV
○ /AMR/OD_ALLOCATIONRESULT_SRV
○ /AMR/OD_BASKET_SRV
○ /AMR/OD_ALLOCATIONPLAN_SEARCH_SRV
○ /AMR/OD_CAPACITYMANAGEMENT_SRV

SAP Assortment ○ /DMF/CURRENCY_LIST_SRV

Planning ○ /DMF/LOCATION_CLUSTERSET_SRV
○ /DMF/MASTER_DATA_SRV
○ /DMF/MODULE_MANAGEMENT_SRV
○ /DMF/OBJ_ATTRIBUTE_SRV
○ /DMF/PLAN_CONFIG_SRV
○ /DMF/SEARCH_LOCATIONS_SRV
○ /DMF/SEARCH_PRODUCTS_SRV
○ /DMF/SEASONS_SRV
○ /RAP/ASSORTMENT_LIST_SRV
○ /RAP/OPTION_PLAN_SRV
○ /RAP/PHP_MATCH_SRV
○ /RAP/VALIDITY_PERIOD_SRV
○ /RAP/V_OP_KPI_Q_CDS_CDS
○ /RAP/OPT_PLN_KPI_SRV
○ /RAP/V_OP_OCLST_PRSL_Q_CDS_CDS

SAP Merchandise Not applicable (this application has no SAP Fiori apps)
Planning

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 105
 For this Application... Activate These OData Services...

SAP Promotion ○ /DMF/PROD_MD_SRV (Master Data Retrieval)

Management ○ /DMF/OFFER_MANAGEMENT_V2_SRV (Manage Promotional Offers)

○ /DMF/PRODUCT_GROUP_SRV (Manage Product Groups)
○ /DMF/LOCATION_SUBGROUP_SRV (Manage Location Subgroups)
○ /PRM/OFFER_CONTENT_SRV (Offer Content Assignment)
○ /PRM/EVENT_PREVIEW_SRV (Preview Events Service)

SAP Replenishment For information about the OData services for SAP Replenishment Planning, see Set Up
Planning SAP Fiori Apps for SAP Replenishment Planning [page 287] and refer to subsection Acti­
vate Application-Specific OData Services for SAP Replenishment Planning.

4. If a required service is not active, select it and choose Add Selected Services. Follow the instructions.

 Note

User roles are only needed if you want to have connections to multiple back-end systems or multiple
clients on the same back-end. The user roles are system-specific and are not delivered by default. If
required, you must create them manually. If you define multiple user roles for different connections,
make sure you have only one role assigned to your user at any time. If you need to change roles, first
remove the old role from your user, then assign the new role.

Result
The application-specific OData services that you have selected are now active in your SAP Gateway system.

 Tip

To ensure that your apps start quickly from the launchpad, you can schedule a report to enable regular
updating of cached OData metadata. For more information, see Scheduling Update of OData Metadata
Caching.

6.1.1.7.4 Calculate SAPUI5 Application Index for SAP Fiori

Apps

Configure and run the /UI5/APP_INDEX_CALCULATE (Calculation of SAPUI5 Application Index for SAPUI5
Repositories) report in your front-end system. The report updates the SAPUI5 application index. If the index is
up-to-date, the system can find data related to SAP Fiori apps significantly faster.

Use

The SAPUI5 application index provides indexing and caching for data related to SAP Fiori apps, components,
and libraries. This data is contained in SAPUI5 repositories on the SAP NetWeaver Application Server for ABAP.

Initially, the index is empty. It is calculated and updated each time you run the report.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
106 PUBLIC Set Up the Applications
Prerequisites

You are familiar with the prerequisites, configuration options, and requirements of the /UI5/
APP_INDEX_CALCULATE report. For more information, see the following:

● SAP Note 2227577 (Recalculation of the SAPUI5 Application Index After Implementing an SAP Note)
● Report documentation in transaction SE38
● SAPUI5: UI Development Toolkit for HTML5: Here you can find detailed information on the SAPUI5
application index and the report.
For more information, see SAPUI5 Application Index.

Configuration

To configure how the index should be calculated, you can choose from several options in the /UI5/
APP_INDEX_CALCULATE report:

● Tab Complete Index, option Depending on Expiry Period and Import of Transport Requests:
This option updates those SAPUI5 repositories and the distribution layer where either the specified
expiration period (in hours and minutes) has elapsed or where a transport has changed the content of the
repositories and the distribution layer since the last update.

 Note

This is the default mode with an expiration period of 24 hours. We recommend that you use this mode
when scheduling the report for periodic execution.

● Tab Complete Index, option Full Calculation:

This option performs a full update of all SAPUI5 repositories and the distribution layer regardless of any
expiration dates.
● Single SAPUI5 Repository Only: Here you select the repository for which you wish to update the index.
● SAPUI5 Distribution Layer Only: Here you update the index only based on the distribution layer.

Operation

Configure and run the report in all your front-end systems.

 Tip

You can run the report manually, but we recommend the following best practices:

● Schedule the report as a periodic job for all follow-on systems to which the changes are transported.
This ensures that the application index is updated based on the transports imported by each system.
For example, you can use transaction SM36 for this purpose.
For more information, see Scheduling the Creation of the SAPUI5 Application Index.
● Always run the report in the following situations:
○ after any changes to the content of SAPUI5 ABAP repositories (for example, implementation of
SAP Notes, upgrades, changes to SAP Gateway systems)

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 107
 ○ after installing a new version of the distribution layer
○ after implementing an SAP Note containing changes to an SAP Fiori app

Procedure

 Note

If you experience issues, see the following troubleshooting tips for possible solutions:

● SAP Note 2364579 (SAPUI5 application index is not calculated, is outdated or contains errors)
● SAP Community at Fiori - How to Troubleshoot SAPUI5 Application Index Specific Issues

1. Log on to your front-end system.

2. Execute transaction SE38, specify /UI5/APP_INDEX_CALCULATE as the program (report), and choose
Execute ( F8 ).
3. Configure the report.
4. Choose Execute ( F8 ) again to run the report manually.

 Tip

Schedule the report to run on a regular basis in all your front-end systems.

Result

The SAPUI5 application index is updated based on your settings.

6.1.1.7.5 Invalidate Caches for SAP Fiori Apps

Run several reports in your front-end system to invalidate different caches. This ensures that the SAP Fiori
launchpad and SAP Fiori apps run correctly after an upgrade and load quickly.

Context

Web browsers store static resources, like JavaScript files, stylesheets, and images in the browser cache. When
these resources are changed in a software upgrade, you want the browser to load the new resources from the
server rather than from the cache, without having to manually clear the browser cache.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
108 PUBLIC Set Up the Applications
Procedure

1. Log on to your front-end server.

2. In transaction SE38, execute the following reports one after the other to invalidate the corresponding
caches:

Reports for Invalidating Caches on Front-End Server

Read this Information Before Exe­
Report What It Does cuting the Report

/UI2/INVALIDATE_GLOBAL_CACHES Invalidates all UI2 caches (caches See the report documentation in
(Global Cache Invalidation) of /UI2/* services). transaction SE38.

/UI2/INVALIDATE_CLIENT_CACHES Invalidates the client caches for se­ See SAP Help Portal for SAP Fiori
(Client Cache Invalidation) lected resources / users. launchpad at https://help.sap.com/
viewer/product/DRAFT/
 Note SAP_FIORI_LAUNCHPAD/EXTER­

You only need to run this report in NAL/en-US. Choose SAP Fiori
exceptional cases, that is, if you Launchpad in SAP NetWeaver with
are using the SAPUI5 cache bust­ SAP_UI Component <your SAP
ing mechanism for your SAP Fiori NetWeaver version on the front-end
launchpad.
server> Administration Guide

Operations Performance Client-

Side Cache Cache Buster for SAP

Fiori Launchpad and SAP Fiori Apps

and the subsection Invalidating Client
Caches.

/UI2/DELETE_CACHE_AFTER_IMP Clears the UI2 cache on the front-end See the report documentation in
(Delete UI2 Cache after import of a server after upgrading to a new sup­ transaction SE38.
Support Package) port package stack.
After executing the report, you can
see how many entries have been de­
leted, for how many users, and for
how many clients.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 109
 Read this Information Before Exe­
Report What It Does cuting the Report

/UI5/UPD_ODATA_METADATA_CACHE Updates cache tokens for OData serv­ See the report documentation in
(Update Caching of OData Metadata) ices of connected back-end systems. transaction SE38.

Run this report after custom develop­

ment changes and upgrades of your
SAP Gateway and/or SAP Fiori sys­
tem.

 Tip
To ensure the cache buster to­
kens are up-to-date, execute the
report periodically. We recom­
mend an hourly execution inter­
val.

6.1.2 Advanced (Optional)

After you have completed the core steps, perform the advanced steps that are relevant to your scenario. The
advanced steps are optional. They enable specific functionality in SAP Customer Activity Repository.

Prerequisites

You have completed the steps in Core (Mandatory for All Applications) [page 81].

Advanced Steps

Replicate Optional Tables [page 111]

Set up the table replication from your SAP CRM source system and from your SAP Marketing Cloud
source system. Both procedures are optional.

Configure SAP Smart Business for Multichannel Sales Analytics [page 116]
Do these procedures if you wish to use the SAP Smart Business for multichannel sales analytics
cockpit. The cockpit provides you with an overview of the most important key performance indicators
for a category manager. The KPI tiles are provided using the SAP Smart Business framework. They
serve as access points to analytical SAP Fiori apps.

Install Alternate Storage [page 117]

You only need to implement this procedure if you plan on using the Table Content Aging report delivered
with SAP Customer Activity Repository. This report allows you to copy your transaction log (TLOG)

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
110 PUBLIC Set Up the Applications
 data and its extensions from your SAP HANA database to an alternate storage technology (such as
SAP IQ or Apache Hadoop), thereby reducing your total cost of hardware ownership.

Adjust Totals When Excluding Post-Voided Transactions [page 127]

This procedure is relevant for the POS Data Transfer and Audit module. You must perform the
procedure if you have existing transactional data prior to the upgrade.

Partition /POSDW/TLOGF and Aggregation Tables [page 127]

If you wish to use the POS Data Transfer and Audit module, we recommend that you partition the /
POSDW/TLOGF table and several aggregation tables (such as /POSDW/TLOGF_EXT). This improves
standard database operations (such as inserting, updating, deleting, and reading) and mass operations
(such as archiving or index merging).

Complete UDF Setup [page 128]

Set up the Unified Demand Forecast (UDF) module in SAP Customer Activity Repository to enable
demand modeling and forecasting for different scenarios and consuming applications. To be able to
use UDF, you must at least do the mandatory steps. We also point you to helpful performance
information for UDF.

Set Up SAP Fiori Apps for SAP Customer Activity Repository [page 135]
Perform common setup steps that are required for all the apps in SAP Customer Activity Repository.
For example, check the prerequisites and prepare the system landscape. Then set up the apps that you
want to use in your scenario.

Configure On-Shelf Availability [page 148]

Configure the On-Shelf Availability (OSA) module in SAP Customer Activity Repository. All steps are
optional and depend on your implementation scenario.

Configure Omnichannel Article Availability and Sourcing for Use with SAP Customer Activity Repository
[page 151]
To set up the OAA module, you need to integrate the source master data system (SAP S/4HANA or
SAP Retail), SAP Customer Activity Repository, SAP Commerce, and SAP Commerce, integration
package for SAP for Retail. You also need to set up asynchronous order management and the data
replication between SAP S/4HANA or SAP Retail, SAP Commerce, and SAP Customer Activity
Repository.

Configure Omnichannel Promotion Pricing for Use with SAP Customer Activity Repository [page 160]
To use the OPP module, you need to activate the functionality in Customizing and configure it for your
specific scenario.

6.1.2.1 Replicate Optional Tables

Set up the table replication from your SAP CRM source system and from your SAP Marketing Cloud source
system. Both procedures are optional.

6.1.2.1.1 Replicate SAP CRM Tables (Optional)

Set up the replication of tables from your SAP CRM source system. You only need to perform this procedure if
you have an SAP CRM system in your SAP Customer Activity Repository landscape and you are planning to use

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 111
the standard SAP implementation of customer identification delivered with the SAP Customer Activity
Repository.

Procedure

1. Ensure that the SAP LT Replication Server is installed and that a user with the appropriate authorizations is
set up in the target SAP HANA database.
If you have already ensured proper installation of the SAP LT Replication Server during previous
procedures, skip to the next step. Otherwise, refer to one of the following for more information:
○ http://help.sap.com/hana SAP HANA SAP HANA Options SAP HANA Real-Time Replication
SAP HANA Trigger-Based Data Replication Using SAP LT Replication Server Installation Information
○ http://help.sap.com/hana SAP HANA SAP HANA Options SAP HANA Real-Time Replication
SAP HANA Trigger-Based Data Replication Using SAP LT Replication Server System Administration
and Maintenance Information Technical Prerequisites and Authorization Aspects
2. Set up a user in the source SAP CRM system and grant relevant authorizations to this user.
For more information, see http://help.sap.com/hana SAP HANA SAP HANA Options SAP HANA
Real-Time Replication SAP HANA Trigger-Based Data Replication Using SAP LT Replication Server
System Administration and Maintenance Information Configuration Information and Replication Concepts
System Connections and Authorizations .
3. Specify a configuration in SAP LT Replication Server, which contains the definition of the connections
between:
○ The source SAP CRM system and the SAP LT Replication Server
○ The SAP LT Replication Server and the target SAP HANA database
For more information, see http://help.sap.com/hana SAP HANA SAP HANA Options SAP HANA
Real-Time Replication SAP HANA Trigger-Based Data Replication Using SAP LT Replication Server
System Administration and Maintenance Information Accessing the Configuration and Monitoring
Dashboard .
The name that you assign to your configuration will be also be used as the name of the database catalog
schema that is automatically created on the target SAP HANA database. This is the schema to which you
will replicate the tables from the source SAP CRM system.
Once you save the configuration, a schema GUID and a mass transfer ID are automatically created and
assigned to the configuration. Furthermore, several dictionary tables are automatically replicated from
your source system to your target SAP HANA database.
For more information, see http://help.sap.com/hana SAP HANA SAP HANA Options SAP HANA
Real-Time Replication SAP HANA Trigger-Based Data Replication Using SAP LT Replication Server
System Administration and Maintenance Information Important Transactions and Control Tables .
4. Define client transformation rules for all the SAP CRM tables that you plan to replicate.
In most cases, you need to apply transformation rules to map the client of the source SAP CRM system to
the client on the target SAP Customer Activity Repository system.

 Caution

Transformation rules must be defined prior to replicating tables.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
112 PUBLIC Set Up the Applications
 For more information, refer to one of the following:
○ Set Up SAP Client section in the Common Installation Guide.
○ http://help.sap.com/hana SAP HANA SAP HANA Options SAP HANA Real-Time Replication
SAP HANA Trigger-Based Data Replication Using SAP LT Replication Server System Administration
and Maintenance Information Important Transactions and Control Tables Data Transformation
Capabilities within SAP Landscape Transformation Replication Server
○ SAP Note 1733714
5. Specify which SAP ERP tables to replicate using information from one of the two following sources:
○ SAP Note 2538135 , for installations based on the SAP_ECC schema
○ SAP Note 2538187 , for installations based on the SAP_S4H schema
For more information, see:
○ http://help.sap.com/hba Installation, Security, Configuration, and Operations Information
Administrator's Guide Configuration Steps Replicate Data (Side-by-Side Only)
○ http://help.sap.com/hana SAP HANA SAP HANA Options SAP HANA Real-Time Replication
SAP HANA Trigger-Based Data Replication Using SAP LT Replication Server System Administration
and Maintenance Information Configuration Information and Replication Concepts ( <Managing
the Replication Process Using the SAP HANA Studio> and <Important Transactions
and Control Tables>)
6. Map the authoring schema SAP_CRM to your particular physical database schema which contains the SAP
CRM tables. If the physical database schema is already named SAP_CRM,this schema mapping is not
required.

Authoring Schema Physical Schema

SAP_CRM <Name of Your Schema for Storing SAP_CRM

Data>

For more information, see http://help.sap.com/hana_platform Development and Modeling SAP

HANA Modeling Guide Importing Table Definitions and Data Map Authoring Schema to the Physical
Schema .

 Note

Every time you make changes to the schema mapping, the SAP HANA content must be redeployed.

You can do this using one of two methods:

○ Execute the /CAR/ACTIVATE_HANA_CONTENT report as described in SAP Note 2330386 .
○ Manually redeploy only those SAP HANA objects which are impacted by your schema mapping
change.

6.1.2.1.2 Replicate SAP Marketing Cloud Tables (Optional)

Set up the replication of tables from your SAP Marketing Cloud source system. You only need to perform this
procedure if you have a SAP Marketing Cloud system in your SAP Customer Activity Repository landscape and

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 113
you are planning to use the standard SAP implementation of customer identification delivered with the SAP
Customer Activity Repository.

Procedure

1. If you plan to implement SAP Marketing Cloud co-deployed with SAP Customer Activity Repository, the
SAP Marketing Cloud tables will not be replicated because they already exist in the same SAP HANA
database and the same database schema.

 Note

Client transformation is not possible without table replication, therefore a co-deployed scenario is only
possible if the client numbers in the two back-end systems are identical.

For more information, see Set Up SAP Client section in the Common Installation Guide.

2. If you plan to implement SAP Marketing Cloud side-by-side with SAP Customer Activity Repository, do the
following:
1. Define client transformation rules for all the SAP Marketing Cloud tables that you plan to replicate.
In most cases, you need to apply transformation rules to map the client of the source SAP Marketing
Cloud system to the client on the target SAP Customer Activity Repository system.

 Caution

Transformation rules must be defined prior to replicating tables.

For more information, refer to one of the following:

○ Set Up SAP Client section in the Common Installation Guide.
○ http://help.sap.com/hana SAP HANA SAP HANA Options SAP HANA Real-Time
Replication SAP HANA Trigger-Based Data Replication Using SAP LT Replication Server System
Administration and Maintenance Information Important Transactions and Control Tables Data
Transformation Capabilities within SAP Landscape Transformation Replication Server
○ SAP Note 1733714
2. Specify which SAP ERP tables to replicate using information from one of the two following sources:
○ SAP Note 2538135 , for installations based on the SAP_ECC schema
○ SAP Note 2538187 , for installations based on the SAP_S4H schema
For more information, see:
○ http://help.sap.com/hba Installation, Security, Configuration, and Operations Information
Administrator's Guide Configuration Steps Replicate Data (Side-by-Side Only)
○ http://help.sap.com/hana SAP HANA SAP HANA Options SAP HANA Real-Time
Replication SAP HANA Trigger-Based Data Replication Using SAP LT Replication Server System
Administration and Maintenance Information Configuration Information and Replication Concepts
( <Managing the Replication Process Using the SAP HANA Studio> and
<Important Transactions and Control Tables>)
3. Regardless of whether you implement SAP Marketing Cloud co-deployed or side-by-side with SAP
Customer Activity Repository, map the authoring schema SAP_CUAN to your particular physical database

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
114 PUBLIC Set Up the Applications
 schema that contains the SAP CRM tables. If the physical database schema is already named SAP_CUAN,
this schema mapping is not required.

Authoring Schema Physical Schema

SAP_CUAN <Name of Your Schema for Storing SAP

Marketing Cloud Data>

For more information, see http://help.sap.com/hana_platform Development and Modeling SAP

HANA Modeling Guide Importing Table Definitions and Data Map Authoring Schema to the Physical
Schema .

 Note

Every time you make changes to the schema mapping, the SAP HANA content must be redeployed.

You can do this using one of two methods:

○ Execute the /CAR/ACTIVATE_HANA_CONTENT report as described in SAP Note 2330386 .
○ Manually redeploy only those SAP HANA objects that are impacted by your schema mapping
change.

Side-by-Side Scenario (SLT)

1. Define client transformation rules for all the SAP Marketing Cloud tables that you plan to replicate.
In most cases, you need to apply transformation rules to map the client of the source SAP Marketing Cloud
system to the client on the target SAP Customer Activity Repository system.

 Caution

Transformation rules must be defined prior to replicating tables.

For more information, refer to one of the following:

○ Set Up SAP Client section in the Common Installation Guide.
○ http://help.sap.com/hana SAP HANA SAP HANA Options SAP HANA Real-Time Replication
SAP HANA Trigger-Based Data Replication Using SAP LT Replication Server System Administration
and Maintenance Information Important Transactions and Control Tables Data Transformation
Capabilities within SAP Landscape Transformation Replication Server
○ SAP Note 1733714
2. Read SAP Note 1897025 and replicate the tables listed in the .txt file attached to this SAP Note.
For more information, see http://help.sap.com/hana SAP HANA SAP HANA Options SAP HANA
Real-Time Replication SAP HANA Trigger-Based Data Replication Using SAP LT Replication Server
System Administration and Maintenance Information .

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 115
6.1.2.2 Configure SAP Smart Business for Multichannel
Sales Analytics

Do these procedures if you wish to use the SAP Smart Business for multichannel sales analytics cockpit. The
cockpit provides you with an overview of the most important key performance indicators for a category
manager. The KPI tiles are provided using the SAP Smart Business framework. They serve as access points to
analytical SAP Fiori apps.

Use

The steps in this section are optional and depend on your specific implementation requirements.

 Note

For more information about the cockpit, see the application help for SAP Customer Activity Repository at
https://help.sap.com/viewer/p/CARAB. Search for section SAP Smart Business for Multichannel Sales
Analytics.

6.1.2.2.1 Configure SAP Web Dispatcher for the SAP Smart

Business Modeler Apps

SAP Web Dispatcher lies between the Internet and your SAP system. It is the entry point for HTTP(s) requests
into your system. As a “software web switch”, SAP Web Dispatcher can reject or accept connections. It
contributes to security and also balances the load in your SAP system.

Where to Find Configuration Information

To find the SAP Web Dispatcher information for your SAP NetWeaver release, see the following:

● Central SAP Web Dispatcher note: 908097 SAP Web Dispatcher: Release, Installation, Patches,
Documentation
● Product documentation: https://help.sap.com/viewer/p/SAP_NETWEAVER. Choose your SAP NetWeaver
Platform and select the support package stack at the top right.
For configuration information, search for “Administration of the SAP Web Dispatcher”.
For a configuration example, search for “SAP Web Dispatcher Configuration Reference”.
For architecture information, search for “Architecture and Functions of the SAP Web Dispatcher”.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
116 PUBLIC Set Up the Applications
How to Configure SAP Web Dispatcher for the SAP Smart Business Modeler
Apps

The following parameters values are required:

● Source master data system: SAP ECC

Parameter wdisp/system_542 requires the following URL: /sap/is/retail/car/mcsa/odata
Resulting setting: wdisp/system_542 /sap/is/retail/car/mcsa/odata
● Source master data system: SAP S/4HANA
Parameter wdisp/system_542 requires the following URL: /sap/is/retail/car_s4h/mcsa/odata
Resulting setting: wdisp/system_542 /sap/is/retail/car_s4h/mcsa/odata

Other Solutions

If you use any other reverse proxy, see the manufacturer's documentation for more information.

6.1.2.3 Install Alternate Storage

You only need to implement this procedure if you plan on using the Table Content Aging report delivered with
SAP Customer Activity Repository. This report allows you to copy your transaction log (TLOG) data and its
extensions from your SAP HANA database to an alternate storage technology (such as SAP IQ or Apache
Hadoop), thereby reducing your total cost of hardware ownership.

Use

For more information, see SAP Help Portal at https://help.sap.com/viewer/p/CARAB <Version> Use
Application Help SAP Customer Activity Repository POS Data Transfer and Audit Implementing a POS
Transaction Data Storage Strategy Using the Table Content Aging Report .

 Note

If your scenario includes demand modeling and forecasting with the Unified Demand Forecast (UDF)
module, we recommend retaining the historical sales data in memory.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 117
Process Flow

In order to successfully install alternate storage, you must execute the following procedures:

1. Do one of the following:

○ Install and set up integration with SAP IQ, or
○ Install and set up integration with Apache Hadoop, or
○ Install and set up integration with SAP HANA Dynamic Tiering
2. Create the remote source in SAP HANA studio (not applicable for integration with SAP HANA Dynamic
Tiering).
3. Create the virtual table.
4. Set the deploy mode in SAP HANA Transport for ABAP.

6.1.2.3.1 Install and Set Up Integration with SAP IQ

You use these procedures to install and set up SAP IQ to support the Table Content Aging report
(transaction /CAR/TABLE_AGING) delivered with SAP Customer Activity Repository.

The SAP HANA database points to your SAP IQ database using SAP HANA smart data access (SDA), which
exposes data from SAP IQ remote sources as virtual tables.

For more information, see SAP Help Portal at https://help.sap.com/viewer/p/CARAB <your release> Use
Application Help SAP Customer Activity Repository POS Data Transfer and Audit Implementing a POS
Transaction Data Storage Strategy Using the Table Content Aging Report .

Install SAP IQ

A detailed procedure is described in the SAP IQ Installation and Update Guide.

For more information, see SAP Help Portal at https://help.sap.com/viewer/p/SAP_IQ Implement

Installation and Upgrade SAP IQ Installation and Update Guide for <your operating system> .

Configure SAP IQ

1. Allocate sufficient space into which your data will be loaded.

 Note

The default DBSpaces provided during installation are intended to be used for SAP IQ system
management. You should create your own DBSpace under the Main store with a DB File that is large
enough to satisfy your sizing requirements.

For more information, see SAP Help Portal at https://help.sap.com/viewer/p/SAP_IQ Use

Reference SAP IQ SQL Reference SQL Statements CREATE DBSPACE Statement .

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
118 PUBLIC Set Up the Applications
 2. Create an in-memory row-level versioning (RLV) store.
For more information, see SAP Help Portal at https://help.sap.com/viewer/p/SAP_IQ Operate
Administration SAP IQ Administration: In-Memory Row-Level Versioning About In-Memory Row-Level
Versioning .

 Note

Click View All if topic does not appear in initial list.

3. Create a database under the content created at the beginning of this procedure.

 Note

Ensure the following:

○ The SAP IQ stores are configured with a large enough cache configuration, main memory, and
temporary memory.
○ The page size should be set to 128KB.
○ The concurrency aligns with the amount of processes that will be triggered during the data copy.

For more information, see SAP Help Portal at https://help.sap.com/viewer/p/SAP_IQ Implement

Configuration Performance and Tuning Guide .
4. Create the following tables in the DBSpace created at the beginning of the procedure:
○ /POSDW/TLOGF
○ /POSDW/TLOGF_EXT
○ /POSDW/TLOGF_X
○ /POSDW/PLOGF

 Note

These tables should have the same structure as the tables in your SAP HANA system. One possible
way is to export the table structure via Export SQL on the SAP HANA side, and import it on the SAP IQ
side using the SQL console.

The SQL statement requires some modifications, such as:

○ Converting all the column names in the exported SQL statement to lower case (for example,
“RETAILSTOREID becomes “retailstoreid”).
You can simply convert the entire SQL statement into lower case and then only convert the table
name to upper case to keep the table name unchanged.
○ Renaming of NVARCHAR to VARCHAR.
○ Removing references to CS_* (for example, CS_FIXED).

5. Enable the RLV for the tables you just created.

6. Set the snapshot versioning property of the transaction to row-level.

 Example

set option Snapshot_Versioning = 'Row-level';

7. Enable connection blocking and set the blocking timeout threshold.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 119
  Example

set option blocking = 'On';

set option blocking_timeout = '0';

Install SAP IQ Drivers

Install and configure the ODBC database drivers required to connect to the remote source.

 Note

Each data source driver setup is described in its own section. The prerequisites are given as a simple guide;
you will need to consult the original driver documentation provided by the driver manufacturer for more
detailed information.

A detailed procedure is described in the SAP HANA Administration Guide.

For more information, see SAP Help Portal at http://help.sap.com/viewer/p/SAP_HANA_PLATFORM

Administration SAP HANA Administration Guide for SAP HANA Platform Data Access SAP HANA
Smart Data Access Setting Up ODBC Drivers SAP IQ ODBC Driver .

6.1.2.3.2 Install and Set Up Integration with Apache

Hadoop

You use these procedures to install and set up Apache Hadoop to support the Table Content Aging report
(transaction /CAR/TABLE_AGING) delivered with SAP Customer Activity Repository.

The SAP HANA database points to your Hadoop cluster using SAP HANA smart data access (SDA), which
exposes data from Hadoop remote sources as virtual tables.

For more information, see SAP Help Portal at http://help.sap.com/viewer/p/CARAB <Version> Use
Application Help SAP Customer Activity Repository POS Data Transfer and Audit Implementing a POS
Transaction Data Storage Strategy Using the Table Content Aging Report .

Process Flow

To successfully install and set up integration with Apache Hadoop, you must execute the following procedures:

1. Install Apache Hadoop.

2. Do one of the following:
○ Install and set up the Apache Hive ODBC driver, or
○ Install and set up the SAP HANA Spark controller.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
120 PUBLIC Set Up the Applications
 3. Create and partition tables in Apache Hive.
4. Create a NFS mount on SAP NetWeaver.

Install Apache Hadoop

According to the SAP HANA Administration Guide for SAP HANA Platform, SAP HANA smart data access is
supported by Hortonworks Distribution for Apache Hadoop: version 2.3 (supported on Intel-based hardware
platforms only).

For more information on integration between SAP HANA and Apache Hadoop, see SAP Help Portal at http://
help.sap.com/viewer/p/SAP_HANA_PLATFORM Administration SAP HANA Administration Guide for
SAP HANA Platform Data Access SAP HANA Smart Data Access .

For more information on installing Apache Hadoop, see http://docs.hortonworks.com All HDP 2.3
HDP 2.3.0 (GA) .

Install and Set Up Apache Hive ODBC Driver

 Note

Integration between SAP HANA and Apache Hadoop requires either an Apache Hive ODBC driver or an
SAP HANA Spark controller.

Implement this procedure only if you wish to integrate SAP HANA with Apache Hadoop via the Apache Hive
ODBC driver.

1. According to the SAP HANA Administration Guide for SAP HANA Platform, SAP HANA smart data access is
supported by Hortonworks Distribution for Apache Hadoop: version 2.3 (This includes Apache Hadoop
version 1.0.3 and Apache Hive 0.9.0; supported on Intel-based hardware platforms only).
For more information on integration between SAP HANA and Apache Hadoop, see SAP Help Portal at
http://help.sap.com/viewer/p/SAP_HANA_PLATFORM Administration SAP HANA Administration
Guide for SAP HANA Platform Data Access SAP HANA Smart Data Access .
For more information on installing the Apache Hive ODBC driver, see http://docs.hortonworks.com All
HDP 2.3 HDP 2.3.0 (GA) .
2. Set up the driver as described in the SAP HANA Administration Guide for SAP HANA Platform at http://
help.sap.com/viewer/p/SAP_HANA_PLATFORM Administration SAP HANA Administration Guide for
SAP HANA Platform Data Access SAP HANA Hadoop Integration .

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 121
Install and Set Up the SAP HANA Spark Controller

 Note

Integration between SAP HANA and Apache Hadoop requires either an Apache Hive ODBC driver or an
SAP HANA Spark controller.

Implement this procedure only if you wish to integrate SAP HANA with Apache Hadoop via the SAP HANA
Spark controller.

1. Confirm the right combination of versions required between SAP HANA, Apache Spark, and the SAP HANA
Spark controller. Use the SAP HANA Spark Controller Compatibility Matrix to do this. This document is
available under https://help.sap.com/viewer/p/SAP_HANA_SPARK_CONTROLLER. Navigate to
Additional Information SAP HANA Spark Controller Compatibility Matrix .
2. Install and set up the SAP HANA Spark controller as described in SAP Note 2273047 .

For more information on installing and setting up the SAP HANA Spark controller, see SAP Help Portal at
http://help.sap.com/viewer/p/SAP_HANA_PLATFORM Administration SAP HANA Administration Guide
for SAP HANA Platform Data Access SAP HANA Hadoop Integration .

Create and Partition Tables

Create the SAP schema, tables, and table partitions as described in SAP Note 2317597 .

Create a NFS Mount on SAP NetWeaver

The TLOG data and its extensions are copied from your SAP HANA 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).

 Note

The following steps are only guidelines which provide an example of how to mount Network File System
(NFS) on an SAP NetWeaver Linux-based client.

1. Make sure the NFS client is installed based on the examples provided:

Operating System Command

Red Hat, CentOS sudo yum install nfs-utils

Ubuntu sudo apt-get install nfs-common

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
122 PUBLIC Set Up the Applications
 Operating System Command

SUSE sudo zypper install nfs-client

2. List the NFS shares exported on the server.

Example
showmount -e <host>
3. Set up a mount point for an NFS share.
Example
sudo mkdir <folder>

 Note

You must ensure that the folder paths share the same naming conventions, as follows:

Temporary data folder /tmp/tct_csv_out/temp

Data folder /tmp/tct_csv_out/data

4. Mount the cluster using NFS.

Example
sudo mount -o hard, nolock <host> <folder>

On your HDFS, the different tables are stored under a folder using the following convention:

<data directory>/<schema>/<table>/<businessdaydate=partition_value>/{files}

On the SAP NetWeaver file system, the Hadoop files are stored under a physical path and file name that is
derived from a customer-definable logical path or file name. The configuration is provided via the FILE
transaction. Inside the FILE transaction, you also need to make use of parameters PARAM_1 and PARAM_2.
PARAM_1 will be populated during runtime by the program (generated file name) and PARAM_2 will be
populated by the program during runtime <schema>/<table>/<businessdaydate=partition_value>.

Example (Data Directory)

If the Hadoop data files are stored in Unix/Linux folder ,<schema>/<table>/businessdaydate=partition_value/

{files}PARAM_1.CSV and physical directory /tmp/tct_csv_out/data/hdp/apps/hive/warehouse/
<PARAM_2><FILENAME>.

You create the following logical path in the FILE transaction as follows:

Logical path /CAR/HDFS_DATA

Name HDFS Data

Syntax group UNIX

Physical path /tmp/tct_csv_out/data/hdp/apps/hive/

warehouse/<PARAM_2><FILENAME>

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 123
You create the following logical file in the FILE transaction as follows:

Logical file /CAR/HDFS_DATA

Name HDFS Data

Physical file <PARAM_1>.CSV

Data format WK1

Application area IS

Logical path /CAR/HDFS_DATA

Example (Temporary Directory)

/tmp/tct_csv_out/data/hdp/apps/hive/warehouse/On top of the Hadoop data files, you also need to provide
a temporary directory in which the program will populate script files and also temporarily store data files to be
compressed.

If the temporary files are stored in Unix/Linux folder /tmp/tct_csv_out/temp/{files}, you create the
following logical path in the FILE transaction as follows:

Logical path /CAR/HDFS_TEMP

Name HDFS Temp

Syntax group UNIX

Physical path /tmp/tct_csv_out/temp/<FILENAME>

You create the following logical file in the FILE transaction as follows:

Logical file /CAR/HDFS_TEMP

Name HDFS Temp

Physical file <PARAM_1>.SH

Data format

Application area IS

Logical path /CAR/HDFS_TEMP

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
124 PUBLIC Set Up the Applications
6.1.2.3.3 Install and Set Up Integration with SAP HANA
Dynamic Tiering

You use these procedures to install and set up SAP HANA Dynamic Tiering to support the Table Content Aging
report (transaction /CAR/TABLE_AGING) delivered with SAP Customer Activity Repository.

SAP HANA Dynamic Tiering adds the SAP HANA dynamic tiering service to your SAP HANA system. You use
this service to create the extended store and extended tables. Extended tables behave like all other SAP HANA
tables, but their data resides in the disk-based extended store.

For more information, see SAP Help Portal at http://help.sap.com/viewer/p/CARAB <your release> Use
Application Help SAP Customer Activity Repository POS Data Transfer and Audit Implementing a POS
Transaction Data Storage Strategy Using the Table Content Aging Report .

Install SAP HANA Dynamic Tiering

A detailed procedure is described in the SAP HANA Dynamic Tiering: Installation and Update Guide.

For more information, see SAP Help Portal at http://help.sap.com/hana_options_dt Implement

Installation and Upgrade .

Create Extended Storage

A detailed procedure is described in the SAP HANA Dynamic Tiering: Administration Guide.

For more information, see SAP Help Portal at http://help.sap.com/hana_options_dt Operate

Administration SAP HANA Dynamic Tiering: Administration Guide and consult the following subsections:

● System Administration Managing Extended Storage

● System Administration Managing Tables Extended Store Tables Convert HANA Tables to Extended
Store Tables Using the SAP HANA Cockpit

6.1.2.3.4 Create the Remote Source in SAP HANA Studio

 Note

This step is not applicable if you are integrating the alternate storage feature with SAP HANA Dynamic
Tiering.

Create a remote source by selecting the appropriate adapter and configuring the connection properties and
user credentials.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 125
A detailed procedure is described in the SAP HANA Administration Guide for SAP HANA Platform.

For more information, see SAP Help Portal at http://help.sap.com/viewer/p/SAP_HANA_PLATFORM

Administration SAP HANA Administration Guide for SAP HANA Platform Data Access SAP HANA
Smart Data Access Managing Remote Sources Creating a Remote Source .

6.1.2.3.5 Create the Virtual Table

Create the following virtual tables to access the data stored in remote tables:

Virtual Table Remote Table

VT_TLOGF_NLS /POSDW/TLOGF

VT_TLOGF_X_NLS /POSDW/TLOGF_X

VT_TLOGF_EXT_NLS /POSDW/TLOGF_EXT

VT_PLOGF_NLS /POSDW/PLOGF

A detailed procedure is described in the SAP HANA Administration Guide for SAP HANA Platform.

For more information, see SAP Help Portal at http://help.sap.com/viewer/p/SAP_HANA_PLATFORM

Administration SAP HANA Administration Guide for SAP HANA Platform Data Access SAP HANA
Smart Data Access Managing Virtual Tables .

6.1.2.3.6 Activate Alternate Storage

1. In your back-end system, execute report /CAR/ACTIVATE_HTA.

2. Confirm or set the following:
○ In the ECC Mode section, choose the relevant ECC mode for your system.
○ In the External Systems section, choose Nearline Storage.
3. Press Execute.

This deploys package sap.is.retail.car.nls for ECC mode SAP ERP, or sap.is.retail.car_s4h.nls
for ECC mode S/4HANA. Each package contains views that combine TLOG data from SAP HANA with TLOG
data from the alternate storage system.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
126 PUBLIC Set Up the Applications
6.1.2.4 Adjust Totals When Excluding Post-Voided
Transactions

This procedure is relevant for the POS Data Transfer and Audit module. You must perform the procedure if you
have existing transactional data prior to the upgrade.

Procedure

1. Run transaction /POSDW/REFI against all relevant stores and posting dates to adjust the displayed totals
when post-voided transactions are filtered out of search results.

 Caution

This process is time- and performance-intensive. We recommend that you carefully choose the best
time when to run the transaction.

6.1.2.5 Partition /POSDW/TLOGF and Aggregation Tables

If you wish to use the POS Data Transfer and Audit module, we recommend that you partition the /POSDW/
TLOGF table and several aggregation tables (such as /POSDW/TLOGF_EXT). This improves standard database
operations (such as inserting, updating, deleting, and reading) and mass operations (such as archiving or index
merging).

Use

SAP Customer Activity Repository contains the POS Data Transfer and Audit module, which is used to receive a
large volume of data from your connected stores. POS Data Transfer and Audit, or more specifically, its POS
Inbound Processing Engine (PIPE), processes the incoming transactions and stores them in the /POSDW/
TLOGF table.

Since every point-of-sale transaction line item is stored as a separate row in the /POSDW/TLOGF table, the table
can quickly grow to become very large and should therefore be partitioned.

Also, you can select to store extension segments in a dedicated /POSDW/TLOGF_EXT table using the Store
Extensions in Separate Table option of the Define General Settings Customizing activity. The /POSDW/
TLOGF_EXT table should be partitioned in the same way as the /POSDW/TLOGF table.

For more information about extension segments, see the Appendix section in the SAP Customer Activity
Repository Administration Guide.

 Note

Partitioning is typically used in distributed systems, but it may also be beneficial for single-host systems.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 127
Procedure

1. Read the Table Partitioning in the SAP HANA Database section of the SAP HANA Administration Guide for
SAP HANA Platform at https://help.sap.com/viewer/p/SAP_HANA_PLATFORM.
2. Plan your partition specifications in accordance to the following guidelines:
○ A single partition should not contain more than 1 billion rows.
○ The total number of partitions of a single table should not exceed 1000.
○ Because the actual act of partitioning a table also uses system resources, do not start partitioning
the /POSDW/TLOGF table until its volume has surpassed 250 million rows.
3. Partition the /POSDW/TLOGF table as required according to SAP Note 1719282 (POS TLOG Table
Partitioning Information).
4. Depending on your requirements, you may also optionally partition the following tables. The same SAP
Note is relevant for these as well.
○ /POSDW/TLOGF_EXT
○ /POSDW/AGGR01
○ /POSDW/ACCRTB

6.1.2.6 Complete UDF Setup

Set up the Unified Demand Forecast (UDF) module in SAP Customer Activity Repository to enable demand
modeling and forecasting for different scenarios and consuming applications. To be able to use UDF, you must
at least do the mandatory steps. We also point you to helpful performance information for UDF.

Use

UDF supports the following scenarios:

Scenario Set Up and Configure UDF

SAP Fiori apps for demand forecasting: Mandatory for all the apps (Analyze Forecast, Adjust
Forecast, Manage Demand Influencing Factors, Manage
Alerts)

SAP Replenishment Planning Mandatory

SAP Promotion Management Mandatory (if you want to use UDF to generate what-if fore­
casts)

Optional (without what-if forecasts)

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
128 PUBLIC Set Up the Applications
 Scenario Set Up and Configure UDF

SAP Assortment Planning Optional in general, but depends on your customer scenario

SAP Allocation Management Both applications offer functionality that can use UDF fore­
cast data. For more information, see SAP Help Portal at
https://help.sap.com/viewer/p/CARAB and consult the Ap­
plication Help and Administration Guide of either application.

SAP Merchandise Planning There is currently no integration between UDF and SAP
Merchandise Planning.

Prerequisites

● You have configured the DDF module as described in Configure Demand Data Foundation.
● You have set up the users, roles, and privileges for UDF as described in Verify Authorizations for Unified
Demand Forecast (UDF) [page 84].

Procedure

 Tip

If you encounter issues during the setup, see the Troubleshooting [page 190] section for possible solutions.

Perform Mandatory Setup Steps

1. Log on to your ABAP back-end system.
2. Only relevant if you are upgrading from a release prior to SAP Customer Activity Repository 3.0 FP1
(released as part of SAP Customer Activity Repository applications bundle 2.0 SPS2):
Read SAP Note 2449880 to decide whether you need to implement the redesigned Customizing for
modeling and forecasting.
3. In transaction SPRO, do the Customizing for UDF that is required for all scenarios:

 Note

For more information about each Customizing activity, see the accompanying system documentation.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 129
 Customizing for UDF (All Scenarios)

Do These Steps Here in Customizing

Define the time series source with Cross-Application Components Demand Data Foundation Imported Data
historical demand data that you Time Series Define Time Series for Key Figure Configuration
wish to import to DDF.
 Caution
Additional Customizing for SAP Promotion Management

If you wish to use what-if forecasts in SAP Promotion Management, addi­

tionally configure this second activity:

Cross-Application Components Demand Data Foundation Data

Maintenance Define Time Series Source

Define general settings for modeling Cross-Application Components Demand Data Foundation Modeling and
and forecasting. Forecasting :

See all activities under this node.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
130 PUBLIC Set Up the Applications
 Do These Steps Here in Customizing

Review the default configuration of Cross-Application Components Demand Data Foundation Basic Settings
the UDF exceptions; if necessary, Exception Management :
adjust the configuration.
○ Maintain Configuration Data for High Level Exceptions
1. Execute the activity to display the table of exceptions (messages).
2. Filter the table by the application area /DMF/UDF_BUSINESS. This is
where you find the business exceptions for UDF.
3. In the Default Priority column, check the setting for each exception. If
required, switch to edit mode and adjust the setting for your scenario.
Typically, business exceptions have the effect that the affected product
location is not processed.
If you wish to deactivate an exception, set the priority to Not Relevant/
Switched Off.

 Note
If you wish to display details for an exception, select it in the table
and double-click Assignment Business Area.

○ Maintain Configuration Data for Low Level Exceptions:

(Optional) This activity works similarly to the previous one. Here you can
find the technical exceptions for UDF in the application area /DMF/
UDF_TECHNICAL.
Each technical exception is already assigned to a business exception. Tech­
nical exceptions typically indicate issues that need to be solved by system
administrators.

 Tip
We recommend that you keep the default priorities.

○ Define Customer-Specific Replacement Messages:

(Optional) Configure this activity if you wish to use different message texts
than the ones provided by default.
○ Define Customizable Message Status:
(Optional) Configure this activity if you wish to use different or more sta­
tuses than the ones provided by default.

4. Check and, if necessary, change the setting for how the covariance matrix is generated during modeling.
1. Navigate to Cross-Application Components Demand Data Foundation Modeling and Forecasting
Define Modeling Control Settings and execute the Customizing activity.
2. Check that the MOD_COV_REDUCED parameter is configured correctly for your scenario.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 131
 The parameter controls whether the “full covariance matrix” (default) or the “reduced covariance
matrix” should be generated:

For These Scenarios Use this Setting

You want to use UDF to generate The full covariance matrix is mandatory for the FCI.
the forecast confidence index
(FCI) for SAP Promotion  Note
Management. Be aware that the generation of the full covariance matrix is perform­
ance-intensive.

Correct setting of MOD_COV_REDUCED:

○ Either the parameter is not listed at all under Configuration Type Code.
○ Or the parameter is listed under Configuration Type Code and the
Configuration Value is empty.

Either setting activates the default (full covariance matrix is generated).

All other scenarios, that is: The reduced covariance matrix is sufficient for those scenarios and also
saves runtime.
○ You want to calculate hier­
archical priors (HPRs). Correct setting of MOD_COV_REDUCED:
○ You want to use SAP
○ The parameter is listed under Configuration Type Code and the
Promotion Management, but
Configuration Value is set to X.
without generating the FCI.
○ You want to use other con­ This setting overrides the default.
suming applications, but not
SAP Promotion
Management.

Make any other settings as required for your scenario and save your changes.

5. Configure the modeling and forecasting features that you wish to use in your scenario.
See the Configure Unified Demand Forecast (UDF) section of the SAP Customer Activity Repository
Administration Guide.

 Note

You can find detailed configuration information for a number of UDF features in this section. Use it to
fine-tune UDF for your customer scenario and requirements.

6. Set up your forecast scenario for best performance.

See the following sections of the SAP Customer Activity Repository Administration Guide:

 Tip

We highly recommend that you read this information carefully and implement any performance tips
that are relevant for your scenario.

1. Optimize the performance of modeling, forecasting, and the calculation of hierarchical priors. See
Optimize UDF Performance.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
132 PUBLIC Set Up the Applications
 2. Set up routines for regular data housekeeping. For example, schedule reports to regularly delete
obsolete data. See Performance — Optimize the Data Lifecycle and Administration Tools.
7. Set up the integration and data replication between your source master data system and your SAP
Customer Activity Repository system.
See the following sections of the SAP Customer Activity Repository Administration Guide:
○ For integration information for UDF and DDF, see Introduction to SAP Customer Activity Repository and
Configure DDF Integration Scenarios.
○ For setup information on the data replication framework (DRF, transaction DRFOUT) for replicating
master and transactional data, see Configure Data Replication from SAP ERP and SAP S/4HANA to
DDF.
8. Verify that pricing data is replicated correctly:

 Note

As of SAP Customer Activity Repository applications bundle 5.0, the default table for pricing data has
changed:
○ New default table: /DMF/PRC (Product Pricing Data)
○ Old default table: /DMF/PRODLOC_PRC (Product Location Price Data)

All UDF features that require pricing data use the new table.

Check your data replication settings. Make sure the pricing data from the source master data system is
replicated to the new table /DMF/PRC. For instructions, see the Enable Extended Sales Pricing Data section
in the SAP Customer Activity Repository Administration Guide.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 133
9. In the future development of your scenario, you might implement custom code or change UDF output
tables. Carefully read the following information to ensure that such adaptations will continue to function
correctly for your scenario:

 Caution

With the release of SAP Customer Activity Repository 4.0 FPS03, the UDF database storage design
was refactored to enhance system performance. Be aware that as a result, the following open SQL
statements are no longer supported for the following UDF tables:

Do not use any of these SQL statements... … with any of these tables

UPDATE FROM wa /DMF/UMD_TSD

UPDATE FROM TABLE itab /DMF/UMD_TS

DELETE FROM wa /DMF/UFC_TSD

DELETE FROM TABLE itab /DMF/UFC_TS

DELETE WHERE UP TO N ROWS /DMF/UFC_TRC

/DMF/UMD_PAR
MODIFY FROM wa
/DMF/UMD_PAR_COV
MODIFY FROM TABLE itab
/DMF/UMD_PRI
ORDER BY PRIMARY KEY
/DMF/TS_PS
SELECT SINGLE FOR UPDATE

Usage of Table Buffer

EXPORT/IMPORT

Perform Optional Setup Steps

If relevant for your scenario, implement any of the following additional options:

1. (Recommended) Set up the apps for demand forecasting.

See the Set Up SAP Fiori Apps for SAP Customer Activity Repository [page 135] section.
2. (Recommended) Extend the existing service Calculate Hierarchical Priors with a new option. With this
option, you can run the service in delta mode, where the hierarchical priors (HPRs) are only calculated for
newly listed product locations. See SAP Note 2996880 (Calculate hierarchical priors (delta run)).
3. Verify the data replication results that are relevant for UDF:
For example, verify that the following data is replicated correctly from the source master data system:
product hierarchy, location hierarchy, product prices, delisting information for product locations
(table /DMF/PRODLOC_TD), closing days and public holidays for locations (tables /DMF/LOC, /DMF/
TSTRM, /DMF/LOC_TSTRM, /DMF/TSTRM_DAY).

 Note

For information on the data replication, see Configure Data Replication from SAP ERP and SAP S/
4HANA to DDF section in the SAP Customer Activity Repository Administration Guide.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
134 PUBLIC Set Up the Applications
 4. To achieve a high forecast accuracy right from the beginning, provide ample promotional data:
○ Load the historical promotions into UDF (if this data is available).
○ Define user DIFs in the past to account for historical promotions.
○ Check the offer lift type codes of offers that were created in SAP Promotion Management and
transferred (translated) to UDF. In particular, check for the offer lift type codes 98 and 99 and solve the
underlying issues. For more information, see Verify Integration with SAP Promotion Management.
5. Implement SAP Note 2161484 : Here you can find information about an ABAP validation report that you
can use to check the input data for modeling and forecasting and solve potential issues.
6. Implement SAP Note 2560853 : This note is relevant if you are upgrading from a release prior to SAP
Customer Activity Repository applications bundle 2.0 SPS03 (SAP Customer Activity Repository 3.0 FP2)
and have existing data in the modeling and forecasting tables. The note explains how to update the time
granularity entries in UDF output tables to prevent modeling and forecasting issues.

6.1.2.7 Set Up SAP Fiori Apps for SAP Customer Activity

Repository

Perform common setup steps that are required for all the apps in SAP Customer Activity Repository. For
example, check the prerequisites and prepare the system landscape. Then set up the apps that you want to use
in your scenario.

Context

For a list of the apps included in SAP Customer Activity Repository, see the SAP Fiori for SAP Customer Activity
Repository section of the application help.

 Note

Depending on your scenario, some of the following prerequisites might already be available in your system
landscape. If so, you can skip the corresponding step.

 Tip

For a helpful graphical overview, see SAP Fiori: App Implementation - UI Content and Authorization
Concept and consult the Dependencies between SAP Fiori UI Entities, OData Services, and Authorizations
section.

General Prerequisites

● SAP Fiori front-end server: You have installed the SAP FIORI FRONT-END SERVER version required for
this release. For the minimum version, see section Upgrade the Prerequisites [page 18] and consult the
information under Common Prerequisites SAP Fiori .

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 135
  Tip

There is a quick way how you can check the SAPUI5 version currently installed in your system. See SAP
Note 2282103 (How to check the version of SAPUI5 you have installed).

● SAP Fiori launchpad: You have set up the launchpad as described in the Common Installation Guide, in
section Configure SAP Fiori Launchpad.
● SAP Fiori launchpad designer: You have set up the designer as described in the Initial Setup of the
Launchpad Designer section in the product documentation of SAP Fiori launchpad. Depending on your
front-end system, select a different version at the top.
● SAP Gateway: You have done the general SAP Gateway configuration and you have activated the common
OData services and Internet Communication Framework (ICF) services. See the following:
○ Common Installation Guide, section Configure SAP Gateway, including all subsections
○ SAP Note 1560585 (SAP Gateway 2.0 Release Note)

Prerequisites Specific to SAP Customer Activity Repository applications

bundle

1. You have installed the correct SAP RTL AFL FOR SAP HANA revision in the SAP HANA database. See
section Download and Install SAP RTL AFL FOR SAP HANA (Mandatory) [page 67].
2. You have upgraded the back-end product version. This step ensures that all app features of the current
release are supported by the back-end. See section Upgrade SAP CARAB Back-End Product Version [page
74].
3. You have upgraded the front-end product version. This step ensures that you get the newest app UIs on the
front-end. See section Upgrade SAP FIORI FOR SAP CARAB Front-End Product Version [page 77].
4. You have implemented all the SAP Notes (corrections) for the apps that you wish to set up. See section
Implement SAP Notes for the Upgrade [page 29] and consult the release information notes (RINs)
mentioned there and also the table for SAP Customer Activity Repository.
5. You have performed all mandatory setup steps for SAP Customer Activity Repository. For example, this
includes activating the OData services for the apps or calculating the SAPUI5 application index. For a
complete list of the steps, see section Core (Mandatory for All Applications) [page 81].
6. You have set up the system connections:
○ You have set up dedicated RFC connections between your front-end system and your back-end
system, and between your front-end system and your source master data system.
○ You have defined a system alias for your back-end system.
7. (Optional) These prerequisites apply if you wish to set up any of the apps for demand forecasting (Analyze
Forecast, Adjust Forecast, Manage Demand Influencing Factors, Manage Alerts):
1. You have set up Unified Demand Forecast (UDF). UDF is the common forecasting engine in the back-
end. You must at least do the mandatory setup steps for UDF. See section Complete UDF Setup [page
128].
2. (Optional, recommended) You have enabled the in-app help with the underlying Web Assistant
framework. See section Enable In-App Help (Web Assistant) [page 325].

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
136 PUBLIC Set Up the Applications
  Note

After a successful setup, you can see the Help icon (question mark) at the top of each app. Simply
choose this icon to display on-screen help directly in the app and easily call up a detailed app
description.

3. You are aware of the following configuration changes as of SAP Customer Activity Repository
applications bundle 5.0:
○ There are no more configuration steps in transaction LPD_CUST (Launchpad Customizing).
○ When configuring the target mapping for an app tile in the SAP Fiori launchpad designer, you must
now select the application type SAPUI5 Fiori App. The application type SAP Fiori App using
LPD_CUST, which was required in previous releases, is no longer supported. For more information,
see SAP Note 2614740 (Usage of LPD_CUST as Application Type in FLP Deprecated).
The setup procedures for the apps will lead you through the correct steps.
8. (Optional) If you wish to set up the apps included in OAA, follow the steps in section Configure
Omnichannel Article Availability and Sourcing for Use with SAP Customer Activity Repository.

Result

After you have prepared the system landscape in this way, you can now set up the apps that you wish to use.

 Tip

If you encounter issues during the setup, see section Troubleshooting SAP Fiori Apps in the SAP Fiori:
Operations documentation.

Set Up the Analyze Forecast App (Upgrade Scenarios) [page 138]

Upgrade the Analyze Forecast app to the current release. Several steps are required on the back-end
and the front-end.

Set Up the Adjust Forecast App (Upgrade Scenarios) [page 139]

Upgrade the Adjust Forecast app and the related tiles Forecast Correction Overlapping Rules and
Forecast Correction Classification to the current release. Several steps are required on the back-end
and the front-end.

Set Up the Manage Demand Influencing Factors App (Upgrade Scenarios) [page 140]
Upgrade the Manage Demand Influencing Factors app and the related tile Demand Influencing Factors
Library to the current release. Several steps are required on the back-end and the front-end.

Set Up the Manage Alerts App [page 140]

Perform several tasks on the front-end server and the back-end server to set up the transactional app
Manage Alerts. This is one of the apps for demand forecasting (UDF) included in SAP Customer Activity
Repository.

Set Up the Demand Data Foundation (DDF) Apps [page 143]

Do this procedure to set up the DDF apps for standalone scenarios. The DDF apps are: Configure
Distribution Curves, Manage Location Clusters, Manage Product Attributes, Manage Product Groups,
Manage Promotional Offers. To access any of these apps, you need to assign the required role(s) to your
front-end user. This gives you access to the relevant business catalogs and business catalog groups so
that you can then open the apps in SAP Fiori launchpad.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 137
6.1.2.7.1 Set Up the Analyze Forecast App (Upgrade
Scenarios)

Upgrade the Analyze Forecast app to the current release. Several steps are required on the back-end and the
front-end.

Context

This app is one of the “apps for demand forecasting”, a group of forecast-related apps delivered with SAP
Customer Activity Repository. All apps for demand forecasting have the following in common:

● The forecasting engine in the back-end is Unified Demand Forecast (UDF). The UDF application function
library (delivered via the SAP RTL AFL FOR SAP HANA component) runs directly in the SAP HANA
database.
● Cross-navigation is supported. For example, users can navigate directly between Analyze Forecast, Adjust
Forecast, and Manage Demand Influencing Factors.

Procedure

 Note

SAP Customer Activity Repository applications bundle 5.0 is a new major release, providing a new back-end
product version and a new front-end product version. You must therefore perform a new setup of the app,
irrespective of your upgrade scenario.

For prerequisites and step-by-step instructions, see the Set Up the Analyze Forecast App section of the
Common Installation Guide.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
138 PUBLIC Set Up the Applications
6.1.2.7.2 Set Up the Adjust Forecast App (Upgrade
Scenarios)

Upgrade the Adjust Forecast app and the related tiles Forecast Correction Overlapping Rules and Forecast
Correction Classification to the current release. Several steps are required on the back-end and the front-end.

Context

This app is one of the “apps for demand forecasting”, a group of forecast-related apps delivered with SAP
Customer Activity Repository. All apps for demand forecasting have the following in common:

● The forecasting engine in the back-end is Unified Demand Forecast (UDF). The UDF application function
library (delivered via the SAP RTL AFL FOR SAP HANA component) runs directly in the SAP HANA
database.
● Cross-navigation is supported. For example, users can navigate directly between Analyze Forecast, Adjust
Forecast, and Manage Demand Influencing Factors.

Procedure

 Note

SAP Customer Activity Repository applications bundle 5.0 is a new major release, providing a new back-end
product version and a new front-end product version. You must therefore perform a new setup of the app,
irrespective of your upgrade scenario.

For prerequisites and step-by-step instructions, see the Set Up the Adjust Forecast App section of the Common
Installation Guide.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 139
6.1.2.7.3 Set Up the Manage Demand Influencing Factors
App (Upgrade Scenarios)

Upgrade the Manage Demand Influencing Factors app and the related tile Demand Influencing Factors Library to
the current release. Several steps are required on the back-end and the front-end.

Context

This app is one of the “apps for demand forecasting”, a group of forecast-related apps delivered with SAP
Customer Activity Repository. All apps for demand forecasting have the following in common:

● The forecasting engine in the back-end is Unified Demand Forecast (UDF). The UDF application function
library (delivered via the SAP RTL AFL FOR SAP HANA component) runs directly in the SAP HANA
database.
● Cross-navigation is supported. For example, users can navigate directly between Analyze Forecast, Adjust
Forecast, and Manage Demand Influencing Factors.

Procedure

 Note

SAP Customer Activity Repository applications bundle 5.0 is a new major release, providing a new back-end
product version and a new front-end product version. You must therefore perform a new setup of the app,
irrespective of your upgrade scenario.

For prerequisites and step-by-step instructions, see the Set Up the Manage Demand Influencing Factors App
section of the Common Installation Guide.

6.1.2.7.4 Set Up the Manage Alerts App

Perform several tasks on the front-end server and the back-end server to set up the transactional app Manage
Alerts. This is one of the apps for demand forecasting (UDF) included in SAP Customer Activity Repository.

Context

The Manage Alerts app supports different scenarios and consuming applications, such as SAP Replenishment
Planning. The app enables demand planners to review, manage and change status of alerts for High Forecast
alert type.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
140 PUBLIC Set Up the Applications
Prerequisites

● You have set up Unified Demand Forecast as described in Complete UDF Setup [page 128].
● You have verified the prerequisites and prepared the system landscape as described in Set Up SAP Fiori
Apps for SAP Customer Activity Repository [page 135].
● You know where to find additional information on Manage Alerts if necessary:
○ Technical details for each delivery of the app are available in the SAP Fiori apps reference library. For
the latest delivery (latest wave), see https://fioriappslibrary.hana.ondemand.com/sap/fix/
externalViewer/index.html#?appId=F5163.
○ If you need information on the app features see https://help.sap.com/viewer/p/CARAB. Choose your
version at the top, open the application help for SAP Customer Activity Repository, and search for
section Manage Alerts.

Generate and Maintain Alerts

● You can run the Generate Alerts report to generate alerts. All the alerts are created with the status New. You
can access the Generate Alerts report either in the system on the SAP Easy Access Menu screen
(transaction /DMF/ALERTS_GEN) or from the SAP Fiori Launchpad (Generate Alerts tile).
● You can use the Purging of Alerts report to delete obsolete alerts from the database. You can access the
Purging of Alerts report either in the system on the SAP Easy Access Menu screen (transaction /DMF/
ALERTS_PURGE) or from the SAP Fiori Launchpad (Purge Alerts tile).

Define Alert Statuses

You can add, maintain and delete alert statuses using the Customizing activity Define Alert Statuses in
Customizing for Cross-Application Components under Demand Data Foundation Basic Settings
Exception Management . Several standard statuses are available by default. You can also add custom statuses
based on your scenario.

Verify that ICF Services are Active

Context
After an upgrade, you must ensure that the Internet Communication Framework (ICF) services required for the
app are still active.

Procedure
1. Log on to your front-end server.
2. Execute transaction SICF.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 141
3. In the Define Services screen, make the following selections:
○ Hierarchy Type: SERVICE
○ Virtual Host: DEFAULT_HOST
○ Service Path: /sap/bc/ui5_ui5/sap/rtlplngalrtman
4. Choose Execute ( F8 ).
5. Under Virtual Hosts / Services, double-click the rtlplngalrtman service to open the Create/Change a
Service screen.
6. To activate a service, choose Service/Host Activate .

 Note

You can check the activation status by selecting the service and opening the context menu. If the
Activate Service option is grayed out, this means the service is already active.

7. Repeat steps 3 to 6, this time using /sap/bc/ui5_ui5/sap/udfreuse/ as the service path.

8. Repeat steps 3 to 6, this time using /sap/bc/ui5_ui5/sap/nw_aps_chd_lib/ as the service path.

Verify that OData Services are Active

1. See section Verify that OData Services are Active [page 101] and consult the table for SAP Customer
Activity Repository.
2. Make sure that all mandatory OData services for the app are active.

Front-End Server

Component Technical Name

OData Service (Version Number) /DMF/MANAGE_RTLPLNG_ALERTS_SRV (1)

Re-Use Component Technical Name

OData Service (Version Number) APS_CHANGE_DOCUMENTS_SRV (1)

Enable the App for SAP Fiori Launchpad

Context

To be able to access the app from the SAP Fiori launchpad, your front-end system user must have the
necessary role(s) assigned. This allows you to access the business catalogs and technical catalogs required for
to access the app.

The app requires the following business role SAP_DPL_TCR_T and technical catalog.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
142 PUBLIC Set Up the Applications
Front End Server: Catalog Details

Component Technical Name

Technical Catalog SAP_DPL_TC_T

 Note

You can select the Manage Alerts tile manually from the technical catalog to add it to the Fiori launchpad.

Procedure
1. Log on to your front-end system.
2. Execute transaction SU01 to open the User Maintenance screen.
3. Enter your front-end user name in the User field and choose Change.
4. On the Roles tab, assign the (SAP_DPL_TCR_T) role to your user.
5. Save your changes.

 Tip

If you already have an SAP Fiori launchpad open, clear your browser cache or you won't be able to see
the changes.

Back-End Server: Set Up Authorizations

Context
For the Manage Alerts app, the following authorization objects are relevant:

Authorization Object
Authorization Object Description Field Value Field Description

/DMF/MNGAT
Authorization to dis­ ACTVT Display Activity

play and change alert

Maintain
status by using the
Manage Alerts app.

6.1.2.7.5 Set Up the Demand Data Foundation (DDF) Apps

Do this procedure to set up the DDF apps for standalone scenarios. The DDF apps are: Configure Distribution
Curves, Manage Location Clusters, Manage Product Attributes, Manage Product Groups, Manage Promotional
Offers. To access any of these apps, you need to assign the required role(s) to your front-end user. This gives
you access to the relevant business catalogs and business catalog groups so that you can then open the apps
in SAP Fiori launchpad.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 143
Context

The DDF apps are available as part of SAP Customer Activity Repository. They support different scenarios and
consuming applications.

Different Scenarios for DDF Apps

● Standalone scenarios: You can use the apps standalone, that is, to support generic scenarios in SAP
Customer Activity Repository.
● Integrated scenarios: Or you can integrate the apps with the consuming application installed on top of
SAP Customer Activity Repository (for example, SAP Assortment Planning, SAP Allocation Management,
or SAP Promotion Management).

 Note

Some apps support only specific consuming applications. For more information, see the product
documentation of the application that you wish to use.

Procedure

 Note

The steps are always the same, regardless of how many of the DDF apps you wish to use.

1. Determine the scenario for which you want to use the apps. Follow the instructions for your scenario:

Scenario Instructions

Standalone — SAP Customer Activity Repository Continue with step 2 below.

Integrated — SAP Assortment Planning Assign Roles, Catalogs, and Groups in SAP Fiori Launch­
pad

Integrated — SAP Allocation Management Assign Roles, Catalogs, and Groups in SAP Fiori Launch­
pad

Integrated — SAP Promotion Management Activate Internet Communication Framework (ICF) Serv­
ices

2. Log on to your front-end system.

3. Execute transaction SU01 to open the User Maintenance screen.
4. Enter your front-end user name in the User field and choose Change.
5. On the Roles tab, assign the Demand Data Foundation Administrator (SAP_ISR_BR_DDF_ADMIN) role to
your user.
6. Save your changes.
7. Execute transaction LPD_CUST to open the Overview of Launchpads.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
144 PUBLIC Set Up the Applications
 8. Verify that the following two roles are listed:
○ UIPMR001
○ UIRAP001
9. Open SAP Fiori launchpad and verify that you can see and access the tiles for the apps.

 Tip

If you already have an SAP Fiori launchpad open, clear your browser cache to see the changes.

10. If your app is Manage Product Attributes, continue with the Set Up the Manage Product Attributes App
[page 145] section and do any steps not covered here.

6.1.2.7.5.1 Set Up the Manage Product Attributes App

Perform several tasks on the front-end server and the back-end server to set up the transactional app Manage
Product Attributes. This is one of the Demand Data Foundation (DDF) apps included in SAP Customer Activity
Repository.

Context

The Manage Product Attributes app supports different scenarios and consuming applications (such as SAP
Allocation Management, SAP Assortment Planning, the similar products search, or the calculation of
distribution curves). The app enables planning administrators to create, configure, assign, and maintain
product attributes for a selected product hierarchy.

Prerequisites

● You are aware of the technical implementation information for the app in the SAP Fiori apps reference
library:
For the latest delivery (latest wave), see: https://fioriappslibrary.hana.ondemand.com/sap/fix/
externalViewer/index.html?appId=F0829A
● You have performed all setup tasks under Core (Mandatory for All Applications) in this guide.
● You have checked whether there are any corrections for the app in the current release:
See section Implement SAP Notes for the Upgrade [page 29]. Implement any corrections relevant for the
app.
● You have done the general setup for the DDF apps. See Set Up the Demand Data Foundation (DDF) Apps
[page 143].

 Note

To set up the app, do the steps in the following sections.

If your scenario includes SAP Allocation Management or SAP Assortment Planning, some steps might
already have been performed in your system landscape. If so, skip the step and continue with the next one.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 145
Verify that ICF Services are Active

Context

After an upgrade, you must ensure that the Internet Communication Framework (ICF) services required for the
app are still active.

Procedure

1. Log on to your front-end server.

2. Execute transaction SICF.
3. In the Define Services screen, make the following selections:
○ Hierarchy Type: SERVICE
○ Virtual Host: DEFAULT_HOST
○ Service Path: /sap/bc/ui5_ui5/sap/attribmgmt_v2/
4. Choose Execute ( F8 ).
5. Under Virtual Hosts / Services, double-click the attribmgmt_v2/ service to open the Create/Change a
Service screen.
6. To activate a service, choose Service/Host Activate .

 Note

You can check the activation status by selecting the service and opening the context menu. If the
Activate Service option is grayed out, this means the service is already active.

7. Repeat steps 3 to 6, this time using /sap/bc/ui5_ui5/sap/ddfreuse_v2/ as the service path.

Verify that OData Services are Active

1. See section Verify that OData Services are Active [page 101] and consult the table for SAP Customer
Activity Repository.
2. Make sure that all mandatory OData services for the app are active.

Enable the App for SAP Fiori Launchpad

Context

To be able to access the app from the SAP Fiori launchpad, your front-end system user must have the
necessary role(s) assigned. This allows you to access the business catalogs and business catalog groups
required for the app.

The app requires the following business role: Demand Data Foundation Administrator
(SAP_ISR_BR_DDF_ADMIN)

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
146 PUBLIC Set Up the Applications
  Note

Should you wish to use the app for SAP Allocation Management or SAP Assortment Planning, use the
Planning Administrator (SAP_RAP_BCR_PLANNING_ADMIN) business role instead.

Procedure

1. Log on to your front-end system.

2. Execute transaction SU01 to open the User Maintenance screen.
3. Enter your front-end user name in the User field and choose Change.
4. On the Roles tab, assign the Demand Data Foundation Administrator (SAP_ISR_BR_DDF_ADMIN) role to
your user.
5. Save your changes.

 Tip

If you already have an SAP Fiori launchpad open, clear your browser cache or you won't be able to see
the changes.

6. Verify role settings for SAP Fiori launchpad.

1. Execute transaction LPD_CUST to open the Overview of Launchpads.
2. Double-click the role UIRAP001 to view the role details.
3. Expand the role Planning Administrator and select the Manage Product Attributes app.
4. Display the advanced parameters and check that the app has all the mandatory settings listed below.
You do not need to make any additional settings.
○ Link Text: Manage Product Attributes
○ Application Type: URL
○ URL: /sap/bc/ui5_ui5/sap/attribmgmt_v2
○ Application Alias: AssignProductAttribute
○ Additional Information: SAPUI5.Component=retail.ddf.attributemgmtv2
○ Navigation Mode: EXT_HEAD Leaderless Portal Window
○ History Mode: 1 Navigation Entry can Occur Once in History
○ Parameter Forwarding: G Get Parameters
If you have updated any settings, save your changes.

Assign Area of Responsibility (AOR) to ABAP Back-End User

You can only display and select product hierarchies in the app that have been assigned as the area of
responsibility to your ABAP back-end user.

1. Log on to your ABAP back-end system.

2. Execute transaction NWBC to open the SAP NetWeaver Business Client.
3. Choose Services Maintain Area of Responsibility Product Hierarchy .
4. Select your ABAP back-end user, choose Continue, and define the AOR.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 147
  Tip

For step-by-step instructions, see the application help for SAP Customer Activity Repository at https://
help.sap.com/viewer/p/CARAB. Search for section Maintain Area of Responsibility and follow the
instructions.

6.1.2.8 Configure On-Shelf Availability

Configure the On-Shelf Availability (OSA) module in SAP Customer Activity Repository. All steps are optional
and depend on your implementation scenario.

 Note

The configuration of OSA is mandatory if you want to generate intraday forecasts. For this feature, you
need the combined functionality of OSA and Unified Demand Forecast (UDF). For more information, see
https://help.sap.com/viewer/p/CARAB and open the application help for SAP Customer Activity
Repository. Search for the Generate Intraday Forecasts section.

 Tip

If you encounter any issues, see the Troubleshooting [page 190] section for possible solutions.

Generate Run IDs for OSA Processing Steps [page 148]

Define the range of run IDs for the four processing steps of On-Shelf Availability (OSA): Intraweek
Pattern, Estimation, Monitoring, and Analysis.

Check Field Contents in SAP HANA Content for On-Shelf Availability [page 149]
Check the fields of the customizable SAP HANA views for OSA.

6.1.2.8.1 Generate Run IDs for OSA Processing Steps

Define the range of run IDs for the four processing steps of On-Shelf Availability (OSA): Intraweek Pattern,
Estimation, Monitoring, and Analysis.

Use

Each scheduled run of a processing step of On-Shelf Availability (OSA) has a generated run ID. This is the
unique identifier of a job.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
148 PUBLIC Set Up the Applications
The run ID is used to distinguish several runs within one period. Each processing step has its own ID generator:

Processing Step Transaction for the ID Generator

Intraweek Pattern /OSA/NR_IWP

Estimation /OSA/NR_EST

Monitoring /OSA/NR_MON

Analysis /OSA/NR_ANA

For each of the four ID generator transactions, you must define the range of run IDs.

Procedure

Do the following steps for each transaction:

1. Log on to your back-end system.

2. Execute the transaction by specifying either /n<transaction> or /o<transaction>.

 Example

For the first transaction: /n/OSA/NR_IWP

3. Choose Intervals in change mode.

4. In the first row of the table, enter the following values for the following fields:
○ Field No: 01
○ Field From No.: 0000000000000001
○ Field To Number: 9999999999999999
5. Save your changes.

6.1.2.8.2 Check Field Contents in SAP HANA Content for

On-Shelf Availability

Check the fields of the customizable SAP HANA views for OSA.

Use

There are two OSA-specific SAP HANA views that can be customized:

● AN_TRANSACTION
● PROMOTION_TRANS

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 149
You must check if the fields in these views contain the mappings or formulas you need.

 Caution

If you need to modify a view, be aware that a new installation will rewrite the modifications. We therefore
recommend that you perform a back-up of the modified views.

Procedure

To change the mapping or the formula of a field, follow these steps:

1. Define the data foundation that is the source for the view, that is, the table /POSDW/TLOGF.
2. Define filters for the view.
3. Map the fields from source to target.
4. Create measures and calculation fields.

For more information, see the documentation under https://help.sap.com/viewer/p/SAP_HANA_PLATFORM

<Version> Development .

 Example

Example: Definitions for the AN_TRANSACTION View

The following definitions are set by default for the AN_TRANSACTION view:

● The source of the view is the table /POSDW/TLOGF.

● Examples of filters for the views:
○ RECORDQUALIFIER = '5': Only sales records are used.
○ DATASTATUS in ('2' , '3'): Only those records are used that passed the SAP Customer Activity
Repository validation.
○ RETAILQUANTITY > 0.0: Negative quantities are not used by On-Shelf Availability.
○ VOIDEDLINE = '': Canceled transactions are not used by On-Shelf Availability.
● Examples of fields mappings:
○ MANDT: Client ID. This field is mapped to the MANDT column of the /POSDW/TLOGF table.
○ STORE_ID: Store ID. This field is mapped to the RETAILSTOREID column of the /POSDW/TLOGF table.
○ BUSINESSDAYDATE: Business day. This field is mapped to the BUSINESSDAYDATE column of the /
POSDW/TLOGF table.
● Examples of measures:
○ RETAILQUANTITY: Amount of units sold. Refers to the SALESUOM (Sales Unit of Measure) field that is
also defined in the /POSDW/TLOGF table. Contains the value of the RETAILQUANTITY field.
○ PRICE: Price specified in the store currency. Contains the value of the ACTUALUNITPRICE field.
● Examples of calculated fields:
○ TRANS_TIME_DBL: Value of the TRANS_TIME output field of type DOUBLE. The format of the
transaction time that is stored in BEGINTIMESTAMP and ENDTIMESTAMP is <YYYYMMDDhhmmss>.
○ DISCOUNT: Total relative discount applied on the item (product).
Calculated as (ITEMDISC + DISTDISC) / (RETAILQUANTITY * ACTUALUNITPRICE). If the price
is not a positive number, 0 is returned.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
150 PUBLIC Set Up the Applications
 Definitions:
○ DISTDISC: global discount on the whole purchase; currently not used.
○ ITEMDISC: item-specific discount; currently used.

6.1.2.9 Configure Omnichannel Article Availability and

Sourcing for Use with SAP Customer Activity
Repository

To set up the OAA module, you need to integrate the source master data system (SAP S/4HANA or SAP Retail),
SAP Customer Activity Repository, SAP Commerce, and SAP Commerce, integration package for SAP for
Retail. You also need to set up asynchronous order management and the data replication between SAP S/
4HANA or SAP Retail, SAP Commerce, and SAP Customer Activity Repository.

6.1.2.9.1 Set up Data Replication Between SAP S/4HANA

or SAP Retail, and SAP Commerce

In SAP S/4HANA or SAP Retail, and SAP Commerce, set up the asynchronous order management scenario
as follows:

1. Set up asynchronous replication of articles via the Data Hub from SAP S/4HANA or SAP Retail to SAP
Commerce.
For more information, see the documentation for SAP Commerce at https://help.sap.com/viewer/
50c996852b32456c96d3161a95544cdb/latest/en-US/8bc6b884866910148532f2e1e500f95f.html
Getting Started with SAP S/4HANA or SAP ERP Integration. Follow the steps for the asynchronous order
management scenario.
2. Set up asynchronous replication of orders via the Data Hub from SAP Commerce to SAP S/4HANA or
SAP Retail (see link above).
3. Configure asynchronous order management.
For more information, see the documentation for SAP Commerce at https://help.sap.com/viewer/
50c996852b32456c96d3161a95544cdb/latest/en-US/e2be57a501da41cc9ebdf7cf7d3aa229.html
Configuring Order Management for SAP Commerce with One or More SAP Back Ends.

6.1.2.9.2 Set Up Data Replication Between SAP Commerce

and SAP Customer Activity Repository

1. In SAP Commerce, in the Backoffice application under SAP Integration HTTP Destination , create the
HTTP destination of SAP Customer Activity Repository that is used for availability calculation and sourcing.
2. In SAP Commerce, in the Backoffice application under SAP Integration SAP Global Configuration
Backend Connectivity , enter the HTTP destination of SAP Customer Activity Repository created before.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 151
  Note

In the standard Solr configuration for products in SAP Commerce, ProductStoreStockValueProvider

is used to replicate the store availability situation from the SAP Commerce database into the Solr index.

If you use OAA, availability information is provided through synchronous calls into SAP Customer Activity
Repository for every article/store combination instead. If your product catalog is rather large, this is why
indexing the complete product catalog can take very long. In this case, we recommend to either deactivate
the value provider or to create a custom one. If you deactivate the value provider, faceted search according
to store availability is not possible in the product catalog. OAA functionality is not affected.

6.1.2.9.3 Set Up Live Connection Between SAP Customer

Activity Repository and SAP Analytics Cloud

This step is optional. You only need to execute it if you want to use the set of OAA analyses that has been
predefined in SAP Analytics Cloud and that is part of the standard delivery of SAP Analytics Cloud. If you are
using a different analytics tool, or if you do not run analytics at all, you may skip this step.

Context

Procedure

1. Configure SAP Customer Activity Repository to support cross-origin resource sharing (CORS), for cross-
domain communication from the browser.

For more information, see Live Data Connection to SAP BW Using a Direct Connection and Password
Authentication, steps 1 and 2 of the procedure.

2. In SAP Analytics Cloud, navigate to Home Connection and select live connection SAPRTOAA (SAP
Retail Omnichannel Article Availability and Sourcing). This connection is part of the standard delivery.
3. Click Edit Connection and enter your custom details for Host, HTTPS Port, and Client.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
152 PUBLIC Set Up the Applications
6.1.2.9.4 Check Version of SAP Customer Activity
Repository in SAP Commerce

SAP Commerce can be connected against different versions of SAP Customer Activity Repository. As there
were incompatible changes in the OAA REST service APIs, a Spring profile property in SAP Commerce controls
the mapping to the different API versions.

Context

Check the spring.profiles.active property in the local.properties file of your SAP Commerce
installation, for example from <hybris_installation_path>/hybris/config/local.properties.

The following profiles are supported:

Version of SAP Customer Activity Repository Profile Value

CAR 3.0 (CARAB 2.0) or higher sapoaa_carApiVersionLatest

CAR 2.0 FP3 (CARAB 1.0 FP3) sapoaa_carApiVersion1

As of SAP Commerce, integration package for SAP for Retail 2.4 / SAP Commerce 6.4, the property is set
automatically to sapoaa_carApiVersionLatest.

6.1.2.9.5 Adapt Customizing for Eligible Sources in OAA

Profile

Context

If you have used OAA in version 2.0 FP3 of SAP Customer Activity Repository already and are upgrading to
version 3.0 or higher, and if you want to continue using OAA profile mode, you need to adapt your Customizing
for the eligible sources assigned to the OAA profile (Customizing path: SAP Customer Activity Repository
Omnichannel Article Availability and Sourcing (OAA) OAA Profile Mode Define OAA Profiles ) at the start of
your project using report /OAA/SPLIT_SOURCES. This report enables you to continue using your 2.0 FP3
Customizing settings for eligible sources. In version 2.0 FP3, there was one single Customizing view that
covered DCs and stores alike, while in version 3.0, this view was replaced with three new views, one each for
DCs, stores, and external vendors. The report moves your entries to the new views.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 153
Procedure

1. In transaction SE38, execute report /OAA/SPLIT_SOURCES.

The report checks your entries for eligible sources in the old view and transfers those for DCs to the new
view for DCs and those for stores to the new view for stores.
2. Check the error log.

For all entries that do not fall into either category, the system issues an error message.
3. Process the entries in the error log manually.

6.1.2.9.6 Adapt Customizing for RFC Destination (SAP S/

4HANA Only)

As of SAP S/4HANA 1709 FPS2, setting the RFC destination that is used for the replication of the ATP snapshot
from SAP S/4HANA to SAP Customer Activity Repository was moved to the new Customizing activity Define
System Connections.

Context

If you have used OAA in combination with a version of SAP S/4HANA 1709 prior to FPS2 and want to upgrade
to SAP S/4HANA 1709 FPS2 or higher, you need to manually adapt your Customizing for the RFC destination.

In Customizing for SAP S/4HANA, proceed as follows:

Procedure

1. Go to Sales and Distribution Basic Functions Availability Check and Transfer of Requirements
Availability Check Availability Check with ATP Logic or Against Planning Retail: Omnichannel Article
Availability and Sourcing (OAA) Define System Connections .
2. Create a system connection ID for the RFC destination that is used for the replication of the ATP snapshot
from SAP S/4HANA to SAP Customer Activity Repository.

3. Go to Sales and Distribution Basic Functions Availability Check and Transfer of Requirements
Availability Check Availability Check with ATP Logic or Against Planning Retail: Omnichannel Article
Availability and Sourcing (OAA) Define ATP Parallelization Profiles for DC Articles .
4. Enter the system connection ID into your ATP parallelization profile.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
154 PUBLIC Set Up the Applications
6.1.2.9.7 Activate BAdI Implementation for Using OAA with
Vendor Articles

If you use vendors from SAP S/4HANA or SAP Retail as sources in OAA and want to benefit from the automatic
creation of purchase requisitions, BAdI implementation VENDOR_OAA_SALES_PUR_REQ of BadI
BADI_SD_SALES_ME_REQ must be set to active.

Context

The implementation serves to enter the fixed vendor, the net price of the article, and the purchasing
organization into the purchase requisition that is automatically created for the vendor articles, from the sales
order. As a default, this BAdI implementation is delivered in an inactive state.

As of the following versions of your back-end application you can activate this BAdI implementation via a
Customizing activity, from the following path: Sales and Distribution Basic Functions Availability Check
and Transfer of Requirements Availability Check Availability Check with ATP Logic or Against Planning
Retail: Omnichannel Article Availability and Sourcing (OAA) Implementation: Data Required for Purchase
Requisitions for Vendor Articles :

● SAP S/4HANA 1709 SPS3

● SAP Retail 6.0 EHP7 SP17
● SAP Retail 6.0 EHP8 SP11

If you currently use a lower version of SAP S/4HANA or SAP Retail and want to upgrade to an SP that is still
lower than the SPs mentioned above, you need to manually activate this BadI implementation. Proceed as
follows:

Procedure

1. Go to transaction SE19.
2. Enter VENDOR_OAA_SALES_PUR_REQ as enhancement implementation and choose Edit.
3. Select Implementation is active and save your changes.

Results

You need to activate this BAdI implementation again using transaction SE19 each time you implement a new
support package of SAP S/4HANA or SAP Retail.

Only when you reach the support package that holds the new Customizing activity (see above) do you activate
the BAdI implementation directly in Customizing. This setting will then last with all future upgrades.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 155
6.1.2.9.8 Check the REST Services of Your Implementation

Context

As of SAP Customer Activity Repository 3.0, the REST services for omnichannel article availability and sourcing
were modified. For more information, see SAP Note 2434053 .

6.1.2.9.9 Activate OData Services for Omnichannel Article

Availability and Sourcing

A number of OData services are required to run the SAP Fiori apps for omnichannel article availability and
sourcing (OAA).

Context

Make sure that you have activated the OData services required for OAA, as described and listed in Verify that
OData Services are Active [page 101]. Depending on your back end, different services are required.

6.1.2.9.10 Upgrade Data Structures of Sources

Sales channel mode only: With SAP Customer Activity Repository 4.0, the OAA data structures for sources, for
the SAP Fiori app Manage Sources, were changed. You need to run two reports to upgrade the data structures.

Prerequisites

You have not used the SAP Fiori app Manage Sources with SAP Customer Activity Repository 4.0 or higher
productively yet.

Context

Execution of the reports is mandatory for all upgrade scenarios where you upgrade from a version prior to 4.0
to version 4.0 or higher. You need to execute the reports once only.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
156 PUBLIC Set Up the Applications
Procedure

1. In SAP Customer Activity Repository, in transaction SE38, execute report /OAA/CREATE_TRIGGERS.

In addition to the trigger that updates temporary reservations, this report now also creates a trigger that
creates and exposes data structures for the source properties you maintain in the SAP Fiori app Manage
Sources. Each time a new source becomes available in SAP Customer Activity Repository, the trigger is set
off.
2. In SAP Customer Activity Repository, in transaction SE38, execute report /OAA/SOURCE_UPGRADE.
○ If you have not used the app in an earlier version of SAP Customer Activity Repository yet,
report /OAA/SOURCE_UPGRADE creates and exposes the new data structures for the sources that are
already available in the system, thus enabling use of the enhanced app.
○ If you have already used the app in an earlier version of SAP Customer Activity Repository, the report
moves the source properties, such as status, general capacity, capacity exceptions for weekdays and
individual dates, from the old data structures to the new data structures. This enables you to
seamlessly continue using the app and the data already available in the app.

6.1.2.9.11 Use New Apps (SAP S/4HANA Only)

With SAP Customer Activity Repository 4.0, the Manage Sources and Manage Sourcing Networks apps were
renamed and duplicated, in order to split apps between back ends.

Context

The functional scope of each pair of apps is identical. The apps are called as follows:

Old App Split Into

Manage Sources (Fiori ID F3003) Manage Sources -SAP S/4HANA (Fiori ID F3392)

Manage Sources - SAP Retail (Fiori ID F3003)

Manage Sourcing Networks (Fiori ID F2530) Manage Sourcing Networks -SAP S/4HANA (Fiori ID F3391)

Manage Sourcing Networks - SAP Retail (Fiori ID F2530)

Procedure

If your back end is SAP S/4HANA, use the new apps. Your existing data was migrated to the new apps
automatically.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 157
  Note

Make sure that the corresponding OData services have been activated before. For more information, see
Verify that OData Services are Active [page 101].

If your back end is SAP Retail, you may continue using the former apps.

6.1.2.9.12 Use New Tracing Tables for Analytics

With SAP Customer Activity Repository 4.0 FPS01, the programming tables introduced in version 4.0 and used
to store tracing information were rendered obsolete and were replaced with new tables that are better suited
for analytics.

Context

The tables were replaced as follows:

Replaced with Trace Table in SAP Customer Activity

Trace Table in SAP Customer Activity Repository 4.0 Repository 4.0 FPS01

/OAA/TRC_DS_ES /OAA/TRC_SRC_ES

Trace table for building block Read Sources New trace table for sources

/OAA/TRC_BO_1DEL /OAA/TRC_REASON

Trace table for business objective Apply Rule: One Failure reason trace table
Consignment Today

/OAA/TRC_BO_AFC /OAA/TRC_REASON + /OAA/TRC_BO_CONS

Trace table for business objective Apply Rule: As Few Failure reason and consignments trace tables
Consignments as Fast as Possible

/OAA/TRC_BO_AFCA /OAA/TRC_REASON + /OAA/TRC_BO_CONS

Trace table for business objective Apply Rule: As Few Failure reason and consignments trace tables
Consignments as Fast as Possible (Advanced)

The old trace tables are not filled any longer. Instead, the new tables are used.

Procedure

1. If you have used tracing for custom analytics in version 4.0 of SAP Customer Activity Repository and want
to continue using this functionality when upgrading to version 4.0 FPS01 or higher, adapt your custom
coding for analytics so that the new tables are referenced instead of the old ones.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
158 PUBLIC Set Up the Applications
 2. If you want to continue using your historic tracing data, adapt your custom coding for analytics so that
historic trace data and new trace data can be analyzed together.

6.1.2.9.13 Use New Tables for ATP Snapshot and

Reservations and Delete Obsolete Entries

With SAP Customer Activity Repository 4.0 FPS02, the programming tables used to store ATP snapshot data
and temporary reservations were rendered obsolete and were replaced with new tables, to allow integration of
the Context field and to improve performance.

Context

 Note

If you have not used OAA in a version of SAP Customer Activity Repository earlier than 4.0 FPS02, you may
skip this step.

The tables were replaced as follows:

Table in SAP Customer Activity Repository 4.0 FPS01 and Replaced with Table in SAP Customer Activity Repository
Earlier 4.0 FPS02

/OAA/ATP_SNP_HDR and /OAA/ATP_SNP_ITM /OAA/ATP_SNPSHOT

Header table and item table for ATP snapshot data Both old tables were merged into this new one.

/OAA/ATP_RESV_H and /OAA/ATP_RESV_I /OAA/ATP_RESV

Header table and item table for temporary reservations Both old tables were merged into this new one.

The old tables are not filled any longer. Instead, the new tables are used. Existing data is copied automatically
to the new tables during the upgrade, without being deleted from the old tables. If you have enhanced the
tables with custom fields, this makes sure that entries in these fields are preserved.

Procedure

● If you have not enhanced the ATP snapshot tables or the temporary reservation tables with custom fields,
run report /OAA/MIGRATED_DATA_DELETION to delete all obsolete table entries.
● If you have enhanced the ATP snapshot tables or the temporary reservation tables with custom fields,
migrate this data to the new tables, if required. Then run report /OAA/MIGRATED_DATA_DELETION to
delete all obsolete table entries.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 159
6.1.2.9.14 Schedule Report for Deletion of Temporary
Reservations

With SAP Customer Activity Repository 4.0 FPS02, the deletion logic for temporary reservations was changed.

Context

Outdated temporary reservations are no longer deleted while the ATP snapshot is generated but are deleted
through a dedicated report.

Schedule report /OAA/ATP_OUTDATED_RESV_CLEANUP (Deletion of Outdated Temporary Reservations).

 Note

Scheduling this report is a mandatory prerequisite for running omnichannel article availability and sourcing
(OAA).

6.1.2.9.15 Trigger Initial Full Run of ATP Snapshot Replication

(SAP S/4HANA 1909 Only, Sales Channel Mode
Only)

Sales channel mode only; SAP S/4HANA 1909 only: With SAP Customer Activity Repository 4.0 FPS02, the
delta mode of the ATP snapshot replication was changed.

Context

The delta mode of the ATP snapshot replication works correctly only after an initial full run of the replication.

Trigger a full run of report /OAA/ATP_SNP_CALC (Generation and Replication of ATP Snapshot).

6.1.2.10 Configure Omnichannel Promotion Pricing for Use

with SAP Customer Activity Repository

To use the OPP module, you need to activate the functionality in Customizing and configure it for your specific
scenario.

 Tip

For information on how to configure the promotion pricing service in SAP Commerce, see the Administrator
Guide of SAP Commerce, integration package for SAP for Retail on SAP Help Portal under https://

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
160 PUBLIC Set Up the Applications
 help.sap.com/viewer/p/IPR <Version> Administration Omnichannel Promotion Pricing
Configuration .

Related Information

Activate Omnichannel Promotion Pricing (OPP) [page 161]

Activate the Data Replication Framework (DRF) [page 163]
Configure the Transformation of Offers into OPP Promotions [page 161]
Configure the Local Deployment of the Promotion Pricing Service [page 162]
Configure the Central Deployment of the Promotion Pricing Service [page 177]
Update the PPS SAP HANA XSA Application [page 187]
Use the Extended Sales Pricing Model (DDF) [page 188]

6.1.2.10.1 Activate Omnichannel Promotion Pricing (OPP)

To use omnichannel promotion pricing for the calculation of the effective sales price, you have to activate the
functionality.

In Customizing for SAP Customer Activity Repository, choose Omnichannel Promotion Pricing Configure
Omnichannel Promotion Pricing Activate OPP .

6.1.2.10.2 Configure the Transformation of Offers into OPP

Promotions

Related Information

Enforce the Compatibility to Transform Offers into OPP Promotions [page 162]
Enable Offers with Enhanced Product Groups [page 162]
Enable Offers with Zero Discount [page 162]

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 161
6.1.2.10.2.1 Enforce the Compatibility to Transform Offers
into OPP Promotions

To transform offers into OPP promotions, it is recommended to enforce the compatibility to make sure that an
offer can only be set to an operative status, for example Approved, if the transformation into an OPP promotion
was successful.

In Customizing for SAP Customer Activity Repository under Omnichannel Promotion Pricing (OPP)
Configure Omnichannel Promotion Pricing Enforce Compatibility .

6.1.2.10.2.2 Enable Offers with Enhanced Product Groups

If you want to include or exclude product groups from your offers or use them in mix-and-match offers, you
have to enable enhanced product groups.

In Customizing for SAP Customer Activity Repository under Omnichannel Promotion Pricing (OPP)
Configure Omnichannel Promotion Pricing Enable Product Groups .

Additionally, you have to enable product groups for the promotion pricing service. For more information about
the configuration of product groups, see the Development and Extension Guide for OPP on SAP Help Portal at
https://help.sap.com/viewer/p/CARAB <Version> Development Development and Extension Guide for
Omnichannel Promotion Pricing under Promotion Pricing Service PPS Module calcengine-gk Default
Settings and Properties .

6.1.2.10.2.3 Enable Offers with Zero Discount

By default offers with discount type Everyday Low Price (EDLP) are transformed into OPP promotions like
offers with discount type Regular Price. If a monetary discount of zero should be applied to the previous price,
you can enable the discount type Zero Discount. In this case, a retail price modifier is returned in the calculation
response, but the previous price does not change.

You can enable this discount type in Customizing for SAP Customer Activity Repository under Omnichannel
Promotion Pricing (OPP) Configure Omnichannel Promotion Pricing Enable Zero Discount .

6.1.2.10.3 Configure the Local Deployment of the Promotion

Pricing Service

For a local deployment scenario, you have to replicate regular prices and OPP promotions from the central
price and promotion repository (SAP Customer Activity Repository) to an external system to create a local
storage for prices and promotions. This replication can be done via IDocs. For that, you have to configure
application link enabling (ALE) and Data Replication Framework (DRF). For OPP promotions, there are two

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
162 PUBLIC Set Up the Applications
options to configure this replication: the promotion-centric outbound processing and the location-specific
outbound processing.

Prerequisites

● You have defined receiving systems and clients in the system landscape directory (SLD).

Procedure

1. Activate OPP functionality as described in Activate Omnichannel Promotion Pricing (OPP) [page 161].
2. Activate DRF functionality as described in Activate the Data Replication Framework (DRF) [page 163].
3. Define number ranges as described in Define Number Ranges [page 163].
4. Configure the Application Link Enabling for the outbound processing of regular prices and OPP promotions
(promotion-centric or location-specific outbound processing):
○ Configure Application Link Enabling for the outbound processing of regular prices and promotion-
centric OPP promotions. [page 164]
○ Configure Application Link Enabling for the location-specific outbound processing of OPP promotions
[page 172]
5. Configure the Data Replication Framework for the outbound processing of regular prices and OPP
promotions (promotions-centric or location-specific outbound processing):
○ Configure the data replication for the outbound processing of regular prices and OPP promotions
(promotion-centric outbound processing) [page 167]
○ Configure the data replication for OPP promotions (location-specific outbound processing) [page 175]

6.1.2.10.3.1 Activate the Data Replication Framework (DRF)

To send regular prices and OPP promotion to an external system via IDocs, you have to activate the Data
Replication Framework (DRF) functionality.

In transaction SFW5, activate business function DRF_FOUNDATION.

6.1.2.10.3.2 Define Number Ranges

To send OPP promotions to an external system via IDocs, you can define number ranges to generate unique
identifiers for all promotion-related entities.

In Customizing for SAP Customer Activity Repository, choose Omnichannel Promotion Pricing (OPP)
Define Number Ranges .

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 163
6.1.2.10.3.3 Configure the Outbound Processing for Regular
Prices and OPP Promotions

Configuration of the outbound processing of regular prices and promotion-centric OPP promotions.

Application Link Enabling

In Customizing for SAP NetWeaver, under Application Server IDoc Interface / Application Link Enabling
(ALE) , see the system documentation to check the settings for distributing data between application
systems based on Application Link Enabling and IDoc interface technology. With omnichannel promotion
pricing, this functionality is used to distribute OPP promotions and regular prices from SAP Customer Activity
Repository to an external system, for example an SAP Commerce system. You need to perform the following
steps:

Transaction BD54: Defining a Logical System

With ALE IDoc distribution, you can exchange data between logical systems. You use the logical system name
to identify a system uniquely within the network. If you already use ALE IDoc distribution, the logical system for
the sending system has already been defined. In this case, you only need to define a logical system for the
receiving system. In SAP Customer Activity Repository, do the following:

In Display View "Logical System": Overview, create a new logical system. Enter the following values:

Field Name Value

Log. System <receiving system>

Name <receiving system>

Transaction SM59: Defining an RFC Destination

1. Create the RFC destination in the HTTP Connections to External Server folder and enter the following
values:

Field Name Value

RFC Destination <name of the RFC destination>

Connection Type Enter connection type G HTTP Connection to External

Server.

Description Enter at least Description 1 in the description section.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
164 PUBLIC Set Up the Applications
 2. In Technical Settings, enter the following values for Target System Settings:

Field Name Value

Target Host <name of the target host>

Path Prefix /sapppspricing/idocinbound

Port <service number for https or http

connection>

 Note
With OPP, an https connection is recommended.

3. In Logon and Security, select Basic Authentication for Logon with User, and enter the following values:

Field Name Value

User <user name that you have created in SAP

Commerce Backoffice>

Password <password that you have created in SAP

Commerce Backoffice>

In Security Options select SSLActive to send your data via https connection and enter an appropriate
certificate.

 Note

We strongly recommend to use Secure protocols (SSL, SCN) whenever possible.

For more information, see Transport Layer Security and Web Services Security in the SAP NetWeaver
Security Guide.

Transaction WE21: Defining a Port

1. Create this ALE port in the XML HTTP folder and enter the following values:

Field Name Value

Port <name of port>

Description <description of port>

RFC destination <name of the RFC destination created in

the previous step>

2. Select Text/XML for Content Type.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 165
Transaction WE20: Defining a Partner Profile
A partner profile contains parameters that define the electronic interchange of data between systems using the
IDoc interface. There is only one partner profile required for the receiving system and it needs to contain all the
parameters that your scenario requires for sending OPP promotions and regular prices to that receiving
system.

Basic Partner Profile Information

To set up the basic partner profile information, do the following:

1. In Partner Profiles, create a logical system partner. Enter the following values:

Field Name Value

Partner No. <partner number>, which must be the same as the receiving system that you
defined in section Defining a Logical System

Partner Type LS for regular prices and OPP promotions sent via promotion-centric outbound
processing

2. In the Post processing: permitted agent tab, enter the following values:

Field Name Value

Ty. US (for User)

Agent <users to be notified> should be an agent who can process IDocs with
errors

Lang. <notification language>

Outbound Parameters

Field Name Value

Message Type ● /ROP/BASE_PRICE for regular prices

● /ROP/PROMOTION for OPP promotions

Outbound Options tab

Receiver port <receiver port> as defined in section Defining a Port

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
166 PUBLIC Set Up the Applications
 Field Name Value

Output Mode ● Pass IDoc Immediately

○ Select this option to transfer IDocs directly after creation for a better integra­
tion to the DRF transfer log.
○ Select this option to make sure that IDocs are sent in the same order in
which they have been created.
● Collect IDocs
○ Select this option to collect IDocs and transfer them sequentially with trans­
action WE14.

IDoc Type ● /ROP/BASE_PRICE01 for regular prices

● Depending on the receiving system /ROP/PROMOTION01 or /ROP/PROMOTION02
for OPP promotions

Cancel Processing After Syntax Ensure that this field is selected to avoid sending erroneous IDocs.
Error

Data Replication Framework

In Customizing for Cross-Application Components under Processes and Tools for Enterprise Applications
Master Data Governance, Central Governance General Settings Data Replication Overall Information ,
see the system documentation to check how data is sent to one or more target systems. With OPP, the Data
Replication Framework functionality is used to send regular prices and OPP promotions from an SAP Customer
Activity Repository system to external systems. You need to perform the following steps:

Transaction DRFIMG: Defining Custom Settings for Data Replication

In Customizing, you have to perform the following configuration steps under Data Replication Define
Custom Settings for Data Replication :

1. In Customizing activity Define Technical Settings for Business Systems, define a business system and a
logical system for the receiving systems. The following business object types are available to send OPP
promotions and regular prices, and can be assigned to the business system:

Business Object Type Description Communication Channel

ROP_PROMO OPP promotion Replication via IDoc

ROP_PRICE Regular price Replication via IDoc

2. In Customizing activity Define Replication Models, specify the content of the replication model (regular
prices or OPP promotions), the outbound implementation that is to be used, and the business system to
which this object is to be sent. You can specify a different destination system for each outbound

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 167
 implementation that contains business object, filter object, and business logic. You can also add an
expiration time for the log. The following predefined outbound implementations exist:

Outbound Imple­ Supported Replication

mentation Description Model Filter Object

ROP_PRICE Outbound implementation Initialization, Change, and ROP_PRICE

for regular prices Manual
 Note
For this outbound implementa­
tion, the filter application time
needs to be set to Filter Before
Change Analysis.

ROP_PROMO Outbound implementation Initialization, Change, and ROP_PROMO

for OPP promotions sent Manual
via promotion-centric out­
bound processing

ROP_PRC_MG Outbound implementation Initialization, Change, and ROP_PRICE

for multi-level generated Manual
regular prices  Note
Use this additional out­ For this outbound implementa­
bound implementation for tion, the filter application time
regular prices instead of needs to be set to Filter Before
ROP_PRICE to support the Change Analysis.
extended sales pricing
model for Demand Data
Foundation (DDF).

For more information, see

Use the Extended Sales
Pricing Model (DDF) [page
188].

Outbound Parameters

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
168 PUBLIC Set Up the Applications
 The following outbound parameters must be assigned to each replication model:

Outbound Parameter for

Regular Prices Description Typical Value*

/ROP/PACK_SIZE_BULK This parameter sets the maximum number of regular prices that 20,000-100,000
are processed per IDoc. This is an approximate value because
regular prices are assigned to different IDocs for each group of
business unit with items and prices.

 Note
If this parameter is set to 0, restricting regular prices is not
possible and it is only the number of products that deter­
mines the IDoc size.

PACK_SIZE_BULK This parameter controls the number of products for which regu­ 200-1,000
lar prices can be stored in a compressed format at the same
time, and sets the maximum number of products that are proc­
essed per IDoc.

 Note
If this parameter is not set, the default is 1. If you increase
this value, performance at runtime is improved since fewer
IDocs need to be processed.

TASK_SIZE_PROCMSG This parameter is only relevant if you execute the data replication 400-2,000
using parallel processing . This parameter sets the maximum
number of products that are processed per parallel package. It
must be greater or equal to the PACK_SIZE_BULK parameter.

 Note
This parameter value does not define the number of regular
prices per package. If this parameter is set to 0, all products
are processed in one package. This means that parallel proc­
essing is not possible.

/ROP/SEQ_READ_SIZE This parameter sets the maximum number of products for which 100-200
the regular prices are read in one select statement. In this way
you can limit memory consumption for products with a large
number of regular prices.

 Note
If this parameter is set to 0, all products of the correspond­
ing package are read within one call.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 169
 Outbound Parameter for
Regular Prices Description Typical Value*

/ROP/DAY_OFFSET_PAST This parameter is only used, if the selection of prices in the past 30
is restricted with the validity end date as a filter criteria and if the
validity end date is not too far in the past.

During a delta replication, this parameter defines a time range in

days that lies before the date of the last replication run. The sys­
tem subtracts this value from the last replication date and uses
the resulting date to construct the select-option for the validity
end date.

During an initial replication the system calculates a date (current

date minus the time range in days defined in this parameter). If
the date that you entered for the validity end is earlier than the
calculated date, the calculated date is used automatically.

In this way you ensure that also regular prices with a validity end
date in the specified past time range are transferred.

 Note
If this parameter is not set, relevant regular prices might not
be transferred. See SAP Note 2338714 . In this case the
default is set to 30 days.

Outbound Parameter for

OPP Promotions Description Typical Value*

PACK_SIZE_BULK This parameter sets the maximum number of OPP promotions 100-1,000
that are processed per IDoc. It must be smaller than the
TASK_SIZE_PROCMSG parameter and is relevant for both, the se­
quential and the parallel execution of DRF outbound.

 Note
If this parameter is not set, the default is 1. If you increase
this value, performance at runtime is improved since fewer
IDocs need to be processed.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
170 PUBLIC Set Up the Applications
 Outbound Parameter for
OPP Promotions Description Typical Value*

TASK_SIZE_PROCMSG This parameter is only relevant with parallel processing . It sets 100-5,000
the maximum number of OPP promotions that are processed
per parallel package. It must be greater or equal to the
PACK_SIZE_BULK parameter.

 Note
This parameter value does not define the number of OPP
promotions per package. If this parameter is set to 0, inde­
pendently of the value that you enter in transaction
DRFOUT, parallel processing is not possible.

/ROP/Generic_ENH_MAP This parameter activates the automatic mapping of customer- x

specific fields that are stored in the CI-Inlcudes of promotional
entities to the corresponding extension segments in the OPP
promotion IDocs.

 Note
Internal tables, structures, and so on, are not supported.

*This value gives you an idea of usable values for the replication of regular prices and OPP promotions, it is
not a recommendation.

3. Optional: In Customizing activity Define Business Object Settings, specify the application link enabling
(ALE) message type that is to be used for each business object. In this way, you can determine the
retention period for change pointers that are related to the business object. For the outbound processing of
regular prices, no change pointers are used and the retention period is not relevant. The following message
types are relevant for the outbound processing of regular prices and OPP promotions from the central
price and promotion repository:

Business Object Type Message Type

ROP_PRICE /ROP/BASE_PRICE

ROP_PROMO /ROP/PROMOTION

For more information, see Customizing for Cross Application Components under Processes and Tools for
Enterprise Applications Master Data Governance, Central Governance General Settings Data
Replication Overall Information .

Transaction DRFF: Defining Filter Criteria

In Define Filter Criteria, specify your data selection for each replication model and business object. The filter
criteria are valid for Initial replication and Change replication.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 171
Parallel Processing for Regular Prices and OPP Promotions

DRF enables outbound implementations to be executed by using parallel tasks. This feature is supported for
both, the outbound implementation for regular prices and the outbound implementation for OPP promotions.
You can transfer the different tasks to different servers by defining and choosing server groups. Before
replicating the data, you can define the maximum number of work processes that can run in parallel. These
parameters combined with the outbound parameters mentioned above provide a flexible configuration.

6.1.2.10.3.4 Configure the Location-Specific Outbound

Processing of OPP Promotions

The location-specific outbound processing of OPP promotions enables you to distribute a location-specific
view of OPP promotions. With this outbound option OPP promotions are sent from the central price and
promotion repository to its assigned locations. You can use this option if you, for example, want to send OPP
promotions to POS systems in your physical stores. This section describes how to configure the Application
Link Enabling (ALE) layer and Data Replication Framework (DRF) for the sending of IDocs.

Application Link Enabling

In Customizing for SAP NetWeaver, under Application Server IDoc Interface / Application Link Enabling
(ALE) , see the system documentation to check the settings for distributing data between application
systems based on Application Link Enabling and IDoc interface technology. With omnichannel promotion
pricing, this functionality is used to distribute OPP promotions and regular prices from SAP Customer Activity
Repository to an external system, for example an SAP Commerce system. You need to perform the following
steps:

Transaction SM59: Defining an RFC Destination

For each receiving system that initially receives the created IDocs, you have to create an RFC destination. If you
use a middleware, this RFC destination refers to the host in which the middleware is running, If you use a 1:1
connection, all receiving systems require a separate RFC destination. The attributes of the RFC destination are
determined by the receiving system. In the following we assume that we want to setup a location-specific
outbound processing to a local promotion pricing service in a SAP Commerce system that is directly
connected to the SAP Customer Activity Repository.

1. In Technical Settings, enter the following values for Target System Settings:

Field Name Value

Target Host <name of the target host>

Path Prefix /sapppspricing/idocinbound

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
172 PUBLIC Set Up the Applications
 Field Name Value

Port <service number for https or http

connection>

 Note
With OPP, an https connection is recommended.

2. In Logon and Security, select Basic Authentication for Logon with User, and enter the following values:

Field Name Value

User <user name that you have created in SAP

Commerce Backoffice>

Password <password that you have created in SAP

Commerce Backoffice>

In Security Options select SSLActive to send your data via https connection and enter an appropriate
certificate.

 Note

We strongly recommend to use Secure protocols (SSL, SCN) whenever possible.

For more information, see Transport Layer Security and Web Services Security in the SAP NetWeaver
Security Guide.

Transaction WE21: Defining a Port

1. Create this ALE port in the XML HTTP folder and enter the following values:

Field Name Value

Port <name of port>

Description <description of port>

RFC destination

2. Text/XML.

Transaction WE20: Defining a Partner Profile

A partner profile contains parameters that define the electronic interchange of data between systems using the
IDoc interface. There is only one partner profile required for the receiving system and it needs to contain all the
parameters that your scenario requires for sending OPP promotions and regular prices to that receiving
system.<name of the RFC destination created in the previous step>

Basic Partner Profile Information

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 173
To set up the basic partner profile information, do the following:

1. In Partner Profiles<, create a logical system partner. Enter the following values:

Field Name Value

Partner No. External ID of the receiving DDF location

Partner Type LO for OPP promotions replicated via location-specific outbound processing

 Note

For this partner type, only the first 10 characters of the DDF location ID are taken into account, the
location type and logical system are ignored. If you want to use a different logic, use transaction WE44
to define a different partner type or to change the validation logic.

Select a content type supported with the receiving system. If you configure a localIf you need a
different implementation of BAdI /ROP/PROMO_STORE_OUTBOUND, see Customizing for SAP Customer
Activity Repository and choose Omnichannel Promotion Pricing (OPP) Business Add-Ins (BAdIs)
Outbound Processing of OPP Promotions BAdI: Location-Specific Outbound Processing .

2. In the Post processing: permitted agent tab, enter the following values:

Field Name Value

Ty. US (for User)

Agent <users to be notified>, which should be an agent who can process IDocs
with errors.

Lang. <notification language>

Outbound Parameters

Field Name Value

Message Type /ROP/PROMOTION for OPP promotions

Outbound Options tab

Receiver port <receiver port> as defined in section Defining a Port

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
174 PUBLIC Set Up the Applications
 Field Name Value

Output Mode ● Pass IDoc Immediately

○ Select this option to transfer IDocs directly after creation for a better integra­
tion to the DRF transfer log.
○ Select this option to make sure that IDocs are sent in the same order in
which they have been created.
● Collect IDocs
○ Select this option to collect IDocs and transfer them sequentially with trans­
action WE14.

IDoc Type Depending on the receiving system /ROP/PROMOTION01 or /ROP/PROMOTION02 for

OPP promotions

Cancel Processing After Syntax Ensure that this field is selected to avoid sending erroneous IDocs.
Error

Data Replication Framework

In Customizing for Cross-Application Components under Processes and Tools for Enterprise Applications
Master Data Governance, Central Governance General Settings Data Replication Overall Information ,
see the system documentation to check how data is replicated to one or more target systems. With OPP, the
Data Replication Framework functionality is used to send regular prices and OPP promotions from an SAP
Customer Activity Repository system to external systems. You need to perform the following steps:

Transaction DRFIMG: Defining Custom Settings for Data Replication

In Customizing, you have to perform the following configuration steps under Data Replication Define
Custom Settings for Data Replication :

1. In Customizing activity Define Technical Settings for Business Systems, define a business system and a
logical system for the receiving systems. The following business object types are available to replicate OPP
promotions and regular prices, and can be assigned to the business system:

Business Object Type Description Communication Channel

ROP_PRO_ST Location-specific outbound process­ Replication via IDoc

ing of OPP promotions

2. In Customizing activity Define Replication Models, specify the content of the replication model (regular
prices or OPP promotions), the outbound implementation that is to be used, and the business system to
which this object is to be sent. You can specify a different destination system for each outbound

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 175
 implementation that contains business object, filter object, and business logic. You can also add an
expiration time for the log. The following predefined outbound implementations exist:

Outbound Imple­ Supported Replication

mentation Description Model Filter Object

ROP_PRO_ST Outbound implementation Initialization, Change, and ROP_PRO_ST

for OPP promotions sent Manual
via location-specific out­
bound processing

Outbound Parameters
The following outbound parameters must be assigned to each replication model:

Outbound Parameter for

OPP Promotions Description Typical Value*

PACK_SIZE_BULK This parameter sets the maximum number of OPP promotions 100-1,000
that are processed per IDoc. It must be smaller than the
TASK_SIZE_PROCMSG parameter and is relevant for both, the se­
quential and the parallel execution of DRF outbound.

 Note
If this parameter is not set, the default is 1. If you increase
this value, performance at runtime is improved since fewer
IDocs need to be processed.

TASK_SIZE_PROCMSG This parameter is only relevant with parallel processing . It sets 100-5,000
the maximum number of OPP promotions that are processed
per parallel package. It must be greater or equal to the
PACK_SIZE_BULK parameter.

 Note
This parameter value does not define the number of OPP
promotions per package. If this parameter is set to 0, inde­
pendently of the value that you enter in transaction
DRFOUT, parallel processing is not possible.

/ROP/Generic_ENH_MAP This parameter activates the automatic mapping of customer- x

specific fields that are stored in the CI-Inlcudes of promotional
entities to the corresponding extension segments in the OPP
promotion IDocs.

 Note
Internal tables, structures, and so on, are not supported.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
176 PUBLIC Set Up the Applications
 *This value gives you an idea of usable values for the replication of regular prices and OPP promotions, it is
not a recommendation.

3. Optional: In Customizing activity Define Business Object Settings, specify the application link enabling
(ALE) message type that is to be used for each business object. In this way, you can determine the
retention period for change pointers that are related to the business object. For the outbound processing of
regular prices, no change pointers are used and the retention period is not relevant. The following message
types are relevant for the outbound processing of regular prices and OPP promotions from the central
price and promotion repository:

Business Object Type Message Type

ROP_PRICE /ROP/BASE_PRICE

ROP_PROMO /ROP/PROMOTION

For more information, see Customizing for Cross Application Components under Processes and Tools for
Enterprise Applications Master Data Governance, Central Governance General Settings Data
Replication Overall Information .

Transaction DRFF: Defining Filter Criteria

In Define Filter Criteria, specify your data selection for each replication model and business object. The filter
criteria are valid for Initial replication and Change replication.

6.1.2.10.4 Configure the Central Deployment of the

Promotion Pricing Service

The promotion pricing service (PPS) is an SAP HANA XS advanced (XSA) application. Therefore the
configuration of, for example, database services and back-end connection information, is done before or during
the deploy time. The needed configuration settings are provided via command line interface, or in an extension
descriptor file. Authentication configuration and authorization configuration is done after deploy time.

Prerequisites

● You have installed SAP HANA XSA version 1.0.88 or higher.

● You have access to the XSA command-line tool version 1.0.82 or higher.
● You have an XSA user with the following role collections:
○ XS_CONTROLLER_ADMIN
○ XS_USER_ADMIN
○ XS_USER_PUBLIC
○ XS_AUTHORIZATION_ADMIN

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 177
  Note

In the following documentation this user will be referred to as XSA PPS admin user.

● You have an XSA user with the business role XS_USER_PUBLIC.

 Note

In the following documentation this user will be referred to as XSA PPS business user.

● You have a database user that can access the standard schema of your SAP Customer Activity Repository
system via the SQL port, in which the database tables of the PPS are located.
● You have created and configured the organization and the space in which you want to install the promotion
pricing service application.
● You have downloaded the SCV file XSACOPPPPS00_<patch level>-80004642.ZIP (for example patch
level 0 for the initial delivery) for the PPS from the SAP Support Portal at https://support.sap.com .

Used XSA Services

The PPS application uses the following XSA services:

Service Instance Service Plan Resource Type Description

ppeHANA User-defined n/a org.cloudfoundry.exist­ Service to access the

ing-service database.

ppServiceUaa xsuaa space com.sap.xs.uaa-space Service for for authen­

tication and authoriza­
tion services.

Plan space allows the

installation of the PPS
app in different XSA
spaces.

ppServiceAuditLog auditlog free com.sap.xs.auditlog Audit log broker on the

XSA platform.

 Note

The services ppServiceUaa and ppServiceAuditLog are created and bound automatically during the
installation of the PPS application.

Procedure

1. Create the ppeHana Database Service [page 179]

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
178 PUBLIC Set Up the Applications
 2. Create the Extension Descriptor File [page 181]
3. Configure Authentication and Authorization Settings [page 183]
4. Advanced Configuration Settings [page 185]

Related Information

● For more technical information about SAP HANA XS advanced, see the SAP HANA Developer Guide for SAP
HANA XS Advanced Model on SAP Help Portal at https://help.sap.com/viewer/product/
SAP_HANA_PLATFORM/ <Version> Development SAP HANA Developer Guide .
● For more information about the installation of SAP HANA XS advanced, see the SAP HANA Server
Installation and Update Guide on SAP Help Portal at https://help.sap.com/viewer/product/
SAP_HANA_PLATFORM/2.0.04/en-US <Version> Installation and Upgrade SAP HANA Server
Installation and Upgrade Guide Installing an SAP HANA System Installing XS Advanced Runtime .
● For more administration information about SAP HANA XS advanced, see the SAP HANA Administration
Guide for SAP HANA Platform on SAP Help Portal at https://help.sap.com/viewer/product/
SAP_HANA_PLATFORM/2.0.04/en-US <Version> Administration SAP HANA Administration Guide
for SAP HANA Platform Application Run-Time Services Maintaining the SAP HANA XS Advanced Model
Run Time .

6.1.2.10.4.1 Create the ppeHana Database Service

To make the PPS run, you have to create the database service ppeHana. How to create this service depends on
your SSL (Secure Socket Layer) configuration settings in your SAP HANA database.

SSL Not Activated in SAP HANA

If SSL is not activated in SAP HANA, proceed as follows:

1. Execute the following xs command to create the database service depending on your local environment
For Windows Command Line use:

 Source Code

xs create-user-provided-service ppeHana -p "{\"user\":\"<DB_USER>\",

\"password\":\"<DB_USER_PASSWORD>\",\"url\":\"jdbc:sap://<HOSTNAME>:<PORT>
\",\"driver\":\"com.sap.db.jdbc.Driver\",\"port\":\"<PORT>\",\"host\":
\"<HOSTNAME>\"}"

For Linux Shell use:

 Source Code

xs create-user-provided-service ppeHana -p
'{"user":"<DB_USER>","password":"<DB_USER_PASSWORD>","url":"jdbc:sap://

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 179
 <DB_USER_PASSWORD>","driver":"com.sap.db.jdbc.Driver","port":"<PORT>","host
":"<HOSTNAME>"}'

2. Adjust the following entries in angle brackets (<...>) in the command line:

Entry Comment

<DB_USER> Replace this entry with a valid database user of your SAP
Customer Activity Repository system.

With this user, you must be able to access the standard

schema of your SAP Customer Activity Repository system
via the SQL port, in which the database tables of the PPS
are located.

<DB_USER_PASSWORD> Replace this entry with the password of your database

user (in clear text) in your SAP Customer Activity
Repository system.

 Note
If your password policy forces a password change af­
ter the first login, it must be changed before you cre­
ate ppeHana.

<HOSTNAME> Replace this entry with the database host name of your
SAP Customer Activity Repository system.

<PORT> Replace this entry with the database SQL port of your SAP
Customer Activity Repository system.

 Tip

When you have created the database service, clear the command history to prevent unauthorized
disclosure of the password.

SSL Activated in SAP HANA

If SSL is activated in SAP HANA proceed as follows:

1. Execute the following xs command to create the database service depending on your local environment
For Windows Command Line use:

 Source Code

xs create-user-provided-service ppeHana -p "{\"user\":\"<DB_USER>\",

\"password\":\"<DB_USER_PASSWORD>\",\"url\":\"jdbc:sap://<HOSTNAME>:<PORT>
\",\"driver\":\"com.sap.db.jdbc.Driver\",\"port\":\"<PORT>\",\"host\":
\"<HOSTNAME>\"}"

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
180 PUBLIC Set Up the Applications
 For Linux Shell use:

 Source Code

xs create-user-provided-service ppeHana -p
'{"user":"<DB_USER>","password":"<DB_USER_PASSWORD>","url":"jdbc:sap://
<DB_USER_PASSWORD>","driver":"com.sap.db.jdbc.Driver","port":"<PORT>","host
":"<HOSTNAME>"}'

2. If you want to validate the server certificate, set <VALUE> of validateCertificate to true. In this case, you
either have to ensure that your Java VM trusts the server certificate, or you must set the parameter
certificate as shown in the following example of a ppeHana service instance:

 Sample Code

{
"name" : "ppeHana",
"credentials" : {
"password" : "<DB_USER_PASSWORD>",
"driver" : "com.sap.db.jdbc.Driver",
"port" : "<PORT>",
"host" : "<HOSTNAME>",
"user" : "<DB_USER>",
"url" : "jdbc:sap://<HOSTNAME>:<PORT>/?
encrypt=true&validateCertificate=true",
"certificate" : "-----BEGIN CERTIFICATE-----\nMIIFpzCww[…]----END
CERTIFICATE-----\n"
}
}

 Tip

When you have created the database service, clear the command history to prevent unauthorized
disclosure of the password.

6.1.2.10.4.2 Create the Extension Descriptor File

To store the PPS-specific configuration settings, you must create an extension descriptior file.

1. Create a text file with suffix .mtaext, for example config-op.mtaext.

2. To create the extension descriptor file, copy the following content to the new file that you have created in
step 1:

 Note

This content includes the minimum settings that are necessary to create the extension descriptior file.
Further configuration settings, for example settings for caching, can be added to this file as required.

 Source Code

_schema-version: "2.0.0"
ID: com.sap.retail.ppservice.XSAC_OPP_PPS
extends: com.sap.retail.ppservice.XSAC_OPP_PPS
modules:

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 181
 - name: ppservice-approuter
parameters:
memory: 128M
- name: ppservice-webapp-central
parameters:
memory: 1024M
properties:
sap.dataaccess-common.db.client: "<DB_CLIENT>"
sap.dataaccess-common.logSys: "<LOGSYS>"
DISABLE_SUCCESSFUL_LOGIN_AUDIT_LOG: "<AUDIT_LOG_FLAG>"
JBP_CONFIG_RESOURCE_CONFIGURATION: "['tomcat/webapps/ROOT/WEB-INF/
classes/ppe-schema-orm.xml': {'sap.dataaccess-
common.schema':'<DB_SCHEMA>'},'tomcat/webapps/ROOT/META-INF/context.xml':
{'ppeHana-service-name':'ppeHana'}]"
JBP_CONFIG_JAVA_OPTS: 'java_opts: -D'
provides:
- name: java

 Note

This configuration is written in YAML format. Make sure that you copy the format of the code block
correctly.

3. Adjust the following entries in angle brackets (<...>) in the file:

Entry Comment

<AUDIT_LOG_FLAG> If you set this flag to true, the system creates audit log
messages only for failed login attempts. If you set this flag
to false, every login is recorded. This is of limited use for
an A2A communication. To achieve optimal performance,
SAP recommends to set this flag to true.

<DB_SCHEMA> Replace this entry with the standard database schema of

your SAP Customer Activity Repository system.

<DB_CLIENT> Replace this entry with the client of your SAP Customer
Activity Repository system.

<LOGSYS> Replace this entry with the logical system ID of your mas­
ter data system that is connected to your SAP Customer
Activity Repository client.

If you want to support multiple master data systems in

your SAP Customer Activity Repository client, you need
one promotion pricing service for each system (in differ-
ent spaces).

 Tip

If you need higher values for default memory settings, especially for ppservice-webapp-central,
you can choose larger cache sizes.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
182 PUBLIC Set Up the Applications
 4. Assuming that your extension descriptor file is called config-op.mtaext and that the command is called
from the directory in which your extension descriptor file is stored, execute the following command to
install the application:

 Source Code

xs install <pathToScvFile>/XSACOPPPPS<software_component_version>.ZIP -e
config-op.mtaext

5. Save the extension descriptor file for later update or patch activities.

 Note

If you want to reinstall the same software component version, add the following parameter to the install
command -o ALLOW_SC_SAME_VERSION.

For more information about possible additional parameters, see the documentation of this install
command.

6.1.2.10.4.3 Configure Authentication and Authorization

Settings

To use the central promotion pricing service, you must have the necessary roles created and assigned.

Creating and Assigning a PPS Role Collection

Execute the following steps with your XSA PPS admin user.

1. Create a role collection for the PPS with the following xs command:

 Source Code

xs create-role-collection <NAME> [<DESCRIPTION>]

e.g., xs create-role-collection PPE_ROLE_COLLECTION "PPE ROLE COLLECTION"

2. Navigate to the organisation and space in which the PPS has been installed.

 Tip

You can change organisations and spaces with the xs command xs target -o <ORG_NAME> -s
<SPACE_NAME>.

3. Check if the role template ppservice-webapp-central is listed in the space.

 Note

If the installation has been successful, this role template must be listed in this space. You can verify this
by listing all role templates with xs command xs role-templates.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 183
4. Create a role with the PPS role template:

 Source Code

xs create-role <APP> <ROLE_TEMPLATE> <ROLE_NAME> <DESCRIPTION>

e.g., xs create-role ppservice-webapp-central PPE_ROLE_TEMPLATE
PPE_ROLE_XYZ "PPE role for xyz"

5. Add the new role to the new role collection:

 Source Code

xs update-role-collection <ROLE_COLLECTION> --add-role <ROLE>

e.g., xs update-role-collection PPE_ROLE_COLLECTION --add-role PPE_ROLE_XYZ

6. Assign the new role collection to the XSA PPS business user:

 Source Code

xs assign-role-collection <ROLE_COLLECTION> <USER>

e.g., xs assign-role-collection PPE_ROLE_COLLECTION PPSUSER

 Tip

You can call xs help -a to get an overview of other xs commands regarding role management.

7. Verify that the PPS user that you have created in the prior step is working. For this, you have to enter the
following request details in your REST Client (like Postman for Chrome) to send a calculation request:

Request Details Value

HTTP Request Method POST

Authorization Type = Basic Authentication

User name = <name of the XSA PPS business

user>

Password = <password of the XSA PPS

business user>

 Note
If your password policy prompts users to change their
password when they log on to the system for the first
time, this needs to be done before a request is sent
via Rest Client.

Headers Accept = application/xml

Content-Type = application/xml

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
184 PUBLIC Set Up the Applications
 Request Details Value

URL 1. Call the command xs apps and check for the URL
of the ppservice-approuter app.
2. Append /restapi/ to the URL and enter this infor­
mation in your REST Client.

Body <PriceCalculate xmlns="http://

www.sap.com/IXRetail/namespace/"/>

 Note

If you send this request, you get HTTP response code 400 (Bad Request) because you send an empty
request body.

If you receive HTTP response code 401 (Unauthorized) or 403 (Forbidden), there is something wrong with
your service user, or application. Double-check all steps that you have performed in this chapter.

6.1.2.10.4.4 Advanced Configuration Settings

The following settings are not mandatory in a default setup but help you to adapt the PPS to your specific
needs. Some settings become mandatory if you use the Demand Data Foundation (DDF) extended sales
pricing model.

Configuration of Caches

By default, all database accesses to OPP promotion and regular price entities are cached. You can use the
following two types of caches:

● Object cache based on JPA

In this case, OPP promotions and their child entities (price derivation rules, texts, and so on) are stored in
the L2 object cache of the JPA provider.
● Query result cache based on Spring Framework
In this case, regular prices and the results of search queries for IDs of price derivation rule eligibilities are
stored in a cache. This cache is used via Spring cache abstraction. The cache provider determines the
settings for the query result cache (regular prices, eligibility IDs). Google Guava is the default cache
provider and allows the configuration of the cache via a cache specification string per cache region.

Query Result Caches for OPP Promotions and Regular Prices

The following example shows the setting of the query caches for OPP promotions and regular prices:

 Source Code

# Use Spring caching for promotions and regular prices - true is the default
setting
sap.dataaccess-common.cachenamedqueries=true
# Spring cache for promotions

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 185
 sap.dataaccess-
common.promocachespec=maximumSize=10000,expireAfterAccess=10m,expireAfterWrite
=20m
# Spring cache for regular prices
sap.dataaccess-
common.basepricecachespec=maximumSize=10000,expireAfterAccess=10m,expireAfterW
rite=20m

To apply these settings, they have to be part of the extension descriptor in the properties section. The
following example, merchandise sets are supported and dynamic weaving is activated. It also shows how multi-
line strings can be set in the MTAEXT file which follows the YAML syntax:

properties:
sap.dataaccess-common.db.client: "<DB_CLIENT>"
sap.dataaccess-common.logSys: <LOGSYS>
sap.dataaccess-common.cachenamedqueries: "true"
sap.dataaccess-common.promocachespec:
"maximumSize=10000,expireAfterAccess=10m,expireAfterWrite=20m"
sap.dataaccess-common.basepricecachespec:
"maximumSize=10000,expireAfterAccess=10m,expireAfterWrite=20m"
JBP_CONFIG_JAVA_OPTS: >
java_opts: -DmerchandiseSetsEnabled=true
-Dspring.profiles.active=sapweaving

 Note

● It is also possible to set the PPS configuration properties via -D in the java_opts element of
JBP_CONFIG_JAVA_OPTS. In this case, changing the environment variables, for example via xs set-
env followed by a restart of the application, has no effect.
● Spring profiles and the PCE-related configuration, such as enabling the support for merchandise sets,
must be set in the java_opts element of JBP_CONFIG_JAVA_OPTS. The list of configuration
properties is part of the Functional Guide for the Promotion Calculation Engine on SAP Help Portal at
https://help.sap.com/viewer/p/CARAB <Version> Development Functional Guide for the
Promotion Calculation Engine .

If you want to use the Demand Data Foundation (DDF) extended sales pricing model for OPP, you have to
activate the spring profile sapmultilevelprc, which supports multi-level generated regular prices:

properties:
sap.dataaccess-common.db.client: "<DB_CLIENT>"
sap.dataaccess-common.logSys: <LOGSYS>
sap.dataaccess-common.cachenamedqueries: "true"
sap.dataaccess-common.promocachespec:
"maximumSize=10000,expireAfterAccess=10m,expireAfterWrite=20m"
sap.dataaccess-common.basepricecachespec:
"maximumSize=10000,expireAfterAccess=10m,expireAfterWrite=20m"
JBP_CONFIG_JAVA_OPTS: >
java_opts: -DmerchandiseSetsEnabled=true
-Dspring.profiles.active=sapmultilevelprc

For more information on the DDF extended sales pricing model, see Use the Extended Sales Pricing Model
(DDF) [page 188].

To support both dynamic weaving and the DDF extended sales pricing model, both profiles must be activated:

properties:
sap.dataaccess-common.db.client: "<DB_CLIENT>"
sap.dataaccess-common.logSys: <LOGSYS>

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
186 PUBLIC Set Up the Applications
 sap.dataaccess-common.cachenamedqueries: "true"
sap.dataaccess-common.promocachespec:
"maximumSize=10000,expireAfterAccess=10m,expireAfterWrite=20m"
sap.dataaccess-common.basepricecachespec:
"maximumSize=10000,expireAfterAccess=10m,expireAfterWrite=20m"
JBP_CONFIG_JAVA_OPTS: >
java_opts: -DmerchandiseSetsEnabled=true
-Dspring.profiles.active=sapweaving,sapmultilevelprc

Related Information

● For more information about optional properties that can be set via the extension descriptor, see the
module descriptions and the corresponding property files in the Development and Extension Guide for
Omnichannel Promotion Pricing on SAP Help Portal at https://help.sap.com/viewer/p/CARAB <Version>
Development Development and Extension Guide .
● For more information about caching options, see the Development and Extension Guide for Omnichannel
Promotion Pricing on SAP Help Portal at https://help.sap.com/viewer/p/CARAB <Version>
Development under Promotion Pricing Service PPS Module dataaccess-common .

6.1.2.10.4.5 Update the PPS SAP HANA XSA Application

The promotion pricing service is an SAP HANA XS advanced (XSA) application. Therefore, you have to
download the latest XSA component to update or patch the service. The minimum required XSA version is
1.0.88.

Procedure

The following steps describe how to update the XSA component from version 1.2.12 to 2.0.0:

1. Check the current version of your XSA component with the following command:

 Source Code

xs list-components

The following output is displayed:

 Source Code

Getting software components in org "<ORG>" / space "<SPACE>" as <USER>...

Found software components:
software component
version
--------------------------------
XSAC_OPP_PPS (sap.com) 1.2.12

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 187
2. Download the new SCV file XSACOPPPPS00_<patch level>-80004642.ZIP from the SAP Support
Portal at https://support.sap.com .
3. Assuming that your extension descriptor file is called config-op.mtaext and that the command is called
from the directory in which your extension descriptor file is stored, execute the following command to
install the new or patched application:

 Source Code

xs install <pathToScvFile>/XSACOPPPPS00_<patch level>-80004642.ZIP -e

config-op.mtaext

4. Execute the command used in step 1 and the following output is displayed:

 Source Code

Getting software components in org "<ORG>" / space "<SPACE>" as <USER>...

Found software components:
software component
version
--------------------------------
XSAC_OPP_PPS (sap.com) 2.0.0

6.1.2.10.5 Use the Extended Sales Pricing Model (DDF)

To use the Demand Data Foundation (DDF) extended sales pricing model for omnichannel promotion pricing,
you have to perform several steps for the central and local deployment scenario.

Overview

As of CARAB 5.0, omnichannel promotion pricing (OPP) supports the DDF extended sales pricing model.
Pricing data available in the DDF module of SAP Customer Activity Repository (CAR) has been extended to
include additional levels of sales prices created in the source master data system. The former model stores
prices on product location level only. For more information on the extended sales pricing model, see the DDF
documentation: Definition and Use of Extended Sales Pricing Data.

You must activate the extended sales pricing model and using it is highly recommended. To facilitate a smooth
migration for you, the old model is still available. If you want to use the old model during your migration phase,
prices are replicated for both the extended and old pricing model and stored twice in SAP Customer Activity
Repository. The OPP pricing model itself remains the same as in previous releases because the DDF pricing
model is mapped to the OPP pricing model. Both central and local deployment scenarios for OPP are
compatible with the extended sales pricing model.

 Note

If you are setting up OPP for the first time, you don't migrate as such but you still have to perform the
following steps.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
188 PUBLIC Set Up the Applications
Prerequisites

● You have migrated to the DDF extended sales pricing model for the replication of sales prices from SAP
ERP or S/4HANA to SAP Customer Activity Repository as described in Definition and Use of Extended
Sales Pricing Data. This part is not OPP-specific and concerns your configuration of SAP Customer Activity
Repository.
● If you want to use the old pricing model for the local or central deployment of the promotion pricing service
(PPS), the regular prices must be replicated on product location level from SAP ERP or S/4HANA .

Restrictions

Omnichannel promotion pricing supports the DDF extended sales pricing model but provides the same
functionality and features as with the old model.

With the extended sales pricing model, you can have different regular prices per distribution chain, even for
prices defined per individual DDF location. However, OPP always reads the regular prices for the default
distribution chain of a given business unit (location).

Procedure

To migrate from the old to the extended sales pricing model, you have to differentiate between the local and
central deployment scenario.

Migration in the Local Deployment Scenario

In a local deployment scenario, the price data replication from the central price and promotion repository (SAP
Customer Activity Repository) to an external system, for example SAP Commerce system, takes place. This
data replication is done via iDocs and the Data Replication Framework (DRF) using replication models and
outbound implementations.

To migrate to the extended sales pricing model, you have to use the Data Replication Framework (DRF) with the
outbound implementation for regular prices ROP_PRC_MG (outbound implementation for multi-level generated
regular prices) instead of ROP_PRICE (outbound implementation for regular prices). For a migration in one go,
you have to use the DRF replication model Initialization for all locations (stores). Afterwards, you can
apply the replication model Changes as usual. This one-step migration must be handled just as if you would
start with the data replication from the beginning.

For instructions, see Configure the Outbound Processing for Regular Prices and OPP Promotions → Data
Replication Framework [page 167].

Alternatively, you can do the migration in stages. This is recommended if you have a high data volume. A
common approach is to start with a small amount of data and then gradually increase the data volumes in an
iterative manner until all necessary data has been included. Here, you migrate only groups of locations stage by
stage. For this, you also have to use the DRF replication model Initialization for each location of the group
you want to migrate.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 189
Migration in the Central Deployment Scenario
In a central deployment scenario, the SAP HANA XS advanced (XSA) application for the promotion pricing
service (PPS) is concerned. To use the extended sales pricing model for the central deployment, you have to
deploy the PPS to XSA again and apply a specific configuration for caches. With the spring profile
sapmultilevelprc, you can migrate to the extended sales pricing model. This setting is part of the extension
descriptor in the properties section. For instructions, see Advanced Configuration Settings [page 185].

You can deploy the XSA application for the PPS twice to use either the extended or old pricing model per
deployment according to your price requests. The migration is managed by DDF based on the SAP ERP or S/
4HANA replication scenario.

For more information on the central deployment process, see Configure the Central Deployment of the
Promotion Pricing Service [page 177].

 Note

During your migration phase, you can decide which pricing model you want to use for the respective
deployment scenarios. For example, you can migrate to the extended sales pricing model for the local
scenario and keep using the old model for applying XSA (central deployment).

6.1.3 Troubleshooting

Diagnose and resolve issues that may arise when you install, upgrade, and set up your scenario. If you need to
report a customer incident, see the information at the end of this section.

 Tip

For quick access to support information, log in to the SAP ONE Support Launchpad at https://
launchpad.support.sap.com/#/productsearch . Search for SAP CARAB (back-end product version) or
SAP FIORI FOR SAP CARAB (front-end product version). Find related SAP Knowledge Base articles,
documentation, guided answers, questions & blogs, and download information — all on one page.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
190 PUBLIC Set Up the Applications
Troubleshoot Installation, Upgrade, and Implementation Issues

Installation, Upgrade, and Implementation Issues

Area Symptom Cause Possible Solutions

Installation / Upgrade You want to upgrade the on- Local temporary tables SAP Note 2576497
shelf availability dispatcher (LOCAL_EXCL_PRODUCT,
(transaction /OSA/ LOCAL_LISTED_PRODUCT,
DISPATCH). However, you get and LOCAL_PS_CONF), which
the error SQL Error Code are created and used by OSA
274 : inserted value too large for internal dispatcher proc­
for column. essing, are not dropped auto­
matically during runtime. As
a result, new tables (such as
any containing CHAR40
fields) cannot be created.

This causes an SQL error

when a CHAR40 material is
supplied. If the tables already
exist, subsequent structural
changes to their definition re­
quire a manual intervention.

Installation / Upgrade When upgrading to SAP Not relevant, as the error The error doesn't impact
Customer Activity Repository doesn't impact functionality functionality and can be ig­
5.0 using the zero downtime and can be ignored. nored.
option, you get the following
error in the log file: Error
when deploying HDI objects;
see SAPC-* INRTLCAR and
SAP Note 2602571.

Installation / Upgrade You want to download a revi­ You need the exact download See section Download and
sion of software component path on the SAP Support Install SAP RTL AFL FOR SAP
SAP RTL AFL FOR SAP Portal at http:// HANA (Mandatory) [page
HANA. support.sap.com . 67].

Installation / Upgrade You want to know which revi­ You are looking for an easy 1. Execute transaction
sion of the SAP RTL AFL way to look up the revision in­ db02 to open the
FOR SAP HANA component formation. Diagnostics: Missing
is currently installed. Tables and Indexes
screen.

2. Choose Current

Status Overview

Installed Plug-Ins and

click on RTL.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 191
Area Symptom Cause Possible Solutions

Installation / Upgrade You get an error indicating You must install compatible ● Section Download and
that software component releases (“revisions”) of the Install SAP RTL AFL FOR
SAP RTL AFL FOR SAP following: SAP HANA (Mandatory)
HANA is not compatible. [page 67].
● SAP RTL AFL FOR
SAP HANA ● SAP Note 2818378
(Which releases of SAP
● SAP HANA DATABASE
HANA Platform are sup­
● SAP HANA AFL
ported for which releases
of SAP Customer Activ­
ity Repository applica­
tions bundle (SAP
CARAB)?)

Installation / Upgrade You want to know what AFLs For example, you want to SAP Note 2188129
(application function libra­ check if an AFL was installed
ries) are installed and active or upgraded correctly.
in your SAP HANA database.

Installation / Upgrade You want to verify if your revi­ For example, you might be SAP Note 2375176
sion of SAP HANA Platform experiencing compatibility is­
is compatible with your ver­ sues following an upgrade.
sion of SAP HANA studio.

Installation / Upgrade You have upgraded to com­ Something went wrong dur­ Revisit SAP Note 2377894
patible revisions of the fol­ ing the upgrade. and make sure that you have
lowing components but are carefully followed all the
still experiencing issues: SAP steps for your scenario.
RTL AFL FOR SAP HANA,
SAP HANA AFL, SAP HANA
DATABASE

Installation / Upgrade You want to install or upgrade You need information on pos­ ● SAP Note 2078425
an application function li­ sible causes and solutions. ● SAP Note 2082466
brary (such as SAP RTL AFL
● SAP HANA Server Instal­
FOR SAP HANA) and are ex­ lation and Update Guide
periencing issues with the for your SAP HANA Plat­
SAP HANA Lifecycle Man­ form version under
agement tool (hdblcm, https://help.sap.com/
hdblcmgui). viewer/p/
SAP_HANA_PLATFORM

<Version>
Installation and

Upgrade

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
192 PUBLIC Set Up the Applications
 Area Symptom Cause Possible Solutions

Installation / Upgrade You want to know whether The activation of business You don't need to take action
you need to activate any functions might have been and you don't need to acti­
business functions for either necessary in older releases. vate any business functions
Unified Demand Forecast You want to make sure that for UDF or DDF. While busi­
(UDF) or Demand Data Foun­ you set up UDF or DDF cor­ ness functions might still ex­
dation (DDF). rectly. ist as objects in the systems,
they are not needed for the
setup any longer.

Installation / Upgrade You get the error CAR RETAIL You are using the SAP HANA SAP Note 2022080
APPLSAP DBTech JDBC: AFL software component and
[258]: insufficient privilege: have performed an upgrade
Not authorized. of your SAP HANA Platform.
Previously assigned privi­
leges might have been lost
during the upgrade.

Installation / Upgrade In an upgrade, you get the An issue with CDS views SAP Note 2340418
following error when running must be fixed.
program RUTDDLSCREATE:

3 ETW678Xstart export of
R3TRDDLS<CDS view
name> ...

3WETW000 DDLS <CDS

view name> is not activated.

2EETW190 "DDLS" <CDS

view name> has no active
version.

4 ETW679 end export of

R3TRDDLS<CDS view
name>.

Installation / Upgrade You need information about For example, you have a SAP Note 2568783 (Re­
the Software Provisioning question regarding the instal­ lease Note for Software Provi­
Manager. lation, copy, transformation, sioning Manager 2.0 (recom­
or deletion of a system based mended: SWPM 2.0 SP05))
on SAP NetWeaver ABAP on
SAP HANA.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 193
Area Symptom Cause Possible Solutions

Installation / Upgrade You have implemented an You need to start the recalcu­ SAP Note 2227577
SAP Note with a correction lation manually.
for the SAPUI5 application or
for the calculation of the ap­
plication index. The SAPUI5
application index is not recal­
culated automatically.

Installation / Upgrade You want to install or upgrade As of SAP HANA Platform 2.0 ● Workaround: SAP Note
to a release of SAP Customer SPS04, a message that was 2789289 (Activation
Activity Repository considered a “warning” in of Calculation View Fails
applications bundle using the older releases is now consid­ With Error "column store
Software Update Manager ered an “error”. This error error: [34011] Inconsis­
(transaction SUM). During the prevents the SUM process tent calculation model")
SAP HANA deployment from completing. ● Alternative: Convert the
phase, you get errors such as SAP HANA error mes­
the following: sage back into a warn­

● Datatype string(1333) of ing, then rerun SUM:

JOIN 1. Execute the follow­

$A""TTRIBUTE_VALUE ing SQL statement:
$IMAGE_ID does no""t ALTER SYSTEM
match to datatype ALTER
raw(16) of"" attribute CONFIGURATION
IMAGE_ID in node CLTT ('indexserver
.ini',
'SYSTEM' )
SET
('calcengine'
,
'enable_depre
cated_compone
nt_flags') =
'8192' WITH
RECONFIGURE;
2. Restart transaction
SUM and repeat the
installation or up­
grade step.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
194 PUBLIC Set Up the Applications
 Area Symptom Cause Possible Solutions

Installation / Upgrade You want to install or upgrade The software component SAP You must install a higher revi­
to a release of SAP Customer RTL AFL FOR SAP HANA sion of SAP RTL AFL FOR
Activity Repository that is currently installed in SAP HANA. For the minimum
applications bundle using the your back-end system is not revision required for this re­
Software Update Manager up to date. lease, see the Common Pre­
(transaction SUM). You get requisites in Upgrade the Pre­
the following error: requisites [page 18]. Consult
the requirements for SAP
● Could not create catalog
HANA Platform 2.0 and for
object: invalid name of
SAP RTL AFL FOR SAP
function or procedure;
HANA.
no procedure with name
UDFCORE_AREA_FORE
CAST_15_PROC.

SAP HANA Platform You are experiencing per­ You need performance rec­ See the Performance — Opti­
ommendations to investigate
formance issues after instal­ mize Processes in SAP HANA
the issue and improve the
ling or upgrading to a new section of the SAP Customer
SAP HANA performance in
SAP HANA revision. your customer scenario. Activity Repository Adminis­
tration Guide.

SAP HANA content You have run the /CAR/ You want to know which ob­ ● Execute transaction
ACTIVATE_HTA activation re­ jects have not been activated SLG1 to display the re­
port but the selected SAP correctly and what errors port log:
HANA content is not acti­ have occurred. Towards the bottom of
vated. the log you will generally
find a section that lists
the objects with activa­
tion errors. Keep in
mind, though, that those
objects might not have
any issues themselves
but that the root cause
can also be in depend­
ent objects.
● In transaction
SCTS_HTA_DEPLOY,
try to reproduce the er­
rors by manually rede­
ploying the objects.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 195
Area Symptom Cause Possible Solutions

SAP HANA content You want to perform schema Different causes are possible ● Check that you have en­
mapping in SAP HANA stu­ that can lead to mapping is­ tered the correct
dio. That is, you want to map sues in SAP HANA studio. schema names.
the authoring schemas of ● In particular, make sure
this release to the physical that there are no leading
schemas of your customer or trailing spaces before
system landscape. However, or after the schema
you are encountering issues names. Space charac­
and the mapping doesn’t ters cause issues during
work. schema mapping.
● For step-by-step instruc­
tions, see Verify Correct
Schema Mapping [page
48].

SAP HANA content You have run the /CAR/ The SAP HANA user needs SAP Note 2586850
ACTIVATE_HTA activation re­ additional authorizations
port but get the error (privileges).
Insufficient privilege: Not
authorized.

SAP HANA content You have run the /CAR/ You might have an authoriza­ ● Check if SAP HANA da­
ACTIVATE_HTA activation re­ tion issue. tabase user _SYS_REPO
port but the selected SAP has been assigned privi­
HANA content is not acti­ lege SELECT with option
vated. Grantable to others. If
not, you can grant the
missing privilege using
the following example
SQL statement:
GRANT SELECT ON
SCHEMA <your
schema name> TO
_SYS_REPO WITH
GRANT OPTION;
● Check that other re­
quired authorizations
have been set up cor­
rectly. For more informa­
tion, see section Verify
Back-End Users and
Roles of the Common In­
stallation Guide.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
196 PUBLIC Set Up the Applications
 Area Symptom Cause Possible Solutions

SAP HANA content You have run the /CAR/ You might have a circular de­ SAP Note 2404872
ACTIVATE_HTA activation re­ pendency issue. In particular,
port but the selected SAP you get an error that a
HANA content is not acti­ SQLScript procedure (such
vated. as
SP_SR_GET_PROD_HR_XR_B
Y_DATE) cannot be acti­
vated.

SAP HANA content You have run the /CAR/ You might have a deployment ● SAP Note 2109690
ACTIVATE_HTA activation re­ error in SAP HANA Transport (Error in SAP HANA re­
port but the selected SAP for ABAP (HTA). pository deployment im­
HANA content is not acti­ port step)
vated. ● SAP Note 2321486
(Troubleshooting for SAP
HANA Transport for
ABAP (HTA) deploy­
ment)

SAP HANA content You want to activate SAP Several causes are possible. Check that you have done
HANA content for scenarios Open the error log file and the following tasks as descri­
of SAP Customer Activity search for udf.cor. For ex­ bed in this guide:
Repository applications ample, the following errors ● Have you installed com­
bundle using the /CAR/ can occur: patible revisions of the
ACTIVATE_HTA report in
● Could not create catalog SAP HANA database
transaction SE38. However, and the AFL compo­
object
you are getting errors. nents (SAP HANA AFL,
● Invalid name of function
or procedure SAP RTL AFL FOR

● No procedure with name SAP HANA)? See the

UDFCORE_AREA_MODE Common Prerequisites

L_POS_XX_PRO in section Upgrade the
Prerequisites [page 18].
See also section Down­
load and Install SAP RTL
AFL FOR SAP HANA
(Mandatory) [page 67].
● Have you done the
schema mapping as de­
scribed in this guide?
See Verify Correct
Schema Mapping [page
48].

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 197
Area Symptom Cause Possible Solutions

SAP HANA content You want to activate SAP Several causes are possible. ● Workaround and list of
HANA content for scenarios Open the error log file and affected SAP HANA da­
of SAP Customer Activity search for udf.cor. For ex­ tabase revisions: SAP
Repository applications ample, the following errors Note 2525644 (Input
bundle using the /CAR/ can occur: Variables are set to an
ACTIVATE_HTA report in Empty String When not
● There is neither a default
transaction SE38. However, Mapped in Top-Level
value nor a data input
you are getting errors. Calculation Scenario)
mapping for …"
● If possible for your sce­
● A2EESCTS_HOT 532
nario, consider upgrad­
ing to an SAP HANA da­
tabase revision not af­
fected by the issue.

SAP HANA content After running the /CAR/ You want to know whether SAP Note 2467113
ACTIVATE_HTA activation re­ the activation was successful
port, you get two conflicting and whether any additional
messages: action is required.

● The following scenario

was deployed
successfully...
● But returned error/
warning/information
message(s)...

SAP HANA content You want to generate pre- You might not have activated When you run the /CAR/
season sales projections in all the required SAP HANA ACTIVATE_HTA activation re­
SAP Assortment Planning content. port, make sure to select the
but get an error. required options. See Acti­
vate SAP HANA Content
[page 92].

SAP HANA content You want to check the de­ You might need this informa­ ● In SAP HANA studio: Se­
pendencies of a specific view. tion to solve a dependency or lect the view and choose
activation issue for SAP Auto Documentation
HANA views. from the context menu.
This generates a file with
detailed information on
the view. Consult the
Cross References sec­
tion.
● If you are using the SAP
HANA Live View Browser
app: Select the view and
choose Cross
References.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
198 PUBLIC Set Up the Applications
 Area Symptom Cause Possible Solutions

SAP HANA content You have a question regard­ For example, you want to ● In this guide, search for
ing users or schemas in SAP know what the names of the schema mapping.
HANA. standard SAP HANA users ● SAP Note 2535951
and schemas are. (FAQ: SAP HANA Users
and Schemas)

SAP HANA content You get an error indicating You have not installed soft­ See section Download and
that you are attempting to ware component SAP RTL Install SAP RTL AFL FOR SAP
access inactive or invalid SAP AFL FOR SAP HANA. The HANA (Mandatory) [page
HANA content. component contains back- 67].
end functionality for the Uni­
fied Demand Forecast mod­
ule and the On-Shelf Availa­
bility module in SAP
Customer Activity
Repository. If you don't in­
tend to use those modules,
you don't need to configure
them. However, you must al­
ways install the software
component.

SAP HANA content You get the error Table A program error must be ● SAP Note 2218875
ABAP:/DMF_ORG_ASSIGN fixed. ● SAP Note 2224582
not found.

SAP HANA content You get the error Object A program error must be SAP Note 2224582
DDF_ORG_ASSIGN fixed.
(Calculation View), package
sap.is.ddf.udf.data_validation,
was processed with errors.

SAP HANA content You get the error SQLScript: A program error must be SAP Note 2125672
Could not derive table type fixed.
for variable
"UDF_FC_HORIZON".

SAP HANA content SAP HANA views in the A program error must be SAP Note 2203930
sap.is.ddf.fms package fixed.
do not activate properly.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 199
Area Symptom Cause Possible Solutions

SAP HANA content You need to manually deploy The automatic deployment ● Search for the following
SAP HANA objects and pack­ to the SAP HANA repository sections in the product
ages. of the target system has documentation of your
failed. SAP NetWeaver plat­
form at https://
help.sap.com/viewer/p/
SAP_NETWEAVER: SAP
HANA Transport for
ABAP and Manually De­
ploying SAP HANA Ob­
jects and Packages. Fol­
low the instructions.
● Execute transaction
SCTS_HTA_DEPLOY
for the manual deploy­
ment of SAP HANA con­
tent and consult the ac­
companying system
documentation.

SAP HANA content You get any of the following The root cause is the usage You can ignore the error mes­
errors: of CDS (Core Data Services) sages and continue with the
on top of external views. installation or upgrade proc­
● View "/AMR/..." does not
ess. For explanations, see
exist in data base
SAP Note 2330184 .
● "DDL Source" "/
AMR/...." could not be
activated
● "DDL Source" "/DMF/
DIST_..." could not be
activated

SAP HANA content You get the error SQL Script The root cause is the usage You can ignore the error mes­
message: invalid table name: of CDS (Core Data Services) sages and continue with the
Could not find table/ on top of external views. installation or upgrade proc­
view /AMR/V. ess. For explanations, see
SAP Note 2441184 .

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
200 PUBLIC Set Up the Applications
 Area Symptom Cause Possible Solutions

SAP HANA content You get the error View with A data element that is new or SAP Note 2289913
par. <CDS view name>: data has been redefined is used in
element <data element> par. the new definition in a Core
& does not exist or not active. Data Services (CDS) view
with parameters for the defi-
nition of a parameter.

The system does not con­

sider the dependency be­
tween data elements and the
type definition of the param­
eters for views with parame­
ters.

SAP HANA content When doing ATC (ABAP Test The system does not con­ SAP Note 2374190
Cockpit) checks of database sider base information of the
objects or runtime objects, AMDP table function entity.
you get errors related to ref­
erence tables and reference
fields:

● Priority 1 error: View

<view_name> is not
consistent
● Priority 1 error:
<view_name-field> is not
consistent
● Inconsistencies in fields
related to reference ta­
bles and reference fields

SAP HANA Platform You cannot install the SAP You cannot install XSA as SAP Note 2388443
HANA XS advanced (XSA) long as SAP HANA dynamic
runtime. tiering is active on the same
host.
For example, you need XSA
to use the Omnichannel Pro­
motion Pricing (OPP) module
in SAP Customer Activity
Repository.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 201
Area Symptom Cause Possible Solutions

SAP HANA Platform You are experiencing per­ Several causes are possible. ● SAP Note 2600030
formance issues in the SAP (Parameter Recommen­
HANA Platform. dations in SAP HANA En­
vironments)
● SAP Note 2100040
(FAQ: SAP HANA CPU)
● SAP HANA Trouble­
shooting and Perform­
ance Analysis Guide for
your SAP HANA Plat­
form version under
https://help.sap.com/
viewer/p/
SAP_HANA_PLATFORM

SAP HANA Platform You want to perform an SAP You need information on spe­ SAP Note 1969700 (SQL
HANA database analysis to cial SQL statements for such Statement Collection for SAP
investigate a complex issue. an analysis. HANA)
The information that you
want to retrieve is not or is  Note
only partially available in
For additional trouble­
standard tools (such as SAP
shooting and perform­
HANA studio).
ance tips, see the FAQ: ...
notes under References.

SAP HANA Platform You are not sure if the instal­ You need a list of the compat­ SAP Note 2375176 (SAP
led SAP HANA revision is ible revisions. HANA Revisions and Compat­
compatible with the installed ible SAP HANA Studio Ver­
SAP HANA studio version. sions)

SAP HANA Platform You are experiencing network You need information on net­ SAP Note 2222200 (FAQ:
or performance issues in work settings and analyses in SAP HANA Network)
your SAP HANA environ­ SAP HANA environments.
ment.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
202 PUBLIC Set Up the Applications
 Area Symptom Cause Possible Solutions

Hierarchies You get errors when creating The system does not gener­ ● See section Configure
or updating location hierar­ ate the flat structures for the Automatic Flattening of
chies and/or product hierar­ hierarchies. You need to do Hierarchies of the Com­
chies. some configuration steps so mon Installation Guide.
that the hierarchies get flat- ● See the following sec­
tened automatically. tions of the SAP
Customer Activity
Repository Administra­
tion Guide at https://
help.sap.com/viewer/p/
CARAB:
○ Configure Demand
Data Foundation
(DDF)
○ Configure Data Rep­
lication from SAP
ERP to DDF

Hierarchies You get errors when import­ A program error must be ● SAP Note 2244521
ing article hierarchies (prod­ fixed. ● SAP Note 2245134
uct hierarchies) from your
master data system.

Hierarchies You want to know which loca­ You can implement an easy SAP Note 2208619
tions are included in each enhancement for ta­
version of an offer. ble /DMF/OFR_LG_LOC.

Hierarchies An error occurs for a DDL A program error must be SAP Note 2377525
SQL view when you execute fixed.
the CREATE VIEW state­
ment.

DRF data replication frame­ You have deleted a vendor A program error must be SAP Note 1872136
work (transaction DRFOUT) from the /DMF/D_VENDOR fixed.
table but this deletion is not
replicated to the master data
system.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 203
Area Symptom Cause Possible Solutions

DRF data replication frame­ You get an error when using A program error must be ● SAP Note 1904782
work (transaction DRFOUT) the DRF with the PMPL SAP fixed. ● SAP Note 2167629
ERP outbound implementa­ ● See the application help
tion. for SAP Customer
Activity Repository at
https://help.sap.com/
viewer/p/CARAB

<Version>

Application Help SAP

Customer Activity

Repository Demand

Data Foundation
Integration Information

Master Data
Replication from SAP
ERP to Demand Data

Foundation

DRF data replication frame­ You get the error Product &1, A program error must be SAP Note 2163602
work (transaction DRFOUT) location &2: The Valid From fixed.
time for &3 must be
00:00:00 (message 364 in
message class /DMF/
MSG_HL).

DRF data replication frame­ You have changed the listing A program error must be SAP Note 1932525
work (transaction DRFOUT) information in your source fixed.
master data system and re­
plicated the changes to your
SAP Customer Activity
Repository system. However,
the listing information there
is not updated correctly.

Performance You are experiencing per­ You need information on how See the SAP HANA Trouble­
formance issues in your SAP to troubleshoot and resolve shooting and Performance
HANA database. those issues and how to en­ Analysis Guide under https://
hance performance in gen­ help.sap.com/viewer/p/
eral. SAP_HANA_PLATFORM

<Version>

Administration .

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
204 PUBLIC Set Up the Applications
 Area Symptom Cause Possible Solutions

Performance You get a runtime error or Different causes are possible. Use the ABAP dump analysis
exit message and need infor­ (transaction ST22) to search
mation about possible for short dumps and call up
causes and solutions. detailed error information.

Performance You are using the Update You can enhance the per­ SAP Note 2080423
Sales Projection function in formance by implementing
SAP Assortment Planning an SAP Note.
(workbooks Product Planning
and Size Planning). You are
experiencing performance is­
sues when using the function
with large data volumes.

OData During the execution of an The Core Data Services SAP Note 238998
OData service based on (CDS) view uses a table func­
SADL with CDS, an assertion tion that is not active in the
fails in class database. The trigger that is
CL_SADL_SQL_STATEMENT, supposed to activate it fails
method because of missing parame­
EXECUTE_PREPARED_STATE ters if only $count is quer­
MENT. The OData request ied.
uses the system query option
$count.

Support You have a customer incident You need information on how ● SAP Note 35010
and need to set up a service to set up the service connec­ (overview)
connection to SAP. tion. ● SAP Note 1634848
(service connection for
SAP HANA database)
● SAP Note 1592925
(service connection for
SAP HANA studio)

Source Master Data Systems You get the error The error is caused by the SAP Note 2249880
SYSTEM_ABAP_ACCESS_DE “Blacklist Monitor” in SAP S/
NIED. 4HANA.

SAP Fiori ● You want to start an SAP You must set up the adapta­ SAP Note 2283716
Fiori app for a key user tion transport organizer
and get the error (ATO) to be able to transport
Application is not key user extensions.
configured. Find details
in SAP Note 2283716.
● You want to activate ex­
tensibility for key users.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 205
Area Symptom Cause Possible Solutions

SAP Fiori You want to check the SA­ There are several methods SAP Note 2282103
PUI5 version installed in your how you can check the ver­
system. sion.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
206 PUBLIC Set Up the Applications
 Area Symptom Cause Possible Solutions

SAP Fiori You cannot open the Analyze Several reasons are possible. Use section Set Up the Ana­
Forecast app. See the checklist at the right lyze Forecast App in the Com­
and verify that the app is set mon Installation Guide for ref­
up correctly. erence and check the follow­
ing:

1. In transaction SE80,
navigate to package
UICAR001, subpackage
UISCAR01. Check that
the BSP Applications for
the app
(ANALYZFCST_V2) and
the reuse library
(UDFREUSE) are de­
ployed.
2. In Launchpad
Customizing (transac­
tion LPD_CUST), check
that the Internet Com­
munication Framework
(ICF) services for
ANALYZFCST_V2 and for
UDFREUSE are active.
3. Clear the cache on the
server side by running
the following reports in
transaction SE38:
○ /UI5/
APP_INDEX_CALCU
LATE: Select Single
SAPUI5 Repository
Only and run the re­
port once for
ANALYZFCST_V2
and once for
UDFREUSE.
○ /UI2/
INVALIDATE_GLOB
AL_CACHES: Run
this report in execu­
tion mode.
○ /UI2/
INVALIDATE_CLIE
NT_CACHES: Run

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 207
Area Symptom Cause Possible Solutions

this report for all

users.
4. Clear the browser cache.
5. Check if you can now ac­
cess the app.

Support You have an issue that in­ Various causes are possible. For a successful remote sup­
volves modeling and fore­ For example, the issue might port session, make sure that
casting with the Unified De­ be in the ABAP layer, the the required authorizations
mand Forecast (UDF) mod­ foundation component (such and debugging privileges for
ule in SAP Customer Activity as SAP S/4HANA founda­ UDF are all set up. Otherwise,
Repository. You cannot de­ tion), or in the SAP HANA da­ the support team cannot ac­
bug the issue yourself. You tabase. cess your UDF system envi­
need assistance from SAP ronment.
via a remote support session.
See SAP Note 2920776 .

Help Portal You cannot access the con­ Customers and partners See SAP Note 2499831
tent on the SAP Help Portal. need to log on with their S- (SAP Help Portal S-User Man­
For example, you might get user IDs (NOT their email ad­ agement).
one of the following errors: dress) to see content author­
ized specifically for custom­
● We're sorry, but this con­
ers/partners.
tent is not accessible
● HTTP 403 forbidden

Troubleshoot Operation Issues

You also may experience issues during the day-to-day running of your application. For troubleshooting
information, see the application-specific Administration Guides at https://help.sap.com/viewer/p/CARAB:

● SAP Customer Activity Repository Administration Guide: section Troubleshooting for SAP Customer Activity
Repository Modules
● SAP Allocation Management Administration Guide: section Troubleshooting
● SAP Assortment Planning Administration Guide: section Troubleshooting
● SAP Merchandise Planning Administration Guide: section Troubleshooting
● SAP Promotion Management Administration Guide: section Management of SAP Promotion Management

Report a Customer Incident

● If you experience an issue with your back-end or front-end system, we recommend that you first search for
existing solutions in the SAP Support Portal at http://support.sap.com/ . There you can find SAP Notes
(corrections), SAP Knowledge Base articles, and a wealth of information in the SAP Community.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
208 PUBLIC Set Up the Applications
 ● To view or report an incident, see again http://support.sap.com/ and choose My Support Product
Support Report an Incident .
● For more information on reporting incidents for SAP Customer Activity Repository, see the Support Desk
Management section of the SAP Customer Activity Repository Administration Guide.

6.2 SAP Merchandise Planning

This upgrade guide describes upgrading from SAP Merchandise Planning 4.0 Initial Shipment Stack to SAP
Merchandise Planning 5.0 Initial Shipment Stack. You must have completed the upgrade activities in this guide
under SAP Customer Activity Repository Core (Mandatory) .

6.2.1 Verify SAP HANA Content for SAP Merchandise

Planning

Verify all SAP HANA Transport for ABAP (HTA) objects that are required for SAP Merchandise Planning
application.

Prerequisites

As a mandatory prerequisite for a successful activation of SAP HANA content for SAP Merchandise Planning,
you must have successfully completed all of the procedures listed in the previous sections of this guide as
pertains to SAP Customer Activity Repository Core (Mandatory for All Applications) . In particular, you
must have created all the necessary tables, as described in Create/Replicate Source Master Data System
Tables [page 88].

You must also have mapped all the necessary schemas, as described in Verify Correct Schema Mapping [page
48].

Context

In this procedure you perform the final activation of SAP HANA content (views and stored procedures) required
by the SAP Merchandise Planning application. This final activation results in a full activation of the SAP HANA
content for SAP Merchandise Planning. Several SAP HANA views depend on local BI Content objects. The SAP
HANA views must be in active state before activating the BI Content objects as described in Activate
Application BI Content Upgrade [page 210] .

For more information, see https://help.sap.com/viewer/p/SAP_HANA_PLATFORM, choose the SAP HANA

Developer Guide and search for section Activating Objects.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 209
Procedure

1. Log on to SAP HANA studio.

2. Open the Modeler and use the Navigator to access your back-end system.
3. Expand the Content folder located under your system name in the Navigator.
4. Expand the listed packages to verify the underlying folders listed below are active.

Based on the selected ECC Mode in the above report the following packages should exist:

○ SAP ERP:
○ sap.is.ddf.ecc
○ Fashion Management:
○ sap.is.ddf.ecc
○ sap.is.ddf.fms
○ S/4HANA:
○ sap.is.ddf.fms_s4h
5. The following packages should exist resulting from the standard installation:
○ sap.is.ddf.ddf
○ sap.is.retail.rap.ap
○ sap.is.retail.rap.common_bw
○ sap.is.retail.rap.mpr
○ sap.is.retail.rap.mpr_oc

If any of these packages are missing, you must activate those relative to the order above due to
dependencies. Use transaction SCTS_HTA_DEPLOY to activate each missing package, don’t include sub-
packages in case you decide to activate the above mentioned packages using this transaction .

6.2.2 Activate Application BI Content Upgrade

 Caution

Proper authorization is required to complete these steps.

These instructions are to activate content under the Merchandise Planning Omni Channel ( /RAP/MPOC)
InfoArea for the following objects types:

● Advanced DataStore Objects

● Workbooks (will automatically activate):
○ Composite Providers
○ Aggregation Levels
○ Queries
○ Planning Sequences
○ Reactivate Advance Datastore Objects (aDSOs)

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
210 PUBLIC Set Up the Applications
Planning Sequences
Planning Sequence
Planning Sequence

/RAP/MHDS2_A3_PS01

/RAP/MHDS2_A3_PS02

/RAP/MPDS0_A0_PS01

/RAP/MPDS0_A0_PS02

/RAP/MPDS0_A0_PS03

/RAP/MPDS0_A2_PS01

/RAP/MPDS1_A1_PS01

/RAP/MPDS1_A1_PS02

Activation Steps

The object types must be activated in the order above. Each object type and the detail objects are listed in the
tables below and should be compared to the activated objects in your environment. To activate, use transaction
RSOR to launch the BW workbench.

1. Verify transport connections.

1. Select Transport Connection in the left-hand frame.
2. Select Object Types.
3. Locate and expand Source System.
4. Double click Select Objects to ensure that the back-end system is selected as the source system in the
pop up window.
5. Choose Transfer Selections in the same window.
6. In the title bar of he right-hand frame, above the list of Collected Objects, choose Grouping and select
Only Necessary Objects in the context menu.
7. At the top of the right-hand frame, choose Collection Mode and select Collect Automatically.
2. If you have modified standard /RAP/* BI Content objects in your local environment, you must enable the
Match (X) or copy option. Otherwise go to step 3.
1. During the activation of each BI Content object type, you will be asked to carry out an additional
Transfer selections step. In this step, select to install the Active Version (that is, your modified version)
or the Content Version (that is, the SAP delivered, and possibly updated version of the object). The
project implementation team should advise you on which option is required for each object.
3. Activate the InfoObject catalog. If at any point during the installation of BI Content objects you are
presented with a dialog asking you to add objects to a personal list, we recommend that you select No.

 Remember

You can ignore activation warnings listed under Activation Warnings [page 236].

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 211
Activate Advanced DataStore Objects

 Note

A window being referenced, may be hidden. Use the Data Warehousing Workbench menu in the main
window title bar to hide/unhide the following windows: Navigation, All Objects, and Collected Objects.

● Use transaction RSOR to launch the BW workbench Transport Connection.

● In the navigation window, locate and select Object Types. In the window All Objects According to Types,
expand node DataStore Objects (advanced) and double click Select Objects. In the popup window, select
the following objects and select button Transfer Selections.

DataStore Object (advanced)

aDSO Description aDSO

Market Hierarchy CR based on Planning Configuration Set /RAP/MHDS1

Market Hierarchy CR aDSO for LY and LLY /RAP/MHDS2

aDSO for actuals of LY and LLY KPIs /RAP/MPDS0

MP - Regional Month Sales Target for Omni Channel /RAP/MPDS1

MP - Local Month Sales Inventory Targets for Retail and E- /RAP/MPDS2

Co

MP - Local Month Sales and Inventroy Targets for Whol­ /RAP/MPDS3

sale

Product Hierarchy CR based on Planning Configuration /RAP/PHDS1

Set

Product Hierarchy CR aDSO for LY and LLY /RAP/PHDS2

Merchandise Plan YSCT Characteristic Relationship /RAP/SCTDS

● Select Yes to the system prompt Do you want to add the objects to the personal list.
● When prompted for Source System, do not choose any and select OK.
● For each aDSO, right click on the object and select option Install All Below.
● Install and Activate each aDSO.

Activate Analysis Office Excel Workbooks 2.0

In this section you will continue from the above step and activate the workbooks.

● From the left navigation panel for BI Content locate and expand folder More Types. Expand Analysis Office
Excel Workbook and double click Select Objects. Use the filter in the popup window to define a filter on
column Object Name having values of /RAP/MP_*.
In the pop up window, select the following objects and select button Transfer Selections.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
212 PUBLIC Set Up the Applications
 Workbooks
Workbook Object Name

/RAP/MP_ECOM_PHN5_WB_01

/RAP/MP_OTB_OTS_PHN5_WB_01

/RAP/MP_OTB_OTS_PHN5_WB_02

/RAP/MP_RTL_PHN5_WB_01

/RAP/MP_RT_PHN5_M_WB_01

/RAP/MP_RT_PHN7_WB_01

/RAP/MP_RT_SSN_PHN5

/RAP/MP_WHS_PHN5_M_WB_01

● Select Yes to the system prompt Do you want to add the objects to the personal list.
● For each workbook, right click and select option Install All Below.
● Install and Activate each workbook.

Verify Installed Objects

In addition to the advanced DataStore Objects in the above steps, see the tables below to verify all expected
objects are installed.

Composite Providers

Composite Provider Description Composite Provider

Merchandise Financial Plan Omni Channe /RAP/CP15

Aggregation Levels

Aggregation Description Aggregation Name

MP Regional Targets Sales Mix - PHN 5 /RAP/C15A01

MP Regional Targets SSN Sales Mix - PHN 5 /RAP/C15A02

MP Regional Targets SSN Sales Mix - PHN 7 /RAP/C15A03

MP Local Targets - ECommerce - Sales Mix - PHN 5 /RAP/C15A11

MP Local Targets - ECommerce - Sales Mix - PHN 5 - PF /RAP/C15A12

MP Local Targets - Retail - Sales Mix - PHN 5 /RAP/C15A21

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 213
Aggregation Description Aggregation Name

MP Local Targets - Retail - Sales Mix - PHN 5 - PF /RAP/C15A22

MP Local Targets - WHS - Sales Mix - PHN 5 /RAP/C15A31

MP Local Targets - WHS - Sales Mix - PHN 5 - PF /RAP/C15A32

MP - OTB - Retail - ECom - WHS /RAP/C15A41

AL for Market Hier CR for LY and LLY /RAP/MHDSA2

Product Hierarchy CR based on Planning Configuration Set /RAP/PHDSA1

SCT CR based on Planning Configuration Set /RAP/SCTDA1

AL for Product Hier CR for LY and LLY /RAP/PHDSA2

Market Hierarchy Aggregation Level /RAP/MHDSA1

AL for Actuals of LY and LLY KPIs /RAP/MPDSA0

Queries

Query Name Technical Name

MP - Regional Targets - Prompt Query - PHN5 /RAP/CP15A01_Q01

MP - Regional Targets - Sales Mix - PHN5 /RAP/CP15A01_IRQ01

MP - Regional Targets - Season Prompt Query - PHN5 /RAP/CP15A02_Q01

MP - Regional Targets - Season Flow - PHN5 /RAP/CP15A02_IRQ00

MP - Regional Targets - Season Sales Mix - PHN5 /RAP/CP15A02_IRQ01

MP - Regional Targets - Season Flow Chart - PHN5 /RAP/CP15A02_Q00

MP - Regional Targets - Season Flow - PHN7 /RAP/C15A03_IRQ00

MP - Regional Targets - Season Sales Mix - PHN7 /RAP/CP15A03_IRQ01

MP - Regional Targets - Season Flow Chart - PHN7 /RAP/CP15A03_Q00

MP - Regional Targets - Prompt Query - PHN7 /RAP/CP15A03_Q01

MP - Local Targets - ECom - Sales Mix - PHN5 /RAP/CP15A11_IRQ01

MP - Local Targets - ECom - Inventory Mix - PHN5 /RAP/CP15A11_IRQ02

MP - Local Targets - ECom - Prompt Query - PHN5 /RAP/CP15A11_Q01

MP - Local Targets - Rtl - Sales Mix - PHN5 /RAP/CP15A21_IRQ01

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
214 PUBLIC Set Up the Applications
 Query Name Technical Name

MP - Local Targets - Rtl - Inventory Mix - PHN5 /RAP/CP15A21_IRQ02

MP - Local Targets - Rtl - Prompt Query - PHN5 /RAP/CP15A21_Q01

MP - Local Targets- WHS - Sales Mix - PHN5 /RAP/CP15A31_IRQ01

MP - Local Targets - WHS - Inventory Mix - PHN5 /RAP/CP15A31_IRQ02

MP - Local Targets - WHS - Prompt Query - PHN5 /RAP/CP15A31_Q01

MP - OTB Reconciliation Report - Prompt Query /RAP/CP15_Q001

MP - OTB Reconciliation Report /RAP/CP15_Q01

MP - OTB Reconciliation Season Prompt Query /RAP/CP15_Q002

MP - OTB Reconciliation Report - Season /RAP/CP15_Q02

Merchandise Planning Workbooks

Workbook Description Workbook Technical Name

1.1 Regional Monthly Plan /RAP/MP_RT_PHN5_M_WB_01

1.2 Regional Seasonal Plan /RAP/MP_RT_SSN_PHN5

1.3 Regional Seasonal Plan /RAP/MP_RT_PHN7_WB_01

2.1 Retail Monthly Plan /RAP/MP_RTL_PHN5_WB_01

3.1 Wholesale Monthly Plan RAP/MP_WHL_PHN5_M_WB_01

4.1 Ecommerce Monthly Plan /RAP/MP_ECOM_PHN5_WB_01

5.1 OTB & OTS Reconciliation /RAP/MP_OTB_OTS_PHN5_WB_01

5.2 OTB & OTS Sseason Reconciliation /RAP/MP_OTB_OTS_PHN5_WB_02

Change aDSO Behavior

You must change the loading behavior for each aDSO. Select the InfoProvider node under Modeling. Locate the
central InfoProvider column and expand the Merchandise Planning Omni Channel change the loading
behavior for each aDSO. To change the loading the behavior, locate each object in the DataStore (advanced)
table above and then right click to select Planning-Specific Properties Change Real-Time Load Behavior.
Select radio button Real-Time Target Can Be Planned; Data Loading Not Allowed.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 215
  Remember

BI Content developed on top of aggregation levels /RAP/T15A23, /RAP/T15A24, /RAP/T15A25, /RAP/

T15A27, /RAP/T15A34 and /RAP/T15A35 are for internal testing and do not need to be activated.

6.2.3 Verify Time Data

Ensure that the previously generated calendar time data is still for running your SAP Merchandise Planning
process.

Procedure

Ensure that the time data for the Fiscal calendar has been generated far enough into the past and future.

For more information, see the following:

○ Maintain Fiscal Year Variants section of the Common Installation Guide

6.3 SAP Assortment Planning

This section lists the steps for the different SAP Assortment Planning upgrade scenarios.

This upgrade guide describes upgrading fromSAP Assortment Planning 4.0 FP00 to SAP Assortment Planning
5.0. You must have completed the upgrade activities in this guide under Core (Mandatory) .

6.3.1 4.0/4.0 FPS01/FPS02/FPS03/SPS05 to 5.0

Upgrade information.

This section is intended for existing SAP Assortment Planning customers who have installed and configured
SAP Assortment Planning 4.0, 4.0 FPS01, 4.0 FPS02, 4.0 SPS03 or 4.0 SPS05 and would like to upgrade to
SAP Assortment Planning 5.0.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
216 PUBLIC Set Up the Applications
6.3.1.1 Perform Core Steps for SAP Customer Activity
Repository

To set up this application, you must first perform the Core (Mandatory) steps for SAP Customer Activity
Repository. The core steps are mandatory for all the consuming applications.

Procedure

Perform all steps listed under Core (Mandatory for All Applications) [page 81].

6.3.1.2 Adjust Customizing Settings

Customizing to maintain following an upgrade to SAP Assortment Planning 5.0.

Context

Following the upgrade, you need to make settings in Customizing to be able to use SAP Assortment Planning
5.0.

Procedure

1. Log on to your back-end system.

2. If you use the Retail SAP BW Structure and you don't want to use planning configuration, do the following:
a. Disable Use Planning Configuration and Prompt in Manage Location Clusters (using transaction SPRO)
under Cross-Application Components Assortment Planning Imported Demand Data Foundation
Settings Basic Settings Define Default Values .

You must disable this Customizing setting to continue using the Retail SAP BW Structure. For more
information, see section Reactivate Planning Framework Content (SAP Assortment Planning).
b. Disable the implementation of BAdI: Read Merchandise Planning KPI Data under Cross-Application
Components Demand Data Foundation Data Maintenance Planning Configuration
Enhancements Using Business Add-Ins .

You must disable the implementation of this BAdI to continue using the Retail SAP BW Structure. For
more information, see section Reactivate Planning Framework Content (SAP Assortment Planning).

If you use the Omnichannel SAP BW structure, make sure that Use Planning Configuration is enabled.

3. Maintain the monthly fiscal year variant (using transaction SPRO) under Cross-Application Components
Assortment Planning Imported Demand Data Foundation Settings Basic Settings Define Default

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 217
 Values Monthly FY Variant . This is necessary to use the view Sales & Inventory Analysis in the My
Assortment Lists app.

For more information, see Fiscal Year Variant.

4. Define the business week (using transaction SPRO) under Cross-Application Components Demand
Data Foundation Basic Settings Define Business Week .

5. Maintain number ranges for planning configurations under Cross-Application Components Assortment
Planning Number Ranges Maintain Number Range for Planning Configuration .

6. Maintain number ranges for parameter configurations under Cross-Application Components

Assortment Planning Number Ranges Maintain Number Range for Parameter Configuration .
7. Make sure that the settings in Customizing activity Assortment List Settings fit to your planning process.

The Assortment List Settings activity is available in Customizing under Cross-Application Components
Assortment Planning Assortment Lists .
8. If you want to allow users access to the Analyze Forecast app via links from the My Assortment Lists app,
enable the Create option to generate a location hierarchy out of every location cluster set activated in SAP
Assortment Planning. This option is available in the Location Clustering Settings Customizing activity under
Cross-Application Components Assortment Planning for Retail Imported Demand Data Foundation
Settings Data Maintenance Location Clustering Location Clustering Settings .

If the Create option is not visible, choose New Entries.

9. To use forecasted values in the Sales & Inventory Analysis view within the My Assortment Lists app,
configure Unified Demand Forecast (UDF). For more information, see the SAP Customer Activity Repository
Administration Guide, section Configure Unified Demand Forecast (UDF).
10. Verify default implementation of BAdI: Determine Product Season Classification and, if necessary, provide a
custom implementation.

The BAdI, BAdI: Determine Product Season Classification is available under Cross-Application
Components Assortment Planning Enhancements Using Business Add-Ins .

6.3.1.3 Verify Fiscal Calendar

Verify that the previously generated calendar time data is still running following an upgrade to SAP Assortment
Planning 5.0.

Context

The generation of time data (Fiscal calendar) is required for using the Sales & Inventory Analysis view in the My
Assortment Lists app. The fiscal calendar is also required to initialize the SAP Assortment Planning BW
structure, as it allows for planning on fiscal periods.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
218 PUBLIC Set Up the Applications
Procedure

If required and not already done, ensure that the time data has been generated far enough into the past and
future for SAP Assortment Planning 5.0.

For more information, see the following:

○ Generate Time Data - Fiscal Calendar section of the Common Installation Guide
○ Management section of the SAP Assortment Planning Administration Guide

6.3.1.4 Reactivate Planning Framework Content (SAP

Assortment Planning)

There are two distinct BW structures supported in SAP Assortment Planning:

Omnichannel SAP BW Structure

 Caution

New functionality will be only available for the Omnichannel SAP BW structure. Therefore, we recommend
to use the Omnichannel SAP BW structure which provides an extensive feature set.

● If you already use the Omnichannel SAP BW structure, reactivate it.

● If you were using the previously existing Retail SAP BW structure, we recommend that you reactivate it
during the upgrade. If later you would like to switch to the new Omnichannel SAP BW structure, please
contact SAP for assistance with your upgrade project.

Make sure that you have enabled the optimized in-memory planning capabilities of the integrated planning
engine in SAP Business Warehouse. For more information, see the Common Installation Guide, section Enable
Optimized In-Memory Planning Capabilities of SAP BW Integrated Planning.

Prerequisite

To use the Omnichannel SAP BW structure, the following prerequisites must be met:

● Enable the usage of planning configurations under Cross-Application Components Assortment

Planning Imported Demand Data Foundation Settings Basic Settings Define Default Values . The
Omnichannel SAP BW structure only works when planning configurations are used.
● Enable the implementation of BAdI: Read Merchandise Planning KPI Data under Cross-Application
Components Demand Data Foundation Data Maintenance Planning Configuration Enhancements
Using Business Add-Ins .

The Omnichannel SAP BW structure consists of local BI Content only. To create workbooks on top of the
Omnichannel SAP BW structure, contact SAP Digital Business Services for a custom implementation project.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 219
Retail SAP BW Structure

 Caution

If you were using the Retail SAP BW Structure in a previous release, we recommend that you reactivate this
structure during the upgrade. The Retail SAP BW Structure will be supported with maintenance, however
no new functionality will be developed for this structure. If later you would like to switch to the new
Omnichannel SAP BW structure, please contact SAP for assistance with your upgrade project.

Prerequisite

To use the Retail SAP BW structure, the following prerequisites must be met:

● Disable the usage of planning configurations under Cross-Application Components Assortment

Planning Imported Demand Data Foundation Settings Basic Settings Define Default Values . You
cannot use the Retail SAP BW structure with planning configurations.
● Disable the implementation of BAdI: Read Merchandise Planning KPI Data under Cross-Application
Components Demand Data Foundation Data Maintenance Planning Configuration Enhancements
Using Business Add-Ins .

6.3.1.5 Upgrade from Omnichannel SAP BW Structure

If you already use the Omnichannel SAP BW structure, activate the local BI Content objects as described in
subsection Activate Application BI Content (Omnichannel SAP BW Structure).

6.3.1.5.1 Activate Application BI Content (Omnichannel

SAP BW Structure)

Context

In this procedure, you perform a sequential, step-by-step activation of the local BI Content objects delivered in
the Omnichannel SAP BW structure of the SAP Assortment Planning application. SAP Assortment Planning
uses this application BI Content to consume data stored in the back-end system

 Note

To ensure correct activation of the BI Content objects, carry out the activation sequentially, as specified in
the following procedures. Resolve any activation warnings, except for the ones listed under Result [page
228], which can be ignored.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
220 PUBLIC Set Up the Applications
 Also, do not disable the default BI setting to collect and activate all dependencies. The instructions below
activate a minimum subset of objects, and it assumed that all their dependencies are collected and
activated.

The consumed data from the back-end system can be created by the SAP Assortment Planning application, or
be replicated from a source master data system. In both cases, beware of limitations with regard to the
characters allowed by SAP BW. For more information, see:

● SAP Assortment Planning Administration Guide under Initial Load of Data to DDF Using DRFOUT
● 173241
● Customizing activity Maintain permitted extra characters under SAP NetWeaver Business Warehouse
General Settings .

Procedure

1. On your back-end SAP Assortment Planning system, open the Data Warehousing Workbench (transaction
RSA1).
2. Verify transport connections.
1. Select Transport Connection in the left-hand frame.
2. Select Object Types.
3. Expand Source System.

Selecting Source Systems

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 221
 4. Use Select Objects to ensure that the back-end system is selected as the source system.
5. Choose Transfer Selections.
6. At the top of the right-hand frame, above the list of Collected objects, choose Grouping and select Only
Necessary Objects.
7. At the top of the right-hand frame, choose Collection Mode and select Collect Automatically.

Grouping and Collection Settings

3. Determine if you need to enable to Match (X) or copy option for the BI Content, which you will activate in
the subsequent steps.

Match(X) or copy Selection

Installation Type Selection

New Installation Do not enable the Match (X) or copy option for any of the BI Content objects.

Upgrade Standard /RAP/* BI Content ob­ Standard /RAP/* BI Content objects have been
jects have not been modified in modified in your local environment1
(Previously installed/
your local environment1
activated any of
the /RAP/* BI Content) Do not enable the Match (X) or copy Enable the Match (X) or copy option.
option for any of the BI Content ob­
During the activation of each BI Content object type,
jects.
you will be asked to carry out an additional Transfer
selections step. In this step, select to install the
Active Version (that is, your modified version) or the
Content Version (that is, the SAP delivered, and pos­
sibly updated version of the object). The project im­
plementation team should advise you on which op­
tion is required for each object.

 Caution
When you choose to install the Content Version,
the SAP delivered objects included in the current
release will be installed regardless of any modifi-
cations made to the currently existing BI Con­
tent objects.

1 As a system administrator, you may need to contact the SAP Assortment Planning project implementation team to
learn if standard, SAP-delivered, BI Content objects have been modified in your local environment.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
222 PUBLIC Set Up the Applications
 4. Activate InfoObject catalogs.

If at any point during the installation of BI Content objects you are presented with a dialog asking you to
add objects to a personal list, we recommend that you select No.

 Remember

You can ignore activation warnings listed under Result [page 228].

1. Select BI Content in the left-hand frame.

2. Select Object Types and expand InfoObject Catalog.

3. Use Select Objects to select the /RAP/CHAR_CAT and the /RAP/KYF_CAT catalogs.
4. Choose Transfer Selections.
5. In the right-hand frame, in the list of Collected objects, verify that both InfoObject catalogs are listed.
6. Right-click on each of the InfoObject catalogs, and choose Install all Bellow.
7. Choose Install.
If an information dialog box appears, choose Continue. Choose Local Object or enter a package if you
need to transport the objects.
5. Activate Variables.

 Remember

You can ignore activation warnings listed under Result [page 228].

1. Select BI Content in the left-hand frame.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 223
 2. Select Object Types and expand Query Elements followed by Variable.
3. Use Select Objects to select the following variables:
○ /RAP/PLCND_ESM_02
○ /RAP/PLCSET_ESM_02
○ /RAP/PCYCLE_EMM_01
○ /RAP/PLNHR_MSO_01
○ /RAP/PLNHN1_MSO_01 to /RAP/PLNHN9_MSO_01 (inclusive)
○ /RAP/PRDHN1_MMO_01 to /RAP/PRDHN9_MMO_01 (inclusive)

4. Choose Transfer Selections.

5. In the right-hand frame, in the list of Collected objects, verify that all of the selected variables are listed
and that the option in the Install column is enabled .
6. Choose Install.
If an information dialog box appears, choose Continue. Choose Local Object or enter a package if you
need to transport the objects.
6. Maintain version master data.

1. In the left-hand frame, select Modeling InfoObjects .

2. In the right-hand frame under Assortment Planning for Retail RAP Character InfoObject Catalog ,
search in the object list for the InfoObject /RAP/VERSN.
3. Right-click the InfoObject /RAP/VERSN, choose Maintain Master Data from the context menu, and
maintain the following entries on the Time Independent tab:

Version Short description

# An empty version value that you must maintain

ALV Assortment List Vsn

APF Vsn of final plan

 Note

Save your changes and activate them.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
224 PUBLIC Set Up the Applications
 7. Activate Advanced DataStore Objects.

If during the installation, you are presented with a message stating that your source system is not active,
navigate to the Modeling tab, locate your source system under Source Systems, and activate it by right-
clicking and selecting Activate. If prompted, choose Only Activate .

 Remember

You can ignore activation warnings listed under Result [page 228].

1. Select BI Content in the left-hand frame.

2. Select Object Types and expand DataStore Object (advanced).
3. Use Select Objects to select all DataStore Objects starting with /RAP/DS*.
4. Choose Transfer Selections.
5. In the list of Collected objects, verify that the option in the Install column is enabled for each of the
objects.
6. Choose Display List .
7. Right-click the tree node DataStore Object (advanced) and choose Install all Below.
8. Choose Install. If an information dialog box appears, choose Continue. Choose Local Object or enter a
package if you need to transport the objects.
9. Remodel the following Advanced DataStore Objects if a corresponding message appears: /RAP/
DS40, /RAP/DS42, /RAP/DS54, and /RAP/DS55.

 Note

Set all affected Advanced DataStore Objects to Load Mode before starting the remodeling process.
After the remodeling process, make sure that all new Advanced DataStore Objects are set to
Planning Mode.

 Tip

To set an Advanced DataStore Object to Load Mode:

1. Select Modeling in the left-hand frame.

2. Select InfoProvider in the left-hand frame.
3. Right-click the Advanced DataStore Object that you want to set to Load Mode.

4. Choose Planning-Specific Properties Change Real-Time Load Behavior .

5. Choose Real-Time Data Target Can Be Loaded With Data; Planning Not Allowed and confirm.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 225
  Tip

To remodel an Advanced DataStore Object:

1. Select Modeling in the left-hand frame.

2. Select InfoProvider in the left-hand frame.
3. Right-click the Advanced DataStore Object that you want to remodel.

4. Choose Additional Functions Remodeling Monitor .

5. Select a remodeling rule.
6. Choose Start Request. The Start Time window opens.
7. In the Start Time window, select a start time for the remodeling request and confirm.

8. Activate CompositeProviders.

 Remember

You can ignore activation warnings listed under Result [page 228].

1. Select BI Content in the left-hand frame.

2. Select Object Types and expand CompositeProvider.
3. Use Select Objects to select all CompositeProviders from /RAP/CP40 to /RAP/CP46 (inclusive).
4. Choose Transfer Selections.
5. In the list of Collected objects, verify that the option in the Install column is enabled for each of the
objects.
6. Choose Display List .
7. Right-click the tree node DataStore Object (advanced) and choose Install all Below.
8. Choose Install. If an information dialog box appears, choose Continue. Choose Local Object or enter a
package if you need to transport the objects.
9. Activate Aggregation Levels.

 Remember

You can ignore activation warnings listed under Result [page 228].

1. Select BI Content in the left-hand frame.

2. Select Object Types and expand Planning Aggregation Level .
3. Use Select Objects to select the following Aggregation Level:

Aggregation Levels

Aggregation Levels

/RAP/C44A01

/RAP/C44A02

/RAP/C44A03

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
226 PUBLIC Set Up the Applications
 Aggregation Levels

/RAP/C44A04

/RAP/C46A02

4. Choose Transfer Selections.

5. In the list of Collected objects, verify that the option in the Install column is enabled for each of the
objects.
6. Choose Install. If an information dialog box appears, choose Continue. Choose Local Object or enter a
package if you need to transport the objects.

10. Activate Planning Sequence Objects.

 Remember

You can ignore activation warnings listed under Result [page 228].

1. Select BI Content in the left-hand frame.

2. Select Object Types and expand Planning Planning Sequence .
3. Use Select Objects to select the following Planning Sequences:

Planning Sequences

Planning Sequences

/RAP/D50A01_PS01

/RAP/D57A01_PS01

/RAP/C40A01_PS01

/RAP/C40A05_PS01

/RAP/C46A01_PS01

/RAP/C46A03_PS01

/RAP/C46A04_PS01

/RAP/C46A04_PS02

4. Choose Transfer Selections.

5. In the list of Collected objects, verify that the option in the Install column is enabled for each of the
objects.
6. Choose Install. If an information dialog box appears, choose Continue. Choose Local Object or enter a
package if you need to transport the objects.

11. Activate Planning Function Type Objects.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 227
  Remember

You can ignore activation warnings listed under Result [page 228].

1. Select BI Content in the left-hand frame.

2. Select Object Types and expand Planning Function Type for Planning .
3. Use Select Objects to select the following Planning Function:

Planning Functions

Planning Functions

/RAP/OP_BUFFER_DATA

4. Choose Transfer Selections.

5. In the list of Collected objects, verify that the option in the Install column is enabled for each of the
objects.
6. Choose Install. If an information dialog box appears, choose Continue. Choose Local Object or enter a
package if you need to transport the objects.

12. Choose Exit to leave the transaction.

Results

If activation warnings similar to the ones displayed below appear, you can ignore them.

● CMP problem occurred in characteristic <CHAR> for InfoProvider <INFO_PROV>

● Rounding inaccuracies occur with data type FLOAT for AMOUNT and QUANTITY
● Characteristic <CHAR>: Lower case makes selection of char. values difficult
● Data type of char. <CHAR> (<TYPE1>) is not equal to data type of attribute <ATTR> (<TYPE2>)
● Length of characteristic <TEXT CHAR> (<LENGTH1>) and assigned attribute <ATTR> (<LENGTH2>) not
same
● The short text of DataSource <SOURCE> is not maintained in language <LANG>
● Skip key figure <KYF>: aggregation type NO2 not supported
● Attribute <ATTR>: Conversion routine <CONV> ignored
● Attribute <ATTR>: Compounding ignored
● Datatype FLTP for datafield <FIELD> of the DSO is not allowed
● Conversion problems possible for source field <FIELD1> / target field <FIELD2>

6.3.1.6 Upgrade from Retail SAP BW Structure

If you were using the previously existing Retail SAP BW structure, activate the local BI Content objects and
ensure that the previously generated time data (Gregorian calendar) is sufficient.

For detailed information, see the subsections Activate Application BI Content (Retail SAP BW Structure) and
Verify Gregorian Calendar.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
228 PUBLIC Set Up the Applications
6.3.1.6.1 Activate Application BI Content (Retail SAP BW
Structure)

Context

In this procedure, you perform a sequential, step-by-step activation of the local BI Content objects delivered in
the Retail SAP BW structure of the SAP Assortment Planning application. SAP Assortment Planning uses this
application BI Content to consume data stored in the back-end system.

 Caution

As of SAP Assortment Planning 2.0 FP2, a new (Omnichannel) SAP BW Structure has been introduced.
Please contact SAP for assistance with your upgrade project.

 Note

To ensure correct activation of the local BI Content objects, carry out the activation sequentially, as
specified in the following procedures. Resolve any activation warnings, except for the ones listed under
Activation Warnings [page 236], which can be ignored.

Also, the default BI setting to collect and activate all dependencies must not be disabled by the user. The
instructions below activate a minimum subset of objects, and it assumed that all their dependencies will be
collected and activated.

The consumed data from the back-end system can be created by the SAP Assortment Planning application, or
be replicated from a source master data system. In both cases, beware of limitations with regard to the
characters allowed by SAP BW. For more information, see 173241 and Customizing activity Maintain
permitted extra characters under SAP NetWeaver Business Warehouse General Settings .

Procedure

1. On your back-end SAP Assortment Planning system, open the Data Warehousing Workbench (transaction
RSA1).
2. Verify transport connections.
1. Select Transport Connection in the left-hand frame.
2. Select Object Types.
3. Expand Source System.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 229
 Selecting Source Systems
4. Use Select Objects to ensure that the back-end system is selected as the source system.
5. Choose Transfer Selections.
6. At the top of the right-hand frame, above the list of Collected objects, choose Grouping and select Only
Necessary Objects.
7. At the top of the right-hand frame, choose Collection Mode and select Collect Automatically.

Grouping and Collection Settings

3. Determine if you need to enable to Match (X) or copy option for the BI Content which you will activate in the
subsequent steps.

Match(X) or copy Selection

Installation Type Selection

New Installation Do not enable the Match (X) or copy option for any of the BI Content objects.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
230 PUBLIC Set Up the Applications
 Installation Type Selection

Upgrade Standard /RAP/* BI Content ob­ Standard /RAP/* BI Content objects have been
jects have not been modified in modified in your local environment1
(Previously installed/
your local environment1
activated any of
the /RAP/* BI Content) Do not enable the Match (X) or copy Enable the Match (X) or copy option.
option for any of the BI Content ob­
During the activation of each BI Content object type,
jects.
you will be asked to carry out an additional Transfer
selections step. In this step, select to install the
Active Version (that is, your modified version) or the
Content Version (that is, the SAP delivered, and pos­
sibly updated version of the object). The project im­
plementation team should advise you on which op­
tion is required for each object.

 Caution
When you choose to install the Content Version,
the SAP delivered objects included in the current
release will be installed regardless of any modifi-
cations made to the currently existing BI Con­
tent objects.

1 As a system administrator, you may need to contact the SAP Assortment Planning project implementation team to
learn if standard, SAP-delivered, BI Content objects have been modified in your local environment.

4. Activate InfoObject catalogs.

If at any point during the installation of BI Content objects you are presented with a dialog asking you to
add objects to a personal list, we recommend that you select No.

 Remember

You can ignore activation warnings listed under Activation Warnings [page 236].

1. Select BI Content in the left-hand frame.

2. Select Object Types and expand InfoObject Catalog.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 231
 3. Use Select Objects to select the /RAP/CHAR_CAT and the /RAP/KYF_CAT catalogs.
4. Choose Transfer Selections.
5. In the right-hand frame, in the list of Collected objects, verify that both InfoObject catalogs are listed.
6. Right-click on each of the InfoObject catalogs, and choose Install all Below.
7. Choose Install.
If an information dialog box appears, choose Continue. Choose Local Object or enter a package if you
need to transport the objects.
5. Activate Variable /RAP/DISTM_MSM_01.

 Remember

You can ignore activation warnings listed under Activation Warnings [page 236].

1. Select BI Content in the left-hand frame.

2. Select Object Types and expand Query Elements.
3. Use Select Objects to select the /RAP/DISTM_MSM_01 Variable.

4. Choose Transfer Selections.

5. In the right-hand frame, in the list of Collected objects, verify that the /RAP/DISTM_MSM_01 Variable is
listed and that the option in the Install column is enabled.
6. Choose Install.
If an information dialog box appears, choose Continue. Choose Local Object or enter a package if you
need to transport the objects.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
232 PUBLIC Set Up the Applications
 6. Maintain version master data.
1. Select Modeling in the left-hand frame.
2. Expand InfoObjects.
3. Search for InfoObject /RAP/VERSN, located under Assortment Planning RAP Character InfoObject
Catalog .
4. Right-click the InfoObject /RAP/VERSN, choose Maintain Master Data from the context menu, and
maintain the following entries on the Time Independent tab:

Version

# - An empty version value that you must maintain

000

AP1

AP2

APF

AW1

AW2

OP1

OP2

PRJ

REF

The supported planning versions are described in detail in the Maintain Customizing Table /RAP/
RS_VARCUST section of the Common Installation Guide.

 Note

Save your changes and activate them.

7. Activate DataStore Objects.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 233
  Remember

You can ignore activation warnings listed under Activation Warnings [page 236].

1. Select BI Content in the left-hand frame.

2. Select Object Types and expand DataStore Object (Classic).
3. Use Select Objects to select all DataStore Objects starting with /RAP/*.
4. Choose Transfer Selections.
5. In the list of Collected objects, verify that the option in the Install column is enabled for each of the
objects.
6. Choose Install. If an information dialog box appears, choose Continue. Choose Local Object or enter a
package if you need to transport the objects.
If during the installation, you are presented with a dialog asking you to add objects to a personal list,
select No.
8. Activate InfoCubes.

 Remember

You can ignore activation warnings listed under Activation Warnings [page 236].

1. Select BI Content in the left-hand frame.

2. Select Object Types and expand InfoCube.
3. Use Select Objects to select all InfoCubes starting with /RAP/RC*.
4. Similarly, select InfoCubes /RAP/VC20 and /RAP/VC21.
5. Choose Transfer Selections.
6. In the list of Collected objects, verify that the option in the Install column is enabled for each of the
objects.
7. Choose Install. If an information dialog box appears, choose Continue. Choose Local Object or enter a
package if you need to transport the objects.
9. Activate CompositeProviders.

 Remember

You can ignore activation warnings listed under Activation Warnings [page 236].

1. Select BI Content in the left-hand frame.

2. Select Object Types and expand CompositeProvider.
3. Use Select Objects to select all CompositeProviders from /RAP/CP20 to /RAP/CP37 (inclusive).
4. Choose Transfer Selections.
5. In the list of Collected objects, verify that the option in the Install column is enabled for each of the
objects.
6. Choose Install. If an information dialog box appears, choose Continue. Choose Local Object or enter a
package if you need to transport the objects.
10. Activate Aggregation Levels.

 Remember

You can ignore activation warnings listed under Activation Warnings [page 236].

1. Select BI Content in the left-hand frame.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
234 PUBLIC Set Up the Applications
 2. Select Object Types and expand Planning Aggregation Level .
3. Use Select Objects to select the following Aggregation Levels:
These should be active from the previous installation, if not, select them to be installed again:

Aggregation Levels

Aggregation Level

/RAP/D20A01

/RAP/R20A02

/RAP/R20A06

/RAP/R20A08

/RAP/R20A11

/RAP/R20A12

/RAP/R20A15

/RAP/R20A17

/RAP/R23A01

4. Choose Transfer Selections.

5. In the list of Collected objects, verify that the option in the Install column is enabled for each of the
objects.
6. Choose Install. If an information dialog box appears, choose Continue. Choose Local Object or enter a
package if you need to transport the objects.

11. Reactivate Planning Sequence Objects.

 Remember

You can ignore activation warnings listed under Activation Warnings [page 236].

1. Select BI Content in the left-hand frame.

2. Select Object Types and expand Planning Planning Sequence .
3. Use Select Objects to select the following Planning Sequences:
These should be active from the previous installation, if not, select them to be installed again:

Planning Sequences

Planning Sequence

/RAP/C21A01_PS01

/RAP/C25A03_PS01

/RAP/D23A01_PS01

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 235
 Planning Sequence

/RAP/D24A01_PS01

/RAP/R20A08_PS01

4. Choose Transfer Selections.

5. In the list of Collected objects, verify that the option in the Install column is enabled for each of the
objects.
6. Choose Install. If an information dialog box appears, choose Continue. Choose Local Object or enter a
package if you need to transport the objects.

12. Reactivate Workbooks.

 Remember

You can ignore activation warnings listed under Activation Warnings [page 236].

1. Select BI Content in the left-hand frame.

2. Select Object Types and expand More Types Analysis Office Excel Workbook .
3. Use Select Objects to select the following workbooks:
These should be active from the previous installation, if not, select them to be installed again:

Workbooks

Workbook

/RAP/PLANASSORTMENT

/RAP/PLANOPTIONS

4. Choose Transfer Selections.

5. In the list of Collected objects, verify that the option in the Install column is enabled for each of the
objects.
6. Choose Install. If an information dialog box appears, choose Continue. Choose Local Object or enter a
package if you need to transport the objects.

13. Choose Exit to leave the transaction.

Activation Warnings

If activation warnings similar to the ones displayed below appear, you can ignore them.

● CMP problem occurred in characteristic <CHAR> for InfoProvider <INFO_PROV>

● Rounding inaccuracies occur with data type FLOAT for AMOUNT and QUANTITY
● Characteristic <CHAR>: Lower case makes selection of char. values difficult
● Data type of char. <CHAR> (<TYPE1>) is not equal to data type of attribute <ATTR> (<TYPE2>)
● Length of characteristic <TEXT CHAR> (<LENGTH1>) and assigned attribute <ATTR> (<LENGTH2>) not
same

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
236 PUBLIC Set Up the Applications
 ● The short text of DataSource <SOURCE> is not maintained in language <LANG>
● Skip key figure <KYF>: aggregation type NO2 not supported
● Attribute <ATTR>: Conversion routine <CONV> ignored
● Attribute <ATTR>: Compounding ignored
● Datatype FLTP for datafield <FIELD> of the DSO is not allowed
● Conversion problems possible for source field <FIELD1> / target field <FIELD2>

6.3.1.6.2 Verify Gregorian Calendar

Ensure that the previously generated time data (Gregorian calendar) is sufficient for the current release of SAP
Assortment Planning.

Context

Execute this procedure to generate time data (Gregorian calendar).

Procedure

1. Log on to SAP HANA studio.

2. In the SAP HANA Modeler perspective, on the Quick Launch tab, select your ABAP back-end system and
choose Generate Time Data.
3. Select Gregorian as the Calendar Type.

For example, SAP HANA views included in the SAP HANA content for SAP Customer Activity Repository
require the presence of time data in _SYS_BI.TIME_DIMENSION* SAP HANA database tables.
4. Enter a range of years that includes all the years of data that you plan to store in SAP Customer Activity
Repository.

Example: If you plan to start using SAP Assortment Planning on January 1, 2014, enter 2014 as your
starting year. But if you plan to access sales documents created in SAP ERP that date from January 2013,
specify 2013 as your starting year.
5. Define the granularity as Day, which is the minimum granularity required by SAP Customer Activity
Repository. You can choose a finer level of granularity, for example Hour, if necessary.
6. Choose the day that is the first day of the week in your company.
7. Choose Finish.

For more information, see:

○ https://help.sap.com/viewer/p/SAP_HANA_LIVE Installation and Upgrade Administrator's Guide

Configuration Steps Generate Time Data

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 237
 ○ https://help.sap.com/viewer/p/SAP_HANA_PLATFORM <Version> Development SAP HANA
Modeling Guide (for SAP HANA studio) Creating Information Views and Previewing its Output
Generate Time Data

6.3.1.7 Verify that Data Replication Is Running Following

the Upgrade

Following the upgrade, ensure that all of the data replication described in the Configure Data Replication section
of the Common Installation Guide is still running.

 Caution

The data you replicate in this step is consumed by the SAP Assortment Planning application through local
BI Content. Only a subset of ASCII characters is considered valid by SAP BW. As a result, object identifiers,
which are mapped to external IDs in DDF (for example, EXT_LOC_ID or EXT_PROD_ID), should only consist
of valid characters.

We recommend that you avoid the usage of invalid characters in the source master data system. This is
controlled by the system administrator or the implementation team who define the value ranges and
formatting for object identifiers (for example, product or location IDs).

If the recommended approach is not possible, then in your SAP Assortment Planning back-end system, you
need to allow for additional special characters in Customizing activity Maintain permitted extra characters
under SAP NetWeaver Business Warehouse General Settings . For more information, see 173241 .

In particular, following the upgrade, you need to pay attention to the following:

● SAP Assortment Planning supports the use of time-dependent article hierarchies. This is enabled by
implementing SAP Note 2196323 in the connected SAP Retail or SAP S/4HANA system.
Following the implementation of these notes in SAP Retail or SAP S/4HANA, if your hierarchy is already a
time-dependent hierarchy, you need to re-import the product hierarchies into SAP Assortment Planning
using the DRFOUT framework.
○ SAP Retail Description: Article Hierarchy
○ DRFOUT Outbound Implementation: PAHY
○ DDF Inbound Interface: /DMF/MDIF_PROD_HIER_INBOUND
● All the tables listed in the spreadsheet of the CARAB 5.0 - SLT Tables archive for your version of SAP
Customer Activity Repository applications bundle (SAP Assortment Planning) are being replicated. For
more information, see the Create/Replicate Source Master Data System Tables section in the Common
Installation Guide.
● Ensure that season classification data is being loaded from the appropriate source. For more information,
see the Load Season Classification Data section in the SAP Assortment Planning Administration Guide.
● Ensure that wholesale data is being loaded. Set up the Mapping report to convert sales orders into /DMF/
TS_WS table report (/DMF/WHOLESALE_SO_SHP_TO_TS_WS in transaction SE38) to run as a background
job to regularly import replicated sales order and shipment data into DDF. For more information, see the
Load Wholesale Data section in the SAP Assortment Planning Administration Guide.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
238 PUBLIC Set Up the Applications
6.3.1.8 Run the Validation Report

1. Run transaction /DMF/VAL_CAR_INSTALL.

Alternatively, run transaction SE38 and execute the /DMF/VALIDATE_CAR_INSTALLATION report.
2. Select the Assortment Planning scenario and select Execute.
In the dialog that appears, select whether to validate the Retail SAP BW structure, the Omnichannel SAP
BW structure, or both. The SAP BW structure to validate depends on the structure that you have selected
to reactivate during the upgrade in a previous step, see section Reactivate SAP Assortment Planning
Planning Framework Content.
Running this report allows you to verify the success of the installation, providing a log of potential issues.
For example, you may be presented with the following results:

Validation Report Results

View the long text associated with each message to see the link to the documentation describing the
procedure you have to troubleshoot.

6.3.1.9 Activate SAP Assortment Planning ICF Services

Use

Following an upgrade, you must ensure that all ICF services required for the SAP Assortment Planning SAP
Fiori apps are activated.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 239
Procedure

1. Log on to your front-end server.

2. Open service maintenance (transaction SICF).
3. In the Define Services screen, select the Location Clustering service by specifying the following:
○ Hierarchy Type: SERVICE
○ Virtual Host: DEFAULT_HOST
○ Service Path: /sap/bc/ui5_ui5/sap/locclsts_v2/
4. Choose Execute.
5. To activate the service, choose Service/host Activate.
6. Repeat steps 3 to 5 to ensure that all of the following services are activated:
○ /sap/bc/ui5_ui5/sap/attribmgmt_v2/
○ /sap/bc/ui5_ui5/sap/assortlist/
○ /sap/bc/ui5_ui5/sap/ddfreuse_v2/
○ /sap/bc/ui5_ui5/sap/locclsts_v2/
○ /sap/bc/ui5_ui5/sap/modulemgmt_v2/
○ /sap/bc/ui5_ui5/sap/optionplan_v2/
○ /sap/bc/ui5_ui5/sap/phpmatch_v2/
○ /sap/bc/ui5_ui5/sap/plnconfig/
○ /sap/bc/ui5_ui5/sap/optionplanning
○ /sap/bc/ui5_ui5/sap/styleplan
○ /sap/bc/ui5_ui5/sap/rankingkey
○ /sap/bc/ui5_ui5/sap/businessrule

6.3.1.10 Define System Alias for Back-End Transactions

Use

A number of SAP Fiori apps, installed on your front-end system, launch transactions directly on the back-end
system. For example, the Manage Products tile actually launches the Demand Data Foundation (DDF)
POWL_EASY WebDynpro application.

Following an upgrade, you must ensure that all required RFC connections and system alias definitions remain
set.

Procedure

1. Log on to your front-end system, that is, the system where you have installed the user interface (UI)
components of your application.
2. Launch Configuration of RFC Connections (transaction SM59).

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
240 PUBLIC Set Up the Applications
 3. Create an RFC connection with the following settings:
○ RFC Destination: SAP_ISR_CARAB
Connection Type: H (HTTP connection)
Ensure to maintain all of the settings required to connect to your back-end system, in particular, the Target
Host entry on the Technical Settings tab.
4. Save your changes.
5. Create another RFC connection with the following settings:
○ RFC Destination: SAP_ERP_ISR_CARAB
Connection Type: H (HTTP connection)
Ensure to maintain all of the settings required to connect your front-end system to the source master data
system, in particular, the Target Host entry on the Technical Settings tab.
6. Save your changes.
7. Open Launchpad Customizing (transaction LPD_CUST).
8. Select the SAP Assortment Planning role ( UIRAP001), and choose Display.
The two catalogs, Assortment Planner and Planning Administrator, are displayed.
9. In each of the catalogs, selecting one app at a time, make the following settings:

Catalog App System Alias Description

Assortment View Log SAP_ISR_CARAB This setting allows the My Assortment Lists app to
Planner launch transaction SLG1 on the back-end system.

 Note
This application is only used to configure a link to
the back-end system, you do not need to add this
app to your SAP Fiori launchpad.

View ExtAssort SAP_ERP_ISR_CAR This setting allows the My Assortment Lists app to
Listing Conditions AB launch transaction WSL10 on the connected SAP Retail
or SAP S/4HANA system.

 Note
This application is only used to configure a link to
the SAP Retail or SAP S/4HANA system, you do not
need to add this app to your SAP Fiori launchpad.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 241
 Catalog App System Alias Description

View External SAP_ERP_ISR_CAR This setting allows the My Assortment Lists app to
Assortments AB launch:

Transaction WRF_WS0A3 on the connected SAP Retail

system

Transaction WS0A3 on the connected SAP S4HANA sys­

tem.

 Note
This application is only used to configure a link to
the SAP Retail or SAP S/4HANA system, you do not
need to add this app to your SAP Fiori launchpad.

Planning Manage Category SAP_ISR_CARAB This setting allows the Manage Category Responsibilities
Administrator responsibilities app to launch the corresponding DDF WebDynpro appli­
cation.

Manage Market SAP_ISR_CARAB This setting allows the Manage Market Responsibilities
responsibilities app to launch the corresponding DDF WebDynpro appli­
cation.

Manage Products SAP_ISR_CARAB This setting allows the Manage Products app to launch
the corresponding DDF WebDynpro application.

Manage Locations SAP_ISR_CARAB This setting allows the Manage Locations app to launch
the corresponding DDF WebDynpro application.

6.3.1.11 Troubleshoot Front-End Server Upgrade

Use

Following the upgrade of the product version on the front-end server, you may not be able to see some of the
SAP Assortment Planning SAP Fiori tiles in your launchpad. This section outlines how to troubleshoot these
issues, should you experience them.

These steps are also listed in the Troubleshooting section of the SAP Assortment Planning Administrator's
Guide available on the SAP Help Portal at http://help.sap.com/viewer/p/CARAB <Your Version>
Administration SAP Assortment Planning Administration Guide .

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
242 PUBLIC Set Up the Applications
Process

Do the following:

1. Check that all of the required BSP applications are listed in the UIRAP001 package.
1. Log on to your front-end system (your SAP Gateway system).
2. Launch the Object Navigator (transaction SE80).
3. In the Repository Browser, open package UIRAP001.
4. Expand all of the embedded packages of embedded package CONTENT_RAP_TRANS.
5. Verify that the following BSP Applications are listed:

BSP Applications
6. If you do not see one or more of the BSP applications listed above, right-click on each of the
RETAIL_DDF and RETAIL_RAP_AP packages, and select Other Functions Rebuild Object List .

 Caution

Do not rebuild objects on a higher package level.

2. Clean the cache.

1. Log on to your front-end system (your SAP Gateway system).
2. In Customizing (transaction SPRO), navigate to SAP NetWeaver UI Technologies SAP Fiori
Data Administration Invalidate Caches .

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 243
 This activity launches the /UI2/INVALIDATE_GLOBAL_CACHES report. This report invalidates all
server-side caches in SAP NetWeaver user interface services, which can become out-of-date following
an upgrade.
3. If necessary, implement instructions listed in SAP Note 2147669 .
3. Remove any previously customized versions of the UIRAP001 launchpad.
1. Log on to your front-end system (your SAP Gateway system).
2. Launch the Overview for Launchpads (transaction LPD_CUST).
3. Search for Role UIRAP001, and see whether any instances exist where the User Name is not SAP. If so,
this means that customized versions of the UIRAP001 launchpad exist, and these take precedence
over the standard launchpad instance delivered by SAP.
4. Delete all but the launchpad instance delivered by SAP.
4. Recalculate SAPUI5 application index, following any changes to the content of the SAPUI5 ABAP repository
(for example, installation of a new version of the SAPUI5 distribution layer or implementation of an SAP
Note containing changes to an SAPUI5 app).
For more information, see the Configure Index Calculation section in the Common Installation Guide and
SAP Note 2227577 .

6.3.2 2.0 SP6/SP7/SP8 to 5.0

This section is intended for existing SAP Assortment Planning customers who have installed and configured
SAP Assortment Planning 2.0 SP6, 2.0 SP7, or 2.0 SP8 and would like to upgrade to SAP Assortment Planning
5.0.

6.3.2.1 Quick Guide

Upgrade to SAP Assortment Planning 5.0.

Checklist

Prerequisites

Ensure that you have carried out all the steps listed in the previous sections of this guide.

Follow-Up Activities

Mandatory Steps

☐ Perform mandatory core steps for SAP Customer Activity Repository. See Core (Mandatory for All
Applications) [page 81].
☐ Verify SAP HANA and back-end system roles. See Verify Users, Privileges, and Roles.
☐ Adjust Customizing settings.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
244 PUBLIC Set Up the Applications
 ☐ Reactivate SAP Assortment Planning planning framework content.
☐ Verify that data replication is running following the upgrade.
☐ Run the validation report.
☐ Run the SAP Assortment Planning 4.0 update report.
☐ If you want to purge assortment lists using the /DMF/PURGE_AGENT report, you must execute the /DMF/
WUF_MIGRATE_ASRTLIST report once using transaction SE38.
For detailed information, read the system documentation associated with the report.
☐ Verify that all SAP Assortment Planning OData services are active following the upgrade. For detailed
information, see Verify that OData Services are Active [page 101].
☐ Verify that all the ICF services relevant to SAP Assortment Planning are active following the upgrade.
☐ Verify the definition of system aliases for back-end transactions.
☐ Troubleshoot front-end server upgrade.

6.3.2.2 Perform Core Steps for SAP Customer Activity

Repository

To set up this application, you must first perform the Core (Mandatory) steps for SAP Customer Activity
Repository. The core steps are mandatory for all the consuming applications.

Procedure

Perform all steps listed under Core (Mandatory for All Applications) [page 81].

6.3.2.3 Adjust Customizing Settings

Customizing to maintain following an upgrade to SAP Assortment Planning 5.0.

Context

Following the upgrade, you need to make settings in Customizing to be able to use SAP Assortment Planning
5.0.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 245
Procedure

1. Log on to your back-end system.

2. If you use the Retail SAP BW Structure and you don't want to use planning configuration, do the following:
a. Disable Use Planning Configuration and Prompt in Manage Location Clusters (using transaction SPRO)
under Cross-Application Components Assortment Planning Imported Demand Data Foundation
Settings Basic Settings Define Default Values .

You must disable this Customizing setting to continue using the Retail SAP BW Structure. For more
information, see section Reactivate Planning Framework Content (SAP Assortment Planning).
b. Disable the implementation of BAdI: Read Merchandise Planning KPI Data under Cross-Application
Components Demand Data Foundation Data Maintenance Planning Configuration
Enhancements Using Business Add-Ins .

You must disable the implementation of this BAdI to continue using the Retail SAP BW Structure. For
more information, see section Reactivate Planning Framework Content (SAP Assortment Planning).

If you use the Omnichannel SAP BW structure, make sure that Use Planning Configuration is enabled.

3. Maintain the monthly fiscal year variant (using transaction SPRO) under Cross-Application Components
Assortment Planning Imported Demand Data Foundation Settings Basic Settings Define Default
Values Monthly FY Variant . This is necessary to use the view Sales & Inventory Analysis in the My
Assortment Lists app.

For more information, see Fiscal Year Variant.

4. Define the business week (using transaction SPRO) under Cross-Application Components Demand
Data Foundation Basic Settings Define Business Week .

5. Maintain number ranges for planning configurations under Cross-Application Components Assortment
Planning Number Ranges Maintain Number Range for Planning Configuration .

6. Maintain number ranges for parameter configurations under Cross-Application Components

Assortment Planning Number Ranges Maintain Number Range for Parameter Configuration .
7. Make sure that the settings in Customizing activity Assortment List Settings fit to your planning process.

The Assortment List Settings activity is available in Customizing under Cross-Application Components
Assortment Planning Assortment Lists .
8. If you want to allow users access to the Analyze Forecast app via links from the My Assortment Lists app,
enable the Create option to generate a location hierarchy out of every location cluster set activated in SAP
Assortment Planning. This option is available in the Location Clustering Settings Customizing activity under
Cross-Application Components Assortment Planning for Retail Imported Demand Data Foundation
Settings Data Maintenance Location Clustering Location Clustering Settings .

If the Create option is not visible, choose New Entries.

9. To use forecasted values in the Sales & Inventory Analysis view within the My Assortment Lists app,
configure Unified Demand Forecast (UDF). For more information, see the SAP Customer Activity Repository
Administration Guide, section Configure Unified Demand Forecast (UDF).
10. Verify default implementation of BAdI: Determine Product Season Classification and, if necessary, provide a
custom implementation.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
246 PUBLIC Set Up the Applications
 The BAdI, BAdI: Determine Product Season Classification is available under Cross-Application
Components Assortment Planning Enhancements Using Business Add-Ins .

6.3.2.4 Verify Fiscal Calendar

Verify that the previously generated calendar time data is still running following an upgrade to SAP Assortment
Planning 5.0.

Context

The generation of time data (Fiscal calendar) is required for using the Sales & Inventory Analysis view in the My
Assortment Lists app. The fiscal calendar is also required to initialize the SAP Assortment Planning BW
structure, as it allows for planning on fiscal periods.

Procedure

If required and not already done, ensure that the time data has been generated far enough into the past and
future for SAP Assortment Planning 5.0.

For more information, see the following:

○ Generate Time Data - Fiscal Calendar section of the Common Installation Guide
○ Management section of the SAP Assortment Planning Administration Guide

6.3.2.5 Reactivate Planning Framework Content (SAP

Assortment Planning)

There are two distinct BW structures supported in SAP Assortment Planning:

Omnichannel SAP BW Structure

 Caution

New functionality will be only available for the Omnichannel SAP BW structure. Therefore, we recommend
to use the Omnichannel SAP BW structure which provides an extensive feature set.

● If you already use the Omnichannel SAP BW structure, reactivate it.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 247
 ● If you were using the previously existing Retail SAP BW structure, we recommend that you reactivate it
during the upgrade. If later you would like to switch to the new Omnichannel SAP BW structure, please
contact SAP for assistance with your upgrade project.

Make sure that you have enabled the optimized in-memory planning capabilities of the integrated planning
engine in SAP Business Warehouse. For more information, see the Common Installation Guide, section Enable
Optimized In-Memory Planning Capabilities of SAP BW Integrated Planning.

Prerequisite

To use the Omnichannel SAP BW structure, the following prerequisites must be met:

● Enable the usage of planning configurations under Cross-Application Components Assortment

Planning Imported Demand Data Foundation Settings Basic Settings Define Default Values . The
Omnichannel SAP BW structure only works when planning configurations are used.
● Enable the implementation of BAdI: Read Merchandise Planning KPI Data under Cross-Application
Components Demand Data Foundation Data Maintenance Planning Configuration Enhancements
Using Business Add-Ins .

The Omnichannel SAP BW structure consists of local BI Content only. To create workbooks on top of the
Omnichannel SAP BW structure, contact SAP Digital Business Services for a custom implementation project.

Retail SAP BW Structure

 Caution

If you were using the Retail SAP BW Structure in a previous release, we recommend that you reactivate this
structure during the upgrade. The Retail SAP BW Structure will be supported with maintenance, however
no new functionality will be developed for this structure. If later you would like to switch to the new
Omnichannel SAP BW structure, please contact SAP for assistance with your upgrade project.

Prerequisite

To use the Retail SAP BW structure, the following prerequisites must be met:

● Disable the usage of planning configurations under Cross-Application Components Assortment

Planning Imported Demand Data Foundation Settings Basic Settings Define Default Values . You
cannot use the Retail SAP BW structure with planning configurations.
● Disable the implementation of BAdI: Read Merchandise Planning KPI Data under Cross-Application
Components Demand Data Foundation Data Maintenance Planning Configuration Enhancements
Using Business Add-Ins .

6.3.2.6 Upgrade from Omnichannel SAP BW Structure

If you already use the Omnichannel SAP BW structure, activate the local BI Content objects as described in
subsection Activate Application BI Content (Omnichannel SAP BW Structure).

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
248 PUBLIC Set Up the Applications
6.3.2.6.1 Activate Application BI Content (Omnichannel
SAP BW Structure)

Context

In this procedure, you perform a sequential, step-by-step activation of the local BI Content objects delivered in
the Omnichannel SAP BW structure of the SAP Assortment Planning application. SAP Assortment Planning
uses this application BI Content to consume data stored in the back-end system

 Note

To ensure correct activation of the BI Content objects, carry out the activation sequentially, as specified in
the following procedures. Resolve any activation warnings, except for the ones listed under Result [page
228], which can be ignored.

Also, do not disable the default BI setting to collect and activate all dependencies. The instructions below
activate a minimum subset of objects, and it assumed that all their dependencies are collected and
activated.

The consumed data from the back-end system can be created by the SAP Assortment Planning application, or
be replicated from a source master data system. In both cases, beware of limitations with regard to the
characters allowed by SAP BW. For more information, see:

● SAP Assortment Planning Administration Guide under Initial Load of Data to DDF Using DRFOUT
● 173241
● Customizing activity Maintain permitted extra characters under SAP NetWeaver Business Warehouse
General Settings .

Procedure

1. On your back-end SAP Assortment Planning system, open the Data Warehousing Workbench (transaction
RSA1).
2. Verify transport connections.
1. Select Transport Connection in the left-hand frame.
2. Select Object Types.
3. Expand Source System.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 249
 Selecting Source Systems
4. Use Select Objects to ensure that the back-end system is selected as the source system.
5. Choose Transfer Selections.
6. At the top of the right-hand frame, above the list of Collected objects, choose Grouping and select Only
Necessary Objects.
7. At the top of the right-hand frame, choose Collection Mode and select Collect Automatically.

Grouping and Collection Settings

3. Determine if you need to enable to Match (X) or copy option for the BI Content, which you will activate in
the subsequent steps.

Match(X) or copy Selection

Installation Type Selection

New Installation Do not enable the Match (X) or copy option for any of the BI Content objects.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
250 PUBLIC Set Up the Applications
 Installation Type Selection

Upgrade Standard /RAP/* BI Content ob­ Standard /RAP/* BI Content objects have been
jects have not been modified in modified in your local environment1
(Previously installed/
your local environment1
activated any of
the /RAP/* BI Content) Do not enable the Match (X) or copy Enable the Match (X) or copy option.
option for any of the BI Content ob­
During the activation of each BI Content object type,
jects.
you will be asked to carry out an additional Transfer
selections step. In this step, select to install the
Active Version (that is, your modified version) or the
Content Version (that is, the SAP delivered, and pos­
sibly updated version of the object). The project im­
plementation team should advise you on which op­
tion is required for each object.

 Caution
When you choose to install the Content Version,
the SAP delivered objects included in the current
release will be installed regardless of any modifi-
cations made to the currently existing BI Con­
tent objects.

1 As a system administrator, you may need to contact the SAP Assortment Planning project implementation team to
learn if standard, SAP-delivered, BI Content objects have been modified in your local environment.

4. Activate InfoObject catalogs.

If at any point during the installation of BI Content objects you are presented with a dialog asking you to
add objects to a personal list, we recommend that you select No.

 Remember

You can ignore activation warnings listed under Result [page 228].

1. Select BI Content in the left-hand frame.

2. Select Object Types and expand InfoObject Catalog.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 251
 3. Use Select Objects to select the /RAP/CHAR_CAT and the /RAP/KYF_CAT catalogs.
4. Choose Transfer Selections.
5. In the right-hand frame, in the list of Collected objects, verify that both InfoObject catalogs are listed.
6. Right-click on each of the InfoObject catalogs, and choose Install all Bellow.
7. Choose Install.
If an information dialog box appears, choose Continue. Choose Local Object or enter a package if you
need to transport the objects.
5. Activate Variables.

 Remember

You can ignore activation warnings listed under Result [page 228].

1. Select BI Content in the left-hand frame.

2. Select Object Types and expand Query Elements followed by Variable.
3. Use Select Objects to select the following variables:
○ /RAP/PLCND_ESM_02
○ /RAP/PLCSET_ESM_02
○ /RAP/PCYCLE_EMM_01
○ /RAP/PLNHR_MSO_01
○ /RAP/PLNHN1_MSO_01 to /RAP/PLNHN9_MSO_01 (inclusive)
○ /RAP/PRDHN1_MMO_01 to /RAP/PRDHN9_MMO_01 (inclusive)

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
252 PUBLIC Set Up the Applications
 4. Choose Transfer Selections.
5. In the right-hand frame, in the list of Collected objects, verify that all of the selected variables are listed
and that the option in the Install column is enabled .
6. Choose Install.
If an information dialog box appears, choose Continue. Choose Local Object or enter a package if you
need to transport the objects.
6. Maintain version master data.

1. In the left-hand frame, select Modeling InfoObjects .

2. In the right-hand frame under Assortment Planning for Retail RAP Character InfoObject Catalog ,
search in the object list for the InfoObject /RAP/VERSN.
3. Right-click the InfoObject /RAP/VERSN, choose Maintain Master Data from the context menu, and
maintain the following entries on the Time Independent tab:

Version Short description

# An empty version value that you must maintain

ALV Assortment List Vsn

APF Vsn of final plan

 Note

Save your changes and activate them.

7. Activate Advanced DataStore Objects.

If during the installation, you are presented with a message stating that your source system is not active,
navigate to the Modeling tab, locate your source system under Source Systems, and activate it by right-
clicking and selecting Activate. If prompted, choose Only Activate .

 Remember

You can ignore activation warnings listed under Result [page 228].

1. Select BI Content in the left-hand frame.

2. Select Object Types and expand DataStore Object (advanced).
3. Use Select Objects to select all DataStore Objects starting with /RAP/DS*.
4. Choose Transfer Selections.
5. In the list of Collected objects, verify that the option in the Install column is enabled for each of the
objects.
6. Choose Display List .
7. Right-click the tree node DataStore Object (advanced) and choose Install all Below.
8. Choose Install. If an information dialog box appears, choose Continue. Choose Local Object or enter a
package if you need to transport the objects.
9. Remodel the following Advanced DataStore Objects if a corresponding message appears: /RAP/
DS40, /RAP/DS42, /RAP/DS54, and /RAP/DS55.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 253
  Note

Set all affected Advanced DataStore Objects to Load Mode before starting the remodeling process.
After the remodeling process, make sure that all new Advanced DataStore Objects are set to
Planning Mode.

 Tip

To set an Advanced DataStore Object to Load Mode:

1. Select Modeling in the left-hand frame.

2. Select InfoProvider in the left-hand frame.
3. Right-click the Advanced DataStore Object that you want to set to Load Mode.

4. Choose Planning-Specific Properties Change Real-Time Load Behavior .

5. Choose Real-Time Data Target Can Be Loaded With Data; Planning Not Allowed and confirm.

 Tip

To remodel an Advanced DataStore Object:

1. Select Modeling in the left-hand frame.

2. Select InfoProvider in the left-hand frame.
3. Right-click the Advanced DataStore Object that you want to remodel.

4. Choose Additional Functions Remodeling Monitor .

5. Select a remodeling rule.
6. Choose Start Request. The Start Time window opens.
7. In the Start Time window, select a start time for the remodeling request and confirm.

8. Activate CompositeProviders.

 Remember

You can ignore activation warnings listed under Result [page 228].

1. Select BI Content in the left-hand frame.

2. Select Object Types and expand CompositeProvider.
3. Use Select Objects to select all CompositeProviders from /RAP/CP40 to /RAP/CP46 (inclusive).
4. Choose Transfer Selections.
5. In the list of Collected objects, verify that the option in the Install column is enabled for each of the
objects.
6. Choose Display List .
7. Right-click the tree node DataStore Object (advanced) and choose Install all Below.
8. Choose Install. If an information dialog box appears, choose Continue. Choose Local Object or enter a
package if you need to transport the objects.
9. Activate Aggregation Levels.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
254 PUBLIC Set Up the Applications
  Remember

You can ignore activation warnings listed under Result [page 228].

1. Select BI Content in the left-hand frame.

2. Select Object Types and expand Planning Aggregation Level .
3. Use Select Objects to select the following Aggregation Level:

Aggregation Levels

Aggregation Levels

/RAP/C44A01

/RAP/C44A02

/RAP/C44A03

/RAP/C44A04

/RAP/C46A02

4. Choose Transfer Selections.

5. In the list of Collected objects, verify that the option in the Install column is enabled for each of the
objects.
6. Choose Install. If an information dialog box appears, choose Continue. Choose Local Object or enter a
package if you need to transport the objects.

10. Activate Planning Sequence Objects.

 Remember

You can ignore activation warnings listed under Result [page 228].

1. Select BI Content in the left-hand frame.

2. Select Object Types and expand Planning Planning Sequence .
3. Use Select Objects to select the following Planning Sequences:

Planning Sequences

Planning Sequences

/RAP/D50A01_PS01

/RAP/D57A01_PS01

/RAP/C40A01_PS01

/RAP/C40A05_PS01

/RAP/C46A01_PS01

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 255
 Planning Sequences

/RAP/C46A03_PS01

/RAP/C46A04_PS01

/RAP/C46A04_PS02

4. Choose Transfer Selections.

5. In the list of Collected objects, verify that the option in the Install column is enabled for each of the
objects.
6. Choose Install. If an information dialog box appears, choose Continue. Choose Local Object or enter a
package if you need to transport the objects.

11. Activate Planning Function Type Objects.

 Remember

You can ignore activation warnings listed under Result [page 228].

1. Select BI Content in the left-hand frame.

2. Select Object Types and expand Planning Function Type for Planning .
3. Use Select Objects to select the following Planning Function:

Planning Functions

Planning Functions

/RAP/OP_BUFFER_DATA

4. Choose Transfer Selections.

5. In the list of Collected objects, verify that the option in the Install column is enabled for each of the
objects.
6. Choose Install. If an information dialog box appears, choose Continue. Choose Local Object or enter a
package if you need to transport the objects.

12. Choose Exit to leave the transaction.

Results

If activation warnings similar to the ones displayed below appear, you can ignore them.

● CMP problem occurred in characteristic <CHAR> for InfoProvider <INFO_PROV>

● Rounding inaccuracies occur with data type FLOAT for AMOUNT and QUANTITY
● Characteristic <CHAR>: Lower case makes selection of char. values difficult
● Data type of char. <CHAR> (<TYPE1>) is not equal to data type of attribute <ATTR> (<TYPE2>)
● Length of characteristic <TEXT CHAR> (<LENGTH1>) and assigned attribute <ATTR> (<LENGTH2>) not
same

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
256 PUBLIC Set Up the Applications
 ● The short text of DataSource <SOURCE> is not maintained in language <LANG>
● Skip key figure <KYF>: aggregation type NO2 not supported
● Attribute <ATTR>: Conversion routine <CONV> ignored
● Attribute <ATTR>: Compounding ignored
● Datatype FLTP for datafield <FIELD> of the DSO is not allowed
● Conversion problems possible for source field <FIELD1> / target field <FIELD2>

6.3.2.7 Upgrade from Retail SAP BW Structure

If you were using the previously existing Retail SAP BW structure, activate the local BI Content objects and
ensure that the previously generated time data (Gregorian calendar) is sufficient.

For detailed information, see the subsections Activate Application BI Content (Retail SAP BW Structure) and
Verify Gregorian Calendar.

6.3.2.7.1 Activate Application BI Content (Retail SAP BW

Structure)

Context

In this procedure, you perform a sequential, step-by-step activation of the local BI Content objects delivered in
the Retail SAP BW structure of the SAP Assortment Planning application. SAP Assortment Planning uses this
application BI Content to consume data stored in the back-end system.

 Caution

As of SAP Assortment Planning 2.0 FP2, a new (Omnichannel) SAP BW Structure has been introduced.
Please contact SAP for assistance with your upgrade project.

 Note

To ensure correct activation of the local BI Content objects, carry out the activation sequentially, as
specified in the following procedures. Resolve any activation warnings, except for the ones listed under
Activation Warnings [page 236], which can be ignored.

Also, the default BI setting to collect and activate all dependencies must not be disabled by the user. The
instructions below activate a minimum subset of objects, and it assumed that all their dependencies will be
collected and activated.

The consumed data from the back-end system can be created by the SAP Assortment Planning application, or
be replicated from a source master data system. In both cases, beware of limitations with regard to the
characters allowed by SAP BW. For more information, see 173241 and Customizing activity Maintain
permitted extra characters under SAP NetWeaver Business Warehouse General Settings .

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 257
Procedure

1. On your back-end SAP Assortment Planning system, open the Data Warehousing Workbench (transaction
RSA1).
2. Verify transport connections.
1. Select Transport Connection in the left-hand frame.
2. Select Object Types.
3. Expand Source System.

Selecting Source Systems

4. Use Select Objects to ensure that the back-end system is selected as the source system.
5. Choose Transfer Selections.
6. At the top of the right-hand frame, above the list of Collected objects, choose Grouping and select Only
Necessary Objects.
7. At the top of the right-hand frame, choose Collection Mode and select Collect Automatically.

Grouping and Collection Settings

3. Determine if you need to enable to Match (X) or copy option for the BI Content which you will activate in the
subsequent steps.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
258 PUBLIC Set Up the Applications
 Match(X) or copy Selection

Installation Type Selection

New Installation Do not enable the Match (X) or copy option for any of the BI Content objects.

Upgrade Standard /RAP/* BI Content ob­ Standard /RAP/* BI Content objects have been
jects have not been modified in modified in your local environment1
(Previously installed/
your local environment1
activated any of
the /RAP/* BI Content) Do not enable the Match (X) or copy Enable the Match (X) or copy option.
option for any of the BI Content ob­
During the activation of each BI Content object type,
jects.
you will be asked to carry out an additional Transfer
selections step. In this step, select to install the
Active Version (that is, your modified version) or the
Content Version (that is, the SAP delivered, and pos­
sibly updated version of the object). The project im­
plementation team should advise you on which op­
tion is required for each object.

 Caution
When you choose to install the Content Version,
the SAP delivered objects included in the current
release will be installed regardless of any modifi-
cations made to the currently existing BI Con­
tent objects.

1 As a system administrator, you may need to contact the SAP Assortment Planning project implementation team to
learn if standard, SAP-delivered, BI Content objects have been modified in your local environment.

4. Activate InfoObject catalogs.

If at any point during the installation of BI Content objects you are presented with a dialog asking you to
add objects to a personal list, we recommend that you select No.

 Remember

You can ignore activation warnings listed under Activation Warnings [page 236].

1. Select BI Content in the left-hand frame.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 259
 2. Select Object Types and expand InfoObject Catalog.

3. Use Select Objects to select the /RAP/CHAR_CAT and the /RAP/KYF_CAT catalogs.
4. Choose Transfer Selections.
5. In the right-hand frame, in the list of Collected objects, verify that both InfoObject catalogs are listed.
6. Right-click on each of the InfoObject catalogs, and choose Install all Below.
7. Choose Install.
If an information dialog box appears, choose Continue. Choose Local Object or enter a package if you
need to transport the objects.
5. Activate Variable /RAP/DISTM_MSM_01.

 Remember

You can ignore activation warnings listed under Activation Warnings [page 236].

1. Select BI Content in the left-hand frame.

2. Select Object Types and expand Query Elements.
3. Use Select Objects to select the /RAP/DISTM_MSM_01 Variable.

4. Choose Transfer Selections.

5. In the right-hand frame, in the list of Collected objects, verify that the /RAP/DISTM_MSM_01 Variable is
listed and that the option in the Install column is enabled.
6. Choose Install.
If an information dialog box appears, choose Continue. Choose Local Object or enter a package if you
need to transport the objects.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
260 PUBLIC Set Up the Applications
 6. Maintain version master data.
1. Select Modeling in the left-hand frame.
2. Expand InfoObjects.
3. Search for InfoObject /RAP/VERSN, located under Assortment Planning RAP Character InfoObject
Catalog .
4. Right-click the InfoObject /RAP/VERSN, choose Maintain Master Data from the context menu, and
maintain the following entries on the Time Independent tab:

Version

# - An empty version value that you must maintain

000

AP1

AP2

APF

AW1

AW2

OP1

OP2

PRJ

REF

The supported planning versions are described in detail in the Maintain Customizing Table /RAP/
RS_VARCUST section of the Common Installation Guide.

 Note

Save your changes and activate them.

7. Activate DataStore Objects.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 261
  Remember

You can ignore activation warnings listed under Activation Warnings [page 236].

1. Select BI Content in the left-hand frame.

2. Select Object Types and expand DataStore Object (Classic).
3. Use Select Objects to select all DataStore Objects starting with /RAP/*.
4. Choose Transfer Selections.
5. In the list of Collected objects, verify that the option in the Install column is enabled for each of the
objects.
6. Choose Install. If an information dialog box appears, choose Continue. Choose Local Object or enter a
package if you need to transport the objects.
If during the installation, you are presented with a dialog asking you to add objects to a personal list,
select No.
8. Activate InfoCubes.

 Remember

You can ignore activation warnings listed under Activation Warnings [page 236].

1. Select BI Content in the left-hand frame.

2. Select Object Types and expand InfoCube.
3. Use Select Objects to select all InfoCubes starting with /RAP/RC*.
4. Similarly, select InfoCubes /RAP/VC20 and /RAP/VC21.
5. Choose Transfer Selections.
6. In the list of Collected objects, verify that the option in the Install column is enabled for each of the
objects.
7. Choose Install. If an information dialog box appears, choose Continue. Choose Local Object or enter a
package if you need to transport the objects.
9. Activate CompositeProviders.

 Remember

You can ignore activation warnings listed under Activation Warnings [page 236].

1. Select BI Content in the left-hand frame.

2. Select Object Types and expand CompositeProvider.
3. Use Select Objects to select all CompositeProviders from /RAP/CP20 to /RAP/CP37 (inclusive).
4. Choose Transfer Selections.
5. In the list of Collected objects, verify that the option in the Install column is enabled for each of the
objects.
6. Choose Install. If an information dialog box appears, choose Continue. Choose Local Object or enter a
package if you need to transport the objects.
10. Activate Aggregation Levels.

 Remember

You can ignore activation warnings listed under Activation Warnings [page 236].

1. Select BI Content in the left-hand frame.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
262 PUBLIC Set Up the Applications
 2. Select Object Types and expand Planning Aggregation Level .
3. Use Select Objects to select the following Aggregation Levels:
These should be active from the previous installation, if not, select them to be installed again:

Aggregation Levels

Aggregation Level

/RAP/D20A01

/RAP/R20A02

/RAP/R20A06

/RAP/R20A08

/RAP/R20A11

/RAP/R20A12

/RAP/R20A15

/RAP/R20A17

/RAP/R23A01

4. Choose Transfer Selections.

5. In the list of Collected objects, verify that the option in the Install column is enabled for each of the
objects.
6. Choose Install. If an information dialog box appears, choose Continue. Choose Local Object or enter a
package if you need to transport the objects.

11. Reactivate Planning Sequence Objects.

 Remember

You can ignore activation warnings listed under Activation Warnings [page 236].

1. Select BI Content in the left-hand frame.

2. Select Object Types and expand Planning Planning Sequence .
3. Use Select Objects to select the following Planning Sequences:
These should be active from the previous installation, if not, select them to be installed again:

Planning Sequences

Planning Sequence

/RAP/C21A01_PS01

/RAP/C25A03_PS01

/RAP/D23A01_PS01

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 263
 Planning Sequence

/RAP/D24A01_PS01

/RAP/R20A08_PS01

4. Choose Transfer Selections.

5. In the list of Collected objects, verify that the option in the Install column is enabled for each of the
objects.
6. Choose Install. If an information dialog box appears, choose Continue. Choose Local Object or enter a
package if you need to transport the objects.

12. Reactivate Workbooks.

 Remember

You can ignore activation warnings listed under Activation Warnings [page 236].

1. Select BI Content in the left-hand frame.

2. Select Object Types and expand More Types Analysis Office Excel Workbook .
3. Use Select Objects to select the following workbooks:
These should be active from the previous installation, if not, select them to be installed again:

Workbooks

Workbook

/RAP/PLANASSORTMENT

/RAP/PLANOPTIONS

4. Choose Transfer Selections.

5. In the list of Collected objects, verify that the option in the Install column is enabled for each of the
objects.
6. Choose Install. If an information dialog box appears, choose Continue. Choose Local Object or enter a
package if you need to transport the objects.

13. Choose Exit to leave the transaction.

Activation Warnings

If activation warnings similar to the ones displayed below appear, you can ignore them.

● CMP problem occurred in characteristic <CHAR> for InfoProvider <INFO_PROV>

● Rounding inaccuracies occur with data type FLOAT for AMOUNT and QUANTITY
● Characteristic <CHAR>: Lower case makes selection of char. values difficult
● Data type of char. <CHAR> (<TYPE1>) is not equal to data type of attribute <ATTR> (<TYPE2>)
● Length of characteristic <TEXT CHAR> (<LENGTH1>) and assigned attribute <ATTR> (<LENGTH2>) not
same

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
264 PUBLIC Set Up the Applications
 ● The short text of DataSource <SOURCE> is not maintained in language <LANG>
● Skip key figure <KYF>: aggregation type NO2 not supported
● Attribute <ATTR>: Conversion routine <CONV> ignored
● Attribute <ATTR>: Compounding ignored
● Datatype FLTP for datafield <FIELD> of the DSO is not allowed
● Conversion problems possible for source field <FIELD1> / target field <FIELD2>

6.3.2.7.2 Verify Gregorian Calendar

Ensure that the previously generated time data (Gregorian calendar) is sufficient for the current release of SAP
Assortment Planning.

Context

Execute this procedure to generate time data (Gregorian calendar).

Procedure

1. Log on to SAP HANA studio.

2. In the SAP HANA Modeler perspective, on the Quick Launch tab, select your ABAP back-end system and
choose Generate Time Data.
3. Select Gregorian as the Calendar Type.

For example, SAP HANA views included in the SAP HANA content for SAP Customer Activity Repository
require the presence of time data in _SYS_BI.TIME_DIMENSION* SAP HANA database tables.
4. Enter a range of years that includes all the years of data that you plan to store in SAP Customer Activity
Repository.

Example: If you plan to start using SAP Assortment Planning on January 1, 2014, enter 2014 as your
starting year. But if you plan to access sales documents created in SAP ERP that date from January 2013,
specify 2013 as your starting year.
5. Define the granularity as Day, which is the minimum granularity required by SAP Customer Activity
Repository. You can choose a finer level of granularity, for example Hour, if necessary.
6. Choose the day that is the first day of the week in your company.
7. Choose Finish.

For more information, see:

○ https://help.sap.com/viewer/p/SAP_HANA_LIVE Installation and Upgrade Administrator's Guide

Configuration Steps Generate Time Data

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 265
 ○ https://help.sap.com/viewer/p/SAP_HANA_PLATFORM <Version> Development SAP HANA
Modeling Guide (for SAP HANA studio) Creating Information Views and Previewing its Output
Generate Time Data

6.3.2.8 Verify that Data Replication Is Running Following

the Upgrade

Following the upgrade, ensure that all of the data replication described in the Configure Data Replication section
of the Common Installation Guide is still running.

 Caution

The data you replicate in this step is consumed by the SAP Assortment Planning application through local
BI Content. Only a subset of ASCII characters is considered valid by SAP BW. As a result, object identifiers,
which are mapped to external IDs in DDF (for example, EXT_LOC_ID or EXT_PROD_ID), should only consist
of valid characters.

We recommend that you avoid the usage of invalid characters in the source master data system. This is
controlled by the system administrator or the implementation team who define the value ranges and
formatting for object identifiers (for example, product or location IDs).

If the recommended approach is not possible, then in your SAP Assortment Planning back-end system, you
need to allow for additional special characters in Customizing activity Maintain permitted extra characters
under SAP NetWeaver Business Warehouse General Settings . For more information, see 173241 .

In particular, following the upgrade, you need to pay attention to the following:

● SAP Assortment Planning supports the use of time-dependent article hierarchies. This is enabled by
implementing SAP Note 2196323 in the connected SAP Retail or SAP S/4HANA system.
Following the implementation of these notes in SAP Retail or SAP S/4HANA, if your hierarchy is already a
time-dependent hierarchy, you need to re-import the product hierarchies into SAP Assortment Planning
using the DRFOUT framework.
○ SAP Retail Description: Article Hierarchy
○ DRFOUT Outbound Implementation: PAHY
○ DDF Inbound Interface: /DMF/MDIF_PROD_HIER_INBOUND
● All the tables listed in the spreadsheet of the CARAB 5.0 - SLT Tables archive for your version of SAP
Customer Activity Repository applications bundle (SAP Assortment Planning) are being replicated. For
more information, see the Create/Replicate Source Master Data System Tables section in the Common
Installation Guide.
● Ensure that season classification data is being loaded from the appropriate source. For more information,
see the Load Season Classification Data section in the SAP Assortment Planning Administration Guide.
● Ensure that wholesale data is being loaded. Set up the Mapping report to convert sales orders into /DMF/
TS_WS table report (/DMF/WHOLESALE_SO_SHP_TO_TS_WS in transaction SE38) to run as a background
job to regularly import replicated sales order and shipment data into DDF. For more information, see the
Load Wholesale Data section in the SAP Assortment Planning Administration Guide.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
266 PUBLIC Set Up the Applications
6.3.2.9 Run the Validation Report

1. Run transaction /DMF/VAL_CAR_INSTALL.

Alternatively, run transaction SE38 and execute the /DMF/VALIDATE_CAR_INSTALLATION report.
2. Select the Assortment Planning scenario and select Execute.
In the dialog that appears, select whether to validate the Retail SAP BW structure, the Omnichannel SAP
BW structure, or both. The SAP BW structure to validate depends on the structure that you have selected
to reactivate during the upgrade in a previous step, see section Reactivate SAP Assortment Planning
Planning Framework Content.
Running this report allows you to verify the success of the installation, providing a log of potential issues.
For example, you may be presented with the following results:

Validation Report Results

View the long text associated with each message to see the link to the documentation describing the
procedure you have to troubleshoot.

6.3.2.10 Run the SAP Assortment Planning for Retail 4.0

Update Report

Context

Run this report to carry out back-end server changes required by the SAP Assortment Planning 5.0 release.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 267
Procedure

1. Run transaction SE38.

2. Execute the /RAP/40_UPGRADE_APR report.

Read the documentation associated with the report for important information on updates performed by
the report.

6.3.2.11 Activate SAP Assortment Planning ICF Services

Use

Following an upgrade, you must ensure that all ICF services required for the SAP Assortment Planning SAP
Fiori apps are activated.

Procedure

1. Log on to your front-end server.

2. Open service maintenance (transaction SICF).
3. In the Define Services screen, select the Location Clustering service by specifying the following:
○ Hierarchy Type: SERVICE
○ Virtual Host: DEFAULT_HOST
○ Service Path: /sap/bc/ui5_ui5/sap/locclsts_v2/
4. Choose Execute.
5. To activate the service, choose Service/host Activate.
6. Repeat steps 3 to 5 to ensure that all of the following services are activated:
○ /sap/bc/ui5_ui5/sap/attribmgmt_v2/
○ /sap/bc/ui5_ui5/sap/assortlist/
○ /sap/bc/ui5_ui5/sap/ddfreuse_v2/
○ /sap/bc/ui5_ui5/sap/locclsts_v2/
○ /sap/bc/ui5_ui5/sap/modulemgmt_v2/
○ /sap/bc/ui5_ui5/sap/optionplan_v2/
○ /sap/bc/ui5_ui5/sap/phpmatch_v2/
○ /sap/bc/ui5_ui5/sap/plnconfig/
○ /sap/bc/ui5_ui5/sap/optionplanning
○ /sap/bc/ui5_ui5/sap/styleplan
○ /sap/bc/ui5_ui5/sap/rankingkey
○ /sap/bc/ui5_ui5/sap/businessrule

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
268 PUBLIC Set Up the Applications
6.3.2.12 Define System Alias for Back-End Transactions

Use

A number of SAP Fiori apps, installed on your front-end system, launch transactions directly on the back-end
system. For example, the Manage Products tile actually launches the Demand Data Foundation (DDF)
POWL_EASY WebDynpro application.

Following an upgrade, you must ensure that all required RFC connections and system alias definitions remain
set.

Procedure

1. Log on to your front-end system, that is, the system where you have installed the user interface (UI)
components of your application.
2. Launch Configuration of RFC Connections (transaction SM59).
3. Create an RFC connection with the following settings:
○ RFC Destination: SAP_ISR_CARAB
Connection Type: H (HTTP connection)
Ensure to maintain all of the settings required to connect to your back-end system, in particular, the Target
Host entry on the Technical Settings tab.
4. Save your changes.
5. Create another RFC connection with the following settings:
○ RFC Destination: SAP_ERP_ISR_CARAB
Connection Type: H (HTTP connection)
Ensure to maintain all of the settings required to connect your front-end system to the source master data
system, in particular, the Target Host entry on the Technical Settings tab.
6. Save your changes.
7. Open Launchpad Customizing (transaction LPD_CUST).
8. Select the SAP Assortment Planning role ( UIRAP001), and choose Display.
The two catalogs, Assortment Planner and Planning Administrator, are displayed.
9. In each of the catalogs, selecting one app at a time, make the following settings:

Catalog App System Alias Description

Assortment View Log SAP_ISR_CARAB This setting allows the My Assortment Lists app to
Planner launch transaction SLG1 on the back-end system.

 Note
This application is only used to configure a link to
the back-end system, you do not need to add this
app to your SAP Fiori launchpad.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 269
 Catalog App System Alias Description

View ExtAssort SAP_ERP_ISR_CAR This setting allows the My Assortment Lists app to
Listing Conditions AB launch transaction WSL10 on the connected SAP Retail
or SAP S/4HANA system.

 Note
This application is only used to configure a link to
the SAP Retail or SAP S/4HANA system, you do not
need to add this app to your SAP Fiori launchpad.

View External SAP_ERP_ISR_CAR This setting allows the My Assortment Lists app to
Assortments AB launch:

Transaction WRF_WS0A3 on the connected SAP Retail

system

Transaction WS0A3 on the connected SAP S4HANA sys­

tem.

 Note
This application is only used to configure a link to
the SAP Retail or SAP S/4HANA system, you do not
need to add this app to your SAP Fiori launchpad.

Planning Manage Category SAP_ISR_CARAB This setting allows the Manage Category Responsibilities
Administrator responsibilities app to launch the corresponding DDF WebDynpro appli­
cation.

Manage Market SAP_ISR_CARAB This setting allows the Manage Market Responsibilities
responsibilities app to launch the corresponding DDF WebDynpro appli­
cation.

Manage Products SAP_ISR_CARAB This setting allows the Manage Products app to launch
the corresponding DDF WebDynpro application.

Manage Locations SAP_ISR_CARAB This setting allows the Manage Locations app to launch
the corresponding DDF WebDynpro application.

6.3.2.13 Troubleshoot Front-End Server Upgrade

Use

Following the upgrade of the product version on the front-end server, you may not be able to see some of the
SAP Assortment Planning SAP Fiori tiles in your launchpad. This section outlines how to troubleshoot these
issues, should you experience them.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
270 PUBLIC Set Up the Applications
These steps are also listed in the Troubleshooting section of the SAP Assortment Planning Administrator's
Guide available on the SAP Help Portal at http://help.sap.com/viewer/p/CARAB <Your Version>
Administration SAP Assortment Planning Administration Guide .

Process

Do the following:

1. Check that all of the required BSP applications are listed in the UIRAP001 package.
1. Log on to your front-end system (your SAP Gateway system).
2. Launch the Object Navigator (transaction SE80).
3. In the Repository Browser, open package UIRAP001.
4. Expand all of the embedded packages of embedded package CONTENT_RAP_TRANS.
5. Verify that the following BSP Applications are listed:

BSP Applications
6. If you do not see one or more of the BSP applications listed above, right-click on each of the
RETAIL_DDF and RETAIL_RAP_AP packages, and select Other Functions Rebuild Object List .

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 271
  Caution

Do not rebuild objects on a higher package level.

2. Clean the cache.

1. Log on to your front-end system (your SAP Gateway system).
2. In Customizing (transaction SPRO), navigate to SAP NetWeaver UI Technologies SAP Fiori
Data Administration Invalidate Caches .
This activity launches the /UI2/INVALIDATE_GLOBAL_CACHES report. This report invalidates all
server-side caches in SAP NetWeaver user interface services, which can become out-of-date following
an upgrade.
3. If necessary, implement instructions listed in SAP Note 2147669 .
3. Remove any previously customized versions of the UIRAP001 launchpad.
1. Log on to your front-end system (your SAP Gateway system).
2. Launch the Overview for Launchpads (transaction LPD_CUST).
3. Search for Role UIRAP001, and see whether any instances exist where the User Name is not SAP. If so,
this means that customized versions of the UIRAP001 launchpad exist, and these take precedence
over the standard launchpad instance delivered by SAP.
4. Delete all but the launchpad instance delivered by SAP.
4. Recalculate SAPUI5 application index, following any changes to the content of the SAPUI5 ABAP repository
(for example, installation of a new version of the SAPUI5 distribution layer or implementation of an SAP
Note containing changes to an SAPUI5 app).
For more information, see the Configure Index Calculation section in the Common Installation Guide and
SAP Note 2227577 .

6.4 SAP Promotion Management

SAP Promotion Management 4.0 SPS05 to SAP Promotion Management 5.0

There are no upgrade activities for SAP Promotion Management 5.0.

SAP Promotion Management 4.0 to SAP Promotion Management 4.0 SPS05

There are no upgrade activities for SAP Promotion Management 4.0 SPS05.

SAP Promotion Management 8.2 FP3 to SAP Promotion Management 4.0

There are no post-installation updates required for this release.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
272 PUBLIC Set Up the Applications
SAP Promotion Management 8.2 FP1 to SAP Promotion Management 8.2 FP3

Prerequisites
● Ensure that you have carried out all the steps listed in the previous sections of this guide.
● Please follow the instructions for RTLAPPS in SAP Note 2592695 .

Follow-Up Activities
1. Perform all the mandatory core steps for SAP Customer Activity Repository under Core (Mandatory for All
Applications) [page 81].
2. Activate the following OData services:
○ /DMFOFFER_MANAGMENT_V2_SRV
○ /DMF/LOCATION_SUBGROUP_SRV
3. Update to the latest version of the UI by installing 2606408

SAP Promotion Management 8.2 FP 2.0 to SAP Promotion Management 8.2

FP3

Prerequisites
● Ensure that you have carried out all the steps listed in the previous sections of this guide.
● Please follow the instructions for RTLAPPS in the following259265

Follow-Up Activities
1. Perform all the mandatory core steps for SAP Customer Activity Repository under Core (Mandatory for All
Applications) [page 81].
2. Activate the following OData services:
○ /DMFOFFER_MANAGMENT_V2_SRV
○ /DMF/LOCATION_SUBGROUP_SRV
3. Update to the latest versions of the UI by installing 2606408

SAP Promotion Management 8.2 SP4 to SAP Promotion Management 8.2

FP3

Prerequisites
● Ensure that you have carried out all the steps listed in the previous sections of this guide.
● Please follow the instructions for the STLAPPS in the following 2606408

Follow-Up Activities
1. Perform all the mandatory core steps for SAP Customer Activity Repository under Core (Mandatory for All
Applications) [page 81].

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 273
2. Activate the following OData services:
○ /DMFOFFER_MANAGMENT_V2_SRV
○ /DMF/LOCATION_SUBGROUP_SRV
3. Update to the latest version of the UI by installing 2606408

6.5 SAP Allocation Management

Post-upgrade setup for SAP Allocation Management

1.5 (CARAB 2.0 SPS0) to 4.0, 4.0 FPS02, 4.0 FPS03, 4.0 SPS04, 4.0 SPS05, or 5.0 [page 274]
Summary of follow-up activities to upgrade your SAP Allocation Management installation from release
1.5 to release 4.0, 4.0 FPS02, 4.0 FPS03, 4.0 SPS04, 4.0 SPS05, or 5.0.

2.0 FP1 to 4.0, 4.0 FPS02, 4.0 FPS03, 4.0 SPS04, 4.0 SPS05, or 5.0 [page 276]
Summary of follow-up activities to upgrade your SAP Allocation Management installation from release
2.0 FP1 to release 4.0, 4.0 FPS02, 4.0 FPS03, 4.0 SPS04, 4.0 SPS05, or 5.0

2.0 FP2 and FP3 to 4.0, 4.0 FPS02, 4.0 FPS03, 4.0 SPS04, 4.0 SPS05, or 5.0 [page 278]
Summary of follow-up activities to upgrade your SAP Allocation Management installation from release
2.0 FP2 and 2.0 FP3 to release 4.0, 4.0 FPS02, 4.0 FPS03, 4.0 SPS04, 4.0 SPS05, or 5.0.

Activate SAP HANA Content for SAP Allocation Management [page 279]
Once all previous steps are successfully completed, you can activate SAP HANA content for SAP
Allocation Management.

Check Procedure Associated with Function GENIOS_SOLVE Is Active [page 283]

For SAP Allocation Management, confirm that the procedure associated with function GENIOS_SOLVE
is active in the _SYS_AFL catalog.

Implement BAdI for Real-Time Inventory [page 284]

You must implement a BAdI to use real-time inventory in SAP Allocation Management.

Troubleshooting for SAP Allocation Management [page 284]

During the upgrade, several issues might arise in the context of CDS activation, SAP HANA content
activation, external view activation, and usage, static ABAP generation, and so on. Then you can
perform the troubleshooting activities. Please also refer to the notes listed in section SAP Notes for
the Upgrade.

6.5.1 1.5 (CARAB 2.0 SPS0) to 4.0, 4.0 FPS02, 4.0 FPS03, 4.0
SPS04, 4.0 SPS05, or 5.0

Summary of follow-up activities to upgrade your SAP Allocation Management installation from release 1.5 to
release 4.0, 4.0 FPS02, 4.0 FPS03, 4.0 SPS04, 4.0 SPS05, or 5.0.

 Note

SAP Allocation Management release 1.5 was included in the SAP Customer Activity Repository applications
bundle 2.0 SPS0 release.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
274 PUBLIC Set Up the Applications
The following steps are required to upgrade your SAP Allocation Management system:

● Perform all mandatory core steps for SAP Customer Activity Repository
● Run SAP Allocation Management reports
● Prepare follow-on system

Perform Mandatory Core Steps for SAP Customer Activity Repository

First do the mandatory core steps for SAP Customer Activity Repository. The core steps are also mandatory
for SAP Allocation Management.

 Note

To upgrade SAP Allocation Management from release 1.5 to 4.0, consider the following major changes:

● No matter which source master data system you are using (ECC or S4H), you must run the SLT table
creation programs that create dummy tables in the schema you are not using. Tables for both
schemas, ECC and S4H, need to be available before you can activate the SAP HANA content.
● The transport handling of HANA content has been migrated from HTC (HANA Transport Container) to
HTA (HANA Transport for ABAP). Report /AMR/ACTIVATE_HANA_CONTENT has been deprecated.
Instead, you must use report /CAR/ACTIVATE_HTA Activate SAP HANA Content for SAP CARAB.

Perform all steps listed under Core (Mandatory for All Applications) [page 81].

Verify that all SAP Allocation Management OData services are active following the upgrade. Especially check
the following new OData services:

● /AMR/OD_PRODUCT_FLOW_SRV Product Flow OData Service

● /AMR/OD_KPI_CONFIG_SRV KPI Configuration
● /AMR/OD_ALLOCATIONRESULT_SRV Fiori App Allocation Results
● /AMR/OD_BASKET_SRV Allocation Basket
● /AMR/OD_ALLOCATIONPLAN_SEARCH_SRV Fiori App Allocation Plan Search
● /AMR/OD_CAPACITYMANAGEMENT_SRV Store Areas and Capacities

Run Migration and Update Reports

● There are additional reports for the migration of market units:

1. Run report /AMR/MIGRATE_MARKET_UNITS_V20 to default the source type for given market units.
2. If you are upgrading to 4.0 FPS02, you must run report /AMR/MIGRATE_MARKET_UNITS_V42.
3. If you are upgrading to 4.0 FPS03, you must run report /AMR/MIGRATE_MARKET_UNITS_V43.

 Caution

These reports must be run before any new market unit is created in SAP Allocation Management 2.0
and must be executed exactly once in the system.

No market unit should be accessed in parallel while running these reports.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 275
● For the integration to SAP Assortment Planning, run the following two reports. The structure of the location
cluster sets has changed from release to release. Check the report long texts for further instructions.
1. To update location cluster set data created in SAP Assortment Planning 2.0 SPS1 to a format
consumable by SAP Assortment Planning 2.0 FP1, run report Update Location Clusters for SAP
Assortment Planning for Retail 2.0 FP01 /DMF/CLSTS_UPDATE_2_0_FP1.
2. To update location cluster set data created in SAP Assortment Planning 2.0 FP1 to a format
consumable by SAP Assortment Planning 2.0 FP2, run report Update Location Clusters for SAP
Assortment Planning for Retail 2.0 FP2 /DMF/CLSTS_UPDATE_2_0_FP02.

Prepare Follow-On System

In the follow-on system, use the new and enhanced RFC function module for the creation of allocation tables in
an ECC system. Follow the instructions in SAP Note 2416853 RFC function module to create allocation table
for SAP Allocation Management.

You can also transfer data to an SAP S/4HANA follow-on system. Follow the instructions in SAP Note 2524857
RFC function module to create allocation table for SAP Allocation Management in S4H system.

Related Information

Core (Mandatory for All Applications) [page 81]

Advanced (Optional) [page 110]

6.5.2 2.0 FP1 to 4.0, 4.0 FPS02, 4.0 FPS03, 4.0 SPS04, 4.0
SPS05, or 5.0

Summary of follow-up activities to upgrade your SAP Allocation Management installation from release 2.0 FP1
to release 4.0, 4.0 FPS02, 4.0 FPS03, 4.0 SPS04, 4.0 SPS05, or 5.0

The following steps are required to upgrade your SAP Allocation Management system:

● Perform all mandatory core steps for SAP Customer Activity Repository
● Prepare follow-on system

Perform Mandatory Core Steps for SAP Customer Activity Repository

First do the mandatory core steps for SAP Customer Activity Repository. The core steps are also mandatory
for SAP Allocation Management.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
276 PUBLIC Set Up the Applications
  Note

For upgrade of SAP Allocation Management from version 2.0 FP1 to 4.0, please consider the following
major change:

No matter which source master data system you are using (ECC or S4H), you must run the SLT table
creation programs that create dummy tables in the schema you are not using. Tables for both schemas,
ECC and S4H, need to be available before you can activate the SAP HANA content.

Perform all steps listed under Core (Mandatory for All Applications) [page 81].

Verify that all SAP Allocation Management OData services are active following the upgrade. Especially check
the following new OData services:

● /AMR/OD_PRODUCT_FLOW_SRV Product Flow OData Service

● /AMR/OD_KPI_CONFIG_SRV KPI Configuration
● /AMR/OD_ALLOCATIONRESULT_SRV Fiori App Allocation Results
● /AMR/OD_BASKET_SRV Allocation Basket
● /AMR/OD_ALLOCATIONPLAN_SEARCH_SRV Fiori App Allocation Plan Search
● /AMR/OD_CAPACITYMANAGEMENT_SRV Store Areas and Capacities

Run Migration and Update Reports

● If you are upgrading to 4.0 FPS02, you must run report /AMR/MIGRATE_MARKET_UNITS_V42.
● If you are upgrading to 4.0 FPS03 , you must run report /AMR/MIGRATE_MARKET_UNITS_V43.
● The structure of the location cluster sets has changed from the previous release. To update location cluster
set data created in SAP Assortment Planning 2.0 FP1 to a format consumable by SAP Assortment Planning
2.0 FP2, run report Update Location Clusters for SAP Assortment Planning for Retail 2.0 FP2 /DMF/
CLSTS_UPDATE_2_0_FP02.

Prepare Follow-On System

In the follow-on system, use the new and enhanced RFC function module for the creation of allocation tables in
an ECC system. Follow the instructions in SAP Note 2416853 RFC function module to create allocation table
for SAP Allocation Management.

You can also transfer data to an SAP S/4HANA follow-on system. Follow the instructions in SAP Note 2524857
RFC function module to create allocation table for SAP Allocation Management in S4H system.

Related Information

Core (Mandatory for All Applications) [page 81]

Advanced (Optional) [page 110]

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 277
6.5.3 2.0 FP2 and FP3 to 4.0, 4.0 FPS02, 4.0 FPS03, 4.0
SPS04, 4.0 SPS05, or 5.0

Summary of follow-up activities to upgrade your SAP Allocation Management installation from release 2.0 FP2
and 2.0 FP3 to release 4.0, 4.0 FPS02, 4.0 FPS03, 4.0 SPS04, 4.0 SPS05, or 5.0.

The following steps are required to upgrade your SAP Allocation Management system:

● Refer to the information and procedure description for SAP HANA content activation for SAP Allocation
Management in section Activate SAP HANA Content for SAP Allocation Management [page 279].

 Note

No matter which source master data system you are using (ECC or S4H), you must run the SLT table
creation programs that create dummy tables in the schema you are not using. Tables for both
schemas, ECC and S4H, need to be available before you can activate the SAP HANA content.

● Perform all mandatory core steps for SAP Customer Activity Repository
● Prepare the follow-on system.

Perform Mandatory Core Steps for SAP Customer Activity Repository

First do the mandatory core steps for SAP Customer Activity Repository. The core steps are also mandatory
for SAP Allocation Management.

Perform all steps listed under Core (Mandatory for All Applications) [page 81].

Verify that all SAP Allocation Management OData services and Core Data Services (CDS) views are active
following the upgrade:

● For a list of required OData services, refer to the SAP Allocation Management Administration Guide.
● For CDS views, see Troubleshooting: Missing Views in Database [page 283].

Run Migration Reports

● If you are upgrading to 4.0 FPS02, you must run report /AMR/MIGRATE_MARKET_UNITS_V42.
● If you are upgrading to 4.0 FPS03, you must run report /AMR/MIGRATE_MARKET_UNITS_V43.

Prepare Follow-On System

In the follow-on system, use the new and enhanced RFC function module for the creation of allocation tables in
an ECC system. Follow the instructions in SAP Note 2416853 RFC function module to create allocation table
for SAP Allocation Management.

You can also transfer data to an SAP S/4HANA follow-on system. Follow the instructions in SAP Note 2524857
RFC function module to create allocation table for SAP Allocation Management in S4H system.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
278 PUBLIC Set Up the Applications
Related Information

Core (Mandatory for All Applications) [page 81]

Advanced (Optional) [page 110]

6.5.4 Activate SAP HANA Content for SAP Allocation

Management
Once all previous steps are successfully completed, you can activate SAP HANA content for SAP Allocation
Management.

Prerequisites

Before starting with the activation of the SAP HANA content for SAP Allocation Management, you must do the
following:

● Ensure that you have at least one of the SAP_ECC or SAP_S4H schemas in the SAP HANA database. Based
on your source system for all SAP ERP data, you have either an SAP_ECC schema or an SAP_S4H schema
(either physical schemas with these names, or at least authoring schemas). If you have both these
systems, you must have two schemas.
● Ensure that all tables listed for SLT replication are available in the relevant schemas. The spreadsheet with
tables that are relevant for replication and SAP HANA content activation is available on SAP Help Portal at
https://help.sap.com/viewer/p/CARAB. Select the relevant version of SAP Customer Activity Repository at
the top and choose Implement. Download the SLT Tables for SAP Customer Activity Repository applications
bundle 5.0 archive and extract the spreadsheet. Also ensure that you have implemented SAP Note
2995707 (Prewave Note before HANA Content Activation).
Ensure that you have successfully set up the SLT tables in the schemas.

SAP HANA Content Activation Steps

1. Run the report /AMR/INSERT_SLT_TABLES_TO_DB (Insert SLT Table Entries to Database) in insert mode
(by deselecting the simulation setting).
2. Deploy SAP Allocation Management delivered procedures, functions, and views.
SAP Allocation Management delivers several native HANA objects as a part of the application. These
objects are delivered via HANA transport for ABAP (HTA) and must be explicitly deployed into the SAP
HANA database. Without this deployment, you do not see these objects in the SAP HANA database. Once
deployed, you can find the content via the path sap.is.retail.rap.amr.db.
3. Activate SAP Customer Activity Repository and Demand Data Foundation (DDF) SAP HANA content.

 Note

If the SAP Customer Activity Repository and DDF SAP HANA content is already active, you can skip this
step.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 279
 SAP Allocation Management depends on active SAP HANA content for SAP Customer Activity Repository
and DDF. Therefore, it is recommended that you first activate the SAP HANA content for SAP Customer
Activity Repository and DDF.
Run the program Activate SAP HANA Content for SAP CARAB (/CAR/ACTIVATE_HTA) and select the ECC
Mode relevant to your installation. Under Business Scenario Activation, select the Customer Activity
Repository and Demand Data Foundation options.
Run the activation report. As a result, you have successfully activated and deployed the SAP HANA content
for SAP Customer Activity Repository and DDF.

 Caution

Do not select Allocation Management in this activation run for a simultaneous activation of SAP
Allocation Management SAP HANA content. Simultaneous activation leads to activation problems.

4. Check and maintain schema mapping.

Check the names you use for your physical schema. If you are using the default names below, no further
action is required:
○ SAP_S4H, for your S/4HANA schema
○ SAP_ECC, for your ECC or FMS schema
If the names you have chosen for your physical schema are different from the names above, you must do
the following:

Maintain a schema mapping in your SAP HANA database, where your customer-specific names are used
as authoring schemas for the physical schema.
5. Run the dummy schema and dummy table creation reports.
The reports check for a missing physical schema and create this physical schema and the corresponding
dummy tables in the schema if necessary. The successful completion of this step is a prerequisite for a
successful SAP HANA content activation for SAP Allocation Management.

 Note

The running of the report requires a database user in the ABAP system with the authorization to create
the dummy schema. Check the application log for the report if there were errors.

In your back-end system, start transaction SE38 and execute the following two reports, in the sequence in
which they are listed:
○ /DMF/CREATE_SLT_TABLES (Create SLT Tables)
1. Select your source system. For S/4HANA, enter the release.
2. Enter the physical source and dummy schema names. For the Physical Source Schema, enter the
physical schema name into which your SLT tables are replicating. For the Physical Dummy Schema,
enter the name for the schema to be created. If the physical source schema already exists in the SAP
HANA database, then only the dummy tables in this schema are created when you execute the report.
3. Select the simulation mode for a test run. After the simulation run, you can check for errors in the
application log.
4. Run the report again, this time without simulation mode.
5. If you have chosen a dummy schema name that is neither SAP_ECC nor SAP_S4H, maintain schema
mapping for the dummy schema. Follow the guidelines mentioned in Step 4.
○ /AMR/CREATE_DYNAMIC_SLT_TABLES (Create SLT Tables Dynamically)
1. Select your source system. For S/4HANA, enter the release.
2. Enter the physical source and dummy schema names. For the Physical Source Schema, enter the
physical schema name into which your SLT tables are replicating. For the Physical Dummy Schema,

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
280 PUBLIC Set Up the Applications
 enter the name for the schema to be created. If the physical source schema already exists in the SAP
HANA database, then only the dummy tables in this schema are created when you execute the report.
3. Select the simulation mode for a test run. After the simulation run, you can check for errors in the
application log.
4. Run the report again, this time without simulation mode.
5. If you have chosen a dummy schema name that is neither SAP_ECC nor SAP_S4H, maintain schema
mapping for the dummy schema. Follow the guidelines mentioned in Step 4.
6. Activate relevant inactive SAP HANA content for DDF.
Based on your scenario, there may be inactive packages in DDF, even though you have activated the
content earlier via the report /CAR/ACTIVATE_HTA (Activate SAP HANA Content for SAP CARAB).
For the following packages in DDF, perform these actions:
○ In the table CTS_HOT_PREWORK, set the PREWORK_DONE indicator to X for these packages.
○ Call up transaction SCTS_HTA_DEPLOY (SAP HANA Transport for ABAP - Deployment) to check and to
deploy (if not already deployed) these packages, strictly in the sequence they are listed. Do not select
the option to Include subpackages:
○ sap.is.ddf.ecc
○ sap.is.ddf.fms
○ sap.is.ddf.fms_s4h
○ sap.is.ddf.cross.ecc
○ sap.is.ddf.cross.fms
○ sap.is.ddf.cross.fms_s4h
○ sap.is.ddf.cross

 Note

The package names are case-sensitive.

If your SAP Retail release has tables that do not contain any FMS fields, some views might not be
activated successfully in the fms and fms_s4h packages. You can nevertheless continue with further
activation steps.

7. Grant authorization.
The two SLT table creation reports use the database user maintained in the ABAP system to create the
dummy schemas. The _SYS_REPO user needs the exact same authorizations on the newly created dummy
schema that this user already has on the physical source schema. In addition, to display the schema in the
navigator, a SELECT authorization on the schema (with GRANT option) must be provided to the database
user for the content activation.

 Note

This step must be performed by the SAP HANA database administrator who has the authorization for
these activities.

8. Set Prework Done for SAP Allocation Management packages.

A precondition for SAP HANA Transport for ABAP (HTA) activation is that the PREWORK_DONE indicator is
set for all packages with activation mode P – prework needed. You can check this setting in the table
CTS_HOT_PACKAGE in field HOT_ACTIVATION_MODE.
You can set the PREWORK_DONE indicator for all packages relevant for SAP Allocation Management
manually or by implementing an SAP Note. To make the setting manually, follow the additional steps listed

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 281
 in this step. Alternatively, implement SAP Note 2861929 (Setting the PREWORK_DONE flag in table
CTS_HOT_PREWORK for AMR HANA Content packages) instead of setting the indicator manually.
The manual steps are as follows:
1. Set the PREWORK_DONE indicator to X for all packages in the CTS_HOT_PREWORK table. The indicator
shows that the SAP HANA content in all packages relevant for SAP Allocation Management is ready for
deployment.
2. Call transaction SE16 (Data Browser) and display the content of table CTS_HOT_PACKAGE.
Search for package names sap.is.retail.rap.amr* in the field HANA_PACKAGE_ID. Please note
that the package names are case-sensitive.
You should find 163 entries that match the search criterion. Copy the package names from the result
list of your search.
3. Run the program Activate SAP HANA Content for SAP CARAB (/CAR/ACTIVATE_HTA) with the
following settings:
○ Select the relevant setting under ECC Mode.
○ Under Business Scenario Activation, select the Allocation Management option.
○ Under Processing Control, select Perform Prerequisite Check.
4. Display the selection screen of table CTS_HOT_PREWORK. Enter the HANA_PACKAGE_ID for all
packages from the result list of your search in table CTS_HOT_PACKAGE.
9. Once you have successfully deployed all content as described in the previous steps, call up transaction SAP
HANA Transport for ABAP - Deployment (SCTS_HTA_DEPLOY). To deploy the SAP Allocation Management
packages, enter package name sap.is.retail.rap.amr* and choose Execute.

 Note

With this step, the SAP HANA content for SAP Allocation Management is finally deployed. This is the
last and most critical activation step.

Checking for Missing Views

If content activation errors occur, check for missing views in the database. For more information, see
Troubleshooting: Missing Views in Database [page 283].

Related Information

Create/Replicate Source Master Data System Tables [page 88]

Activate SAP HANA Content [page 92]

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
282 PUBLIC Set Up the Applications
6.5.4.1 Troubleshooting: Missing Views in Database

After the SAP HANA content activation, you can check for missing views in transaction DB02.

Check if SAP Allocation Management views are highlighted as objects missing in the database. There could be
some missing objects, despite having received success messages from the previous step of activating SAP
Allocation Management SAP HANA content.

1. Call up transaction Diagnostics: Missing Tables and Indexes (DB02)

2. Select Diagnostics Tables/Views and enter the technical name.
3. Check if any SAP Allocation Management views are displayed as missing in the database.
4. If there are views missing in the database, raise a support ticket.

6.5.5 Check Procedure Associated with Function

GENIOS_SOLVE Is Active

For SAP Allocation Management, confirm that the procedure associated with function GENIOS_SOLVE is active
in the _SYS_AFL catalog.

Prerequisites

You have configured the AFL usage and confirmed that the OFL algorithm was installed successfully as
described in section Check the OFL Installation [page 58].

Context

Procedure

1. Go to SAP HANA Systems view in the SAP HANA Development Perspective.

2. In your system, filter for catalog _SYS_AFL.
3. In the _SYS_AFL catalog, filter on procedures to search for OFL_AREA_GENIOS_DOLVE_PROC
4. Confirm that this procedure OFL_AREA_GENIOS_SOLVE_PROC is available.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 283
6.5.6 Implement BAdI for Real-Time Inventory

You must implement a BAdI to use real-time inventory in SAP Allocation Management.

As of SAP Customer Activity Repository applications bundle 5.0, a BAdI implementation is required to obtain
real-time data inventory data for SAP Allocation Management.

You can implement a BAdI using standard logic or implement your own logic. For more information and detailed
steps, please see SAP Note 2982741 - SAP Allocation Management - BAdI Implementation for Real-Time
Inventory View.

6.5.7 Troubleshooting for SAP Allocation Management

During the upgrade, several issues might arise in the context of CDS activation, SAP HANA content activation,
external view activation, and usage, static ABAP generation, and so on. Then you can perform the
troubleshooting activities. Please also refer to the notes listed in section SAP Notes for the Upgrade.

After the SAP HANA content activation, some Core Data Services (CDS) views may not be active. In this case,
you can run program RADMASG0 in transaction SE38 for the collective activation of CDS views and external
views. Select Direct Objects and enter /AMR/V* in the View Name selection field. Then execute the report.

Related Information

Implement SAP Notes for the Upgrade [page 29]

6.6 SAP Replenishment Planning

Post-upgrade setup for SAP Replenishment Planning

1. Ensure that the SAP XRP AFL component is installed. For more information, see Download and Install SAP
XRP AFL (Only for SAP Replenishment Planning) [page 71].
2. Perform Core Steps for SAP Customer Activity Repository [page 217]
3. Complete UDF Setup [page 128]
4. Implement SAP Notes for the Integration of SAP Replenishment Planning with SAP ERP or SAP S/4HANA
[page 285]
5. Specify RFC Destinations for Source Master Data Systems [page 286]
6. Enable the Use of Scheduling Groups [page 286]
7. Set Up SAP Fiori Apps for SAP Replenishment Planning [page 287]
8. Set Up Database Roles and Authorizations [page 309]
9. Set Up Back-End Roles and Authorizations [page 310]
10. Set Up Authorizations for Transfer of Order Plan Items to Source Master Data System [page 315]

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
284 PUBLIC Set Up the Applications
 11. Perform Configuration Steps in SAP Customer Activity Repository [page 316]
12. Configure SAP Replenishment Planning [page 317]
13. Define the Parameterization Profiles and the Assignment [page 319]
14. Configure Exception Management [page 320]
15. Verify Real-Time Inventory Integration [page 322]

6.6.1 Perform Core Steps for SAP Customer Activity

Repository

To set up this application, you must first perform the Core (Mandatory) steps for SAP Customer Activity
Repository. The core steps are mandatory for all the consuming applications.

Procedure

Perform all steps listed under Core (Mandatory for All Applications) [page 81].

6.6.2 Implement SAP Notes for the Integration of SAP

Replenishment Planning with SAP ERP or SAP S/
4HANA

There are notes that provide the functionality for receiving order plan items from SAP Customer Activity
Repository and notes that provide the functionality for the replication of additional information relevant for SAP
Replenishment Planning from SAP ERP or SAP S/4HANA.

To decide whether you have to install these notes on your SAP ERP or SAP S/4HANA system or not, please
check if the following notes are already included in the support packages that you have installed (by checking
the Support Packages & Patches section of these notes).

SAP Notes for Receiving Order Plan Items from SAP Customer Activity Repository

SAP Note Description

2806257 This note provides the reference field EXTERNALREFEREN­

CEID in table EKPO for receiving the order plan item ID.
Enhancement of table EKPO by the field EXTERNALREFER­
ENCEID

2800988 This note provides the enhancement for persisting the infor­
mation about the origin of the purchase order item and the
Grouping of Order List Items: External Reference persisted
corresponding reference number.
(EXTERNALREFERENCEID)

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 285
SAP Note Description

2679390 This note provides the proxy functionality in SAP ERP and
SAP S/4 HANA for the transfer of order plan items.
Integration Proxy for CAR-based Replenishment (Order Plan
to Purchase Order)

2834608 This note contains instructions for creating DDIC objects

that are required for implementing SAP note 2679390.
Automatic implementation of manual changes for note
2679390 (SAP S/4)

SAP Notes for Replicating Additional Information Relevant for SAP Replenishment Planning from SAP ERP or SAP S/4HANA

SAP Note Description

2918510 This note describes how to determine which notes are re­
quired for the data integration from a source master data
How to find notes to get integration up to date for DRFOUT to
system (SAP ERP or SAP S/4HANA) to the Demand Data
DDF
Foundation module of SAP Customer Activity Repository.

2774819 This note lists the DRF outbound implementations that are
available to replicate master and transaction data from a
DRFOUT Implementations by scenario for Customer Activity
source master data system (SAP ERP or SAP S/4HANA) to
Repository Application Bundle
the applications of SAP Customer Activity Repository.

6.6.3 Specify RFC Destinations for Source Master Data

Systems
To transfer order plan items to a source master data system (SAP ERP or SAP S/4HANA), you must specify an
RFC destination for each master data system to which you want to transfer order plan items for purchase order
creation.

You specify an RFC destination as follows in the Customizing for Demand Data Foundation:

1. In transaction SPRO, navigate to Cross-Application Components Replenishment Planning Basic

Settings Maintain RFC Mapping and execute this Customizing activity.
2. For each master data system to which you want to transfer order plan items for purchase order creation,
create a mapping entry with the following values:
○ Application: Order Plan Export to Purchasing
○ Sender System: Name of the master data system to which order plan items are to be sent
○ RFC Destination: Name of the RFC destination assigned to the master data system

6.6.4 Enable the Use of Scheduling Groups

The scheduling group is a master data attribute of product and product location in the Demand Data
Foundation (DDF) that can be used as selection criterion for the workload selection of the replenishment

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
286 PUBLIC Set Up the Applications
calculation or as condition for configuration assignments. There is no standard replication of the scheduling
group from SAP ERP or SAP S/4HANA Retail to DDF.

To use scheduling groups for SAP Replenishment Planning, implement one or both of the following Business
Add-Ins (BAdI) of enhancement spot ES_DMF_BADI in the source master data system. These BAdIs serve to
replicate information from SAP ERP or SAP S/4HANA to the DDF scheduling group at product or product
location level:

● DMF_BADI_PRODUCT_SCHED_GRP for mapping of information to product scheduling group

● DMF_BADI_PRODLOC_SCHED_GRP for mapping of information to product location scheduling group

Use one or both BAdIs depending on the level where you store or where you use the data. Both BAdIs provide
an example implementation (class) for mapping the loading group from the source master data system to the
scheduling group in DDF, either at article (product) level (MAW1-WLADG) to product scheduling group, or at
article/site (product/location) level (MARC-LADGR) to product location scheduling group.

Once a BAdI is implemented, you must implement the change pointer for the field you are mapping the
scheduling group to. For detailed information, see the documentation of the Business Add-Ins that you plan to
implement in the source master data system.

6.6.5 Set Up SAP Fiori Apps for SAP Replenishment Planning

After you have set up and configured your system landscape, you implement the SAP Fiori apps for SAP
Replenishment Planning by performing different tasks on the front-end server and on the back-end server.

Context

The SAP Fiori launchpad is the single entry point for the SAP Fiori apps delivered with SAP Replenishment
Planning. In addition to these setup instructions, technical implementation information is available for each
app.

● App Implementation: Manage Configuration Assignments [page 292]

● App Implementation: Manage Constraint Profiles [page 295]
● App Implementation: Manage Cost Profiles [page 296]
● App Implementation: Manage Procurement Schedules [page 298]
● App Implementation: Manage Shelf Cost Profiles [page 300]
● App Implementation: Review Order Plan Items [page 302]
● App Implementation: Simulate Replenishment [page 305]
● App Implementation: Manage Alerts [page 307]

Prerequisites

● You have installed and configured the system landscape.

For information, see Implement the Prerequisites.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 287
● You have configured SAP Gateway.

 Note

The common OData services are delivered as part of the SAP Fiori front-end server and are located in
the SAP Gateway system. They are required for the SAP Fiori launchpad and you must always activate
them.

For information, see Verify that OData Services are Active [page 101].

● You have installed the UDF reuse component (SAP UI5 Application UDFREUSE and OData service /DMF/
DEMAND_PLAN_UTILITIES). For information, see Set Up the UDF Reuse Component [page 291].
● (Optional, recommended) To be able to display on-screen help directly in the app and easily call up a
detailed app description, you must have enabled the in-app help with the underlying Web Assistant
framework. See section Enable In-App Help (Web Assistant) [page 325].

Process Steps

To set up the SAP Fiori apps for SAP Replenishment Planning, perform the following steps.

Activate ICF Services

For security reasons, the Internet Communication Framework (ICF) services are delivered in an inactive state.
You must activate the services that are required for the apps.

 Note

After an upgrade, you must ensure that the Internet Communication Framework (ICF) services required for
the apps are still active.

To activate the ICF services required for the apps:

1. Log on to your front-end server.

2. Execute transaction SICF.
3. In the Define Services screen, make the following selections:
○ Hierarchy Type: SERVICE
○ Virtual Host: DEFAULT_HOST
○ Service Path:

App Service Path

Manage Configuration Assignments /sap/bc/ui5_ui5/sap/configassignman

Manage Constraint Profiles /sap/bc/ui5_ui5/sap/prflconstrntman

Manage Cost Profiles /sap/bc/ui5_ui5/sap/prflcostsman

Manage Procurement Schedules /sap/bc/ui5_ui5/sap/procschedeman

Manage Shelf Cost Profiles /sap/bc/ui5_ui5/sap/prflshlfcapman

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
288 PUBLIC Set Up the Applications
 App Service Path

Review Order Plan Items /sap/bc/ui5_ui5/sap/review_opi

Simulate Replenishment /sap/bc/ui5_ui5/sap/repl_simulation

Manage Alerts /sap/bc/ui5_ui5/sap/rtlplngalrtman

4. Choose Execute ( F8 ).
5. Under Virtual Hosts / Services, double-click a service to open the Create/Change a Service screen.

App ICF Service

Manage Configuration Assignments configassignman

Manage Constraint Profiles Prflconstrntman

Manage Cost Profiles prflcostsman

Manage Procurement Schedules procschedeman

Manage Shelf Cost Profiles prflshlfcapman

Review Order Plan Items review_opi

Simulate Replenishment repl_simulation

Manage Alerts Rtlplngalrtman

6. To activate a service, choose Service/Host Activate .

 Note

You can check the activation status by selecting the service and opening the context menu. If the
Activate Service option is grayed out, this means the service is already active.

7. Repeat steps 3 to 6, this time using /sap/bc/ui5_ui5/sap/udfreuse/ as the service path.

Activate Application-Specific OData Services for SAP Replenishment Planning

To activate the application-specific OData services required for SAP Replenishment Planning:

Enable the Apps for SAP Fiori Launchpad

To be able to access the apps from the SAP Fiori launchpad, your front-end system user must have the
necessary role(s) assigned. This allows you to access the business catalogs and business groups required for
the apps.

You can use the following role as a template for your own roles: Replenishment Planner (SAP_XRP_TCR_T). The
following catalogs and business groups are assigned to this role:

Component Technical Name

Technical Catalog SAP_XRP_TC_REPL (Replenishment Planning)

Business Catalog SAP_XRP_BC_REPL (Replenishment Planning)

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 289
Component Technical Name

Business Group SAP_XRP_BCG_REPL_CONFIG (Replenishment

Configuration)

Business Group SAP_XRP_BCG_REPL_PLANNING (Replenishment Planning)

Business Group SAP_XRP_BCG_SIMULATION (Replenishment Simulation)

Business Group SAP_XRP_BCG_ALERT_MANAGEMENT (Alert Management)

To enable the apps for SAP Fiori launchpad:

1. Log on to your front-end system.

2. Execute transaction SU01 to open the User Maintenance screen.
3. Enter your front-end user name in the User field and choose Change.
4. On the Roles tab, assign the Replenishment Planner (SAP_XRP_TCR_T) role to your user or assign a
custom role that was created by using the Replenishment Planner (SAP_XRP_TCR_T) role as a template.
5. Save your changes.

 Tip

If you already have an SAP Fiori launchpad open, clear your web browser cache to see the changes.

 Note

To access the Analyze Forecast app either from the SAP Fiori launchpad or in the Review Order Plan Items
app and to run the UDF reuse component, the Demand Planner (Retail) (SAP_DPL_TCR_T) business role is
required.

Assign Area of Responsibility (AOR) to ABAP Back-End User

You can only display and select product hierarchies in the app that have been assigned as an AOR to your ABAP
back-end user.

To assign an area of responsibility (AOR) to an ABAP back-end user:

1. Log on to your ABAP back-end system.

2. Execute transaction NWBC to open the SAP NetWeaver Business Client.
3. Choose Services Maintain Area of Responsibility Product Hierarchy .
4. Select your ABAP back-end user, choose Continue, and define the AOR.
For instructions, see the application help for SAP Customer Activity Repository at https://help.sap.com/
viewer/p/CARAB. Search for Maintain Area of Responsibility and follow the instructions.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
290 PUBLIC Set Up the Applications
6.6.5.1 Set Up the UDF Reuse Component

Before implementing an app for SAP Replenishment Planning, you must install the UDF reuse component.

Context

The UDF reuse component consists of two parts:

● Front-end server: SAP UI5 Application UDFREUSE

● Back-end server: OData service /DMF/DEMAND_PLAN_UTILITIES

Process Steps

To set up the UDF reuse component, perform the following steps:

Activate ICF Services

For security reasons, the Internet Communication Framework (ICF) services are delivered in an inactive state.
You must activate the services that are required for the UDF reuse component.

 Note

After an upgrade, you must ensure that the Internet Communication Framework (ICF) services required for
the UDF reuse component are still active.

To activate the ICF services required for the UDF reuse component:

1. Log on to your front-end server.

2. Execute transaction SICF.
3. In the Define Services screen, make the following selections:
○ Hierarchy Type: SERVICE
○ Virtual Host: DEFAULT_HOST
○ Service Path:

Component Service Path

UDF reuse component /sap/bc/ui5_ui5/sap/udfreuse

4. Choose Execute ( F8 ).
5. Under Virtual Hosts / Services, double-click a service to open the Create/Change a Service screen.

Component ICF Service

UDF reuse component udfreuse

6. To activate a service, choose Service/Host Activate .

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 291
  Note

You can check the activation status by selecting the service and opening the context menu. If the
Activate Service option is grayed out, this means the service is already active.

Create your custom copy of the /DMF/DPL role on the back-end server

1. Log on to the back-end server.

2. Execute transaction PFCG to open the Role Maintenance screen.
3. Search for the /DMF/DPL role.

 Note

/DMF/DPL (Demand Planner (Retail)) is the back-end server authorization role required for the apps for
demand forecasting (Analyze Forecast, Adjust Forecast, Manage Demand Influencing Factors) and SAP
Replenishment Planning (Review Order Plan Items, Simulate Replenishment).

 Caution

/DMF/DPL is one of the standard roles delivered by SAP.

Standard roles are delivered as templates (most begin with the prefix SAP_*). Never change the
standard roles, but only your custom copies of these roles (Z_*). Otherwise, any standard roles that
you have changed will be overwritten by newly delivered standard roles during a later upgrade or
release change.

4. Create your custom copy of /DMF/DPL on the back-end server:

Choose Role Copy and enter a name from the customer namespace for your copied role.
5. Save your changes.

The authorization object /DMF/DPL is assigned to the role /DMF/DPL. This authorization object implements
the following components:

● Product and product hierarchy filters

● Location and location hierarchy filters
● Chart component consisting of time series chart, decomposition chart and table view

Among others, these components are used by the Review Order Plan Items and Simulate Replenishment apps.

6.6.5.2 App Implementation: Manage Configuration

Assignments

 Tip

You can also find the data required to implement the Manage Configuration Assignments app in the SAP
Fiori apps reference library at https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/
index.html#?appId=F4644.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
292 PUBLIC Set Up the Applications
Prerequisites

Before implementing the app, you must ensure the following:

● You have installed the UDF reuse component (SAP UI5 Application UDFREUSE and OData service
/DMF/DEMAND_PLAN_UTILITIES). For information see Set Up the UDF Reuse Component [page 291].

System Landscape Requirements

For information about the system requirements, see Implement the Prerequisites.

Implementation Tasks

The following section lists tasks that have to be performed to implement this app. The tables contain the app-
specific data required for these tasks.

Front-End Server: Activate OData Services

Component Technical Name

OData Service (Version Number) /DMF/PARAMETER_ASSIGNMENT_SRV (1)

For more information about activating OData services, see Set Up SAP Fiori Apps for SAP Replenishment
Planning [page 287] under Activate Application-Specific OData Services for SAP Replenishment Planning.

Front-End Server: Activate SAPUI5 Application

Component Technical Name

SAP UI5 Application CONFIGASSIGNMAN

For more information about how to activate the ICF service, see Set Up SAP Fiori Apps for SAP Replenishment
Planning [page 287] under Activate ICF Services.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 293
Front-End Server: Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps
that have been assigned by an administrator to the catalog designed for this user's role. For more information,
see Set Up SAP Fiori Apps for SAP Replenishment Planning [page 287] under Enable the Apps for SAP Fiori
Launchpad.

SAP delivers technical catalogs for groups of SAP Fiori apps as repositories to create your own catalogs in the
launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app.

Front End Server: Catalog Details

Component Technical Name

Technical Catalog SAP_XRP_TC_REPL

Business Catalog SAP_XRP_BC_REPL

Business Group SAP_XRP_BCG_REPL_CONFIG

Back-End Server: Set Up Authorizations

On the back-end server, set up the authorizations for SAP Replenishment Planning as described in Set Up
Back-End Roles and Authorizations [page 310]. For the Manage Configuration Assignments app, the following
authorization objects are relevant:

Authorization Object
Authorization Object Description Field Value Field Description

/DMF/DPL
Authorization to use ACTVT Execute Activity

the product and prod­

uct hierarchy filters
and the location and
location hierarchy fil-
ters in the Manage
Configuration
Assignments app.

/DMF/MCASG
Authorization to dis­ ACTVT Display Activity

play and change con­

Change
figuration assignments
by using the Manage
Configuration
Assignments app.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
294 PUBLIC Set Up the Applications
6.6.5.3 App Implementation: Manage Constraint Profiles

 Tip

You can also find the data required to implement the Manage Constraint Profiles app in the SAP Fiori apps
reference library at https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html#?
appId=F4477 .

System Landscape Requirements

For information about the system requirements, see Implement the Prerequisites.

Implementation Tasks

The following section lists tasks that have to be performed to implement this app. The tables contain the app-
specific data required for these tasks.

Front-End Server: Activate OData Services

Component Technical Name

OData Service (Version Number) /DMF/PROFILE_CONSTRAINT_PARAM_SRV (1)

For more information about activating OData services, see Set Up SAP Fiori Apps for SAP Replenishment
Planning [page 287] under Activate Application-Specific OData Services for SAP Replenishment Planning.

Front-End Server: Activate SAPUI5 Application

Component Technical Name

SAP UI5 Application PRFLCONSTRNTMAN

For more information about how to activate the ICF service, see Set Up SAP Fiori Apps for SAP Replenishment
Planning [page 287] under Activate ICF Services.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 295
Front-End Server: Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps
that have been assigned by an administrator to the catalog designed for this user's role. For more information,
see Set Up SAP Fiori Apps for SAP Replenishment Planning [page 287] under Enable the Apps for SAP Fiori
Launchpad.

SAP delivers technical catalogs for groups of SAP Fiori apps as repositories to create your own catalogs in the
launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app.

Front End Server: Catalog Details

Component Technical Name

Technical Catalog SAP_XRP_TC_REPL

Business Catalog SAP_XRP_BC_REPL

Business Group SAP_XRP_BCG_REPL_CONFIG

Back-End Server: Set Up Authorizations

On the back-end server, set up the authorizations for SAP Replenishment Planning as described in Set Up
Back-End Roles and Authorizations [page 310]. For the Manage Constraint Profiles app, the following
authorization objects are relevant:

Authorization Object
Authorization Object Description Field Value Field Description

/DMF/PRFLM
Authorization to dis­ ACTVT Display Activity

play and change con­

Change
straint profiles by us­
ing the Manage
Constraint Profiles app.

6.6.5.4 App Implementation: Manage Cost Profiles

 Tip

You can also find the data required to implement the Manage Cost Profiles app in the SAP Fiori apps
reference library at https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html#?
appId=F4478.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
296 PUBLIC Set Up the Applications
System Landscape Requirements

For information about the system requirements, see Implement the Prerequisites.

Implementation Tasks

The following section lists tasks that have to be performed to implement this app. The tables contain the app-
specific data required for these tasks.

Front-End Server: Activate OData Services

Component Technical Name

OData Service (Version Number) /DMF/PROFILE_COST_PARAM_SRV (1)

For more information about activating OData services, see Set Up SAP Fiori Apps for SAP Replenishment
Planning [page 287] under Activate Application-Specific OData Services for SAP Replenishment Planning.

Front-End Server: Activate SAPUI5 Application

Component Technical Name

SAP UI5 Application PRFLCOSTSMAN

For more information about how to activate the ICF service, see Set Up SAP Fiori Apps for SAP Replenishment
Planning [page 287] under Activate ICF Services.

Front-End Server: Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps
that have been assigned by an administrator to the catalog designed for this user's role. For more information,
see Set Up SAP Fiori Apps for SAP Replenishment Planning [page 287] under Enable the Apps for SAP Fiori
Launchpad.

SAP delivers technical catalogs for groups of SAP Fiori apps as repositories to create your own catalogs in the
launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 297
Front End Server: Catalog Details

Component Technical Name

Technical Catalog SAP_XRP_TC_REPL

Business Catalog SAP_XRP_BC_REPL

Business Group SAP_XRP_BCG_REPL_CONFIG

Back-End Server: Set Up Authorizations

On the back-end server, set up the authorizations for SAP Replenishment Planning as described in Set Up
Back-End Roles and Authorizations [page 310]. For the Manage Cost Profiles app, the following authorization
objects are relevant:

Authorization Object
Authorization Object Description Field Value Field Description

/DMF/PRFLM
Authorization to dis­ ACTVT Display Activity

play and change cost

Change
profiles by using the
Manage Cost Profiles
app.

6.6.5.5 App Implementation: Manage Procurement

Schedules

 Tip

You can also find the data required to implement the Manage Procurement Schedules app in the SAP Fiori
apps reference library at https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/
index.html#?appId=F4475.

System Landscape Requirements

For information about the system requirements, see Implement the Prerequisites.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
298 PUBLIC Set Up the Applications
Implementation Tasks

The following section lists tasks that have to be performed to implement this app. The tables contain the app-
specific data required for these tasks.

Front-End Server: Activate OData Services

Component Technical Name

OData Service (Version Number) /DMF/PROCUREMENT_SCHEDULE_SRV (1)

For more information about activating OData services, see Set Up SAP Fiori Apps for SAP Replenishment
Planning [page 287] under Activate Application-Specific OData Services for SAP Replenishment Planning.

Front-End Server: Activate SAPUI5 Application

Component Technical Name

SAP UI5 Application PROCSCHEDEMAN

For more information about how to activate the ICF service, see Set Up SAP Fiori Apps for SAP Replenishment
Planning [page 287] under Activate ICF Services.

Front-End Server: Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps
that have been assigned by an administrator to the catalog designed for this user's role. For more information,
see Set Up SAP Fiori Apps for SAP Replenishment Planning [page 287] under Enable the Apps for SAP Fiori
Launchpad.

SAP delivers technical catalogs for groups of SAP Fiori apps as repositories to create your own catalogs in the
launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app.

Front End Server: Catalog Details

Component Technical Name

Technical Catalog SAP_XRP_TC_REPL

Business Catalog SAP_XRP_BC_REPL

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 299
Component Technical Name

Business Group SAP_XRP_BCG_REPL_CONFIG

Back-End Server: Set Up Authorizations

On the back-end server, set up the authorizations for SAP Replenishment Planning as described in Set Up
Back-End Roles and Authorizations [page 310]. For the Manage Procurement Schedules app, the following
authorization objects are relevant:

Authorization Object
Authorization Object Description Field Value Field Description

/DMF/MPSCH
Authorization to dis­ Display Activity

play and change pro­

Change
curement schedules by
using the Manage
Procurement
Schedules app.

6.6.5.6 App Implementation: Manage Shelf Cost Profiles

 Tip

You can also find the data required to implement the Manage Shelf Cost Profiles app in the SAP Fiori apps
reference library at https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html#?
appId=F4476.

System Landscape Requirements

For information about the system requirements, see Implement the Prerequisites.

Implementation Tasks

The following section lists tasks that have to be performed to implement this app. The tables contain the app-
specific data required for these tasks.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
300 PUBLIC Set Up the Applications
Front-End Server: Activate OData Services

Component Technical Name

OData Service (Version Number) /DMF/PRFL_SHLFCAP_VIOLTN_PARAM_SRV (1)

For more information about activating OData services, see Set Up SAP Fiori Apps for SAP Replenishment
Planning [page 287] under SAP Replenishment Planning.

Front-End Server: Activate SAPUI5 Application

Component Technical Name

SAP UI5 Application PRFLSHLFCAPMAN

For more information about how to activate the ICF service, see Set Up SAP Fiori Apps for SAP Replenishment
Planning [page 287].

Front-End Server: Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps
that have been assigned by an administrator to the catalog designed for this user's role. For more information,
see Set Up SAP Fiori Apps for SAP Replenishment Planning [page 287] under Enable the Apps for SAP Fiori
Launchpad.

SAP delivers technical catalogs for groups of SAP Fiori apps as repositories to create your own catalogs in the
launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app.

Front End Server: Catalog Details

Component Technical Name

Technical Catalog SAP_XRP_TC_REPL

Business Catalog SAP_XRP_BC_REPL

Business Group SAP_XRP_BCG_REPL_CONFIG

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 301
Back-End Server: Set Up Authorizations

On the back-end server, set up the authorizations for SAP Replenishment Planning as described in Set Up
Back-End Roles and Authorizations [page 310]. For the Manage Shelf Cost Profiles under app, the following
authorization objects are relevant:

Authorization Object
Authorization Object Description Field Value Field Description

/DMF/PRFLM
Authorization to dis­ ACTVT Display Activity

play and change shelf

Change
cost profiles by using
the Manage Shelf Cost
Profiles app.

6.6.5.7 App Implementation: Review Order Plan Items

 Tip

You can also find the data required to implement the Review Order Plan Items app in the SAP Fiori apps
reference library at https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?
appId=F4235.

Prerequisites

Before implementing the app, you must ensure the following:

● You have installed the UDF reuse component (SAP UI5 Application UDFREUSE and OData service /DMF/
DEMAND_PLAN_UTILITIES). For information, see Set Up the UDF Reuse Component [page 291].
● You have implemented the Analyze Forecast app as the target for the navigation from the Review Order Plan
Items app (with this, the reuse component is already installed). For information about how to set up the
Analyze Forecast app, see Set Up the Analyze Forecast App and follow the instructions.

System Landscape Requirements

For information about the system requirements, see Implement the Prerequisites.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
302 PUBLIC Set Up the Applications
Implementation Tasks

The following sections list tasks that have to be performed to implement this app. The tables contain the app-
specific data required for these tasks.

Front-End Server: Activate OData Services

Component Technical Name

OData Service (Version Number) /XRP/REVIEW_ORDER_PLAN_ITEMS (1)

For more information about activating OData services, see Set Up SAP Fiori Apps for SAP Replenishment
Planning [page 287] under Activate Application-Specific OData Services for SAP Replenishment Planning.

Front-End Server: Activate SAPUI5 Application

Component Technical Name

REVIEW_OPI
SAPUI5 Application

For more information about how to activate the ICF service, see Set Up SAP Fiori Apps for SAP Replenishment
Planning [page 287] under Activate ICF Services.

Front-End Server: Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps
that have been assigned by an administrator to the catalog designed for this user's role. For more information,
see Set Up SAP Fiori Apps for SAP Replenishment Planning [page 287] under Enable the Apps for SAP Fiori
Launchpad.

SAP delivers technical catalogs for groups of SAP Fiori apps as repositories to create your own catalogs in the
launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app.

Front End Server: Catalog Details

Component Technical Name

Technical Catalog SAP_XRP_TC_REPL (Replenishment Planning)

Business Catalog SAP_XRP_BC_REPL (Replenishment Planning)

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 303
Component Technical Name

Business Group SAP_XRP_BCG_REPL_PLANNING (Replenishment Planning)

Back-End Server: Set Up Authorizations

On the back-end server, set up the authorizations for SAP Replenishment Planning as described in Set Up
Back-End Roles and Authorizations [page 310]. For the Review Order Plan Items app, the following
authorization objects are relevant:

Authorization Object Authorization Object Field Value Field Description

Description

/DMF/DPL
Authorization to: ACTVT Execute Activity

● Use the product

and product hier­
archy filters and
the location and
location hierarchy
filters in the
Review Order Plan
Items app.
● Create forecast
corrections in the
Adjust Forecast
app.
● Create demand in­
fluencing factors
assignments in
the Manage
Demand
Influencing
Factors app.

/XRP/ROPI
Authorization to dis­ ACTVT Display Activity

play and change order

Change
plan items by using the
Review Order Plan
Items app.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
304 PUBLIC Set Up the Applications
6.6.5.8 App Implementation: Simulate Replenishment

 Tip

You can also find the data required to implement the Simulate Replenishment app in the SAP Fiori apps
reference library at https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?
appId=F4396.

Prerequisites

Before implementing the app, you must ensure the following:

● You have installed the UDF reuse component (SAP UI5 Application UDFREUSE and OData service /DMF/
DEMAND_PLAN_UTILITIES). For information, see Set Up the UDF Reuse Component [page 291].

System Landscape Requirements

For information about the system requirements, see Implement the Prerequisites.

Implementation Tasks

The following sections list tasks that have to be performed to implement this app. The tables contain the app-
specific data required for these tasks.

Front-End Server: Activate OData Services

Component Technical Name

OData Service (Version Number) /XRP/OD_REPLNMT_COST_SIMLN_SRV (1)

OData Service (Version Number) /DMF/DEMAND_PLAN_UTILITIES_SRV (1)

For more information about activating OData services, see Set Up SAP Fiori Apps for SAP Replenishment
Planning [page 287] under Activate Application-Specific OData Services for SAP Replenishment Planning.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 305
Front-End Server: Activate SAPUI5 Application

Component Technical Name

SAPUI5 Application retail.xrp.simulation

For more information about how to activate the ICF service, see Set Up SAP Fiori Apps for SAP Replenishment
Planning [page 287] under Activate ICF Services.

Front-End Server: Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps
that have been assigned by an administrator to the catalog designed for this user's role. For more information,
see Set Up SAP Fiori Apps for SAP Replenishment Planning [page 287] under Enable the Apps for SAP Fiori
Launchpad.

SAP delivers technical catalogs for groups of SAP Fiori apps as repositories to create your own catalogs in the
launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app.

Front End Server: Catalog Details

Component Technical Name

Technical Catalog SAP_XRP_TC_REPL (Replenishment Planning)

Business Catalog SAP_XRP_BC_REPL (Replenishment Planning)

Business Group SAP_XRP_BCG_SIMULATION (Replenishment Simulation)

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
306 PUBLIC Set Up the Applications
Back-End Server: Set Up Authorizations

On the back-end server, set up the authorizations for SAP Replenishment Planning as described in Set Up
Back-End Roles and Authorizations [page 310]. For the Simulate Replenishment app, the following
authorization objects are relevant:

Authorization Object Authorization Object Field Value Field Description

Description

/DMF/DPL Authorization to per­ ACTVT Execute Activity

form several actions in
different SAP Fiori
apps. For more infor­
mation, see Set Up
Back-End Roles and
Authorizations [page
310].

/XRP/SIM Authorization to exe­ ACTVT Execute Activity

cute the Simulate Re­
plenishment app and
the replenishment sim­
ulation with re­
port /XRP/
REPLENISHMENT_SIM.

6.6.5.9 App Implementation: Manage Alerts

 Tip

You can also find the data required to implement the Manage Alerts app in the SAP Fiori apps reference
library at https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html#?appId=F5163.

Prerequisites

Before implementing the app, you must ensure the following:

● You have installed the UDF reuse component (SAP UI5 Application UDFREUSE and OData service
/DMF/DEMAND_PLAN_UTILITIES). For information see Set Up the UDF Reuse Component [page 291].

System Landscape Requirements

For information about the system requirements, see Implement the Prerequisites.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 307
Implementation Tasks

The following section lists tasks that have to be performed to implement this app. The tables contain the app-
specific data required for these tasks.

Front-End Server: Activate OData Services

Component Technical Name

OData Service (Version Number) /DMF/MANAGE_RTLPLNG_ALERTS_SRV (1)

Re-Use Component Technical Name

OData Service (Version Number) APS_CHANGE_DOCUMENTS_SRV (1)

For more information about activating OData services, see Set Up SAP Fiori Apps for SAP Replenishment
Planning [page 287] under Activate Application-Specific OData Services for SAP Replenishment Planning.

Front-End Server: Activate SAPUI5 Application

Component Technical Name

SAP UI5 Application Rtlplngalrtman

For more information about how to activate the ICF service, see Set Up SAP Fiori Apps for SAP Replenishment
Planning [page 287] under Activate ICF Services.

Front-End Server: Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps
that have been assigned by an administrator to the catalog designed for this user's role. For more information,
see Set Up SAP Fiori Apps for SAP Replenishment Planning [page 287] under Enable the Apps for SAP Fiori
Launchpad.

SAP delivers technical catalogs for groups of SAP Fiori apps as repositories to create your own catalogs in the
launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
308 PUBLIC Set Up the Applications
Front End Server: Catalog Details

Component Technical Name

Technical Catalog SAP_XRP_TC_REPL

Business Catalog SAP_XRP_BC_REPL

Business Group SAP_XRP_BCG_ALERT_MANAGEMENT

Back-End Server: Set Up Authorizations

On the back-end server, set up the authorizations for SAP Replenishment Planning as described in Set Up
Back-End Roles and Authorizations [page 310]. For the Manage Alerts app, the following authorization objects
are relevant:

Authorization Object
Authorization Object Description Field Value Field Description

/DMF/MNGAT
Authorization to dis­ ACTVT Display Activity

play and change alert

Maintain
status by using the
Manage Alerts app.

6.6.6 Set Up Database Roles and Authorizations

In SAP HANA studio, grant the AFL__SYS_AFL_XRP_EXECUTE role to the SAPHANADB user. This short
procedure is mandatory for the successful execution of SAP Replenishment Planning.

 Note

In this guide, SAPHANADB is used as a variable. Replace it with the name of the database user or database
schema in your ABAP back-end system. You might also come across documentation or user interfaces that
use SAPHANADB. Both variables mean the same.

For more information and an example, see the Important Variables in section Naming Conventions [page 6].

For more information about database users and schemas, see SAP Note 2535951 (FAQ: SAP HANA
Users and Schemas).

Context

The AFL__SYS_AFL_XRP_EXECUTE role enables the SAPHANADB user to call the XRP application function
library (part of the SAP XRP AFL component) in the SAP HANA database.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 309
Prerequisites

● You have installed the SAP XRP AFL component as described in section Download and Install SAP XRP
AFL (Only for SAP Replenishment Planning) [page 71] in this guide.
● You have database administrator rights so that you can grant roles to users.

Procedure

 Tip

● If you encounter issues related to authorization or authentication, see the Security-Related Issues
section of the SAP HANA Troubleshooting and Performance Analysis Guide, which you can find under
https://help.sap.com/viewer/p/SAP_HANA_PLATFORM <Version> Administration .
● We have also provided an example SQL statement below that you can adapt as needed for your system
landscape.

1. In SAP HANA studio, access your back-end system and open the SAP HANA Administration Console.
2. Choose Security Users .
3. Select your SAPHANADB user and open the user details (or double-click the user).
4. On the Granted Roles tab, choose the plus icon and select AFL__SYS_AFL_XRP_EXECUTE as the role
name.
SQL example: grant AFL__SYS_AFL_XRP_EXECUTE to SAPHANADB;
5. Save your changes by choosing the Deploy (F8) icon at the top right.

Result

You have successfully set up the authorizations for SAP Replenishment Planning.

6.6.7 Set Up Back-End Roles and Authorizations

To access the relevant Customizing activities and core SAP Replenishment Planning application functionality,
you must have a user on the ABAP back-end server.

Create roles with the suitable authorization objects according to your demand and based on the segregation of
duties. Then assign the roles to the users depending on their tasks.

Example

Users who are responsible for the parameter maintenance receive a role that contains only the authorization
object for the parameter maintenance. Users who are responsible for running the operative replenishment

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
310 PUBLIC Set Up the Applications
process receive a role that contains only the authorization objects for executing the replenishment calculation
and transferring order plan items.

Standard Authorization Objects

The following table shows the security-relevant authorization objects that are used by SAP Replenishment
Planning.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 311
Authorization Object Authorization Object Field Value Field Description
Description

Authorization to do the ACTVT Execute Activity

/DMF/DPL

following:

● Create forecast
corrections in the
Adjust Forecast
app.
● Create demand in­
fluencing factors
assignments in
the Manage
Demand
Influencing
Factors app.
● Filter for product
and product hier­
archy in the apps
for demand fore­
casting (Analyze
Forecast, Adjust
Forecast, Manage
Demand
Influencing
Factors) and SAP
Replenishment
Planning (Review
Order Plan Items,
Simulate
Replenishment).
● Filter for location
and location hier­
archy in the apps
for demand fore­
casting (Analyze
Forecast, Adjust
Forecast, Manage
Demand
Influencing
Factors) and SAP
Replenishment
Planning (Review
Order Plan Items,
Simulate
Replenishment).

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
312 PUBLIC Set Up the Applications
 Authorization Object Authorization Object Field Value Field Description
Description

● Use/display the
chart component
consisting of time
series chart, de­
composition chart
and table view in
the apps for de­
mand forecasting
(Analyze Forecast,
Adjust Forecast,
Manage Demand
Influencing
Factors).

/DMF/OPPRG Authorization for purg­ ACTVT Execute Activity

ing order plan items
with report /DMF/
ORDERPLAN_PURGE.

/DMF/PRFLM
Authorization to dis­ ACTVT Display Activity
play and maintain pa­
Maintain
rameter profiles by us­
ing the Manage Cost
profiles, Manage
Constraint Profiles and
Manage Shelf Cost
Profiles apps.

/DMF/MPSCH
Authorization to dis­ ACTVT Display Activity
play and maintain pro­
Maintain
curement schedules by
using the Manage
Procurement
Schedules app.

/DMF/MCASG
Authorization to dis­ ACTVT Display Activity
play and maintain con­
Maintain
figuration assignments
by using the Manage
Configuration
Assignments app.

/DMF/MNGAT
Authorization to dis­ ACTVT Display Activity
play and review alerts
Maintain
by using the Manage
Alerts app.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 313
Authorization Object Authorization Object Field Value Field Description
Description

/DMF/ALERT
Authorization for gen­ ACTVT Add Activity
erating alerts with re­
Create
port /DMF/
GENERATE_ALERTS

/DMF/PRGAT
Authorization for purg­ ACTVT Delete Activity
ing alerts with re­
port /DMF/
PURGE_ALERTS

/XRP/OPOUT Authorization to trans­ ACTVT Execute Activity

fer order plan items
into an ERP system
with report /XRP/
ORDERPLAN_OUTBOUN
D.

/XRP/OPUST Authorization to adapt ACTVT Execute Activity

the status of order plan
items with re­
port /XRP/
ORDERPLAN_ADAPT_S
TATUS.

/XRP/PASGN Authorization to main­ ACTVT Execute Activity

tain parameter assign­
ments with re­
port /XRP/
PARAM_ASSIGNMENT.

/XRP/REPL Authorization to exe­ ACTVT Execute Activity

cute the replenishment
calculation with re­
port /XRP/
REPLENISHMENT_CAL
C.

/XRP/ROPI Authorization to dis­ ACTVT Display Activity

play and change order
Change
plan items by using the
Review Order Plan
Items app.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
314 PUBLIC Set Up the Applications
 Authorization Object Authorization Object Field Value Field Description
Description

/XRP/SIM Authorization to exe­ ACTVT Execute Activity

cute the Simulate
Replenishment app
and the replenishment
simulation with re­
port /XRP/
REPLENISHMENT_SIM.

6.6.8 Set Up Authorizations for Transfer of Order Plan Items

to Source Master Data System

To transfer order plan items from SAP Customer Activity Repository to SAP ERP or SAP S/4HANA the user
needs a role with authorization objects in the source master data system.

The following authorization objects are required to transfer order plan items to the source master data system:

Authorization Object Authorization Object Field Value Field Description

Description

M_BEST_BSA Document Type in Or­ ACTVT ● Create or gener­ Activity

der ate
● Change
● Display change
documents
● Display prices

BSART Type of purchasing Purchasing document

document to be cre­ type
ated. The type can be
NB (Standard pur­
chase order), UB
(Stock transport or­
der), or customized.

M_BEST_EKG Purchasing Group in ACTVT ● Create or gener­ Activity

Purchase Order ate
● Change
● Display change
documents
● Display prices

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 315
Authorization Object Authorization Object Field Value Field Description
Description

EKGRP Purchasing group for Purchasing group

which purchase orders
may be processed

M_BEST_EKO Purchasing Organiza­ ACTVT ● Create or gener­ Activity

tion in Purchase Order ate
● Change
● Display change
documents
● Display prices

EKORG Purchase organization Purchasing organiza­

for which purchase or­ tion
ders may be processed

M_BEST_WRK Plant (location) in Pur­ ACTVT ● Create or gener­ Activity

chase Order ate
● Change
● Display change
documents
● Display prices

WERKS Plants (locations) for Plant (location)

which purchase orders
may be processed

6.6.9 Perform Configuration Steps in SAP Customer Activity

Repository

The following configuration steps in SAP Customer Activity Repository that are required for the operation of
SAP Replenishment Planning should have been already done during the configuration of SAP Customer
Activity Repository.

You find detailed information about these configuration steps in the following sections of the SAP Customer
Activity Repository Administration Guide as follows:

● Enabling Demand Data Foundation and Creating Demand Forecast

You must enable Demand Data Foundation (DDF) to support planning, analysis, and forecasting in
consuming applications of SAP Customer Activity Repository and to create a demand forecast with Unified
Demand Forecast (UDF).
● Configure Demand Data Foundation (DDF)
Set up and enable the DDF module in SAP Customer Activity Repository for creating demand forecasts
with Unified Demand Forecast (UDF) and supporting the consuming applications.
● Set Up and Configure DDF Services

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
316 PUBLIC Set Up the Applications
 Set up and configure services that the Demand Data Foundation module in SAP Customer Activity
Repository provides for different scenarios and consuming applications.
● Configure Unified Demand Forecast (UDF)
Configure the UDF module in SAP Customer Activity Repository to adjust demand modeling and
forecasting for your scenario. You can select from multiple UDF features, optimize performance for your
scenario, and configure parameters for modeling and for forecasting. Additionally, you can set up the
demand planning apps.

6.6.10 Configure SAP Replenishment Planning

To customize automated replenishment processes in SAP Replenishment Planning according to your business
needs, set up Customizing activities and use BAdIs.

SAP Replenishment Planning is a consuming application of the Demand Data Foundation module. Therefore, to
set up SAP Replenishment Planning, in addition to make application-specific settings, you also need to make
settings in Customizing in transaction SPRO under Cross-Application Components Demand Data
Foundation . The DDF Customizing activities that are mandatory for SAP Replenishment Planning can be
found in Customizing for Replenishment Planning. Which additional DDF Customizing activities are relevant for
SAP Replenishment Planning can be found in the organizational activities in Customizing for Replenishment
Planning.

 Note

Depending on your existing settings and your business requirements, you might not need to make settings
for all activities; however, we recommend that you check all relevant DDF settings during the initial setup of
SAP Replenishment Planning.

 Note

For alert statuses, you need to ensure that the data from client 000 is cascaded to other relevant clients.

Use the following Customizing activities and Business Add-Ins in transaction SPRO under Cross-Application
Components Replenishment Planning to set up and customize SAP Replenishment Planning:

Mandatory Customizing Activities

Basic Settings
● Maintain Number Range for Replenishment Run ID
Use this Customizing activity to maintain the number range for the replenishment run ID
● Maintain RFC Mapping
With this Customizing activity, you specify an RFC destination for each master data system to which you
want to transfer order plan items for purchase order creation.
● Define Replenishment Types Relevant for Replenishment Planning
With this Customizing activity, you define whether a product location is considered in replenishment
planning by defining replenishment types relevant for replenishment planning.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 317
Optional Customizing Activities and Business Add-Ins

Source of Supply Determination

 Note

If you want internal sources of supply to be considered in the source of supply determination, you need to
include Supplying Site transportation lanes in the transfer of transportation lanes from the ERP source
system to SAP Customer Activity Repository. You can access the relevant Customizing activity in the ERP
system in transaction SPRO under Logistics General Merchandise Lifecycle Optimization Outbound
Handling of Control Parameters Maintain Control Parameters for Source of Supply .

● Define Client-Specific Settings for Source of Supply Determination

With this Customizing activity, you can activate an optional listing check for a product at a receiving
location. If the listing check is activated, the listing is considered as ranking criterion for the selection of the
preferred source of supply.
● BAdI: Determination of Valid Transportation Lanes
You can use this BAdI to implement your own logic for identifying valid transportation lanes during source
of supply determination.
● BAdI: Adaptation of Valid Transportation Lanes
You can use this BAdI to implement your own logic to add new valid transportation lanes and to change or
remove existing transportation lanes during source of supply determination.
● BAdI: Selection of Preferred Transportation Lanes
You can use this BAdI to implement your own logic for selecting preferred transportation lanes during
source of supply determination.

Scheduling
● BAdI: Adaptation of Replenishment Schedule
You can use this BAdI to adapt the replenishment schedule that was calculated by the system.
● BAdI: Deactivation of Listing Check for Schedule Items
You can use this BAdI to deactivate the listing check on procurement schedule items that are used as a
basis for calculating replenishment schedules.

Open Goods Movements

● BAdI: Adaptation of Open Goods Movements Based on Order Plan
You can use this BAdI to adapt open goods movements that have been derived from order plan items.
● BAdI: Adaptation of Open Goods Movements Based on Purchase Orders
You can use this BAdI to adapt open goods movements that have been derived from purchase orders.

Order Plan Processing

● Define Change Reasons for Order Plan Items
With this Customizing activity, you can define reasons for manual changes of order plan items.
● Configure Order Plan Item Change History
With this Customizing activity, you can enable and configure the order plan item change history.
● BAdI: Selection of Order Plan Items
You can use this BAdI to implement your own logic to select order plan items for the order plan outbound
processing.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
318 PUBLIC Set Up the Applications
 ● BAdI: Adaptation of Order Plan Items
You can use this BAdI to implement your own logic to add new order plan items and to change or remove
existing order plan items for the order plan outbound processing.

Alert and Exception Management

● Define Alert Statuses

With this Customizing activity, you can define alert statuses for the Manage Alerts app.

 Note

If you want to add several custom statuses based on your scenario, you must define them using this
Customizing activity. For more information on how to access this Customizing, see the SAP
Replenishment Planning application help and search for Alert Management.

● Maintain Configuration Data for High Level Exceptions

With this Customizing activity, you can change configuration settings for exceptions. For more information,
see Configure Exception Management [page 320].

6.6.11 Define the Parameterization Profiles and the

Assignment

This section provides an overview of the configuration steps for creating configuration objects and
assignments that are valid for every product location that is supposed to be processed by the replenishment
calculation.

The configuration objects comprise single control parameters, groups of parameters (so-called profiles), as
well as other structured objects (such as an entire procurement schedule). For a comprehensive list of the
configuration objects, see the subsection Replenishment Configuration in the Application Help for SAP
Replenishment Planning at https://help.sap.com/viewer/product/CARAB/latest/en-US?task=use_task.

Prerequisites

1. You have set up the authorizations for SAP Replenishment Planning as described in Set Up Back-End Roles
and Authorizations [page 310].
2. You are familiar with the configuration concept, especially with the various configuration objects and the
ways to assign them to product locations. For information about the configuration concept, see subsection
Replenishment Configuration in the Application Help for SAP Replenishment Planning.
3. You are familiar with the various use cases. The configuration hints therein will help you to find the right
parameterization matching to your specific business requirements. As an entry point, you can use the use
case Use Basic Cost-Optimized Ordering and refine your configuration with further use cases. For
information about the use cases, see subsection Use Cases in the Application Help for SAP Replenishment
Planning.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 319
Create and Assign Configuration Objects

1. Create or import procurement schedules. For more information about the maintenance of the
procurement schedules using an app, see the section Manage Procurement Schedules in the application
help. For more information about importing procurement schedules from another system (inbound
processing of procurement schedules), see the documentation of the function module /DMF/
MDIF_PRCSCHD_INBOUND in the system.
2. Configure the parameters in profiles according to your business requirements. For more information about
the configuration of the parameters using apps, see the following sections in the application help:
○ Manage Cost Profiles
○ Manage Shelf Cost Profiles
○ Manage Constraint Profiles
3. You can assign configuration objects to the product locations based on product hierarchy nodes and
location hierarchy nodes. For uniqueness and unambiguity, these assignments can only use hierarchy
nodes from one product hierarchy and one location hierarchy. In turn, these hierarchies must contain all
the nodes relevant for assignments. You have to select these hierarchies prior to creating assignments.
To select these hierarchies, use the transaction /DMF/CONFIGHIER_SET in your ABAP back-end system
according to the following steps:
○ You can access the Define Hierarchies for Configuration Assignments transaction either in the system
on the SAP Easy Access screen (transaction /DMF/CONFIGHIER_SET) or from the SAP Fiori
Launchpad ( Define Hierarchies Configuration Assignments) tile.
○ Ensure that one record exists for each connected master data system which hosts product locations
that are subject to SAP Replenishment Planning. Within these records, specify the product and
location hierarchies that should be used for assignments of configuration objects to product locations
originating from the respective master data system.
4. Assign the parameters and profiles to the product locations. We recommend that you assign them on
global level initially so that they are valid for all product locations without corresponding parameter or
profile assignments on any lower level. Depending on your business requirements, you can create more
specific assignments. For more information, see section Manage Configuration Assignments in the
application help.
5. Assign procurement schedules to product locations depending on your business requirements. Common
procurement schedules are usually applicable for groups of product locations based on special
characteristics. You have to create the assignments accordingly. If, for example, all products in a location
which share the same scheduling group should share the same procurement schedule, you would have to
create assignments specifying the procurement schedule on the assignment level Location, with specific
conditions based on the Scheduling Group attribute. Unlike for the parameters, it is rather unusual that
there is one procurement schedule which can be assigned on global level as a fallback. For more
information, see section Manage Configuration Assignments in the application help.

6.6.12 Configure Exception Management

Standard settings for exception management are delivered so that nothing is missing from a functional point of
view. This includes that all exceptions specific for SAP Replenishment Planning are switched on. If necessary,
you can then adjust the settings to meet the needs of your specific business processes.

We recommend that you check especially the settings for high-level exceptions.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
320 PUBLIC Set Up the Applications
Settings for High-Level exceptions

You can change the settings for high-level exceptions using the Customizing activity Maintain Configuration
Data for High Level Exceptions in Customizing for Cross-Application Components under Replenishment
Planning Alert and Exception Management .

We recommend that you check especially the following settings:

Assignment to Business Areas

Exceptions that might occur during the replenishment calculation or the order plan transfer are assigned to
one or two of the following business areas by default:

● 61 Replenishment Order Plan Transfer

● 62 Replenishment Review Order Plan Items
● 63 Replenishment Calculation

You can change the assignments according to your needs. Further business areas are relevant for SAP
Replenishment Planning. For more information, see the subsection Exception Management of the Application
Help for SAP Replenishment Planning at https://help.sap.com/viewer/product/CARAB/5.latest/en-US?
task=use_task.

Validity Period
You can set the validity period (maximum number of days that an exception object is stored) until the exception
can be deleted by the Purging Exceptions from the Database report. You can access this report in the system on
the SAP Easy Access screen (transaction /DMF/PURGE_EWB_MSG). For more information about purging
exceptions, see subsection Monitor Exceptions in the application help for SAP Customer Activity Repository at
https://help.sap.com/viewer/product/CARAB/latest/en-US?task=use_task.

Priority
You can adjust the priority for each exception. Exceptions that are not relevant are switched off; that is, they are
not generated during runtime.

Relevant DDF settings

We also recommend that you check all relevant DDF settings during the initial setup of SAP Replenishment
Planning.

This includes the following optional settings:

● You can replace standard exception texts by user-defined texts using the Customizing activity Define
Customer-Specific Replacement Messages.
● You can create custom statuses for exception messages using the Customizing activity Define
Customizable Message Status.

For more information about these settings, see the organizational Customizing activity Alert and Exception
Management (DDF) in Customizing for Cross-Application Components under Replenishment Planning Alert
and Exception Management .

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 321
6.6.13 Verify Real-Time Inventory Integration

Check the setup regarding data replication framework (DRF), SAP client(s) in your ABAP back-end system,
tables for replicating data from your source master data system, SAP HANA content with the required options,
and the population of the /POSDW/TLOGUS table.

Ensure that the following steps have been done to enable the use of real-time inventory data (RTI stock) in SAP
Replenishment Planning.

● The data replication framework (DRF, transaction DRFOUT) for replicating master and transactional data is
set up. For more information, see section Complete UDF Setup [page 128] and Configure Data Replication
from SAP ERP and SAP S/4HANA to DDF in the SAP Customer Activity Repository Administration Guide.

 Note

If you activate the real-time inventory determination, make sure that the information about purchase
orders, which are replicated via DRF outbound from SAP ERP or SAP S/4HANA to SAP Customer
Activity Repository, is up to date as well. Only if this information about purchase orders is up to date,
the current state of purchase orders that are considered as open goods movements in the
replenishment calculation is in sync with the stock information. If the stock and the open goods
movements are not in sync, the stock might be considered as too high.

● One or more SAP clients in your ABAP back-end system have been set up and the mapping for the client of
each source master data system to a client in your ABAP back-end system is configured. For more
information, see section Verify SAP Client Setup [page 76].
● Creation of tables in SAP Customer Activity Repository that are required for replicating data from your
source master data system: For more information, see Create/Replicate Source Master Data System
Tables [page 88].
● The SAP HANA content for SAP Customer Activity Repository and Demand Data Foundation (DDF) is
activated with the options that are listed in section Activate SAP HANA Content [page 92].
● The /POSDW/TLOGUS table must be continuously populated with unprocessed POS sales transactions. For
more information, see the following sections in the application help for SAP Customer Activity Repository:
○ Procedure for populating the /POSDW/TLOGUS table: section Creating Worklists for POS Transactions.
○ Background information about the access to the /POSDW/TLOGUS table with the inventory visibility
view (InventoryVisibilityCurrentStock): section Inventory Visibility.

You can activate the use of real-time inventory with the Real-Time Inventory Status parameter in the Manage
Configuration Assignments app.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
322 PUBLIC Set Up the Applications
6.7 Configure Access to Documentation Provided on SAP
Help Portal (Optional for All Applications)

In transaction SR13, you can configure your back-end system to access the documentation for your application
on SAP Help Portal.

Context

You can configure your back-end system to access the documentation that is provided on SAP Help Portal for
SAP Customer Activity Repository applications bundle at https://help.sap.com/viewer/p/CARAB. For example,
if your application is SAP Customer Activity Repository, you can configure access to the application help for
SAP Customer Activity Repository.

Prerequisites

● The documentation you want to access must be available on SAP Help Portal.
● The users who access the documentation must have access to the Internet.
● You can configure an ABAP system to connect to only one combination of product and version. These are
the values that you will specify under Path in the procedure below.

 Note

The product CARAB is valid for all the applications delivered with SAP Customer Activity Repository
applications bundle.

The version depends on the release. For example, version 5.0 is valid for all the application versions
delivered with SAP Customer Activity Repository applications bundle 5.0.

If these prerequisites cannot all be fulfilled, you must install the documentation in your local system landscape
using the download packages or DVDs/CDs provided.

 Note

For more information about installing the documentation in your local system landscape, see the User
Guides for System Provisioning with Software Provisioning Manager - SAP Library. Select your operating
system and following the instructions.

Procedure

1. Open transaction SR13.

2. Select the tab PlainHtmlHttp.
3. Choose New Entries.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 323
  Caution

When selecting an Area, you must create entries for Documentation and for XML Documentation, for
each platform you are using and each language in which you want to provide documentation.

4. To create entries for the Documentation area, enter the following values:

Name Value to be entered

Variant Enter a name for the variant.

Platform Select the platform relevant for your implementation from

the list of available platforms (for example, WN32).

Area Select Documentation from the list; this will display as

IWBHELP in the table.

Server Names https://help.sap.com/http.svc/ahp2

Path (<Product/Version>) CARAB/5.0

 Note
Make sure to enter the exact combination of upper­
case and lowercase characters.

Language Select the language you need from the list.

5. To create entries for the XML Documentation area, enter the following values:

Name Value to be entered

Variant Enter a name for the variant.

Platform Select the platform relevant for your implementation from

the list of available platforms (for example, WN32).

Area Select XML Documentation from the list; this will display
as XML_DOCU in the table.

Server Names https://help.sap.com/http.svc/ahp2

Path (<Product/Version>) CARAB/5.0

 Note
Make sure to enter the exact combination of upper­
case and lowercase characters.

Language Select the language you need from the list.

6. Repeat steps 4 and 5 for each relevant platform and language.

7. Select one entry as the default language for each platform and area.
8. Save your entries.

Results

You have configured your back-end system to point to documentation that is provided on SAP Help Portal.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
324 PUBLIC Set Up the Applications
Related Information

SAP Note 2149786 Customizing help settings in transaction SR13

SAP Note 2652009 Connecting the help to the SAP Help Portal
SAP Note 2572047 SAP provides user assistance (documentation) as HTML, PDF, or directly via SAP Help
Portal

6.8 Enable In-App Help (Web Assistant)

In-app help is available for several SAP Fiori apps of SAP Customer Activity Repository applications bundle. To
enable the in-app help, you need to make it available in the SAP Fiori launchpad and to set up the underlying
Web Assistant framework.

Context

After a successful setup, you can see the Help icon (question mark) in the SAP Fiori launchpad and at the top of
each app that supports in-app help. Simply choose this icon to display the in-app help and easily call up a
detailed app description.

 Note

For example, the in-app help is available for the following apps:

● Apps for demand forecasting (Analyze Forecast, Adjust Forecast, Manage Demand Influencing Factors,
Manage Alerts)
● Apps for SAP Replenishment Planning, for example Review Order Plan Items

The in-app help is not available for the SAP Smart Business apps in SAP Customer Activity Repository.

Procedure

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 325
6.8.1 Install and Configure SAP Web Dispatcher

To make in-app help (Web Assistant) available in the SAP Fiori launchpad, install and configure SAP Web
Dispatcher.

Installation

Install the latest SAP Web Dispatcher version as the reverse proxy. For more information, see SAP Fiori
Implementation Information and search for section Installing SAP Web Dispatcher.

Configuration

1. Adjust the SAP Web Dispatcher profile file.

In the sapwebdisp_pf.txt file, add the following parameters:
○ For the User Assistance Content Platform:
wdisp/system_<number> = SID=<SID1>, EXTSRV=https://cp.hana.ondemand.com:443,
SRCURL=/sap/dfa/help/, SRCSRV=*:*, PROXY=<your proxy>:<your proxy port>,
STANDARD_COOKIE_FILTER=OFF
○ For the script server in your production system:
wdisp/system_<number> = SID=<SID2>, EXTSRV=https://xray.hana.ondemand.com:
443, SRCURL=/resources/sap/dfa/help/, SRCSRV=*:*, PROXY=<your proxy>:<your
proxy port>, STANDARD_COOKIE_FILTER=OFF

 Note

○ Make sure that the numbers following wdisp/system_ are smaller than the numbers that you use
for all your application server. The rules for the context-sensitive user assistance need to come
before the rules for the application servers.
○ Make sure that the SIDs are not the same as your system IDs.

2. Activate the usage of the modification handler:

icm/HTTP/mod_0 = PREFIX=/, FILE=$(DIR_PROFILE)/redirect.txt
For more information about the profile parameter, see SAP Help Portal at ABAP Platform under
Application Server ABAP - Infrastructure Components of Application Server ABAP SAP Web
Dispatcher Administration of the SAP Web Dispatcher SAP Web Dispatcher Parameter Reference
icm/HTTP/mod_<xx>: .
3. Adjust the SAP Web Dispatcher redirect file.
In the redirect.txt file, add the following parameters:

# User Assistance Content Platform - rewrite rule

if %{SID} = <SID1>
begin
SetHeader HOST cp.hana.ondemand.com:443
RegRewriteRawUrl ^/sap/dfa/help/(.*) /dps/$1
end
# Script Server - rewrite rule

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
326 PUBLIC Set Up the Applications
 if %{SID} = <SID2>
begin
SetHeader HOST xray.hana.ondemand.com:443
RegRewriteRawUrl ^/resources/sap/dfa/help/(.*) /xRayControls/
resources/sap/dfa/help/$1
end

 Note

Make sure that the SIDs in the redirect.txt file are the same as in the sapwebdisp_cf.txt file.

4. You can check if the content platform is working properly through the proxy connection by accessing:
https://<your server>:<your port>/sap/dfa/help/odata.svc/?$format=json

 Example

If the content platform is connected correctly, you can see the following output on your screen, for
example:

{"d":{"EntitySets":
["Transport","DeliverableForReplication","Tile","Project","Deliverable","Tran
sportHistory","TourIssue","ReplicationTourIssue","Hotspot","Product","Context
"]}}

5. You can check if the help script server is working properly through the proxy connection by accessing:
https://<yourserver>:<yourport>/resources/sap/dfa/help/sap/cfg/
XrayBootstrapHelpConfig.json

 Example

If the help script server is connected correctly, you can see the following output on your screen, for
example:

{
"description":"This configuration registers the Xray bootstrap plug-in",
"modulePaths":{
"sap.dfa.help":"/resources/sap/dfa/help/~201509221536~"
},
"bootstrapPlugins":{
"BootstrapXrayPlugin":{

"module":"sap.dfa.help.utils.adapters.fiori.BootstrapXrayHelpPlugin"
}
}
}

Result

The in-app help (Web Assistant) is available in the SAP Fiori launchpad.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 327
6.8.2 Set Up the In-App Help (Web Assistant) Plugin

To make in-app help (Web Assistant) available in the SAP Fiori Launchpad, set up the in-app help plugin in the
relevant front-end systems.

Procedure

1. Log on to your front-end system.

2. Execute transaction /UI2/FLP_CUS_CONF.
3. Under FLP Configuration, click on Change → Display and then on New Entries.
4. In the field FLP Property ID, select or enter ENABLE_HELP.
5. Enter the property value true.
6. Click on Save.
7. Double-click on FLP Plugins.
8. Click on Change → Display and then on New Entries.
9. In the field FLP Plugin ID, select or enter WEB_ASSISTANT_HELP_PLUGIN, and in the field Activity State,
choose Active.
10. Highlight the entry WEB_ASSISTANT_HELP_PLUGIN and double-click on Configuration.
11. Click on New Entries.
12. Enter the following values:

FLP Property ID Property Value

BUTTON_LOCATION head

CAROUSEL_ORIENTATION vertical

DATA_URL_UACP https://help.sap.com/webassistant

EDITOR false

LA_COMMUNITY_URL https://community.sap.com/

LEARNING_APP_BACKEND_URL https://education.hana.ondemand.com/education/

LEARNING_APP_WORKSPACE CARAB

NO_HELP_MODE Carousel

PRODUCT CARAB

RO_MODEL UACP

RW_MODEL WPB

SERVICE_LAYER_VERSION UACP

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
328 PUBLIC Set Up the Applications
 FLP Property ID Property Value

USE_GLOBAL_HELP true

VERSION 5.0

13. Optionally, you can configure that Web Assistant opens immediately when the SAP Fiori launchpad or an
app is opened. To configure this behavior, add the following property:

FLP Property ID Property Value

PARAMETERS openImmediately=full

To open Web Assistant in minimized mode, specify the property value openImmediately=minimized.
Note that this property causes Web Assistant to open for all apps irrespective if Web Assistant content is
available or not.

14. Click on Save.

After you have made these settings, the question mark icon for the in-app help is available for the SAP Fiori
launchpad.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Set Up the Applications PUBLIC 329
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.

Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
330 PUBLIC Important Disclaimers and Legal Information
Common Upgrade Guide for SAP Customer Activity Repository applications bundle 5.0
Important Disclaimers and Legal Information PUBLIC 331
www.sap.com/contactsap

© 2020 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. The information contained herein may be changed
without prior notice.

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 or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP 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.

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. All
other product and service names mentioned are the trademarks of their
respective companies.

Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

THE BEST RUN