Demand Data Foundation (DDF) with Unified Demand ...

Administrator's GuideDocument version: 1.07 – 2015-12-04

Demand Data Foundation (DDF) with Unified Demand Forecast (UDF) on SAP HANASAP Customer Activity Repository 1.0 SP7

CUSTOMER

Document History

CautionBefore you start the implementation, make sure that you have the latest version of this document, which you

can find on SAP Service Marketplace at service.sap.com/instguides Installation & Upgrade GuidesIndustry Solutions Industry Solution Guides SAP for Retail SAP Customer Activity Repository <your release> .

For an overview of the most important document changes, see the following table:

Table 1

Version Date Description

1.07 (SP7) 2015-08-05 Minor text changes to update the guide for the current release.

1.06 (SP 6) 2015-08-05 Revised the entire guide to state more clearly that DDF and UDF are modules in SAP Customer Activity Repository; updated SAP Notes for the Installation section; revised the implementation scenarios under Preparation, Installation, and Post-Installation; updated and moved the Component Version Dependencies section; added Troubleshooting section; revised the Security section; revised the Authorization Requirements for Unified Demand Forecast (UDF) section; added partitioning information for UDF and DDF; revised the Upgrade and Migration section; updated Technical System Landscape; updated Standard Authorization Objects

1.05 (SP 5) 2014-07-23 Updated SAP Notes for the Installation section; updated Information Available on SAP Service Marketplace section; updated Naming Conventions section; updated Component-Specific Monitoring section; updated Preparation section; updated Installation section; updated Post-Installation section; updated required SAP_BS_FND software component version from 746

to 747; added installation information for the UDF AFL in section Install or Upgrade the UDF AFL; did minor updates of the Introduction to Demand Data Foundation (DDF) section; appended the Install the Service-Oriented Architecture (SOA) section with note on changed terminology; updated Component Version Dependencies section; updated About this Document section; updated Technical System Landscape section; updated Fundamental Security Guides section; updated Authorization Requirements for Unified Demand Forecast (UDF) section;

1.04 (SP 4) 2014-07-23 Added reference to SAP Note 2020581 for SP4 (collection note providing support package overview and implementation instructions); added reference to SAP Note 1798895 with manual correction instructions for implementing collection notes; added reference to SAP Note 2016825 on the independent release of the UDF AFL as of SAP HANA SPS 08; added information on how to do the optional upgrade to SAP HANA SPS 08; updated Standard Authorization Objects section; updated Component Version Dependencies section; enhanced description of delivery units for SAP HANA content; revised Upgrade and Migration section

1.03 (SP 3) 2014-05-23 Added reference to SAP Note 1997902 for SP3 (collection note providing support package overview and implementation instructions); updated and added several SAP Note numbers; updated installation information for UDF AFL; specifically added reference to new installation

2

CUSTOMER© Copyright 2015 SAP SE or an SAP affiliate company.All rights reserved.

Demand Data Foundation (DDF) with Unified Demand Forecast (UDF) on SAP HANADocument History

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Finstguides

Version Date Description

procedure for UDF AFL as of SAP HANA SPS 08; updated technical implementation information based on DDF implementation scenarios; appended Introduction to Demand Data Foundation (DDF) section, updated Component Version Dependencies section, updated SAP Solution Manager section, updated Standard Authorization Objects section

1.02 (SP 2) 2014-03-14 Updated technical implementation information; updated upgrade and migration information; updated SAP Note numbers; updated information on activation of SAP HANA content; added information on supported implementation scenarios and related pre- and post-installation tasks; updated privileges assigned to UDF roles; updated installation information for UDF AFL

1.01 (SP 1) 2013-09-23 Added reference to SAP Note for SP1 (collection note) providing support package overview and implementation instructions; adapted schema names and workflow for manual SAP HANA content activation; updated referenced SAP Note for manual SAP HANA content activation; added installation prerequisites and upgrade recommendation; added reference to SAP Note regarding load balancing; added information about maximum number of records for load balancing; updated UDF installation sequence

1.0 2013-06-28 Initial version

Demand Data Foundation (DDF) with Unified Demand Forecast (UDF) on SAP HANADocument History

CUSTOMER© Copyright 2015 SAP SE or an SAP affiliate company.

All rights reserved. 3

Content

1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1 About This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.3 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.4 Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.5 Introduction to Demand Data Foundation (DDF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2 Technical Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.1 Technical System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.2 Product Availability Matrix (PAM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.3 Component Version Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.4 Preparation, Installation, and Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2.5 Partition Tables for UDF and DDF (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3 Upgrade and Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.1 Install or Upgrade the UDF AFL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.2 Migration Scenario "From DMF to DDF and UDF" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

4 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.1 Fundamental Security Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.2 Logging and Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.3 User Administration and Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Integration in Single Sign-On (SSO) Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

4.4 Authorizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Standard Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Standard Authorization Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Authorization Requirements for Unified Demand Forecast (UDF) . . . . . . . . . . . . . . . . . . . . . . . . 44

4.5 Security Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

5 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485.1 Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Alert Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Monitor Installation and Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Component-Specific Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Detailed Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Ensure Data Consistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Manage Demand Data Foundation (DDF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Support Desk Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

5.2 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Troubleshoot UDF and DDF Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

4


Demand Data Foundation (DDF) with Unified Demand Forecast (UDF) on SAP HANAContent

6 Solution-Wide Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596.1 SAP Solution Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596.2 Service-Oriented Architecture (SOA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Service Enablement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Install the Service-Oriented Architecture (SOA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Demand Data Foundation (DDF) with Unified Demand Forecast (UDF) on SAP HANAContent



6

CUSTOMER© Copyright 2015 SAP SE or an SAP affiliate company.All rights reserved. Demand Data Foundation (DDF) with Unified Demand Forecast (UDF) on SAP HANA

1 Getting Started

1.1 About This Document

Purpose

This Administrator's Guide is part of the product documentation for SAP Customer Activity Repository 1.0 SP7.

You can find this documentation on SAP Help Portal at help.sap.com/car SAP Customer Activity Repository 1.0 SP7 .

This Administrator's Guide is your central starting point for installing and implementing the Demand Data Foundation (DDF) and Unified Demand Forecast (UDF) modules of SAP Customer Activity Repository. It complements the Installation Guide, SAP Customer Activity Repository.

This Administrator's Guide gives you a technical overview of DDF and UDF, the software units, and the processes. It helps you design your SAP Customer Activity Repository landscape based on your specific implementation scenario. It also provides you with the information required to install and operate DDF and UDF and refers you to required other documentation.

What are DDF and UDF?

DDF and UDF are modules and part of the SAP Customer Activity Repository technology platform:

● DDF (software component version RTLDDF 100) is a reusable data layer. It includes, for example, a data model, data import infrastructure, reuse frameworks, as well as reuse tools and user interfaces for data maintenance. DDF also stores master data that is required for demand modeling and forecasting with UDF. Note that RTLDDF 100 includes the delivery units with the SAP HANA content for both DDF and UDF.

● UDF provides the demand modeling and demand forecasting services. It includes an application function library (UDF AFL) and runs in the SAP HANA database (a component of the SAP HANA Platform). As of SAP HANA Platform SPS 08 revision 82, the UDF AFL is provided as software component version UDFAFL_INST 100. UDF requires DDF for master data and transactional data. DDF acts as a liaison between the UDF AFL in the SAP HANA database and the consuming application.

DDF and UDF provide their functionality and data through the consuming application installed on top of SAP Customer Activity Repository. For more information about DDF and UDF, see the following sources:

● In this guide: Introduction to Demand Data Foundation (DDF) [page 14]

● Application Help for SAP Customer Activity Repository at help.sap.com/car <your release>Application Help SAP Customer Activity Repository Demand Data Foundation

Main Sections of this Guide

This Administrator's Guide is structured as follows:

● Technical Implementation [page 22]

Important technical information, including an overview of the system landscape, the related software units, as well as instructions for setting up different implementation scenarios.

● Upgrade and Migration [page 34]

Information about upgrading or migrating to this release of SAP Customer Activity Repository with DDF and UDF.

Demand Data Foundation (DDF) with Unified Demand Forecast (UDF) on SAP HANAGetting Started



http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fcar


● Security [page 36]

Security-relevant information when setting up and operating DDF and UDF as part of your SAP Customer Activity Repository solution.

● Operation [page 48]

Information about monitoring, exception handling, and troubleshooting for DDF and UDF.

● Solution-Wide Topics [page 60]

Information about configuration information for DDF and UDF in SAP Solution Manager and an overview of the available service-oriented architecture (SOA).

Constraints

This guide does not provide information about the following:

● Installation or configuration of the SAP NetWeaver Platform.

For more information, see help.sap.com/nw74 Installation and Upgrade Information .

● Installation or configuration of the SAP HANA Platform.

For more information, see help.sap.com/hana_platform Installation and Update .

● Installation, configuration, or integration with any of the SAP Business Suite components.

For more information, see help.sap.com/businesssuite .

More Information

● SAP Help Portal for SAP Customer Activity Repository at help.sap.com/car

● For more information on the corrections introduced by this release, see the SAP Support Portal at

support.sap.com/swdc Software Downloads Support Packages and Patches A-Z Index R SAP RTL CAR SAP RTL CAR 1.0 :

1. Choose Comprised Software Component Versions <your component> Support Packages .

2. In the Downloads section at the bottom, select the hyperlink for this release in the Title column.

3. Follow the on-screen instructions to display the corrections for the component.

● SAP Help Portal for SAP HANA Platform at help.sap.com/hana_platform

1.2 SAP Notes for the Installation

The following list includes SAP Notes that you must read (and, when appropriate, implement) before you start the installation. These SAP Notes contain the most recent information about the installation, as well as corrections to the installation documentation.

NoteMake sure that you have the up-to-date version of each of the following SAP Notes, which you can find on the

SAP Support Portal at support.sap.com/notes .

8



http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fnw74

http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fhana_platform

http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fbusinesssuite


http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fswdc


http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fnotes

Table 2: SAP Notes for Demand Data Foundation (DDF) and Unified Demand Forecast (UDF)

SAP Note Number Title Description

You need to read and, when appropriate, implement the following SAP Notes if your implementation scenario includes the following SAP Customer Activity Repository modules:

● Demand Data Foundation (RTLDDF 100) as the reusable data layer

● Unified Demand Forecast (UDFAFL_INST 100, available as of SAP HANA Platform SPS 08 revision 82), as the

demand modeling and forecasting engine that you install and run in the SAP HANA database

1809841 Release strategy for the ABAP add-on RTLDDF

Information about planning the installation and upgrades of the ABAP add-on RTLDDF.

1809840 Release strategy for the ABAP add-on RTLDMF 200

Information about planning the installation and upgrades of the ABAP add-on RTLDMF 200.

1843898 Release strategy for the ABAP add-on RTLCAR

Release and upgrade information for SAP Customer Activity Repository 1.0.

2020641 Installation-Specific Collection Note Up-to-date information about installing SAP Customer Activity Repository 1.0. Always consult this note to complement the information found in this guide.

1803986 Rules to use SUM or SPAM/SAINT to apply SPs for ABAP stacks

Guidance on which transaction and tool to use when installing support packages.

2145356 Activation of SAP HANA content for DDF and UDF when applying SAP Notes

Information on how you must activate the SAP HANA content for DDF and UDF again after implementing a support package or correction to an existing installation (for example, after applying an SAP Note using transaction SNOTE).

2021789 SAP HANA Revision and Maintenance Strategy

Guidance on which SAP HANA database revision to choose for your scenario. Information about different revision types.

1948334 SAP HANA Database Update Paths for Maintenance Revisions

Guidance on which SAP HANA database revision to choose for your scenario. Information about different revision types.

1914052 NetWeaver 7.40 Database Dependencies

Information about dependencies between SAP NetWeaver releases and SAP HANA Platform releases.

2050229 Release and Upgrade Information for Unified Demand Forecast Application Function Library (UDF AFL)

Overview of all independent releases (revisions) of the UDF AFL as of revision 82 on SAP HANA Platform SPS 08 revision 82; instructions for installing or upgrading the UDF AFL.

NoteThis SAP Note is relevant for you if you want to use a UDF AFL revision 82 or higher, on a SAP HANA Platform SPS 08 revision 82 or higher.




http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2F~form%2Fhandler%3F_APP%3D01100107900000000342%26_EVENT%3DREDIR%26_NNUM%3D1809841%26_NLANG%3Den%26_NVERS%3D0











For more information, see Install or Upgrade the UDF AFL [page 34].

2004952 Migration of UDF AFL and POS AFL from SAP HANA AFL as of SAP HANA 1.0 SP08

Instructions for performing the mandatory one-time migration of the product-specific application function libraries (such as the UDF AFL) when upgrading to SAP HANA Platform SPS 08 or higher.

NoteThis SAP Note is relevant for you if you want to upgrade to a UDF AFL revision 82 or higher, on a SAP HANA Platform SPS 08 revision 82 or higher. Note that this upgrade is not mandatory for this support package of SAP Customer Activity Repository 1.0.

1997526 SAP HANA lifecycle manager with SAP HANA Database SPS 08

Information about SAP HANA tools that you can use for installing the Unified Demand Forecast application function library (UDF AFL).

NoteThis SAP Note is relevant for you if you want to use a UDF AFL revision 82 or higher, on a SAP HANA Platform SPS 08 revision 82 or higher.

1981340 ABAP report to create and activate HANA content objects

Only relevant for the "progressive implementation" scenario of SAP Customer Activity Repository, as described in Post-Installation [page 27]. The SAP Note describes how you activate the SAP HANA content for DDF and UDF for this scenario.

2039745 with referenced related notes (optional)

Collection Note: RTLDDF 1.0 SP05 with UDF on SAP HANA

Overview of support package SP 05 of Demand Data Foundation (DDF) 1.0 with Unified Demand Forecast (UDF) on the SAP HANA database; referenced related notes providing details of the changes made for this support package as well as implementation instructions and prerequisites.






Overview of support package SP 03 of Demand Data Foundation (DDF) 1.0 with Unified Demand

10










Forecast (UDF) on the SAP HANA database; referenced related notes providing details of the changes made for this support package as well as implementation instructions and prerequisites.





Collection Note for RTLDDF 1.0 SP01 with UDF on SAP HANA


1825740 Transfer of Site Hierarchies and Groups to DMF and DDF

Information on how to transfer site hierarchies and site groups from SAP ERP to DDF using the DRF data replication framework (transaction DRFOUT).

1830164 Transfer of ERP Promotions to SAP DMF / SAP DDF

Information on how to transfer promotions from SAP ERP to DDF using the DRF data replication framework (transaction DRFOUT).

1911141 Environment variable for UDF performance optimization

Information about setting UDF-specific performance optimization parameters in the SAP HANA database, including global environment variable OMP_NUM_THREADS.

1898341 Modeling or forecasting fails with failed decomposition

Updated information about configuration changes for demand modeling and forecasting with UDF.

1961352 ERP Promo VDM consumption Information on how you can use ERP promotions as input for demand modeling and forecasting with UDF.

1961815 New view for retail promotions without bonus buy

Information on how you can use ERP promotions for software component RTLPOSDM.

2019909 Alternative package building implementation for sales data

Information on how you can improve performance by configuring the /DMF/SET_STAGING_CONFIG_TABLE report in such

a way that it also processes sales data from the staging tables to the production tables.

2065471 Changes to default control settings for modeling and forecasting

Information on how you can improve modeling and forecasting performance by turning off the















UDF demand decomposition feature in Customizing.

2190377 (optional) Table Partitioning for Unified Demand Forecast and Demand Data Foundation

Recommendations for partitioning data tables when forecasting large numbers of products and locations.

1836357 (optional) Install and Configure the UDF Launchpad

Hardware requirements for the optional visualization tool Unified Demand Forecast Launchpad; installation and configuration instructions.

1798895 (optional) Additional information on manual correction process for ABAP on SAP HANA

Information on how you can implement SAP Notes with manual correction instructions for individual SAP HANA objects.

NoteThis SAP Note is only relevant for you if you need to implement corrections manually.

1.3 Additional Information

The following additional information is available:

Table 3: SAP Help Portal

Information About Path Title

SAP Customer Activity Repository help.sap.com/car SAP Customer Activity Repository <your release>

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

Setting up SAP Solution Manager help.sap.com/solutionmanager

<your release> Installation and

Upgrade Information

Master Guide

Installation Guide

Installing SAP NetWeaver 7.4 help.sap.com/nw74 Installation

and Upgrade Information

Installation Guide

Installing the SAP HANA Platform help.sap.com/hana_platform

Installation and Update

SAP HANA Server Installation and Update Guide

Installing SAP HANA database clients help.sap.com/hana_platform


SAP HANA Client Installation and Update Guide

Installing SAP HANA studio help.sap.com/hana_platform


SAP HANA Studio Installation and Update Guide

12







http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fsolutionmanager

http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fsolutionmanager





Information About Path Title

Using SAP HANA help.sap.com/hana_appliance

System Administration

SAP HANA Administration Guide

For developers: creating comprehensive analytical models, building applications with SAP HANA interfaces, integrated development

help.sap.com/hana_platform

Development and Modeling

SAP HANA Developer Guide

For modelers and business analysts: defining data models for use in SAP HANA

help.sap.com/hana_platform

Development and Modeling

SAP HANA Modeling Guide

Implementing SAP HANA Live for SAP ERP

help.sap.com/hba Installation, Security, Configuration, and Operations

Information

Administrator's Guide

Table 4: General Quick Links

Description Path

SAP Help Portal

SAP Help Portal for SAP Retail

help.sap.com

help.sap.com/retail

SAP Support Portal support.sap.com

SAP Software Download Center support.sap.com/swdc

SAP Notes support.sap.com/notes

Product Availability Matrix support.sap.com/pam

SAP Service Marketplace service.sap.com

Early Knowledge Transfer (formerly referred to as Ramp-Up Knowledge Transfer)

service.sap.com/rkt

Platform and Technology Information Center (released platforms, operating systems)

service.sap.com/platforms

Release Notes service.sap.com/releasenotes

Security service.sap.com/security

Sizing (system sizing, performance, scalability) service.sap.com/sizing

1.4 Naming Conventions

The following naming conventions apply throughout this Administrator's Guide, Demand Data Foundation (DDF) with Unified Demand Forecast (UDF) on SAP HANA:




http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fhana_appliance



http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fhba

http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com

http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fretail

http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com


http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fnotes

http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fpam

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Frkt

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Fplatforms

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Freleasenotes

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Fsecurity

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Fsizing

Table 5

Term Description

consuming application An application that makes use of, or consumes, data stored in SAP Customer Activity Repository using SAP HANA views included in the SAP HANA content for SAP Customer Activity Repository. Note that this includes the DDF and UDF modules and their SAP HANA content.

data replication framework (DRF) A utility for replicating master data required for DDF and UDF implementation scenarios. For use cases and configuration information, see Introduction to Demand Data Foundation (DDF) [page 14]. Note that you can use the DRF in addition to trigger-based SAP Landscape Transformation (SLT) replication to distribute the data from the Master Data Governance (MDG) hub (such as your SAP ERP system) to a target system (such as your SAP Customer Activity Repository system).

Early Knowledge Transfer An element of the SAP Solution Ramp-Up process that delivers early product- and task-related knowledge to experienced SAP or partner consultants in ramp-up projects and to all other roles involved in the ramp-up process (such as sales and customer administrators). Formerly referred to as Ramp-Up Knowledge Transfer.

For more information, see service.sap.com/rkt .

SAP HANA content Packages with SAP HANA views and SQLScript procedures that can be maintained in SAP HANA studio. SAP HANA content is contained in delivery units.

DDF and UDF have dedicated SAP HANA content, which is spread over several delivery units (DUs). Each delivery unit is shipped via an SAP HANA Transport Container (HTC, sometimes referred to as ABAP TLOGO object) in the RTLDDF 100 software component version.

Table 6: Variables

Variable Description

<SAPSID> SAP system ID in uppercase letters

<sapsid> SAP system ID in lowercase letters

<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

1.5 Introduction to Demand Data Foundation (DDF)

DDF is a reusable layer that includes a data model, data import infrastructure, reuse framework (such as exception handling and process controller), and reuse tools (such as data maintenance and scheduling interfaces).

14




DDF also supports the Unified Demand Forecast (UDF) forecasting engine, which has been designed to model historical demand data and forecast future demands.

DDF runs on the SAP HANA database, which stores transactional data and master data. The relational data model allows the consuming applications and UDF to use the data in an easily consumable way.

NoteDDF and UDF are modules and part of the SAP Customer Activity Repository technology platform.

DDF and UDF provide their functionality and data through the consuming application installed on top of SAP Customer Activity Repository.

Implementation

The best implementation approach depends on several factors, such as your system landscape, data integration, and blueprinting decisions. For more information, see the Technical Implementation Information [page 24] section.

Correct data integration is important to support the functions of DDF and UDF. When DDF is set up as the foundation for multiple consuming applications, the impact of this data integration becomes greater.

Integrating Master Data

DDF can receive the following master data:

● Image

● Inventory

● Location (mandatory)

● Location Hierarchy

● Offer

● Product (mandatory)

● Product Hierarchy (mandatory)

● Product Location (mandatory)

● Transportation Lane

● Vendor

● Vendor Fund

For more information about the master data objects, see SAP Help Portal at help.sap.com/car <your release> Application Help SAP Customer Activity Repository Demand Data Foundation Data Management Master Data .

DDF receives the data from the master data system in two steps:

1. DDF receives the master data into intermediate tables called staging tables. No business validations are performed at this point.

2. DDF transfers the master data from the staging tables into the production tables. Business validations are performed.

For more information, see SAP Help Portal for SAP Customer Activity Repository at help.sap.com/car<your release> Application Help SAP Customer Activity Repository Demand Data Foundation Integration Information Inbound Processing .

You have the following options for integrating the master data:

1. SAP ERP-based integration






This option is best suited where the master data system of record is an SAP ERP application. SAP ERP sends master data to DDF using the DRF data replication framework (transaction DRFOUT). The standard implementation of this framework maps the SAP ERP fields to the fields of the DDF staging tables. The DRF allows you to filter the data that you want to send to DDF, based on criteria such as project rollouts or data volumes.

NoteThe standard implementation requires SAP ERP 6.0 with Enhancement Package EHP 5 SP Stack 07 or higher or EHP 6 SP Stack 02 or higher. For more information about SAP ERP releases, see SAP Note

1484460 .

For more information about configuring the DRF, see the following:

○ SAP Help Portal for SAP Customer Activity Repository at help.sap.com/car <your release>Application Help SAP Customer Activity Repository Demand Data Foundation Integration Information Master Data Replication from SAP ERP to Demand Data Foundation

○ Business process Enabling Demand Data Foundation and Creating Demand Forecast in business scenario Customer Activity Repository in SAP Solution Manager (consult the information on the Documentation and Configuration tabs; for access instructions, see SAP Solution Manager [page 59])

○ SAP Help Portal for Master Data Governance at help.sap.com/mdg <your release> Application Help SAP Master Data Governance Working with Master Data Governance Working with SAP MDG, Central Governance General Functions Data Replication

2. Legacy System

You can use this option when the system of record for your master data is not an SAP ERP application (SAP ERP 6.0 with Enhancement Package EHP 5 SP Stack 07 or higher or EHP 6 SP Stack 02 or higher). This option includes any legacy system.

DDF provides inbound interfaces to receive the data into the staging tables. For more information, see

help.sap.com/car <your release> Application Help SAP Customer Activity Repository Demand Data Foundation Integration Information .

Integrating Historical Demand Data

Historical demand data is critical to the demand modeling and forecasting processes provided by Unified Demand Forecast (UDF). To use demand data, modeling data, and forecasting data in a consuming application (for example, to perform analytics in SAP Customer Activity Repository), you must provide the historical demand data through one of the ways described in this document. UDF uses this data to analyze and quantify each of the factors that affected your unit sales in the past to be able to accurately forecast future demand.

As output, UDF provides the SAP HANA view sap.is.ddf.udf.viz/CV_POS_TS with forecast information to its consuming applications.

Recommendation● You should provide 2 years of historical input data to ensure the proper interpretation of seasonality,

trend, and other yearly factors.

● Make sure that your historical data is at daily granularity. Weekly data is currently not supported.

DDF can receive different types of historical demand data, based on the following time series types:

● Point-of-sale (POS) data

● Generic consumption data

16





http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fmdg


● Sales orders

Each time series is completely independent. You can have separate outputs as a result of the modeling and forecasting processes. These outputs allow you to see different demand influencing factors (DIFs) by the different data sources in the same system.

NoteFor more information about the time series explained in the following, see SAP Help Portal at help.sap.com/

car <your release> Application Help SAP Customer Activity Repository Demand Data FoundationData Management Time Series .

Time Series

1. Time series source POS_VDM

This virtual data model accesses POS data provided by SAP Customer Activity Repository as daily aggregated transaction log (TLOG) data. Note that to use this time series, you need to configure the POS Data Transfer and Audit module (software component version RTLPOSDM 200) in SAP Customer Activity

Repository. For more information about this module, see help.sap.com/car <your release>Application Help SAP Customer Activity Repository POS Transaction Management .

RecommendationYou should provide 2 years of historical TLOG data as input for modeling and forecasting.

The modeling and forecasting processes can access the TLOG data through the POS_VDM virtual data model. UDF uses this VDM to consume the sap.is.retail.car/POSAggregatedSalesByArticleLocation SAP HANA view in SAP Customer Activity Repository. The data is aggregated dynamically and in real time to the daily level. Note that in this data, the product, location, sales organization, distribution channel, and order channel must match with the master data that is available in DDF.

For more information about this time series, see help.sap.com/car <your release> Application Help SAP Customer Activity Repository Demand Data Foundation Data Management Time SeriesSAP HANA Content for DDF with UDF .

2. Time series source POS_TS

This time series contains point-of-sale (POS) data persisted in DDF from the POS Inbound Processing Engine (PIPE).

Depending on your implementation strategy, you may choose to use the aggregated POS data available in DDF. Note that you can provide data to DDF from an SAP POS Data Management 1.0 system. Once the TLOG data is available in the RTLPOSDM 200 component of SAP Customer Activity Repository, you can switch to forecasting based on the POS_VDM time series source.

Note○ The POS data persisted in DDF uses offers that were created in SAP Promotion Management for

Retail.

○ You cannot use the ERP Promotion SAP HANA view with this time series. For more information about this view, see the Integration Considerations section below.

The following additional information is available on SAP Help Portal:








Table 7

Information About Path

DDF time series help.sap.com/car <your release> Application

Help SAP Customer Activity Repository Demand Data

Foundation Data Management Time Series

POS transaction management, PIPE, RTLPOSDM help.sap.com/car <your release> Application

Help SAP Customer Activity Repository POS

Transaction Management

Sending data to DDF help.sap.com/car <your release> Application

Help SAP Customer Activity Repository POS

Transaction Management Task Processing Tasks for

Sending Data to Follow-On Applications Sending Data to

DMF-Based Applications

3. Time series source POS_TS

This time series contains point-of-sale (POS) data persisted in DDF from a legacy system and provided using enterprise services (service-oriented architecture, SOA) or the data replication framework (DRF).

You can use this option when you have a legacy system that stores transaction log (TLOG) or POS data and you do not want to persist 2 years of TLOG data in SAP Customer Activity Repository, or you do not yet want to fully implement SAP Customer Activity Repository and do not have SAP POS Data Management 1.0.

During a data integration project, you can determine the best way to capture and push this data into DDF. We recommend that you first perform a one-time push of the historical data. Then you include the latest sales data incrementally. This data is at the product, location, day, and channel level.

To receive the data, DDF uses the Sales (/DMF/BI_SALES_DATA) inbound interface. For more information

about this time series, see help.sap.com/car <your release> Application Help SAP Customer Activity Repository Demand Data Foundation Data Management Time Series Sales .

Note○ You cannot use the ERP Promotion view with this time series. For more information about this SAP

HANA view, see the Integration Considerations section below.

○ You must use the historical promotions from the legacy system to match the historical offers with the POS data that is persisted in DDF.

4. Time series source SO_VDM

This virtual data model accesses sales order data in SAP Customer Activity Repository

You can use this option to model and forecast sales orders (typically from a Web channel or non-brick-and-mortar store). Sales orders are available in SAP ERP. They are also available in SAP Customer Activity Repository (with multichannel information) through the SAP Landscape Transformation (SLT) replication. In this data, the product, location, sales organization, distribution channel, and order channel must match the master data that is available in DDF.

The sales order data can be accessed through the SO_VDM virtual data model. UDF uses this VDM to consume the SAP HANA view sap.is.retail.car/SalesDocumentAggregatedSalesByArticleLocation in the SAP HANA content.

18







For more information about this time series, see help.sap.com/car <your release> Application Help SAP Customer Activity Repository Demand Data Foundation Data Management Time SeriesSAP HANA Content for DDF with UDF .

5. Time series source CONS_TS

This time series contains generic consumption data.

In some cases, generic consumption data may be the only data available to understand the historical demand of a particular product in a particular location. This data can either be purchased from a third party, can be available from a retailer in a legacy system, or can be given from a retailer to a manufacturer (such as with consumer packaged goods or manufacturing scenarios). DDF can receive generic consumption data and use it as input to model and forecast demand.

NoteIf your data does not include information on promotions and offers, you can skip the Integrating Promotions and Offers section.

You have the following options to send the consumption data into the DDF staging tables:

○ Use the SAP ERP data replication framework (DRF; PCON outbound implementation).




○ SAP Help Portal for Master Data Governance at help.sap.com/mdg <your release>Application Help SAP Master Data Governance Working with Master Data Governance Working with SAP MDG, Central Governance General Functions Data Replication

○ Use the Generic (/DMF/TS_GENERIC_INBOUND) inbound interface. For more information, see

help.sap.com/car <your release> Application Help SAP Customer Activity RepositoryDemand Data Foundation Data Management Time Series Generic .

Integrating Promotions and Offers

Promotions are available in SAP ERP. Offers are more detailed views of promotions and can be available with SAP Promotion Management for Retail, for example. Offers can include information on tactics and tactic types, allowing you to quantify their impact on the promotion and, ultimately, on the demand of the product.

The following scenarios are possible:

● Historical offers were created in SAP Promotion Management for Retail.

The closed-loop integration ensures that the same offer identifier (ID) can be used across systems. This integration aligns SAP Promotion Management for Retail, SAP ERP, and either SAP POS Data Management 1.0 or SAP Customer Activity Repository.

● Historical offers were not created in SAP Promotion Management for Retail.

The closed-loop integration must be created manually because the register and TLOG data do not distinguish the offer identifier (ID).








NoteThere is no specific table in SAP ERP that keeps a relationship between an offer and a promotion. This relationship is updated in the following tables:

● WAKP (promotion line item if there is a promotion price or discount)

● WAKR (discounts at the level of the multichannel hierarchy or the article hierarchy)

● KNOBBYH (bonus buy)

● WPM_TERM_OFR_MAP (mapping table), used for an exceptional scenario when an offer cannot be mapped to a single bonus buy. This results in doing a logical split in SAP ERP by generating a bogus offer identifier (ID) there. This bogus offer ID is then mapped to the parent offer in SAP Promotion Management for Retail.

In DDF, the /DMF/OFR_EXP_STS table provides the corresponding ERP Promotion information for an offer transferred from SAP Promotion Management for Retail. For more information, see Historical promotions from SAP ERP in the Integration Considerations section.

Integration Considerations

1. ERP Promotion view

Offers created in SAP Promotion Management for Retail are sent to SAP ERP (D Type Code). They are also stored in DDF as the system of record for later reference.

In addition to these offers, you can have promotions that were established in SAP ERP. These promotions provide valuable information to the modeling and forecasting processes.

The SAP ERP promotions are available as an SAP HANA view in SAP Customer Activity Repository through the SAP Landscape Transformation (SLT) replication. The view is used to align the promotions with the time series sources POS_VDM (virtual data model for POS data) and SO_VDM (virtual data model for sales orders).

NoteThe ERP Promotion view does not include the offers that were created in SAP Promotion Management for Retail because this is not the system of record.

2. Historical promotions from SAP ERP

You can use this option when you have historical promotions in SAP ERP and do not want to fully implement SAP Customer Activity Repository from the start. SAP ERP uses the data replication framework (DRF; POFF outbound implementation) to send this data into the DDF staging tables.

NoteYou can only use this option if the historical demand data contains the correct offer identifiers (IDs).




20




○ SAP Help Portal for Master Data Governance at help.sap.com/mdg <your release> Application Help SAP Master Data Governance Working with Master Data Governance Working with SAP MDG, Central Governance General Functions Data Replication

3. Historical promotions from a legacy system

You can use this option when you have historical promotions in a legacy system that is not SAP ERP. DDF uses the Offer (/DMF/OPIF_OFFER_INBOUND) inbound interface to receive this data into the staging tables.

For more information about this interface, see help.sap.com/car <your release> Application HelpSAP Customer Activity Repository Demand Data Foundation Data Management Master Data Offer .

Note○ You can only use this option if the historical demand data contains the correct offer identifiers (IDs).

○ This option involves more effort to extract and transform the data.

4. Future promotions

Future promotions follow the same logic as historical promotions. You should consider future promotions on a frequent basis to ensure that the modeling and forecasting processes have the latest information available.

RecommendationConsider how to automate or schedule your integration option to send frequent updates






2 Technical Implementation

2.1 Technical System Landscape

Demand Data Foundation (DDF) and Unified Demand Forecast (UDF) are modules and part of SAP Customer Activity Repository. For more information about the system landscape, see the following table:

Table 8: System Landscape Information

Landscape overview help.sap.com/car <your release> Installation and Upgrade

Information Master Guide SAP Customer Activity Repository

Overview

Available landscape variants help.sap.com/car <your release> Installation and Upgrade

Information Installation Guide Planning

Software component versions for DDF and UDF in SAP Customer Activity Repository

CautionTechnical dependencies exist between the different components. For more information, see Component Version Dependencies [page 23] and Preparation [page 23].

● RTLDDF 100

NoteThe SAP HANA content for DDF and UDF is contained in delivery units. Each delivery unit is shipped via a dedicated SAP HANA Transport Container (HTC, sometimes referred to as ABAP TLOGO object) inRTLDDF 100.

● RTLDMF 200● RTLMCFND 100● UDFAFL_INST 100

UDF AFL in the SAP HANA database, available as of SAP HANA Platform SPS 8 revision 82. For more information, see Install or Upgrade the UDF AFL [page 34].

2.2 Product Availability Matrix (PAM)

The software components and operating systems for this release of SAP Customer Activity Repository are defined in the Product Availability Matrix (PAM). You can access the PAM from either of the following:

● SAP Help Portal for SAP Customer Activity Repository at help.sap.com/car <your release>Additional Information Product Availability Matrix

● SAP Support Portal at support.sap.com/pam

For more information about the software components and operating systems for this release, see SAP Help Portal

at help.sap.com/car <your release> Installation and Upgrade Information Master Guide SAP Customer Activity Repository Overview Software Units of SAP Customer Activity Repository .

22


Demand Data Foundation (DDF) with Unified Demand Forecast (UDF) on SAP HANATechnical Implementation




http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fpam


2.3 Component Version Dependencies

Before installing or upgrading Demand Data Foundation (DDF) and Unified Demand Forecast (UDF), make sure that you are aware of the following dependencies and have the correct version of each component:

● Shipment

UDF and DDF are modules in SAP Customer Activity Repository and are shipped as part of this application. For more information, see the following sources:

○ SAP Note 2020641 : Installation-Specific Collection Note

○ SAP Note 1843898 : Release strategy for the ABAP add-on RTLCAR

○ SAP Note 1809841 : Release strategy for the ABAP add-on RTLDDF

○ Installation Guide, SAP Customer Activity Repository on SAP Help Portal at help.sap.com/car<your release> Installation and Upgrade Information Installation Guide

● UDF AFL <> SAP HANA Platform

Unified Demand Forecast includes an application function library (UDF AFL) that you install and run in the SAP HANA database (a component of the SAP HANA Platform). The UDF AFL releases are called “revisions”. The AFL revisions follow the release cycle of the SAP HANA Platform. Whenever a new SAP HANA Platform revision is released, a new UDF AFL revision is released.

To use UDF in SAP Customer Activity Repository 1.0, you need SAP HANA Platform SPS 06 or higher. The installation procedure and software component for the UDF AFL depend on your SAP HANA Platform edition (SPS 06 / 07 or SPS 08 / higher). For more information, see Install or Upgrade the UDF AFL [page 34].

For each revision of the UDF AFL, there is only one compatible revision of the SAP HANA database. For example, you can only use revision 85.50 of the UDF AFL with revision 85.05 of the SAP HANA database. When you upgrade the AFL, you must also upgrade the database, and vice versa.

For guidance on selecting the best revision for your scenario, see the following:

○ SAP Note 2050229 : Overview of all UDF AFL revisions as of revision 82, instructions for downloading, installing, and upgrading the AFL

○ Release and maintenance strategy of the SAP HANA Platform: support.sap.com/swdc Support Packages and Patches A-Z H SAP HANA Platform Edition Info Page

○ Dependencies between the SAP HANA Platform and SAP NetWeaver: SAP Note 1914052

● UDF AFL <-> DDF ABAP

○ The ABAP stack for DDF (software component version RTLDDF 100) depends on a minimum revision of the UDF AFL in the SAP HANA database. Backward compatibility is ensured, however, so that you can always install newer revisions of the AFL (and the database).

○ The dependency is bidirectional: Changes in DDF might require a new AFL revision, a new AFL revision might require a DDF correction (SAP Note, patch).

○ The dependency is not restricted to the SAP Retail solution installed on top of SAP Customer Activity Repository. It also applies to any other application powered by SAP HANA that is co-deployed on the same SAP HANA system.

○ Note that RTLDDF 100 includes the delivery units with the SAP HANA content for both DDF and for UDF. For more information, see Post-Installation [page 27].











2.4 Preparation, Installation, and Post-Installation

This section describes the overall technical implementation of Demand Data Foundation (DDF) and Unified Demand Forecast (UDF) as part of your SAP Customer Activity Repository solution. You can choose from different implementation scenarios depending on your requirements.

NotePlease note the following constraints:

● This section does not provide detailed information on superior or subordinate components that might be required for your scenario. Additional technical dependencies may exist without being mentioned explicitly here.

● The implementation scenarios described in the following are intended as examples of how you can use SAP software in your organization. To determine whether you can use a scenario productively, first check your specific requirements and system landscape. The scenario will most likely need adapting before you can run it productively.

2.4.1 Preparation

Depending on how you want to use your SAP Customer Activity Repository solution, you can choose from different implementation scenarios. Each scenario allows you to focus on different aspects of the provided functionality.

Unified Demand Forecast (UDF) and Demand Data Foundation (DDF) are modules of SAP Customer Activity Repository and provide their functionality and data through the respective consuming application. The most common implementation scenarios for UDF and DDF are described in the following. Choose the scenario that best fulfills your business requirements and follow the instructions.

Prerequisites

● You have read SAP Notes 1809841 (Release strategy for the ABAP add-on RTLDDF) and 1843898(Release strategy for the ABAP add-on RTLCAR) and know how the software components for this release are provided.

● You have read the Component Version Dependencies [page 23] section and are aware of the dependencies.

Implementation Scenarios for UDF and DDF in SAP Customer Activity RepositoryTable 9

Scenarios Steps

Full Implementation

All modules of SAP Customer Activity Repository:

● POS Data Transfer and Audit

In this scenario, you want to make full use of the functionalities provided by SAP Customer Activity Repository. This includes DDF (software component version RTLDDF 100) as the reusable data

layer and UDF as the demand modeling and forecasting engine. UDF includes an application function library (UDF AFL) that you install and run in the SAP HANA database.

NoteThe UDF AFL requires SAP HANA Platform SPS 06 or higher. The installation procedure and software component for the UDF AFL depend on your edition of the SAP HANA Platform:

24





Scenarios Steps

● Multichannel Transaction Data Management

● Unified Demand Forecast

● Demand Data Foundation

● Inventory Visibility

● On-Shelf Availability

● SAP HANA Platform SPS 06 or SPS 07

● SAP HANA Platform SPS 08 or higher (upgrading to this edition is optional; it is not a prerequisite for this support package of SAP Customer Activity Repository)

For more information, see Install or Upgrade the UDF AFL [page 34].

To prepare the full implementation of your SAP Customer Activity Repository solution, see the Install Prerequisites to SAP Customer Activity Repository section of the Installation Guide, SAP Customer Activity Repository 1.0 SP7. Follow the instructions for the mandatory prerequisites.

You can find this guide on SAP Help Portal at help.sap.com/car SAP Customer Activity

Repository 1.0 SP7 Installation Guide .

Partial Implementation


● Other modules of SAP Customer Activity Repository

In this scenario, you want to use DDF (software component version RTLDDF 100) as the reusable

data layer in SAP Customer Activity Repository. However, you do not (or not yet) want to do demand modeling and forecasting with UDF.

To prepare the partial implementation of your SAP Customer Activity Repository solution, see the Install Prerequisites to SAP Customer Activity Repository section of the Installation Guide, SAP Customer Activity Repository 1.0 SP7. Follow the instructions for the mandatory prerequisites.

You can find this guide on SAP Help Portal at help.sap.com/car SAP Customer Activity

Repository 1.0 SP7 Installation Guide .

Progressive Implementation

● Phase 1:

○ Unified Demand Forecast

○ Demand Data Foundation

● Phase 2:

○ Other modules of SAP Customer Activity Repository

In this scenario, you want to first focus on the forecast-related functionality in SAP Customer Activity Repository. You start out by implementing DDF (software component version RTLDDF 100) as the reusable data layer and UDF as the demand modeling and forecasting engine. UDF

includes an application function library that you install and run in the SAP HANA database.

NoteThe UDF AFL requires SAP HANA Platform SPS 06 or higher. The installation procedure and software component for the UDF AFL depend on your edition of the SAP HANA Platform:


● SAP HANA Platform SPS 08 or higher (upgrading to this edition is optional; it is not a prerequisite for this support package of SAP Customer Activity Repository)

For more information, see Install or Upgrade the UDF AFL [page 34] and see below for prerequisites.

At a later point in time, you can extend this scenario to include other modules of SAP Customer Activity Repository and benefit from additional functionality.

RecommendationFor example, you might consider this scenario because you do not yet have 2 years of historical transaction log (TLOG) data available for forecasting purposes. However, once 2 years of TLOG data are available, we recommend that you implement the POS Data Transfer and Audit module to be able to use this data as input for forecasting.

To prepare the progressive implementation of your SAP Customer Activity Repository solution, make sure that the following prerequisites for phase 1 are fulfilled:






Scenarios Steps

1. Check your long-term sizing requirements.

CautionWhen determining your sizing requirements, consider phase 1 and phase 2 to avoid long-term undersizing of your system landscape.

2. SAP NetWeaver 7.4 SPS 02 Application Server (or higher)

○ We highly recommend that you upgrade to SAP NetWeaver 7.4 SPS 03 or higher.

○ The SAP Business Suite Foundation component version SAP_BS_FND 747 is

mandatory.

3. SAP HANA Platform SPS 06 (or higher)

○ Make sure that you install the correct revision of the SAP HANA database. For more information, see Component Version Dependencies [page 23].

○ SAP HANA studio

Make sure that your version of SAP HANA studio is in sync with that on the server (DB).

○ Make sure that the script server for the SAP HANA database is activated. For more

information, see SAP Note 1650957 .

○ SAP HANA AFL 1.0 (only applicable with SAP HANA Platform SPS 06 or SPS 07)

For more information, see the SAP HANA Server Installation and Update Guide and the SAP HANA Studio Installation and Update Guide. You can find both guides on SAP Service

Marketplace at service.sap.com/hana . Choose the documentation package for the support package stack (SPS) and revision of your SAP HANA Platform.

4. Set up the required roles and privileges. For more information, see Authorization Requirements for Unified Demand Forecast (UDF) [page 44].

5. If applicable to your business scenario, analyze and implement the following SAP Notes (applicable only for SAP ERP 6.0 EHP5 and higher):

○ 1983853 : DRFOUT: Enhance the product attributes for replication

○ 1994823 : EA-RETAIL: Enhance the product characteristics to include Fashion Grade for replication

○ 2004326 : DRFOUT: Inconsistent product data is replicated in the receiving system

○ 2032294 : DRFOUT: Extension of product attributes for data replication

ResultYou have prepared your implementation scenario. Now you can install the software as described in the next section.

2.4.2 Installation

NoteInstallation: Irrespective of the implementation scenario that you have chosen in the Preparation [page 24] section, you must always install both the Unified Demand Forecast (UDF) module and the Demand Data

26




http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Fhana





Foundation (DDF) module. This step is required to ensure that SAP Customer Activity Repository installs correctly.

Implementation: After the successful installation, you only need to configure those modules that you wish to use in your implementation scenario.

To install UDF and DDF as part of your SAP Customer Activity Repository solution, proceed as follows:

1. Install all components but UDF using the Maintenance Optimizer in SAP Solution Manager. To do this, follow the instructions in the Install SAP Customer Activity Repository Software Components section of the Installation Guide, SAP Customer Activity Repository 1.0 SP 07.

You can find this guide on SAP Service Marketplace at service.sap.com/instguides Installation & Upgrade Guides Industry Solutions Industry Solution Guides SAP for Retail SAP Customer Activity Repository SAP Customer Activity Repository 1.0 SP 07 Installation Guide, SAP Customer Activity Repository 1.0 SP 07 .

2. Install the Unified Demand Forecast application function library as described in Install or Upgrade the UDF AFL [page 34]. The installation procedure and software component for the UDF AFL depend on your edition of the SAP HANA Platform (SPS 06 / SPS 07 or SPS 08 / higher).

NoteUpgrading to SPS 08 or higher is optional; it is not a prerequisite for this release of SAP Customer Activity Repository.

Result

You have installed your SAP Customer Activity Repository solution. Now you can configure the modules that you need for your implementation scenario, as described in the next section.

2.4.3 Post-Installation

Choose the same implementation scenario as in the Installation [page 26] section.

Table 10: Implementation Scenarios for UDF and DDF in SAP Customer Activity Repository

Scenarios Steps

Full Implementation

All modules of SAP Customer Activity Repository:

● POS Data Transfer and Audit

● Multichannel Transaction Data Management

● Unified Demand Forecast


In this scenario, you want to make full use of the functionalities of SAP Customer Activity Repository.

1. Follow the instructions in the Post-Installation section of the Installation Guide, SAP Customer Activity Repository 1.0 SP 07.

You can find this guide on SAP Service Marketplace at service.sap.com/instguides

Industry Solutions Industry Solution Guides SAP for Retail SAP Customer Activity

Repository SAP Customer Activity Repository 1.0 SP 07 Installation Guide, SAP

Customer Activity Repository 1.0 SP 07 .

NoteThe post-installation steps include the activation of all SAP HANA content (SAP HANA views and SQLScript procedures) for SAP Customer Activity Repository. This also includes the SAP HANA content for DDF and UDF, which is described in more detail in the following:






Scenarios Steps

● Inventory Visibility

● On-Shelf Availability

○ Structure: The SAP HANA content for DDF and UDF is spread over 2 delivery units:

○ HCO_DDF_RTLDDF○ HCO_DDF_UDFEach delivery unit is shipped via a dedicated SAP HANA Transport Container (HTC, sometimes referred to as ABAP TLOGO object) in the RTLDDF 100 software

component version.

○ Activation: After installing your SAP Customer Activity Repository solution, you activate the entire SAP HANA content using a dedicated ABAP report (/CAR/ACTIVATE_HANA_CONTENT), as described in the above Installation Guide. This

activation also creates the ABAP schema mapping.

CautionIf you are applying a support package or correction on an existing installation, you must also activate the SAP HANA content again. For example, this is the case when you apply SAP Notes using transaction SNOTE. For more information, see SAP Note

2145356 .

2. Optional: Check whether you want to partition data tables relevant for UDF and DDF. Table partitioning is especially recommended for forecasting scenarios involving large numbers of products and locations. Proceed as described in Partition Tables for UDF and DDF (Optional) [page 32].

Partial Implementation


● Other modules of SAP Customer Activity Repository

In this scenario, you want to use DDF and other modules of SAP Customer Activity Repository, but you do not (or not yet) want to do demand modeling and forecasting with UDF.

1. Follow the instructions in the Post-Installation section of the Installation Guide, SAP Customer Activity Repository 1.0 SP 07 for Activate SAP HANA Content for SAP Customer Activity Repository.

You can find this guide on SAP Service Marketplace at service.sap.com/instguides

Industry Solutions Industry Solution Guides SAP for Retail SAP Customer Activity

Repository SAP Customer Activity Repository 1.0 SP 07 Installation Guide, SAP

Customer Activity Repository 1.0 SP 07 .

CautionIf you are applying a support package or correction on an existing installation, you must also activate the SAP HANA content again. For example, this is the case when you apply

SAP Notes using transaction SNOTE. For more information, see SAP Note 2145356 .

2. Import SAP NetWeaver Portal roles for user authorization.

To set up user authorization, you can use the PFCG roles from the SAP NetWeaver Business Client software and the SAP NetWeaver Portal component. Both sets of roles operate in the same manner. Using the SAP NetWeaver Portal is optional.

The roles have been created for use in SAP NetWeaver Business Client. To use the functions of these roles in SAP NetWeaver Portal, you must upload the roles from the SAP back-end system to the portal. The uploaded objects are converted into portal objects.

28






Scenarios Steps

Use the Role Upload tool to generate the SAP NetWeaver Portal roles automatically. For

more information about the tool, see SAP Note 1685257 .

You can also enhance the roles; for example, you can create your own iViews.

You can upload the following PFCG roles:

○ SAP_ISR_DDF_MASTER○ SAP_ISR_DDF_READONLY_MASTERFor a description of these roles, see Standard Roles [page 39]. For more information about

user authorization in SAP Customer Activity Repository, see help.sap.com/car

<your release> Security Information Security Guide Authorizations .

3. Activate additional business functions:

Recommendation○ Business functions should be activated by a system administrator.

○ Once a business function is active, we recommend that you do not deactivate it.

○ Before activating a business function, read the corresponding business function documentation (transaction SFW5).

○ Activate /DMF/OFR_FIN_CALC_OPT (Optimizations for Offer Financials).

RecommendationAlthough this business function is considered optional, we highly recommend that you activate it. With the business function activated, you get significant improvements in memory and performance.

○ We also recommend that you activate the following optional business functions:

○ /DMF/DDF_IMDB_PL_TD (Decompression of Product Location Price Data)

○ /DMF/DDF_IMDB_TS (Decompression of Time Series Data)

○ /DMF/DDF_IMDB_LANE_TD (Decompression of Lane Price and Time Dependent

Data)

○ Only activate the optional business function /DMF/DDF_IMDB_OFR_FIN (Decompression of Offer Financials Data) if you want to store offer financials data on the database in a decompressed format. The business function enables you to run the /DMF/OFFER_FIN_MIGRATION report, which decompresses this data. For

more information, see the report documentation (transaction SE38).

4. Optional: Check whether you want to partition data tables relevant for DDF (such as /DMF/TS_PS). Table partitioning is especially recommended for scenarios involving large

numbers of products and locations. Proceed as described in Partition Tables for UDF and DDF (Optional) [page 32].

Progressive Implementation

● Phase 1:

○ UDF

In this scenario, you want to first focus on the forecast-related functionality in SAP Customer Activity Repository.

1. Check which business functions you need to activate for DDF and UDF. For more

information, see SAP Help Portal at help.sap.com/car SAP Customer Activity







Scenarios Steps

○ DDF

● Phase 2:

○ Other modules of SAP Customer Activity Repository

Repository 1.0 SP7 Application Help SAP Customer Activity Repository Demand Data

Foundation Business Functions .

Recommendation○ Business functions should be activated by a system administrator.

○ Once a business function is active, we recommend that you do not deactivate it.

○ Before activating the business function, read the corresponding business function documentation (transaction SFW5).

2. For DDF, activate the following business functions:

○ /DMF/DDF_IMDB_PL_TD (Decompression of Product Location Price Data)

○ /DMF/DDF_IMDB_TS (Decompression of Time Series Data)

3. For UDF, activate the following business functions in the following order:

○ /DMF/FORECAST (Activation of Forecast Engine)

○ /DMF/DDF_UDF (Activation of Unified Demand Forecast)

4. Optionally, you can activate additional business functions:

○ Activate /DMF/OFR_FIN_CALC_OPT (Optimizations for Offer Financials).

RecommendationAlthough this business function is considered optional, we highly recommend that you activate it. With the business function activated, you get significant improvements in memory and performance.

○ We recommend that you also activate the optional business function /DMF/DDF_IMDB_LANE_TD (Decompression of Lane Price and Time Dependent Data).

○ Only activate the optional business function /DMF/DDF_IMDB_OFR_FIN (Decompression of Offer Financials Data) if you want to store offer financials data on the database in a decompressed format. The business function enables you to run the /DMF/OFFER_FIN_MIGRATION report, which decompresses this data. For

more information, see the report documentation (transaction SE38).

5. Activate the SAP HANA content for UDF and DDF.

A dedicated ABAP report is available for this progressive implementation scenario. Proceed

as described in SAP Note 1981340 . The activation also creates the ABAP schema mapping.

CautionIf you are applying a support package or correction on an existing installation, you must also activate the SAP HANA content again. For example, this is the case when you apply

SAP Notes using transaction SNOTE. For more information, see SAP Note 2145356 .

NoteThe SAP HANA content (SAP HANA views and SQLScript procedures) for DDF and UDF is provided as follows:

30





Scenarios Steps

○ It is spread over two delivery units:

○ HCO_DDF_RTLDDF○ HCO_DDF_UDF

○ Each delivery unit is shipped via a dedicated SAP HANA Transport Container (HTC, sometimes referred to as ABAP TLOGO object) in the RTLDDF 100 software

component version.

You can find more general information about activating SAP HANA content at

help.sap.com/hana_platform Development and Modeling SAP HANA Developer

Guide (For SAP HANA Studio) Activating Objects .

6. Import the SAP NetWeaver Portal roles:

To set up user authorization, you can use the PFCG roles from the SAP NetWeaver Business Client software and the SAP NetWeaver Portal component. Both sets of roles operate in the same manner. Using the SAP NetWeaver Portal is optional.

The roles have been created for use in SAP NetWeaver Business Client. To use the functions of these roles in SAP NetWeaver Portal, you must upload the roles from the SAP back-end system to the portal. The uploaded objects are converted into portal objects.

Use the Role Upload tool to generate the SAP NetWeaver Portal roles automatically. For

more information about the tool, see SAP Note 1685257 .

You can also enhance the roles; for example, you can create your own iViews.

You can upload the following PFCG roles:

○ SAP_ISR_DDF_MASTER○ SAP_ISR_DDF_READONLY_MASTERFor a description of these roles, see Standard Roles [page 39]. For more information about

user authorization in SAP Customer Activity Repository, see help.sap.com/car

<your release> Security Information Security Guide Authorizations .

7. Analyze and implement the following SAP Notes for UDF:

○ 1898341 : Updated information on configuration changes for demand modeling and forecasting.

○ 1911141 : Setting UDF-specific performance optimization parameters in the SAP HANA database, including global environment variable OMP_NUM_THREADS.

○ Optional: Check the SAP Notes for the Installation [page 8] section for other performance-related notes that you may want to implement.

8. Optional: Check whether you want to partition data tables relevant for UDF and DDF. Table partitioning is especially recommended for forecasting scenarios involving large numbers of products and locations. Proceed as described in Partition Tables for UDF and DDF (Optional) [page 32].

9. Optional: Install and configure the Unified Demand Forecast Launchpad.

The UDF Launchpad is an optional visualization tool that supports the statistical analyst and data analyst in validating the forecasts generated with UDF. The tool allows you to compare historical key performance indicators (KPIs), modeled KPIs, and forecasted KPIs.









Scenarios Steps

Using the UDF Launchpad is optional. You can download it from the SAP Store at

store.sap.com . Please note that the tool has been designed as a template. There is no product support and the user interface is only available in English.

○ Installation and Configuration

To install and configure the UDF Launchpad, read and implement SAP Note 1836357

. Please note that there are additional hardware requirements for using the tool and that you must plan your system landscape accordingly. For more information, see the UDF Launchpad Installation Guide, which you can find in this same note.

For additional installation and configuration information, see the Early Knowledge

Transfer content for UDF at service.sap.com/rkt .

○ Usage

For more information about how to use the tool, see help.sap.com/car SAP

Customer Activity Repository 1.0 SP7 Application Help Demand Data Foundation

General Services Validate Forecasts with UDF Launchpad .

2.5 Partition Tables for UDF and DDF (Optional)

To forecast consumer demand in SAP Customer Activity Repository, you use the Unified Demand Forecast (UDF) and Demand Data Foundation (DDF) modules. UDF provides the actual modeling and forecasting services. DDF provides the data layer required for the import, export, and maintenance processes, for example.

If your forecasting scenario involves large numbers of products and locations, the relevant UDF and DDF tables can become very large. To improve standard database operations (such as inserting, updating, deleting, and reading) and mass operations (such as archiving or index merging), we therefore recommend that you set up partitioning for those tables.

As the Unified Demand Forecast application function library (UDF AFL) runs directly in the SAP HANA Platform, much of the partitioning guidance for SAP HANA systems also applies to forecasting scenarios with UDF (and DDF). Your main reference, therefore, is the SAP HANA Administration Guide, which you can find on SAP Help

Portal at help.sap.com/hana_platform System Administration . Make sure to select the correct guide for your SAP HANA Platform SPS (if necessary, choose Earlier releases).

Prerequisites

● You have installed and configured UDF and DDF as described in this Administrator's Guide.

● You have the system privileges and object privileges required to perform table partitioning operations. See the Authorization for Basic Administration Tasks section of the SAP HANA Administration Guide.

● You are aware of the limitations for table partitioning. See the Partitioning Limits section of the SAP HANA Administration Guide.

32



http://help.sap.com/disclaimer?site=http%3A%2F%2Fstore.sap.com





Procedure

1. Read the Table Partitioning section of the SAP HANA Administration Guide to learn about partitioning of SAP HANA systems.

2. Read SAP Note 2190377 to learn which UDF and DDF tables are relevant for partitioning and what partitioning aspects to consider.

3. Partition the tables according to SAP Note 2190377 .

RecommendationTo help you with the partitioning decisions, consult the sizing information for your system landscape (such as the sizing questionnaire). For example, check the number of records estimated for the large tables to decide which tables to partition and how many partitions you need.

For more information on system sizing for SAP Customer Activity Repository, see SAP Help Portal at

help.sap.com/car <your release> Additional Information Sizing .







3 Upgrade and Migration

This section provides information on upgrade and migration scenarios involving Unified Demand Forecast (UDF) and Demand Data Foundation (DDF). UDF and DDF are modules in SAP Customer Activity Repository and provide their functionality and data through the consuming application installed on top of the repository.

3.1 Install or Upgrade the UDF AFL

NoteUnlike with other components of SAP Customer Activity Repository, you cannot use Maintenance Optimizer in SAP Solution Manager to download and install the UDF AFL. Instead, you need to download the desired UDF AFL revision manually and install it in your SAP HANA database.

In this procedure, you download and install the Unified Demand Forecast application function library (UDF AFL) manually. You do this in the following situations:

● You want to newly use UDF for demand modeling and forecasting and need to do an initial installation.

● You want to upgrade to a new support package of SAP Customer Activity Repository 1.0, including UDF and DDF.

● You want to upgrade your existing UDF AFL to a higher revision to benefit from enhancements and corrections.

● You want to upgrade your SAP HANA database to a higher revision and therefore need to upgrade your UDF AFL as well.

Prerequisites

● You know that the releases of the UDF AFL are called “revisions”.

● You have read the Component Version Dependencies [page 23] section and are aware of the dependencies.

Procedure

Follow the steps for your edition of the SAP HANA Platform:


The UDF AFL is installed as part of the SAP HANA AFL 1.0 when you implement the current support package of SAP Customer Activity Repository 1.0. This is the same process as with previous support packages.

1. To upgrade the AFL, follow the instructions in these documents:

○ Section Perform an Automated Update of the SAP HANA Server Installation and Update Guide

You can find this guide on SAP Help Portal at help.sap.com/hana_platform Installation and Update .

34


Demand Data Foundation (DDF) with Unified Demand Forecast (UDF) on SAP HANAUpgrade and Migration


○ SAP Note 1997526 , which tells you more about AFL installation tools.

● SAP HANA Platform SPS 08 or higher

As of this edition, UDF is delivered as a separate, product-specific AFL (software component version UDFAFL_INST 100). You no longer need the SAP HANA AFL 1.0. As a result, the installation and upgrade procedure changes.

NoteUpgrading to SAP HANA Platform SPS 08 or higher is optional; it is not a prerequisite for this support package of SAP Customer Activity Repository 1.0.

1. To newly install or to upgrade to a UDF AFL revision 82 or higher, follow the instructions in SAP Note

2050229 .

More Information

For more information on the release and maintenance strategy of the SAP HANA Platform, see the following:

● support.sap.com/swdc Support Packages and Patches A-Z H SAP HANA Platform Edition Info Page

● SAP Note 2021789

3.2 Migration Scenario "From DMF to DDF and UDF"

Demand Management Foundation (DMF) is a component of SAP Promotion Management for Retail running on a traditional on-disk database.

The migration scenario From DMF to DDF and UDF becomes necessary when you wish to migrate your SAP Promotion Management for Retail solution to run on SAP HANA Platform and SAP Customer Activity Repository. Demand Data Foundation (DDF) and Unified Demand Forecast (UDF) are modules in the repository.

For more information about this migration scenario, see the SAP Promotion Management for Retail Upgrade and Migration section of the Administrator's Guide, SAP Promotion Management for Retail 8.0 on SAP Customer

Activity Repository 1.0. You can find this guide on SAP Help Portal at help.sap.com/retail-pm SAP Promotion Management for Retail 8.0 on SAP Customer Activity Repository 1.0 Administrator's Guide .

Demand Data Foundation (DDF) with Unified Demand Forecast (UDF) on SAP HANAUpgrade and Migration







http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fretail-pm

4 Security

4.1 Fundamental Security Guides

SAP Customer Activity Repository is built on the SAP NetWeaver Application Server for ABAP and is implemented on the SAP HANA database. Therefore, the corresponding Security Guides also apply to SAP Customer Activity Repository, including the Demand Data Foundation (DDF) and Unified Demand Forecast (UDF) modules.

UDF relies on the access control mechanisms of the SAP HANA database. This includes user management, authentication, and authorization.

Table 11: Fundamental Security Guides

Security Guides for Scenario, Application, or Component Path

Security Guide, SAP Customer Activity Repository help.sap.com/car <your release> Security

Information Security Guide

SAP NetWeaver Application Server for ABAP Security Guide help.sap.com/nw_platform Security Information

Security Guide SAP NetWeaver Security Guide Security

Guides for SAP NetWeaver Functional Units Security Guides

for the Application Server Security Guides for AS ABAP

SAP NetWeaver Application Server for ABAP Security Guide

SAP NetWeaver 7.4 Security Guide help.sap.com/nw74 Security Information Security

Guide

SAP HANA Security Guide help.sap.com/hana_platform Security

More Information

● Available security guides: service.sap.com/securityguide

● Related SAP Notes: support.sap.com/securitynotes

4.2 Logging and Tracing

Logging and Tracing

Demand Data Foundation (DDF) relies on the logging and tracing mechanisms of SAP NetWeaver. For more

information about logging and tracing, see SAP Help Portal at help.sap.com/nw74 Security InformationSecurity Guide Security Guides for SAP NetWeaver Functional Units Security Guides for the Application Server Security Guides for AS ABAP SAP NetWeaver Application Server ABAP Security Guide Auditing and Logging .

36


Demand Data Foundation (DDF) with Unified Demand Forecast (UDF) on SAP HANASecurity


http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fnw_platform



http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Fsecurityguide

http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fsecuritynotes


Logging and Tracing for Customizing Changes

To be able to evaluate changes to the Customizing tables for DDF and UDF, activate the logging of changes to table data (transaction SCU3).

4.3 User Administration and Authentication

As a module in SAP Customer Activity Repository, Demand Data Foundation (DDF) uses the user management and user authentication mechanisms provided with the SAP NetWeaver Platform, in particular the AS ABAP. Therefore, the security recommendations and guidelines for user administration and user authentication as described in the Security Guide for SAP NetWeaver AS ABAP apply to DDF as well.

For more information, see the following sources:

Table 12

Information About Guide Guide Sections

Authentication mechanisms in the SAP NetWeaver Application Server for ABAP

help.sap.com/nw_platform

Security Information Security Guide

SAP NetWeaver Security GuideSecurity Guides for SAP NetWeaver

Functional Units Security Guides for

the Application Server Security Guides

for AS ABAP SAP NetWeaver Application Server for ABAP Security

Guide

User Administration and Authentication -> User Authentication and Integration in Single Sign-On Environments

User administration, authentication, and management in SAP Customer Activity Repository

help.sap.com/car <your

release> Security Information

Security Guide

User Administration and Authentication

4.3.1 User Management

The user management for the Demand Data Foundation (DDF) module in SAP Customer Activity Repository relies on the mechanisms provided by the SAP NetWeaver Application Server for ABAP. This includes tools, user types, and password policies, for example.

For more information, see the sections below as well as the User Management section of the Security Guide, SAP

Customer Activity Repository. You can find this guide on SAP Help Portal at help.sap.com/car <your release> Security Information .







4.3.1.1 User Administration Tools

For more information, see the User Management -> User Administration Tools section of the Security Guide, SAP

Customer Activity Repository. You can find this guide on SAP Help Portal at help.sap.com/car <your release> Security Information .

4.3.1.2 User Types

For more information, see the User Management -> User Types section of the Security Guide, SAP Customer

Activity Repository. You can find this guide on SAP Help Portal at help.sap.com/car <your release>Security Information .

4.3.1.3 Standard Users

The Demand Data Foundation (DDF) module in SAP Customer Activity Repository does not require specialized standard users. Instead, it indirectly uses SAP NetWeaver standard users.

For more information about the SAP NetWeaver standard users, see the SAP NetWeaver Application Server for

ABAP Security Guide, which you can find on SAP Help Portal at help.sap.com/nw_platform Security Information Security Guide SAP NetWeaver Security Guide Security Guides for SAP NetWeaver Functional Units Security Guides for the Application Server Security Guides for AS ABAP SAP NetWeaver Application Server for ABAP Security Guide .

RecommendationWe recommend changing the user IDs and passwords for any users that are created automatically during the installation.

4.3.2 Integration in Single Sign-On (SSO) Environments

Demand Data Foundation (DDF) supports the single sign-on mechanisms provided by the SAP NetWeaver Application Server for ABAP. Therefore, the security recommendations and guidelines for user administration and user authentication as described in the SAP NetWeaver Application Server for ABAP Security Guide also apply to DDF.

You can find this guide on SAP Help Portal at help.sap.com/nw_platform Security Information Security Guide SAP NetWeaver Security Guide Security Guides for SAP NetWeaver Functional Units Security Guides for the Application Server Security Guides for AS ABAP SAP NetWeaver Application Server for ABAP Security Guide .

For more information about the available authentication mechanisms, see the following sections in the guide:

● User Administration and Authentication User Authentication

● User Administration and Authentication Integration in Single Sign-On Environments

38







4.4 Authorizations

As a module in SAP Customer Activity Repository, Demand Data Foundation (DDF) uses the authorization mechanisms provided by the SAP NetWeaver Application Server for ABAP (AS ABAP). Therefore, the recommendations and guidelines for authorizations as described in the SAP NetWeaver Application Server for ABAP Security Guide also apply to DDF.

The SAP NetWeaver authorization concept is based on assigning authorizations to users based on roles. For role maintenance, use the profile generator (transaction PFCG) on the AS ABAP.

For more information, see the following sources:

Table 13

Information About Path Guide Sections

Authorization mechanisms in SAP NetWeaver Application Server for ABAP







Guide

AS ABAP Authorization Concept

Authorizations in SAP Customer Activity Repository

help.sap.com/car <your

release> Security Information

Security Guide

Authorizations

Role creation and administration in SAP NetWeaver







Guide

User and Role Administration of Application Server ABAP -> Configuration of User and Role Administration -> Role Administration

4.4.1 Standard Roles

The following table shows the standard roles (PFCG roles) used by Demand Data Foundation (DDF) and lists the DDF services to which each role grants access:

Note● To maintain roles and view role details, use transaction PFCG.

● To access the services on the SAP Easy Access screen (transaction nwbc), choose Cross-Application Components Services .







Table 14

PFCG Role Grants Access to These Services

SAP_ISR_DDF_MASTER ● Check Mass Maintenance

● Configure Load Balancing

● Define Area of Responsibility

● Location Groups

● Maintain Product Locations

● Monitor Compressed Data

● Monitor Exceptions

● Monitor Imports

● Placeholder Products

● Product

● Product Groups

● Schedule Model and Forecasts

● Remove Time Series

● Search for Schedule Jobs

● Search Placeholder Products

● Transportation Lanes

SAP_ISR_DDF_READONLY_MASTER ● Check Mass Maintenance

● Configure Load Balancing

● Define Area of Responsibility

● Location Groups

● Maintain Product Locations

● Monitor Compressed Data

● Monitor Exceptions

● Monitor Imports

● Placeholder Products

● Product

● Product Groups

● Remove Time Series

● Schedule Model and Forecasts

● Search for Schedule Jobs

● Search Placeholder Products

● Transportation Lanes

4.4.2 Standard Authorization Objects

For more information about an authorization object, see the accompanying system documentation (for example, using transaction SU21).

40



NoteNaming conventions:● ACTVT - activity

● TCODE - transaction code

● TS - time series

Table 15: Authorization Objects for DDF

Authorization Object Fields Values / Activities Description

CA_POWL POWL_APPIDPOWL_CATPOWL_LSELPOWL_QUERYPOWL_RA_ALPOWL_TABLE

Authorization for the functionality of the Personal Object Worklist (POWL) menu for the DDF POWL applications.

S_START Object Name

Object Type

Program ID

/DMF/* and /PRM/* POWLWDYAR3TR

Used when checking the start authorization for particular TADIR objects (such as Web

Dynpro applications). Do not use this authorization object directly in your own coding. It can only be used through the CL_START_AUTH_CHECK class.

For more information about the start authorization check for program objects with object catalog entries, see

SAP Note 1413011 .

/DMF/AOR ACTVT 01 Create

02 Change

03 Display

06 Delete

Authorization for the Maintain Area of Responsibility (AOR) screen.

S_TCODE TCD Report /DMF/TS_DELETERSM37SM37

Transaction check at transaction start.

/DMF/CM_AT ACTVT 01 Create

02 Change

03 Display

06 Delete

Authorization to assign attributes.

/DMF/CM_IM ACTVT 02 Change

03 Display

Authorization to define images.






06 Delete

/DMF/DISCH ACTVT 01 Create or generate

02 Change

03 Display

06 Delete

Authorization for the distribution chain.

/DMF/DMDTS ACTVT 01 Create

02 Change

03 Display

06 Delete

Authorization to access demand time series data, including any business intelligence (BI) interfaces that would be sending point-of-sale (POS) data or generic consumption data.

/DMF/EWB ACTVT 03 Display Authorization for the exception handling framework.

/DMF/FCANA ACTVT 16 Execute

71 Analyze

Authorization to access forecasting and analytics.

/DMF/IMAGE ACTVT 01 Create or generate Authorization for the Image object.

/DMF/INV ACTVT 01 Create or generate

02 Change

03 Display

06 Delete

Authorization for the Inventory object.

/DMF/LANE ACTVT 01 Create or generate

02 Change

03 Display

06 Delete

Authorization for the Transportation Lane object.

/DMF/LBUI ACTVT 01 Create or generate

02 Change

03 Display

06 Delete

32 Save

Authorization for the load balancing configuration and user interface for the DDF server configuration.

/DMF/LOC ACTVT 01 Create

02 Change

03 Display

06 Delete

Authorization for the Location object.

/DMF/LOCHR ACTVT 01 Create

02 Change

Authorization for the Location Hierarchy object.

42




03 Display

06 Delete

/DMF/ME ACTVT 01 Create or generate

02 Change

03 Display

06 Delete

Authorization for the Monitor Exceptions service.

/DMF/MI ACTVT 01 Create or generate

02 Change

03 Display

06 Delete

Authorization check for the Monitor Imports service.

/DMF/OFRSO /DMF/CHCHK (first input

value for this authorization object)

All activities Internal organizational unit identifier for the distribution channel.

/DMF/OFRSO /DMF/SOCHK (second input

value for this authorization object)

All activities Internal organizational unit identifier for the sales organization.

/DMF/OPUI ACTVT 03 Display

16 Execute

Authorization to access the user interface of the Schedule Model and Forecasts service.

/DMF/PHP ACTVT 01 Create

02 Change

03 Display

06 Delete

Authorization for the Placeholder Product object.

/DMF/PROD ACTVT 01 Create

02 Change

03 Display

06 Delete

61 Export

Authorization for the Product object.

/DMF/PRDHR ACTVT 01 Create or generate

02 Change

03 Display

06 Delete

Authorization for the Product Hierarchy object.

/DMF/PRDLC ACTVT 01 Create

02 Change

03 Display

06 Delete

Authorization for the Product Location object in the consumer access layer.





/DMF/TS ACTVT 01 Create or generate

02 Change

03 Display

06 Delete

Authorization for the Time Series Data object in the access layer.

/DMF/SLSH ACTVT 01 Create

03 Display

06 Delete

Authorization for the Sales History object.

4.4.3 Authorization Requirements for Unified Demand Forecast (UDF)

In this procedure, you set up the privileges required for the Unified Demand Forecast application function library (UDF AFL). To do this, you create the following roles in SAP HANA studio, grant each role specific privileges, and then assign the roles to specific users:

● Role UDF_EXECUTEDefines all privileges for executing UDF; enables the SAP<SID> user to execute UDF.

● Role UDF_DEPLOYDefines all privileges for deploying the SAP HANA content for UDF; required to import and activate the SAP HANA content.

● Role UDF_DEPLOY_SYS_REPODefines additional privileges for the _SYS_REPO standard user; required to activate the SAP HANA content.

Additionally, we have provided example SQL statements that you can use and adapt as needed.

NoteThis procedure is part of the Activate SAP HANA Content for SAP Customer Activity Repository procedure, as

described in help.sap.com/car <your release> Installation and Upgrade Information Installation Guide Post-Installation Activate SAP HANA Content for SAP Customer Activity Repository .

If you are familiar with roles and privileges in SAP HANA studio, you can skip directly to the Prerequisites section below. If you want more background first, continue with the next section.

Background

Authorization Concept

The UDF AFL relies on the access control mechanisms of the SAP HANA database. SAP HANA has implemented the regular SQL authorization concept based on privileges. The privileges provide access to views and procedures in the SAP HANA content, which in turn provide access to data and functionality directly on the database level.

You can grant privileges to a user either directly or indirectly (through roles). We recommend that you grant privileges through roles. A role is a collection of privileges. You can grant roles to users and to other roles.

44




For more information, see the following sections of the SAP HANA Security Guide at help.sap.com/

hana_platform Security :

● SAP HANA User Management

● SAP HANA Authentication and Single Sign-On

● SAP HANA Authorization (privilege types and roles)

Managing Users, Roles, Privileges, and Schemas in SAP HANA Studio

Here is some general information to help you with the steps below:

● You find the Users and Roles in the Security folder of your back-end system in SAP HANA studio.

● When you select a role, a details screen opens where you can grant and remove privileges and other roles.

● When you create a database user (such as SAP<SID>), a database schema of the same name is created automatically.

● You find the schemas in the Catalog folder.

● SQLScript procedures are always assigned to a specific schema. For example:

○ Schema _SYS_BIC includes the modeling and forecasting procedures used by the UDF AFL.

○ Schema _SYS_AFL includes the actual UDF AFL procedures.

● Some technical users are available as standard, for example _SYS_REPO.

Prerequisites

● You have installed the UDF AFL in the SAP HANA database as described in Installation [page 26].

● You have an SAP<SID> user and schema in your SAP HANA database (the names must be identical).

● You have checked that the correct schemas are mapped for your back-end system in SAP HANA studio. The setting under SAP HANA Modeler Schema Mapping must be as follows:

Table 16

Authoring Schema Physical Schema

SAP_DDF SAP<SID>

● You have done step 1.1 of the Activate SAP HANA Content for SAP Customer Activity Repository procedure.

Procedure

In this procedure, you create the three roles with privileges for UDF:

1. Select your back-end system in SAP HANA studio and open the SAP HANA Administration Console.

2. Navigate to Security Roles , right-click, and select New Role.

3. Enter UDF_EXECUTE as the role name.

SQL example: create role UDF_EXECUTE;4. Make the following settings for this role:

○ Granted Roles: AFL__SYS_AFL_UDFCORE_AREA_EXECUTESQL example: grant AFL__SYS_AFL_UDFCORE_AREA_EXECUTE to UDF_EXECUTE;

○ Object Privileges:

○ For catalog object (schema) SAP<SID>: SELECT, INSERT, UPDATE, DELETE

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






○ For catalog object (schema) _SYS_BIC: SELECT, EXECUTE

SQL example: grant SELECT, EXECUTE on schema _SYS_BIC to UDF_EXECUTE;○ Analytic Privileges: _SYS_BI_CP_ALL

SQL example: call GRANT_ACTIVATED_ANALYTICAL_PRIVILEGE('_SYS_BI_CP_ALL','UDF_EXECUTE');

Save your settings. You have successfully set up the first role.

5. Open the details screen for user SAP<SID> and assign the role:

○ Granted Roles: UDF_EXECUTESQL example: grant UDF_EXECUTE to SAP<SID>

Save your settings.

6. Navigate again to Security Roles , right-click, and select New Role.

7. Enter UDF_DEPLOY as the role name.

SQL example: create role UDF_DEPLOY;8. Make the following settings for this role:

○ Granted Roles: CONTENT_ADMINSQL example: grant CONTENT_ADMIN to UDF_DEPLOY;

○ System Privileges: CATALOG READSQL example: grant CATALOG READ to UDF DEPLOY;

Save your settings.

9. Open the details screen for user SAP<SID> and assign the role:

○ Granted Roles: UDF_DEPLOYSQL example: grant UDF_DEPLOY to SAP<SID>

Save your settings. You have successfully set up the second role.

10. Navigate again to Security Roles , right-click, and select New Role.

11. Enter UDF_DEPLOY_SYS_REPO as the role name.

SQL example: create role UDF_DEPLOY_SYS_REPO;12. Make the following settings for this role:

○ Object Privileges:

○ For catalog object (schema) SAP<SID>: SELECT, INSERT, UPDATE, DELETE

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

Save your settings. You have successfully set up the third role.

13. Open the details screen for user _SYS_REPO and assign the role:

○ Granted Roles: UDF_DEPLOY_SYS_REPOSQL example: grant UDF_DEPLOY_SYS_REPO to _SYS_REPO;

Save your settings.

You can now continue with the next steps of the Activate SAP HANA Content for SAP Customer Activity Repository procedure.

46



4.5 Security Protection

RecommendationTo increase security and prevent access to the SAP Logon tickets and security session cookies, you should activate secure session management.

We also highly recommend using Secure Sockets Layer (SSL) to protect the network communications where these security-relevant cookies are transferred.

Session Security Protection on the SAP NetWeaver Application Server ABAP

To activate session security on the SAP NetWeaver AS ABAP, set the corresponding profile parameters and activate the session security for the client (transaction SICF_SESSIONS).

For more information, see Activating HTTP Security Session Management on AS ABAP in the SAP NetWeaver Application Server for ABAP Security Guide. You can find this guide on SAP Help Portal at help.sap.com/nw74

Security Information Security Guide Security Guides for SAP NetWeaver Functional Units Security Guides for the Application Server Security Guides for AS ABAP SAP NetWeaver Application Server for ABAP Security Guide .





5 Operation

Demand Data Foundation (DDF) is one of the modules in SAP Customer Activity Repository.

SAP Customer Activity Repository is an add-on to SAP NetWeaver, so no technical configuration specific to DDF is required. DDF only uses basis parameters for the database, operating system, and application server ABAP provided by SAP NetWeaver. The technical configuration required for running DDF is part of SAP NetWeaver.

For additional operating information, see the Application Operations Guide, SAP Customer Activity Repository at

help.sap.com/car <your release> System Administration and Maintenance Information .

5.1 Monitoring

Monitoring is an essential task in managing SAP technology. Monitoring allows you to detect any irregularities or deviations from the ideal business process flow. It also allows you to detect error situations concerning core business processes at an early stage.

As a module in SAP Customer Activity Repository, Demand Data Foundation (DDF) uses the SAP NetWeaver

standard functionality for monitoring. For more information, see SAP Help Portal at help.sap.com/nw74System Administration and Maintenance Information Operations Information .

5.1.1 Alert Monitoring

Proactive, automated monitoring is the basis for ensuring reliable operations for your SAP system environment.

SAP provides you with the infrastructure and recommendations to set up your alert monitoring in such a way that you can identify critical situations as quickly as possible.

5.1.2 Monitor Installation and Setup

The Computing Center Management System (CCMS, transaction RZ20, package SMOI_XMB) is an infrastructure for monitoring system landscapes centrally.

CCMS does the following:

● continually checks all landscape components

● ensures the availability of all productive components

● monitors the overall system health

● provides the central entry point for deeper analysis

You get an overview of the faulty component, and analysis tools guide you directly into helpful expert tools for further analysis.

48


Demand Data Foundation (DDF) with Unified Demand Forecast (UDF) on SAP HANAOperation



● provides auto-alert mechanisms

Alerts are a central element of the monitoring. They quickly and reliably report problems (for example, a value that has exceeded a defined threshold, or a component that has been inactive for a defined period of time). If something is wrong, an alert is triggered, and the person in charge can be notified automatically (for example, via email or SMS).

To enable the auto-alert mechanism of CCMS, read and implement SAP Note 617547 .

5.1.3 Component-Specific Monitoring

The Demand Data Foundation (DDF) and Unified Demand Forecast (UDF) modules provide the SAP DMF monitor set for the Computing Center Management System (CCMS) monitoring.

The SAP DMF monitor set displays the monitoring hierarchy of the following UDF services (transaction RZ20):

Table 17: Services and Processes for CCMS Monitoring

Services Monitoring Tree Elements (MTEs, nodes)

Model by hierarchy DMF_MODEL_PROCESSES_BY_HIER

Model by product location DMF_MODEL_PROCESSES_BY_PROD_LOC

Forecast by hierarchy DMF_FORECAST_PROCESSES_BY_HIER

Forecast by product location DMF_FORECAST_PROCESSES_BY_PROD_LOC

NoteA node may display the MTE class: No MTEs currently available message. This message indicates that the associated UDF service has not yet been run on this system to generate the Monitoring Tree Elements for this node.

5.1.4 Detailed Monitoring

5.1.4.1 Prepare Exception Handling

Demand Data Foundation (DDF) uses the exception handling framework to log errors that have occurred during background processes.

You must first define the exception messages in the system before actual exception instances can be created. For more information, see Configure Exceptions [page 50].

The exception definition is based on the general ABAP message concept. Each exception is identified by the combination of a message class and a message number. Each instance of an exception has a unique internal ID (message handle).

NoteThe following subobjects do not use the exception handling framework:





● /DMF/ENGINE● /DMF/MERCH_PLAN● /DMF/OFFER● /DMF/OFFER_PURGE● /DMF/PHP

5.1.4.2 Configure Exceptions

You can configure and maintain exceptions in Customizing (transaction SPRO) under Cross-Application Components Demand Data Foundation Basic Settings Exception Management .

NoteFor more information about managing and monitoring exceptions, see SAP Help Portal at help.sap.com/car

<your release> Application Help Demand Data Foundation General Services Exception Management

Define High Level Exceptions

You can define high level exceptions under Cross-Application Components Demand Data Foundation Basic Settings Exception Management Maintain Configuration Data for High Level Exceptions .

You can do the following:

● Assign business areas to exceptions

● Assign priorities to exceptions

● Define message types

● Define validity periods for exceptions

Define Low Level Exceptions

Additionally, you can assign a priority to each low level exception under Cross-Application ComponentsDemand Data Foundation Basic Settings Exception Management Maintain Configuration Data for Low Level Exceptions .

Define Customer-Specific Replacement Messages

You can define your own message texts under Cross-Application Components Demand Data FoundationBasic Settings Exception Management Define Customer-Specific Replacement Messages .

Define Customizable Message Status

You can define the available exception statuses under Cross-Application Components Demand Data Foundation Basic Settings Exception Management Define Customizable Message Status .

50




5.1.4.3 Monitor Exceptions

Exceptions are system-based messages that inform users about situations requiring special attention or action. You use the Monitor Exceptions function to review and process the exceptions.

You can do the following:

● Get an overview of the number of exceptions

● Filter the exceptions based on a number of different criteria

● Perform additional filtering based on the business area, context type, or context instance (value)

● Display the selected exceptions in a table

● Display the detailed information on the exception

● Display all low level exceptions assigned to a selected high level exception

More Information

● To access the function on the SAP Easy Access screen (transaction nwbc), choose Cross-Application Components Services Monitor Exceptions .

● For more information about how to use the function, see SAP Help Portal at help.sap.com/car <your release> Application Help SAP Customer Activity Repository Demand Data Foundation General Services Exception Management Monitor Exceptions .

5.1.4.4 Purge Obsolete Exceptions

You might have a high number of exceptions occurring during system operation. We recommend that you regularly purge (delete) obsolete exceptions.

You can configure and perform the purging of exceptions using the Purging Exceptions from the Database report (/DMF/PURGE_EWB_MESSAGES).

More Information

● To access the report on the SAP Easy Access screen (transaction NWBC), choose Services Mass Maintenance Services Purging Exceptions from the Database .

● For more information about the report, see the report documentation (transaction SE38).

5.1.4.5 Application Log

The Application Log function collects messages, exceptions, and errors, and displays them as logs. You can filter the logs for the information that you need. The following information is provided:

● Basic header information on the events that have occurred





● Event details

● Technical information

● Message short and long texts

Procedure

To use the function, follow these steps:

1. Execute transaction SLG1 to open the Analyse Application Log screen.

2. In the Object field, specify /DMF/APPL. This is the object used by Demand Data Foundation (DDF).

3. In the Subobject field, optionally limit the search to one or more of the DDF subobjects:

○ /DMF/ENGINE○ /DMF/MERCH_PLAN○ /DMF/OFFER○ /DMF/OFFER_PURGE○ /DMF/PHP

4. Specify additional criteria as needed and execute the function ( F8 ).

5.1.4.6 Workload Monitoring

Inbound Processing

To manage the import of master data and transactional data from an external system into DDF, you can use the Monitor Imports service. For more information about this service, see SAP Help Portal for SAP Customer Activity

Repository at help.sap.com/car <your release> Application Help SAP Customer Activity RepositoryDemand Data Foundation General Services Monitor Imports .

By default, the inbound processing includes the following steps:

1. The external system sends the data to DDF using a Remote Function Call (RFC) or enterprise services, for example. You can do either an initial load and or a delta load, which transfers only the changed object instances.

2. The import data is stored in the staging tables. Note that no business validations are performed at this step.

3. The data is transferred from the staging tables to the production tables. Business validations are performed.

For more information, see help.sap.com/car <your release> Application Help SAP Customer Activity Repository Demand Data Foundation Integration Information Inbound Processing .

Additional Options

You can use the following options to adapt the inbound processing to your specific scenario:

● If the processing of transportation lane, product location, or sales data from the staging tables to the production tables takes more time than expected, you can use the /DMF/SET_STAGING_CONFIG_TABLE report to activate an alternative packaging. For more information, see the report documentation (transaction

SE38) and SAP Notes 1854313 and 2019909 .

● You can schedule the /DMF/PROCESS_STAGING_TABLES report as a batch job to move the data from the staging tables to the corresponding business object.

52







● You can also move the data from the staging tables to the production tables manually. For this, use the Manual Processing option of the Monitor Imports function.

More Information

help.sap.com/car <your release> Application Help SAP Customer Activity Repository Demand Data Foundation Integration Information

5.1.5 Ensure Data Consistency

Staging Tables

External data providers write data into the staging tables. When performing a Remote Function Call (RFC), the data providers can additionally provide a high resolution time stamp.

Every data record in the staging tables has a high resolution time stamp (field EXT_KEY_TST). The time stamp is part of the data record key.

As a result, different records for the same object can exist in the table at any given point in time. When processing the data from the staging tables, the newest data record of each object is used.

Authorization Checks

The system performs authorization checks on the following function groups:

● /DMF/BI_SALES_INBOUND (Inbound RFC for BI Sales Data)

● /DMF/MDIF_IMAGE_DATA (DMF Inbound RFC Image Data)

● /DMF/MDIF_LANE (DMF Inbound RFC Lane Data)

● /DMF/MDIF_LOCATION (DMF Inbound RFC Location)

● /DMF/MDIF_LOC_HIER (DMF Inbound RFC Location Hierarchy)

● /DMF/MDIF_PRODUCT (DMF Inbound RFC Product)

● /DMF/MDIF_PROD_HIER (DMF Inbound RFC Product Hierarchy)

● /DMF/MDIF_PROD_LOC (DMF Inbound RFC Product Location)

● /DMF/OPIF_INVENTORY (Inbound Staging Modules for Inventory)

● /DMF/TS_GENERIC_INBOUND (Inbound RFC for Generic Time Series)

5.1.6 Manage Demand Data Foundation (DDF)

SAP provides an infrastructure to help your technical support consultants and system administrators manage the SAP components and perform the technical administration and operation tasks required.

Starting and Stopping

When you start SAP NetWeaver, you start the system database, the application servers, and the respective processes which the system provides.





Backup and Restore

We recommend that you perform the following activities:

● Back up the system landscape regularly to ensure that you can restore and recover it in the event of a failure.

● Create a backup and restore strategy for the system landscape.

● Cover disaster recovery processes in the backup and restore strategy.

● Specify in your backup and restore strategy that the normal data and the backup data are stored in separate physical locations, so that both types of data are not lost in the event of a disaster.

● Include the backup and restore strategy in the company’s overall business requirements.

Scheduling Periodic Tasks

Scheduled tasks can be automated using a task scheduler program. You can schedule automated import tasks using the /DMF/PROCESS_STAGING_TABLES report (transaction SE38).

Required Manual Periodic Tasks

A manual task needs a person to execute it. Such tasks may be required for individual components and are therefore relevant in each scenario that uses the component. Other tasks may be relevant for certain business scenarios only. It is important that you monitor the successful execution of these tasks on a regular basis.

The following table provides an overview of manual tasks for managing DDF.

Table 18: Manual Tasks for Managing DDF

Task Tool Supporting the Task Recommended Frequency Description

Purge data Report /DMF/PURGE_AGENT

As required See the documentation for this report (transaction SE38).

Delete obsolete time series data

Report /DMF/TS_DELETE As required You can select the data to be deleted by location and by product using the key figure parameter (KPRM). The

available time series types include:

● Universal (UN)

● Location Universal (UL)

● Point-of-Sale (POS)

Delete obsolete exception message data

Report /DMF/PURGE_EWB_MESSAGES

As required No parameter is required by this report. You can execute it directly or schedule it for execution. The purging is driven by how the exceptions have been configured in Customizing and by the deletions performed on the user interface.

Load Balancing

DDF uses the standard functionality of SAP NetWeaver for logon and load balancing.

54



During workload processing, the system breaks a single operation or service into many smaller tasks (task decomposition, also referred to as request decomposition). It then runs each of these tasks as separate dialog work processes (task requests or screen changes), up to the configured maximum number of work processes.

The system attempts to run this maximum number of processes simultaneously to achieve a level of parallelization. You use the Configure Load Balancing function to help more evenly distribute the workload. To access this function on the SAP Easy Access screen (transaction nwbc), choose Cross-Application Components Services Configure Load Balancing .

For example, you can define the task size in the Number of Records field.

NoteFor the demand modeling and forecasting services, the maximum number of records is essential. You must

enter a value greater than zero in Number of Records (see SAP Note 1898341 ).

For more information about the load balancing function, see SAP Help Portal for SAP Customer Activity

Repository at help.sap.com/car <your release> Application Help SAP Customer Activity RepositoryDemand Data Foundation General Services Configure Load Balancing .

Table Partitioning

For more information, see Partition Tables for UDF and DDF (Optional) [page 32].

Performance Considerations

You have the following performance considerations:

● The demand decomposition can create a large data set based on your business scope, and the original hardware sizing needs to be taken into account. For more information, see the sizing guidelines for SAP

Customer Activity Repository at help.sap.com/car <your release> Additional Information Sizing .

5.1.7 Support Desk Management

Support Desk Management enables you to set up an efficient internal support desk for your support organization that seamlessly integrates your end users, internal support employees, partners, and SAP Active Global Support specialists with an efficient problem resolution procedure.

For support desk management, you need the methodology, management procedures, and tools infrastructure to run your internal support organization efficiently.

The following topics are covered:

● Remote support setup

● Problem message handover

If you need to send a problem message to SAP, please use the following SAP component hierarchy names:

Table 19

SAP Component Hierarchy Name Description

CA-DDF-RT Demand Data Foundation

CA-DDF-RT-UDF Unified Demand Forecast







SAP Component Hierarchy Name Description

CA-RT-CAR SAP Customer Activity Repository

SAP Custom Development

SAP Custom Development is an SAP team that works with customers to extend the standard ABAP functionalities associated with the different software components (such as RTLDDF).

Remote Support

You can set up a read-only user for remote support purposes that provides access to the consuming applications and SAP NetWeaver transactions.

The following roles should be assigned to this user:

● SAP_QAP_BC_SHOW (for SAP NetWeaver)

● Role of the consuming application

5.2 Troubleshooting

5.2.1 Troubleshoot UDF and DDF Issues

This section provides possible solutions to issues that may occur when you set up and operate the Unified Demand Forecast (UDF) and Demand Data Foundation (DDF) modules in your SAP Customer Activity Repository solution. It also provides guidance on how you can improve the system configuration for specific use cases.

Use the following table as a reference and proceed as described.

Table 20

Areas Issues Explanations Possible Solutions

Installation You want to download a revision of the UDF AFL.

You need the exact download path on the SAP Support Portal.

SAP Note 2050229

You get an error indicating that the UDF AFL is not compatible.

You are trying to install incompatible releases (“revisions”) of the UDF AFL and the SAP HANA Platform.

SAP Note 2050229

SAP HANA content

You get an error indicating that you are attempting to access inactive or invalid SAP HANA content.

After applying a correction (such as an SAP Note using transaction SNOTE), you have not activated

the SAP HANA content again.

SAP Note 2145356

You have not installed the UDF AFL.

Follow the steps in Installation [page 26].

You are trying to activate the SAP HANA content as described in SAP Note 1981340 for the

● You might have the wrong scenario. Check again in Post-Installation [page 27].

56







Progressive Implementation scenario.

● You have the right scenario. For solutions, check SAP

Note 1981340 under Causes - Side Effects.

You get the error SQLScript: Could not derive table type for variable "UDF_FC_HORIZON".

A program error must be fixed. SAP Note 2125672

You have implemented an SAP Note or correction instructions involving multiple SAP HANA transport container objects (R3TR NHDU), but you cannot

activate the objects.

Manual post-implementation steps are necessary:

SAP HANA transport containers (HTCs) must be activated after implementing SAP Notes. To check for inactive HTCs and activate them now, you can use the SNHI_NHDU_PROCESS report (transaction SE38).

SAP Note 1920783 , with instructions for the report

Hierarchies You get errors when creating location hierarchies and product hierarchies.

The hierarchy / tree flattening information is not generated.

● SAP Note 1425876

● Execute transaction SWETYPV and check that

the Linkage Activated field is selected for the LOCATION_CREATED and

LOCATION_UPDATED events. The system generates those events whenever a location is imported.

● Consult the configuration information in SAP Solution Manager under

Solutions/Applications

SAP for Retail

Scenarios Customer

Activity Repository

Business ProcessesEnabling Demand Data Foundation and Creating

Demand Forecast Tab:

Configuration Configuring

Demand Data Foundation .









Modeling and forecasting

You get the errors 901 Failed execution for &1 and 926 Failed decomposition.

● The load balancing settings are not correct.

● Or there are no active product locations.

SAP Note 1898341

You get the errors Could not execute 'call _SYS_AFL... or Repository: Internal error during statement execution...

The privileges for calling application function libraries (such as the UDF AFL) are not assigned correctly or are incomplete.

SAP Note 1846194

58





6 Solution-Wide Topics

6.1 SAP Solution Manager

SAP Solution Manager is the central lifecycle management hub for SAP systems and SAP solutions. It accelerates innovation, manages application life cycles, and runs solutions, end-to-end, on one integrated business and IT platform. The current version is SAP Solution Manager 7.1.

We highly recommend using Maintenance Optimizer (MOPZ) in SAP Solution Manager to install and update product versions. SAP Solution Manager calculates the required software components that can be deployed on each server. For more information about Maintenance Optimizer, see SAP Help Portal at help.sap.com/

solutionmanager <your release> Application Help SAP Library SAP Solution Manager Maintenance Management Maintenance Optimizer .

Alternatively, you can download the required files directly from the SAP Support Portal at support.sap.com/

swdc and deploy them manually.

RecommendationMaintenance Optimizer 3.0 is the standard as of SAP Solution Manager 7.1 SP12. You may experience difficulties installing products if you are running an older version of SAP Solution Manager.

We recommend upgrading to the latest version of SAP Solution Manager. If you do not wish to do so, you must

implement SAP Note 1940845 to render the MOPZ front-end compatible with the back-end.

SAP also delivers support services based on the business scenarios designed and documented in SAP Solution Manager. The implementation process can be further accelerated using implementation content specifically tailored to your solution. For more information about the availability of such content, see the SAP Support Portal

at support.sap.com/solutionmanager Processes .

Structure of the Configuration Information in SAP Solution Manager

The configuration information is maintained in the Business Process Repository in SAP Solution Manager. It is structured in three levels:

● Highest level: Here you find the “business scenarios”.

○ Intermediate level: Each business scenario can contain one or more “business processes”.

○ Lowest level: Each business process can contain one or more “business process steps”.

Accessing Configuration Information for DDF and UDF in SAP Solution Manager

To access the configuration information for DDF and UDF for the current release of SAP Customer Activity Repository, follow these steps:

1. Log on to your SAP Solution Manager system.

2. Execute transaction SOLAR_LIBRARY to open the Business Process Repository (BPR).

3. Check that you are in the correct product context and system group:

1. Choose Settings Products & Systems .

2. Under Product Contexts, select SAP Customer Activity Repository.

Demand Data Foundation (DDF) with Unified Demand Forecast (UDF) on SAP HANASolution-Wide Topics








http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fsolutionmanager

3. Under System Group, select SAP Customer Activity Repository.

4. Save your settings.

4. Navigate to the business process for DDF and UDF under Solutions/Applications SAP for RetailScenarios Customer Activity Repository Business Processes Enabling Demand Data Foundation and Creating Demand Forecast .

5. Consult the information on the Documentation and Configuration tabs and follow the instructions.

NoteFor additional configuration information, see the Master Guide, SAP Customer Activity Repository for this

release. You can find this guide on SAP Help Portal at help.sap.com/car <your release> Installation and Upgrade Information Master Guide .

6.2 Service-Oriented Architecture (SOA)

This section deals with the service enablement of SAP Business Suite 7.

NoteSAP’s delivery on service-oriented architecture differs from the purely architectural concept of SOA in the delivery of ready-to use enterprise services. Enterprise services are SAP-defined Web services that provide end-to-end business processes or individual business process steps and can be used to compose entire business scenarios while ensuring business integrity and ease of reuse.

SAP designs and implements enterprise service interfaces to ensure semantic harmonization and business relevance.

6.2.1 Service Enablement

The service enablement of SAP Business Suite consists of one or more of the following SAP components:

● SAP Business Suite 7

Enterprise services are an integral part of the software components of the SAP Business Suite applications. Enterprise services are the technical interfaces to the functionalities available in the business application.

● SAP NetWeaver PI 7.0 or higher

SAP NetWeaver Process Integration (SAP NetWeaver PI) is an open integration and application platform that provides tools enabling you to set up a service-oriented architecture (SOA) for business applications. You can use the platform to provide, discover, and consume services, integrate applications using the integration server, and manage business processes.

Process integration is required in a runtime environment to consume enterprise services in a mediated scenario.

60




NoteAsynchronous services that are enabled for Web Services Reliable Messaging (WSRM) can be called in a point-to-point communication scenario. Otherwise, asynchronous services can only be consumed in a mediated scenario.

We recommend that you use the highest version of SAP NetWeaver PI. For more information, see SAP Notes

1515223 and 1388258 .

RecommendationStarting with SAP NetWeaver PI 7.3, SAP provides the new installation option Advanced Adapter Engine Extended (AEX). AEX is a cost-saving option compared to a classical dual-stack implementation. As AEX is based on the Application Server Java (AS Java) alone, it is easier to install and maintain and requires less memory and data storage. Therefore, you should investigate if a Java-only implementation of an SAP NetWeaver PI system is suitable for your use case.

For more information, see SAP Library for SAP NetWeaver Process Integration on SAP Help Portal at

help.sap.com/nw_platform Application Help SAP NetWeaver Process Integration as well as SAP

Note 1573180 .

● Enterprise Services Repository

The Enterprise Services Repository (ES Repository) is the central repository that contains the definition of all enterprise services and models. It is a design time environment that enables you to create and enhance enterprise service definitions. The ES Repository is shipped with SAP NetWeaver Process Integration (as of SAP NetWeaver PI 7.1) and with SAP NetWeaver Composition Environment (as of SAP NetWeaver CE 7.1).

NoteIn a SAP NetWeaver 7.0x landscape, you use the Integration Repository to create and enhance enterprise service definitions.

● Services Registry

The Services Registry (SR) is shipped is shipped with SAP NetWeaver Process Integration (as of SAP NetWeaver PI 7.1) and with SAP NetWeaver Composition Environment (as of SAP NetWeaver CE 7.1). The Service Registry is only required for the publication of enterprise service end points (Web services) that have been configured and activated in SAP Business Suite.

● SAP NetWeaver CE 7.1 or higher

SAP NetWeaver Composition Environment (SAP NetWeaver CE) provides a robust environment for designing and implementing composite applications.

The design time environment of SAP NetWeaver CE can be used for the model-driven design and development of composite applications based on enterprise services. SAP NetWeaver CE also offers the tools and the environment necessary for running composite applications fast and efficiently in a runtime environment.






http://help.sap.com/disclaimer?site=help.sap.com%2Fnw_platform


6.2.2 Install the Service-Oriented Architecture (SOA)

The installation of service interfaces and the service enablement of SAP Business Suite consist of one or more of the following phases:

● Identify software components and required business functions

Use the technical data section of the enterprise services documentation to identify the following data for each enterprise service:

○ the software component version with which the service was shipped

○ the business functions that need to be activated

● Identify technical usages (relevant for SAP ERP only)

SAP Note 1818596 maps business functions and software component versions to technical usages. Consult this note to identify the required technical usages for your list of software component versions and business functions.

● Install the ECC-SE software component (relevant for SAP ERP only)

The ECC-SE software component contains service implementations for the SAP ERP Central Component (SAP ECC). You need to explicitly install this component if you intend to use enterprise services for SAP ECC functionality. In this case, you must also select the ESA ECC-SE technical usage when installing the enhancement package.

● Select and install together with the other parts of the enhancement package

When installing the enhancement package, you must select all technical usages that you have identified for service enablement and for enhanced features in SAP Business Suite. The technical usages that you select will install the corresponding software components that contain the enterprise services interfaces and implementations.

● Import Enterprise Services Repository (ESR) Content (optional)

To install the content required for the enterprise service definitions, you must select the XI Content technical usage when installing the enhancement package. This usage type downloads the content files for SAP NetWeaver Process Integration (PI) 7.0 or higher. Unpack the ZIP file and copy the tpz files corresponding to your SAP NetWeaver PI version into the import directory of your Integration Repository (for SAP NetWeaver PI 7.0x) or Enterprise Services Repository (for SAP NetWeaver ES Repository 7.1 or higher). Use the import function to import the content files into the corresponding repository. For this, choose Tools Import Design Objects .

● Configure Services Registry (optional)

The Services Registry is shipped starting with SAP NetWeaver Process Integration (PI) 7.1 and SAP NetWeaver Composition Environment (CE) 7.1. You must configure the Services Registry and then publish the enterprise services from the SAP Business Suite application to the registry using the SOAMANAGER transaction in the back-end.

For more information about SAP NetWeaver PI, SAP NetWeaver CE, and the Enterprise Services Repository, see the corresponding SAP NetWeaver Installation Guides and Master Guides, which you can find on SAP

Help Portal at help.sap.com/netweaver .

6.2.3 Related Documentation

For more information about SOA, see:

62




http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fnetweaver

● SAP Community Network at scn.sap.com/community/soa (registration required)

● SAP Note 1359215 : Technical prerequisites for using enterprise services (relevant for SAP ERP only)

● SAP Note 838402 : Problems with non-Unicode system landscapes




http://help.sap.com/disclaimer?site=http%3A%2F%2Fscn.sap.com%2Fcommunity%2Fsoa



Typographic Conventions

Table 21

Example Description

<Example> Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, “Enter your <User Name>”.

Example Example Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the documentation

www.sap.com Textual cross-references to an internet address

/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example ● Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options.

● Cross-references to other documentation or published works

Example ● Output on the screen following a user action, for example, messages

● Source code or syntax quoted directly from a program

● File and directory names and their paths, names of variables and parameters, and names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

64


Demand Data Foundation (DDF) with Unified Demand Forecast (UDF) on SAP HANATypographic Conventions

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.sap.com



www.sap.com

© Copyright 2015 SAP SE or an SAP affiliate company. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

http://www.sap.com

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark

Demand Data Foundation (DDF) with Unified Demand ...

Documents

Transcript of Demand Data Foundation (DDF) with Unified Demand ...