sap accelerated tpm planning 2.0

Administrator's GuideSAP Accelerated Trade Promotion Planning 2.0Using SAP Customer Relationship Management 7.0, Enhancement Packages 1 and 2

Target Audience ■ Consultants ■ Administrators ■ Others

CUSTOMERDocument version: 1.40 – 2013-05-13

Document History

CAUTION

Before you start the implementation, make sure you have the latest version of this document.

You can find the latest version at the following location: http://service.sap.com/

instguides.

The following table provides an overview of the most important document changes.

Version Date Description

1.0 2012-09-19 Initial Version

1.10 2012-10-04 Included BI Content Migration Chapter

1.20 2012-12-06 Minor updates related to release of SP01



2/62 CUSTOMER 2013-05-13

http://service.sap.com/instguides


Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.1 About this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.2 References to Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.2.1 Further Useful Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.2.2 Related Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.3 Important SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 2 System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.1 System Landscape Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.2 Sizing Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3.1 Software Units of SAP Accelerated Trade Promotion Planning . . . . . . . . . . . . 13

Chapter 4 Business Scenarios of SAP Accelerated Trade Promotion

Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4.1 Trade Promotion Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 5 Security Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

5.1 Fundamental Security Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

5.2 Security-Relevant Logging and Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

5.2.1 Security Breach Attempts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 6 Operations Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

6.1 Monitoring of Trade Promotion Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

6.1.1 Trace and Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

6.1.2 Logging of Critical Situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

6.1.3 Trace Tool Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

6.2 Asynchronous Processing of Planning Requests . . . . . . . . . . . . . . . . . . . . . . . . 20

6.3 Influencing Locking when Updating Master Data Records in SAP NetWeaver

BW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

6.4 Archiving Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2013-05-13 CUSTOMER 3/62

6.5 Reporting Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

6.6 Activating Performance Improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

6.6.1 Shared Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

6.6.2 Prerequisites for Activating Shared Memory . . . . . . . . . . . . . . . . . . . . . . . . . . 22

6.6.3 Activating Shared Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

6.6.4 Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

6.6.5 Thresholding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

6.6.6 Define Cell Update Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

6.6.7 Accrual Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

6.6.8 Defining the Height of the Planning Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

6.6.9 Using Optimized BI Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 7 Migration from SAP Trade Promotion Management to SAP Accelerated

Trade Promotion Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

7.1 Functional Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

7.2 Functional Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Chapter 8 BI Content Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

8.1 Objects Used for Key Figure Planning with BPS and Key Figure Planning with

the Planning Applications Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

8.2 Setting Up Your Objects for Key Figure Planning with the Planning

Applications Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

8.3 Setting Up Your Queries for SAP Accelerated Trade Promotion

Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

8.4 Time Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

8.5 Mapping Key Figures to Trade Spends . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

8.6 Suppression of Zero Rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

8.7 Deletion of Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

8.8 Non-Aggregating Key Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

8.9 Setting Restrictions to Period Types for Key Figures . . . . . . . . . . . . . . . . . . . . . 37

8.10 Key Figures Distribution Split . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

8.11 Setting the Buying Pattern Key Figure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

8.12 Read Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

8.13 Reporting Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

8.14 Context to Use for Read Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

8.15 Planning Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

8.16 Planning Function Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

8.17 Planning Functions Based on Formula Extensions (FOX) . . . . . . . . . . . . . . . . 42

4/62 CUSTOMER 2013-05-13

8.18 Example Code for Simple Calculations with FOX . . . . . . . . . . . . . . . . . . . . . . 42

8.19 Baseline Data Retrieval Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

8.20 Example Code for Baseline Data Retrieval with FOX . . . . . . . . . . . . . . . . . . . . 47

8.21 BAdI’s in SAP NetWeaver BW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

8.22 Configuring Extensibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

8.23 Example of BI Content with BPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

8.24 Example of BI Content with the Planning Applications Kit . . . . . . . . . . . . . . . 56

2013-05-13 CUSTOMER 5/62

This page is left blank for documents that are printed on both sides.

1 Introduction

1.1 About this Document

This document is a single source of information for the implementation of SAP Accelerated Trade

Promotion Planning. It contains implementation information, as well as security and operation

information, and is divided into the following main sections:

■ Introduction

References to related documents and relevant SAP notes

■ System Landscape

The first section provides a high-level architecture diagram of the system landscape and sizing

recommendations.

■ Installation Information

This section identifies the software units required for SAP Accelerated Trade Promotion Planning.

■ Business Scenarios

This section identifies the business processes that you can benefit from using SAP Accelerated Trade

Promotion Planning.

■ Security Information

This section provides you with the information that you require to securely operate SAP

Accelerated Trade Promotion Planning.

■ Operation Information

This section provides you with the most relevant information needed for the operation of SAP


■ Migration Information

This section provides you with information to consider if you are migrating from planning with

Business Planning and Simulation (BPS) to planning with the planning applications kit.

■ BI Content Migration Information

This section provides you with a comparison of the objects used with BPS and with the planning

applications kit. It then explains how to set up the new objects to use for planning.

NOTE

You can find the most current version of this document on SAP Service Marketplace at http://

service.sap.com/instguides.

We strongly recommend that you use the document available there. The guide will be updated

according to updates of the software.

1 Introduction

1.1 About this Document

2013-05-13 CUSTOMER 7/62



Constraints

■ This administrator’s guide discusses the overall technical implementation of SAP Accelerated

Trade Promotion Planning, rather than its subordinate components. This means that additional

software dependencies can exist without being mentioned explicitly in this document. You can

find more information on component-specific software dependencies in the corresponding

installation guides.

■ This administrator’s guide only provides information for SAP Accelerated Trade Promotion

Planning that is different from the information included in the guides (master, installation,

operation, and security) for SAP CRM 7.0 enhancement packages. Some sections have been

deliberately excluded from this guide since the information is already included in the guides for

SAP CRM 7.0 enhancement packages.

1.2 References to Related Information

For more information about implementation topics not covered in this guide, see the following content

on SAP Service Marketplace:

Content Location on SAP Service Marketplace

Latest versions of installation and upgrade guides


General information about SAP Customer Relationship Management (SAP CRM)

http://service.sap.com/crm

Sizing and calculation of hardware requirements, such as CPU, disk, and memory resource categories, with the Quick Sizer tool

http://service.sap.com/quicksizer

Released platforms and technology-related topics, such as maintenance strategies and language support

http://service.sap.com/platformsTo access the Product Availability Matrix directly, see http://service.sap.com/pam.

Network security http://service.sap.com/securityguide

High Availability http://www.sdn.sap.com/irj/sdn/ha

Performance http://service.sap.com/performance

Information about support package stacks, latest software versions, and patch level requirements

http://service.sap.com/sp-stacks

Information about Unicode technology

http://www.sdn.sap.com/irj/sdn/i18n

1.2.1 Further Useful Links

The following table lists further useful links on SAP Service Marketplace.

1 Introduction

1.2 References to Related Information

8/62 CUSTOMER 2013-05-13


http://service.sap.com/crm

http://service.sap.com/quicksizer

http://service.sap.com/platforms

http://service.sap.com/pam

http://service.sap.com/securityguide

http://www.sdn.sap.com/irj/sdn/ha

http://service.sap.com/performance

http://service.sap.com/sp-stacks

http://www.sdn.sap.com/irj/sdn/i18n

Content Location on SAP Service Marketplace

Information about creating error messages http://service.sap.com/message

SAP Notes search http://service.sap.com/notes

SAP Software Distribution Center (software download and ordering of software)

http://service.sap.com/swdc

SAP Online Knowledge Products (OKPs) –role-specific learning maps http://service.sap.com/rkt

1.2.2 Related Guides

You can find more information about the relevant applications in the following documents:

Title Location on SAP Service Marketplace

Master Guides for SAP CRM 7.0 enhancement packages

http://service.sap.com/instguides SAP Business Suite Applications SAP CRM

Security Guides for SAP CRM

http://service.sap.com/securityguide SAP Business Suite Applications SAP CRM

Master Guide for SAP NetWeaver Business Warehouse 7.3

http://service.sap.com/instguides SAP NetWeaver SAP NetWeaver 7.3Installation

Upgrade Master Guide for SAP NetWeaver Business Warehouse 7.3

http://service.sap.com/instguides SAP NetWeaver SAP NetWeaver 7.3Upgrade

Master Guide for SAP In-Memory Appliance (SAP HANA)

http://service.sap.com/instguides SAP In-Memory Computing SAP In-Memory Appliance (SAP HANA)

1.3 Important SAP Notes

You must read the following SAP Notes before you start the installation of SAP Accelerated Trade

Promotion Planning.

These SAP Notes contain the most recent information on the installation, as well as corrections to the

installation documentation. Make sure that you have the up-to-date version of each SAP Note, which

you can find on SAP Service Marketplace at http://service.sap.com/notes.

SAP Note Number Title Description

1845111 SAP Accelerated Trade Promotion Planning 2.0 SP03 RIN

This note contains information regarding updates in SAP Accelerated Trade Promotion Planning 2.0., Support Package SP03

1 Introduction


2013-05-13 CUSTOMER 9/62

http://service.sap.com/message

http://service.sap.com/notes

http://service.sap.com/swdc

http://service.sap.com/rkt


http://service.sap.com/securityguide




http://service.sap.com/notes

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1845111&_NLANG=en&_NVERS=0

SAP Note Number Title Description

1796581 Support Packages for TPM_IMP 200 Information about support packages for SAP Accelerated Trade Promotion Planning 2.0.

1735590 Q&A on DSO Planning Information on how to leverage the new DSO planning feature in SAP NetWeaver NW.

1637199 Using the ABAP planning applications KIT

SAP Note provided by SAP NetWeaver Business Warehouse (SAP NetWeaver BW) to identify any functional restrictions when planning with the planning applications kit

1765693 BI_CONT 707/737/747: Information on Add-On Support

Contains information about support packages for Add-ons.

1 Introduction


10/62 CUSTOMER 2013-05-13





2 System Landscape

2.1 System Landscape Overview

The following diagram provides a high-level architectural overview of the system landscape for SAP

Accelerated Trade Promotion Planning:

Figure 1: High-Level System Landscape

CAUTION

We strongly recommend that you use a minimal system landscape for test and demo purposes

only. For performance, scalability, high availability, and security reasons, do not use a minimal

system landscape as your production landscape.

2.2 Sizing Recommendations

We recommend using the existing sizing guide for trade promotion management to size the trade

promotion object. Use the Quicksizer tool to size the SAP NetWeaver BW system and the SAP HANA

database.

2 System Landscape

2.1 System Landscape Overview

2013-05-13 CUSTOMER 11/62

3 Installation

3.1 Software Units of SAP Accelerated Trade Promotion Planning

The following software units are required for SAP Accelerated Trade Promotion Planning.

NOTE

Note: To use the SAP Accelerated Trade Promotion Planning application, you must install SAP

Accelerated Trade Promotion Planning 2.0 SP01.

The following components apply if you are installing SAP Accelerated Trade Promotion Planning on

SAP CRM 7.0 with Enhancement Package 1.

Type of Component Software Unit Description

Software component version SAP CRM ABAP 7.01 SAP CRM ABAP Server Component SAP CRM ABAP 7.01 (SP09)

Software component version TPM IN MEMORY PLANNING 200 TPM In Memory Planning 200 (SAP Accelerated Trade Promotion Planning 2.0) SP01

Software component version BI CONT EXT FOR BI CONT 7.47/7.37 BI Content extension for BI Content 7.47/7.37 (SP03).

Product version SAP NetWeaver 7.3 SAP NetWeaver BW 7.3 (SP08) with SAP HANA PLATFORM EDIT 1.0.

External product Adobe Flash Player, version 10.1 or higher

To display Adobe Flex-based planning layouts in SAP CRM

The following components apply if you are installing SAP Accelerated Trade Promotion Planning on

SAP CRM 7.0 with Enhancement Package 2.


Software component version SAP CRM ABAP 7.02 SAP CRM ABAP Server Component SAP CRM ABAP 7.02 (SP05)

Software component version TPM IN MEMORY PLANNING 200 TPM In Memory Planning 200 (SAP Accelerated Trade Promotion Planning 2.0) SP01

Software component version BI CONT EXT FOR BI CONT 7.47/7.37

BI Content extension for BI Content 7.47/7.37 (SP03).

Product version SAP NetWeaver 7.3 SAP NetWeaver BW 7.3 (SP08) with SAP HANA PLATFORM EDIT 1.0.

3 Installation


2013-05-13 CUSTOMER 13/62


External product Adobe Flash Player, version 10.1 or higher

To display Adobe Flex-based planning layouts in SAP CRM

3 Installation


14/62 CUSTOMER 2013-05-13

4 Business Scenarios of SAP Accelerated Trade Promotion Planning

4.1 Trade Promotion Management

You use SAP Accelerated Trade Promotion Planning with the Trade Promotion Management business

scenario and its related business processes.

For more information about the trade promotion management business scenario, refer to the master

guides for SAP Customer Relationship Management 7.0 Including SAP Enhancement Packages 1 and

2 at http://service.sap.com/instguides SAP Business Suite Applications SAP CRM .

The following documents provide more information about trade promotion planning using SAP

Accelerated Trade Promotion Planning

Content Location

Configuration documentation

The configuration documentation that is specific to SAP Accelerated Trade Promotion Planning is included in the application help structure. For more information see SAP Library on SAP Help Portal athttp://help.sap.com/crmaddons SAP Accelerated Trade Promotion Planning . Under Application Help, open SAP Library and choose SAP Accelerated Trade Promotion Planning Setting up SAP Accelerated Trade Promotion Planning .

4 Business Scenarios of SAP Accelerated Trade Promotion Planning

4.1 Trade Promotion Management

2013-05-13 CUSTOMER 15/62


http://help.sap.com/crmaddons

5 Security Information

This section of the administrator’s guide provides an overview of the security-relevant information

that applies to SAP Accelerated Trade Promotion Planning.

5.1 Fundamental Security Guides

Unless specifically mentioned here, all security information for SAP Customer Relationship

Management (SAP CRM) applies to SAP Accelerated Trade Promotion Planning. For more information,

see the security guides for SAP enhancement packages 1 and 2 for SAP CRM 7.0 on SAP Service

Marketplace at http://service.sap.com/security SAP Security Guides SAP CRM Security Guides .

For more information, see SAP Note 1757230.

5.2 Security-Relevant Logging and Tracing

This section provides an overview of the logging and tracing mechanisms that apply to SAP Accelerated

Trade Promotion Planning.

5.2.1 Security Breach Attempts

If any tampering with the XML content sent from the WebClient UI to the BI Consumer Services (BICS)

is detected, it is recorded in the central application log. To search for security breach attempts search

for object type CRM_IMP and subobject type CRM_IMP_SECURITY in transaction SLG1. If any logs exist for

this object type and subobject type, a security breach attempt has occurred.

5 Security Information

5.1 Fundamental Security Guides

2013-05-13 CUSTOMER 17/62

http://service.sap.com/security


6 Operations Information

6.1 Monitoring of Trade Promotion Planning

6.1.1 Trace and Log Files

Trace files and log files are essential for analyzing problems. Logging and tracing for ABAP components

is done using transaction SLG1. An application log is comprised of a log header and a set of messages.

The log header contains general data (type, created by/on, and so on). Each log in the database also has

the attributes Object and Sub-object. These attributes describe and classify the application that wrote the

log.

6.1.2 Logging of Critical Situations

Failure of Commit or Rollback

In the case that the remote COMMIT (called in IF_CRM_IMP_SESSION_ACTIONS~COMMIT) or ROLLBACK

(called in IF_CRM_IMP_SESSION_ACTIONS~ROLLBACK) fails, a message containing the currently active

objects in the session is logged through the central log service (CL_CRM_IMP_LOG_SERVICE) and is

persisted in the business application log (BAL). The BAL can be accessed through transaction SLG1

(object = CRM_IMP, subobject = CRM_IMP_CONNECTOR).

This helps an administrator to analyze the issue that caused the error, and the user to correct or

reprocess the affected objects.

NOTE

Note that if there are any data inconsistencies between the SAP NetWeaver Business Warehouse

(SAP NetWeaver BW) system and the SAP Customer Relationship Management (SAP CRM)

system, for example, you save some data in SAP CRM that does not appear in the SAP NetWeaver

BW system, you can check the central application log by using the transaction Application Log:

Display Logs (SLG1).

Data Inconsistencies are stored in the object CRM_MKT in the subobjects COMMIT and ROLLBACK. The

central application log indicates the time of the action, but a system administrator must then

check the system log for more details.

Failed Master Data Activation in SAP NetWeaver BW

If you modify the InfoObject (0CRM_MKTELM) by changing the master data of a trade promotion, the

master data is saved and activated in SAP NetWeaver BW. If the master data activation fails, then SAP


6.1 Monitoring of Trade Promotion Planning

2013-05-13 CUSTOMER 19/62

NetWeaver BW sends an error message to SAP CRM and this message is saved in the transaction

Application Log: Display Logs (SLG1) under the log object BW_ENQUE under sub-object SAVE_MAST.

6.1.3 Trace Tool Environment

The trace tool environment (transaction RSTT) has been enabled for the SAP NetWeaver BW system

used for SAP Accelerated Trade Promotion Planning. This environment contains tools that allow you

to log and play back traces, process automatic regression tests, analyze performance, and so on. This

can be used when you encounter an error and wish to send SAP a recording of the trace.

Procedure

To use the trace tool environment, you must first make the following user settings:

1. In SAP CRM, ensure that you have set up a remote function call (RFC) connection so you can

access the SAP NetWeaver BW system from SAP CRM. Check which user is defined for this RFC

connection.

2. In SAP NetWeaver BW, go to the trace tool environment (transaction RSTT).

3. Under User Activation, enter the user name defined in the RFC connection to activate the trace.

NOTE

Any other users who are logged in to the SAP CRM system and are using planning data will affect

the trace. As an alternative, you can also set up a RFC connection with a trusted user.

More Information

For more information about the trace tool environment, see SAP Library for SAP NetWeaver on SAP

Help Portal at http://help.sap.com/netweaver SAP NetWeaver 7.3 Including Enhancement Package 1 ->

Under Application Help, open SAP Library and choose SAP NetWeaver SAP NetWeaver Library: Function-

Oriented View Business Warehouse Generic Tools and Services Test and Trace Tools Trace Tool Environment .

6.2 Asynchronous Processing of Planning Requests

SAP Accelerated Trade Promotion Planning uses ABAP asynchronous remote function calls (RFCs) to

integrate with the planning applications kit. Asynchronous processing is used to reduce the navigation

time from the Trade Promotion overview page on the WebClient UI to the planning layout.

Asynchronous processing is the default mode when a planning session is created from SAP Accelerated

Trade Promotion Planning.

More Information

For more information about asynchronous RFCs, see SAP Library for SAP NetWeaver on SAP Help

Portal at http://help.sap.com/netweaver SAP NetWeaver 7.0 Including Enhancement Package 2 . Under

Application Help, open SAP Library and choose SAP NetWeaver SAP NetWeaver by Key Capability


6.2 Asynchronous Processing of Planning Requests

20/62 CUSTOMER 2013-05-13

http://help.sap.com/netweaver


Application Platform by Key Capability Platform-Wide Services Connectivity Components of SAP Communication

Technology Classical SAP Technologies (ABAP) RFC Calling RFC Function Modules in ABAP CALL

FUNCTION – RFC (RFC Variants Using Asynchronous Remote Function Calls .

6.3 Influencing Locking when Updating Master Data Records in SAP NetWeaver BW

You can enable the activation of master data in SAP NetWeaver BW upon saving your trade promotion

in Customizing for Customer Relationship Management under Trade Promotion Management Key Figure Planning

with the Planning Applications Kit Enable Online Activation of Master Data in SAP NetWeaver BW .

If the records are locked when the system is trying to save or activate the modified master data in SAP

NetWeaver BW, there can be delays. To determine how many times you want the system to request a

lock and to determine the interval between attempts, see SAP Notes 421419 and 954346.

6.4 Archiving Objects

The archiving object CRM_MKTPL is used to archive information for trade promotions created using SAP


You can use the new archiving table CRMD_MKTPL_PSM for the planning synchronization manager for

SAP Accelerated Trade Promotion Planning.

6.5 Reporting Problems

For SAP Accelerated Trade Promotion Planning, you can use the following message components to

report problem messages on the SAP Support Portal at http://service.sap.com/message:

■ CRM-ANA-IMP

Used to report issues related to planning

■ CRM-MKT-MPL-TPM-IMP

Used to report issues related to the application

■ BW-BCT-IMP-TPM

Used to report issues related to the standard BI Content for SAP Accelerated Trade Promotion

Planning.


6.3 Influencing Locking when Updating Master Data Records in SAP NetWeaver BW

2013-05-13 CUSTOMER 21/62



http://service.sap.com/message

6.6 Activating Performance Improvements

6.6.1 Shared Memory

Shared Memory Area CL_CRM_IMP_SHM_AREA

To improve performance and to reduce the overall memory consumption of planning with the

planning applications kit, the shared memory area CL_CRM_IMP_SHM_AREA is used by SAP


The shared area buffers the following query-dependent metadata from SAP NetWeaver BW:

■ query descriptions

■ query key figures

■ query characteristics

■ aggregation level characteristics

■ aggregation level key figures

■ manual planning events

In transaction Shared Objects: Management (SHMA) in SAP CRM, the shared area CL_CRM_IMP_SHM_AREA

is delivered with the following settings:

■ Attributes: Aut. Area Creation

■ Runtime Setting – Area Structure: Autostart for Read Request and Every Invalidation

■ Runtime Setting - Lifetime: Up to 500 Minutes to rebuild

Lifetime specifies the amount of time after which an automatic rebuild will be triggered on an area

instance. You can modify this setting to reflect the customer‘s scenario.

More Information

For more information about the shared objects and area properties, see SAP Library for SAP NetWeaver

on SAP Help Portal at http://help.sap.com/netweaver SAP NetWeaver 7.0 Including Enhancement Package

2 . Under Application Help, open SAP Library and choose SAP NetWeaver SAP NetWeaver by Key Capability

Application Platform by Key Capability ABAP Technology ABAP Programming and Runtime Environment (BC-

ABA) ABAP- Shared Objects Shared Objects – Implementation .

6.6.2 Prerequisites for Activating Shared Memory

Make the following settings before activating shared memory:

Procedure

1. In SAP CRM, complete the Customizing for integrated planning profile groups in Customizing

for Customer Relationship Management under Trade Promotion Management Key Figure Planning with the

Planning Applications Kit Define Integrated Planning Profile Groups .



22/62 CUSTOMER 2013-05-13


2. In SAP NetWeaver BW, define the BI content being used for SAP Accelerated Trade Promotion

Planning, for example, the aggregation levels and queries. Additionally, make your entries in the

transaction Define Events for Queries (RSCRM_EVENTCUST).

6.6.3 Activating Shared Memory

Procedure

To activate shared memory for SAP Accelerated Trade Promotion Planning, do the following:

1. In SAP CRM, use transaction Shared Objects Monitor (SHMM) to create an instance of the shared object

area CL_CRM_IMP_SHM_AREA and propagate it to all the application servers.

More Information

For more information on the shared objects monitor, see SAP Library for SAP NetWeaver on SAP Help

Portal at http://help.sap.com/netweaver SAP NetWeaver 7.0 Including Enhancement Package 2 . Under

Application Help, open SAP Library and choose SAP NetWeaver SAP NetWeaver by Key Capability

Application Platform by Key Capability ABAP Technology ABAP Programming and Runtime Environment (BC-

ABA) ABAP- Shared Objects Shared Objects – Access Shared Objects – Access to Area Instances Shared Objects

Monitor – Transactions SHMM .

6.6.4 Load Balancing

Load balancing optimizes the number of parallel processes running on a single server instance. If the

number of processes is too high, it can lead to performance degradation and ultimately system runtime

issues due to missing process availability. Enabling load balancing makes the application scalable with

the number of concurrent users. Make the following settings to enable load balancing:

Make the following settings to enable load balancing in your SAP NetWeaver BW target system:

1. Create a dedicated server logon group in transaction Maint. Assign. Logon Grp to Instance(SMLG).

2. Select the Extern. RFC enabled indicator in the Attributestab.

For more information see SAP Library for SAP NetWeaver on SAP Help Portal at http://help.sap.com/

netweaver SAP NetWeaver Including Enhancement Package 2 . Under Application Help, open SAP Library

and choose SAP NetWeaver SAP NetWeaver by Key Capability Solution Life Cycle Management by Key

Capability System Management Configuration Logon Load Balancing Recommendations for Logon Load Balancing

and Logon Groups .

Make the following settings to enable load balancing in your SAP CRM system:

1. Create an RFC destination for your target system in transaction RFC Destinations (Display/Maintain)

(SM59).

2. Select the Yes indicator for Load Balancing in the Technical Settings tab.



2013-05-13 CUSTOMER 23/62




3. Enter the Target System, Msg. Server and Group that you defined in your SAP NetWeaver BW system (in

the above steps).

6.6.5 Thresholding

You can use the BAdI: Evaluation of Planning Object Size (RSCRM_IMP_THRESHOLD) in the SAP NetWeaver

BW system to optimize performance based on the size of your trade promotion. To implement the

BAdI, use transaction Business Add-Ins: Definitions (SE18).

6.6.6 Define Cell Update Behavior

You can determine how frequently to send updates to SAP NetWeaver BW when you modify data in

the planning layout. Making updates to multiple cells will always be faster than doing several individual

single cell updates.

You make this setting in Customizing for Customer Relationship Managementunder Trade Promotion

Management Key Figure Planning with the Planning Applications Kit UI Setings Define Cell Update Behavior .

6.6.7 Accrual Calculation

If you are integrated with funds management, during the accrual process, standard functionality allows

you to derive the fiscal period on which the planning data should be posted.

When you are planning by day, if you have the fiscal period included in the data provider, it is filled

automatically during the planning process. The fiscal period can then be used in the accrual process

and be used in the query that reads the data for funds management. Reading the data by fiscal period

significantly improves the performance of accrual processing. This improvement is part of the standard

functionality.

However, if you are not planning by day and are planning by week or by month, custom logic is necessary

to aggregate the data by fiscal period.

6.6.8 Defining the Height of the Planning Layout

By default, the planning layout is displayed with a fixed height of 15 rows. By displaying the planning

layout with a fixed height, you can increase the performance of your application, especially if you are

displaying a large amount of data in the planning layout.

You define the style of the planning layout and the number of rows displayed by default in Customizing

for Customer Relationship Management under Trade Promotion Management Key Figure Planning with the Planning

Applications Kit Define the Height of the Planning Layout .



24/62 CUSTOMER 2013-05-13

6.6.9 Using Optimized BI Content

To optimize performance, your BI Content model should follow that of the example BI Content

delivered by SAP.

For example, all queries should be based on a single provider. If it is necessary for operations to occur

on a MultiProvider, we recommend that you isolate this operation and only execute this one operation

on a MultiProvider. We recommend that you keep your single InfoProvider and MultiProvider

operations separate.

Disaggregation in the query should not be executed in the database if a key figure is restricted to multiple

values, such as several single values or intervals, for a given characteristic. For more information about

this restriction, see SAP Note 1637199.



2013-05-13 CUSTOMER 25/62


7 Migration from SAP Trade Promotion Management to SAP Accelerated Trade Promotion Planning

7.1 Functional Enhancements

The following table explains the functional enhancements in SAP Accelerated Trade Promotion

Planning compared with SAP Trade Promotion Management.

Feature

SAP Trade Promotion Management SAP Accelerated Trade Promotion Planning

Performance and database

Standard performance and database connection.

Enhanced performance and integration with SAP in-memory computing technology using the SAP HANA appliance software.

Planning profile group

A planning profile group contains a grouping of profiles that are defined in SAP NetWeaver Business Warehouse (SAP NetWeaver BW). This controls which layouts and key figures will appear in your planning layouts.

An integrated planning profile group contains a grouping of queries that are defined in SAP NetWeaver BW. This controls which layouts and key figures will appear in your planning layouts.

Multiple remote function call (RFC) destinations

All planning-relevant data for trade promotions, campaigns, deals, account plans, live rates, and validation sheets use BPS and connect to the standard SAP NetWeaver BW target system.

Trade promotions using SAP in-memory computing technology use an alternate SAP NetWeaver BW target system.

Time dimension Planning is done according to calendar month, calendar week, or

Planning is done according to calendar day or calendar week. Planning data is always stored at the level you are planning on but can be displayed in different time dimensions. For example, if you .


7.1 Functional Enhancements

2013-05-13 CUSTOMER 27/62

Feature

SAP Trade Promotion Management SAP Accelerated Trade Promotion Planningcalendar day. Planning data can be stored and displayed at the calendar month, week, or day level.

If you plan by day, you can display your planning information at the calendar month, week, or day level.

Multiple date ranges You can only synchronize one date range to the planning layout.

You can synchronize multiple date ranges to the planning layout, including buying dates, goods receipt dates, and other additional date ranges.

Eventing You can use a small set of BPS-based events and planning sequences.

You can use an eventing mechanism that offers increased flexibility in manipulating your planning data with the use of planning functions.

Business Add-Ins (BAdIs)

Planning-related BAdIs are available.

Some planning-related BAdIs are obsolete or have been replaced with a new BAdI definition or method. For more information, see Customizing for Customer Relationship Management under Trade Promotion Management Key Figure Planning with the Planning Applications Kit

Business Add-Ins (BAdIs) Changes to Planning-Related BAdIs .

7.2 Functional Restrictions

The following features are not supported in SAP Accelerated Trade Promotion Planning 2.0 compared

with SAP Trade Promotion Management:

■ Certain functions when using rates in SAP CRM, including the following:

● Take rates

● Off-invoice caps

● Tiered growth rebates

● Critical changes based on changes to spend values

● Trade promotion guidelines based on spend values

■ Free goods

■ Indirect trade promotions

■ Creating a trade promotion from a deal

■ Reverse key figure schemes

■ Product segment as product planning basis

■ Creating a trade promotion element from a trade promotion

■ Building a hierarchy of trade promotions

■ Uploading trade promotion management (TPM) data from non-SAP systems using SAP NetWeaver

Process Integration (SAP NetWeaver PI) technology



28/62 CUSTOMER 2013-05-13

■ Some features used to set up enhanced layouts with the Settings for Planning Services

(UPX_MNTN) transaction

■ Target group promotions with business partner hierarchy node explosion

■ Integration with deal planning

■ Integration with validation sheet

■ Integration with live rates

■ Integration with workflow

■ Integration with SAP Supply Chain Management (SAP SCM)

■ Integration with the Marketing Calendar

NOTE

Integration with the Integrated Marketing Calendar is supported

■ Trade promotion editable list

■ Display pallet promotions

■ Cell locking to restrict distribution

■ Key performance indicator (KPI) in trade promotion mass approval

■ Version history for SAP CRM

■ Volume maintenance in SAP CRM

■ KPI alerts and traffic lights (Key Performance Indicators assignment block)

■ Significant uplift

■ Purchasing trade spends

■ Layout pagination

■ Hiding columns in the planning layout by standard means

■ Changing the unit of measure of a product in the Products, Product Categories, and Product Groups

assignment blocks

■ Analysis assignment block

■ SAP CRM mobile client integration

■ Totals assignment block in edit mode

■ Custom WebClient UI skins



2013-05-13 CUSTOMER 29/62

8 BI Content Migration

This section describes functional enhancements and restrictions in the SAP Accelerated Trade

Promotion Planning application compared with SAP Trade Promotion Management for SAP

enhancement packages 1 and 2 for SAP Customer Relationship Management 7.0.

8.1 Objects Used for Key Figure Planning with BPS and Key Figure Planning with the Planning Applications Kit

The following table shows the objects that are used for key figure planning with BPS and key figure

planning with the planning applications kit:

Key Figure Planning with BPS Key Figure Planning with the Planning Applications Kit

Real-time InfoCubes are used for storing trade promotion planning data.

DataStoreObjects(DSO) are used for storing trade promotion planning data.

InfoCubes are used for storing baseline data.

DataStoreObjects are used for storing baseline data.

Planning areas based on InfoCubes are used to define data slices and characteristic relationships. Multi-planning areas that combine the characteristics and key figures of several planning areas can be used as well.

MultiProviders combine trade promotion and baseline data from several InfoProviders.

Planning levels are used for the selection of InfoObjects to be included in restrictions on data sets, and for the definition of planning functions and planning packages. Planning levels are used to set restrictions

Aggregation levels are used for the selection of InfoObjects to be included in restrictions on data sets, and for the definition of planning functions and filters. Aggregation levels are used to set restrictions on data sets that are used by queries or planning functions.


8.1 Objects Used for Key Figure Planning with BPS and Key Figure Planning with the Planning Applications Kit

2013-05-13 CUSTOMER 31/62

Key Figure Planning with BPS Key Figure Planning with the Planning Applications Kiton data sets that are used by the planning layouts or planning functions.

Planning packages are used to set further restrictions on data sets that are already restricted by planning levels.

Filters are used to set further restrictions on data sets that are already restricted by aggregation levels by setting values for characteristics.To make queries or planning functions reusable, you can use variables in filters to restrict characteristics instead of fixed values. Variables can have single values, multiple values, or intervals of values.A filter (restriction) defined on an aggregation level applies to all InfoObjects based on this aggregation level. A filter (restriction) defined on an aggregation level can be applied for different use cases, based on different data sets.

Planning layouts are based on planning levels and planning packages. Planning layouts are used for providing data records from InfoCubes for manual planning or data entry. Planning layouts can be enhanced to add calculation formulas, functions, and other features for presenting data. Planning profiles are used to set up user-specific selections of planning objects.

Queries are used instead of planning layouts and enhanced planning layouts.

More Information

For more information about BPS and the planning applications kit, see SAP Library for SAP NetWeaver

on SAP Help Portal at http://help.sap.com/netweaver. In SAP Library, choose SAP NetWeaver Library:

Function-Oriented View Business Warehouse Analytic Engine Planning Engine .

8.2 Setting Up Your Objects for Key Figure Planning with the Planning Applications Kit

The following topic identifies how to set up your BI Content Objects for planning with the planning

applications kit.


8.2 Setting Up Your Objects for Key Figure Planning with the Planning Applications Kit

32/62 CUSTOMER 2013-05-13


Setting Up DataStore Objects for Trade Promotion Planning Data

The minimum technological requirement for implementing SAP Accelerated Trade Promotion

Planning based on DataStoreObjects (DSO) is SAP NetWeaver BW 7.3 SP08.

1. Ensure that the RSADMINparameter RSPLS_DSO_PLANNING has value X.

2. Create a DSO with the following settings :

■ Type of DataStore Object = Direct Update

■ Plan Flag = X

Setting up DataStore Objects for Baseline Data

1. Ensure that the RSADMIN parameter RSPLS_DSO_PLANNING has value X.

2. Create a new DSO with the following settings :

■ Type of DataStore Object = Direct Update or Standard

■ Plan Flag = X

3. To enable the DSO for SAP Accelerated Trade Promotion Planning, in the SAP NetWeaver BW

system used for planning with the planning applications kit, execute the following reports:

■ RSDDB_LOGINDEX_CREATE

■ RSDRI_CONVERT_CUBE_TO_INMEMORY

Setting Up MultiProviders

1. Create a MultiProvider based on the following InfoProviders:

■ DSO for trade promotion planning data

■ DSO for baseline data

2. To define data slices and characteristic relationships, run transaction Planning-Specific Properties of an

InfoProvider (RSPLAN).

DataStore Object Key Field Ordering and Indexes

For performance reasons, when creating a DataStoreObject (DSO), the physical order of its key fields

should be ordered based on the selectivity of the characteristics being part of DSO key fields. The most

selected characteristics should be on the top of DSO key fields characteristics list. For the TPM planning

DSO, the most selected characteristic is CRM Marketing Element (Campaign and Marketing Plan)

(0CRM_MKTELM), therefore it is placed as the first field in the key fields list.

Moreover, indexes can be created over a DSO in order to increase the speed of data access. Be aware

that indexes increase the performance for reading the data but decrease the performance when writing

in a DSO. Indexes are also based on the most selected characteristics as part of a DSO key fields.

8.3 Setting Up Your Queries for SAP Accelerated Trade Promotion Planning

You can use the query Master: BPHN and PCat. & Prod(0TPM_AC03_IRQ0001) as a reference.



2013-05-13 CUSTOMER 33/62

Variables

You can restrict the use of characteristics by using variables. Variables allow you to reuse query objects.

You can use, for example, the characteristic Currency as a free characteristic in your planning, and you

can define a variable that acts as a placeholder for this characteristic value. The planning application

can transfer an appropriate value for the Currency variable (for example, EUR or USD) to the query. The

query restricts the data set and returns the combinations, taking into account only the expected

currency.

When you are setting up your queries for SAP Accelerated Trade Promotion Planning, you can use a

variable for the Trade Promotion ID characteristic to perform a lock on the data combinations related to

this promotion. You can use a variable for the Currency characteristic to perform the appropriate

aggregation related to the currency when a cell is updated during the planning process.

You can define variables in the Data Warehousing Workbench (RSA1) or in the BEx Query Designer. A variable

can have a single value, multiple single values, or a range of single values.

Key Figures

In the BEx Query Designer, you can specify if a key figure is displayed in the planning layout. You can

choose from the following options:

■ Always Show

The key figure is always displayed in the planning layout.

■ Always Hide

The key figure is always hidden in the planning layout.

■ Hide (Can Be Shown)

The key figure is hidden at design time, but can be displayed at runtime.

You can specify the number of decimal places for the value of a key figure, the scaling factor, and the

sign for the value of a key figure.

If you will use trade spend combinations with Percentage as the discount method, you must model a

unique key figure for each trade spend combination

Restricted Key Figures

In the BEx Query Designer, you can define restricted key figures at the aggregation level that can be

used across all queries defined on the same aggregation level.

From the InfoProvider, right-click the Key Figures structure and select New Restricted Key Figure. Every new

query that is created on the same InfoProvider will contain the same restricted key figures.

Default Values for Characteristics

In the BEx Query Designer, you can choose certain characteristics to behave as default characteristics

(part of the query dynamic filter). The SAP Accelerated Trade Promotion Planning application provides

the corresponding characteristic values before the execution of the query. Defaulting values for

characteristics is the default behavior when working with queries online (through APIs).



34/62 CUSTOMER 2013-05-13

Support of Compound Characteristics

The default delivery system will automatically adjust the required internal processes to function with

compound characteristics if the following prerequisites have been met:

1. The parent characteristic values are always single values for each trade promotion.

2. The parent characteristic value(s) are unique for each child characteristic value(s). There cannot

be a child characteristic with a different parent characteristic value(s) within the same trade

promotion.

For information about compounding, see SAP Library for SAP NetWeaver on SAP Help Portal at http://

help.sap.com/nw. In SAP Library, choose SAPNetWeaver Library: Function-Oriented View Business Warehouse

Data Warehousing Modeling Enterprise Data Warehouse Layer Creating InfoObject - Creating InfoObjects:

Characteristics Tab Page: Compounding

Example of a Compounded Characteristic

You can see characteristics using transaction RSD1. On the Compounding tab, you can see the relationship

between parent and child compound characteristics.

The values for the parent characteristics are automatically filled from the runtime query filter and

from the default values of the BEx Query Designer.

Runtime Query Filter

The application sends a runtime query filter during the synchronization process to check whether the

compound parent characteristics are included in the filter.

BEx Query Designer Default Values

If the runtime query filter does not contain the compounded parent value, then the BEx Query Designer

default values are read to determine if the characteristic value is available.

If neither the runtime query filter nor the BEx Query Designer contain the characteristic value, an

exception will occur. The same is true if more than one parent characteristic value is maintained for a

single parent characteristic.

In addition, the default values are combined with the query filter provided by the application from the

application data and sent to the SAP NetWeaver BW system. The default values from the BEx Query

Designer are only applied to the filter sent by the application if no existing characteristic is found in the

filter. For example, if the characteristic 0FISCVARNT is defined in the BEx query designer with a default

value of “K4”, this value will be added to the filter sent by the application if 0FISCVARNT cannot be

found within the filter. If the characteristic 0FISCVARNT is found in the filter sent by the application,

it will not be added at runtime.

Distribution of Key Figure Values

When you are setting up your queries for SAP Accelerated Trade Promotion Planning, you can specify

different types of distribution for the values of different key figures. You can choose from the following

types of distribution:



2013-05-13 CUSTOMER 35/62

http://help.sap.com/nw

http://help.sap.com/nw

■ Equal distribution

■ Analog distribution with a self-reference

■ Analog distribution with a reference to a given object

Display as Hierarchy

In the Query Designer, you can specify for each axis whether all objects on an axis (structures,

characteristics with or without display hierarchies) are displayed as individual hierarchies.

In the Query Designer, open a query and then click on the Rows or Columns tab page. The corresponding

properties dialog for the rows or columns is displayed in the Properties screen area. On the General tab

page, select Active under Display As Hierarchy. Under Expand to, you can choose up to which hierarchy

level the hierarchy is to drilled down in the initial view.

8.4 Time Dimension

You must use the time dimension Calendar Day (0CALDAY) in your DataStoreObjects and create data

sets with characteristic combinations that are on calendar day level. The SAP NetWeaver BW system

derives the time dimensions Calendar Week (0CALWEEK) and Calendar Month (0CALMONTH) from Calendar

Day (0CALDAY).

Also, you must ensure that the time interval used for trade promotion planning is within the time

interval defined in transaction RSRHIERARCHYVIRT.Otherwise, planning operations using SAP

NetWeaver BW cannot be executed.

8.5 Mapping Key Figures to Trade Spends

When using BPS, you were able to map two trade spend combinations with different discount methods

to a single key figure. With SAP Accelerated Trade Promotion Planning, you must map trade spend

combinations with the Percentage discount method to a unique key figure for percentages. No automatic

calculations for percentages will be carried out.

8.6 Suppression of Zero Rows

For planning and read queries, ensure that the effect on rows is set to active so that zeros are suppressed

for all values. This is useful for removing deleted records.

In the BEx Query Designer, under Rows/Columns, choose the following settings:

■ Suppress Zeros: Active (All Values = 0)

■ Effect on: Rows

This setting does not affect master queries.


8.4 Time Dimension

36/62 CUSTOMER 2013-05-13

8.7 Deletion of Records

During a deletion, for example, when products are removed from a trade promotion, or header

attributes of a trade promotion are changed, all corresponding planning records are removed from the

DSO.

8.8 Non-Aggregating Key Figures

The planning applications kit supports the non-aggregating key figures by using DataStore Objects

(DSO) as InfoProviders. The minimum technological requirement to implement non-aggregating key

figures with DataStoreObjects is SAP NetWeaver BW 7.3, SP 08.

A non-aggregating key figure must have the Exception Aggregation property set to value No aggregation (X,

If More Than One Value Occurs)and the Aggregation property set to value No aggregation (X, if more than one value

occurs) that can be defined in Characteristic Maintenance (RSD1).

For example, in SAP Accelerated Trade Promotion Planning, the cost, price, and variable trade spends

key figures must be defined as non-aggregating key figures.

8.9 Setting Restrictions to Period Types for Key Figures

Additional date ranges in SAP Customer Relationship Management (SAP CRM) are denoted by period

types in SAP NetWeaver BW. You map additional date ranges to period types in Customizing for Customer

Relationship Management under Marketing Marketing Planning and Campaign Management Basic Data Define

Additional Date Ranges . In SAP NetWeaver BW, you must restrict the values of the period types for the

key figures.

You use the Period Type characteristic (0PERIOD_TYP), which is used as a restriction for the key figures

that depend on specific date ranges. You create restricted key figures that are dependent on a date range

characteristic. Restricting key figures on certain values of the Period Type characteristic allows you to

specify if the respective key figures are input-ready and if they can receive the distribution of aggregated

values.

Note that for trade spend key figures, these date range restrictions should match the related date range

defined on the Relate Date Range view of the Define Trade Spends for Values Customizing activity. For more

information, see Customizing for Customer Relationship Management under Trade Promotion Management

Trade Promotions Trade Spends Define Trade Spends for Values .

The following table shows an example of the master data associated with the Period Type characteristic:

Period Type Period Type Description

50 Buying

95 Goods Receipt


8.7 Deletion of Records

2013-05-13 CUSTOMER 37/62

For example, you are using the Buying_KYF, Goods_Receipt_KYF, and Rebate_KYFkey figures for your

planning, and you want the following conditions to apply:

■ The Buying_KYF key figure to be ready for input and available for distribution when the value of

Period Type characteristic is Buying for a specific period of time

■ The Goods_Receipt_KYF key figure to be ready for input and available for distribution when the

value of Period Type characteristic is Goods Receipt for a specific period of time

■ The Rebate_KYF key figure to be ready for input and available for distribution when the value of

Period Type characteristic is Buying or Goods Receipt

This means that compared to the Buying_KYF and Goods_Receipt_KYF key figures, the Rebate_KYF key

figure has to be ready for input and available for distribution for the period of time covering both the

period of time used for the Buying_KYF key figure and the period of time used for the

Goods_Receipt_KYF key figure.

To achieve this in the BEx Query Designer, you must restrict the three key figures as follows:

■ For the Buying_KYF key figure, set the characteristic 0PERIOD_TYP to 50 (Buying)

■ For the Goods_Receipt_KYF key figure, set the characteristic 0PERIOD_TYP to 95 (Goods Receipt)

8.10 Key Figures Distribution Split

During the planning process, when you enter a cumulative key figure value in the highest level

aggregation position, the application applies a top-down distribution. The distribution is performed in

two steps;

1. The key figure value is equally distributed at the most granular time unit level, by calendar day.

2. The key figure values are aggregated at the next time unit level, by calendar week.

It is possible that the business weeks you are planning on do not have the same number of days. In this

case, the key figure value aggregation by calendar week can show different values for different calendar

weeks in the planning period.

This is the expected behavior of the application, as compared to planning with the BPS technology

where the top-down distribution of an aggregated key figure value is equally distributed per calendar

week even if the business weeks in the planning period do not have the same number of days.

Example

The following example illustrates the expected behavior of the top-down distribution of a cumulative

key figure value. Consider the planning period from Friday August 3, 2012 until Thursday August 16,

2012. This planning period spans 3 calendar weeks : Week 31, Week 32 and Week 33.

Planning PeriodKYF Value(Top Aggregated Level) Calendar Week

KYF Value(Subtotal 1) Calendar Day

KYF Value(Subtotal 2)

August 3rd, 2012-August 16th, 2012

140 31 30 August 3rd, 2012 10.00

August 4th, 2012 10.00

August 5th, 2012 10.00


8.10 Key Figures Distribution Split

38/62 CUSTOMER 2013-05-13

Planning PeriodKYF Value(Top Aggregated Level) Calendar Week

KYF Value(Subtotal 1) Calendar Day

KYF Value(Subtotal 2)

32 70 August 6th, 2012 10.00

August 7th, 2012 10.00

August 8th, 2012 10.00

August 9th, 2012 10.00

August 10th, 2012 10.00

August 11th, 2012 10.00

August 12th, 2012 10.00

33 40 August 13th, 2012 10.00

August 14th, 2012 10.00

August 15th, 2012 10.00

August 16th, 2012 10.00

8.11 Setting the Buying Pattern Key Figure

If you are using buying patterns, you must define a key figure that represents the buying pattern

percentage in the planning DSO. You define this key figure using transaction RSA1 (Data Warehousing

Workbench: Modeling). You must then map the key figure for buying patterns in Customizing for

Customer Relationship Management under Trade Promotion Management Key Figure Planning with the Planning

Applications Kit InfoObject Mapping Map Key Figure for Buying Patterns .

At runtime, the percentage values for distribution are assigned to the buying pattern key figure. The

buying pattern key figure is not displayed in the planning layout. The buying pattern key figure is a

placeholder for the percentage distribution of other key figures that represent business data. The buying

pattern key figure is of type Amount.

8.12 Read Queries

Read queries are used to retrieve planning data from SAP NetWeaver BW. The data that read queries

retrieve is then used for other purposes, such as for condition generation.

Make the following settings for read queries:

1. Set all characteristics that are used in the query as free characteristics, except for the Trade Promotion

ID (0CRM_MKTELM) characteristic that is used to get the highest aggregated view on the data.

2. Ensure that all characteristics in the query have the following default settings:

1. Access Type for Result Values = Posted Values

2. Filter Value Selection at Query Execution = Only Posted Values for Navigation

3. Make the following settings for all key figures in the query:

1. Change Data = Not Input-Ready (Not Relevant for Locking)

2. Hide=Hide (Can Be Shown)


8.11 Setting the Buying Pattern Key Figure

2013-05-13 CUSTOMER 39/62

The query properties Universal Display Hierarchy and External Hierarchy are not supported by the SAP

Accelerated Trade Promotion Planning application. Therefore, no data drilldown is supported, because

the data is only used for backend processing, and not for processing on the WebClient UI.

NOTE

When using the SOA read service or integrated marketing calendar query context for read queries,

different settings are required. For those query contexts, only the key figures should be added and

those key figures should have the Hide setting set to Always Shown. Read queries for all other query

contexts should be defined as described above.

8.13 Reporting Formulas

Reporting formulas in queries represent calculated key figures based on calculations involving persisted

key figures or other calculated key figures. You define key figure calculations, and the reporting

formulas show the results of the calculations. The results of reporting formulas are not persisted in

the database. Reporting formulas can either only display the result of key figure calculations as defined

in the formula, or they can allow you to change the operands in the formula.

Currently, SAP HANA does not support reporting formulas, and they are processed in ABAP. We

recommend that you use planning functions instead.

8.14 Context to Use for Read Queries

The planning data can be used for different purposes. For this reason, different read queries can be

defined and used depending on the context. The read queries are developed with the Business Explorer

Query Designer, but their use is determined using Customizing settings. The use of read queries is

summarized in the following table:

Application Area Query Context Customizing Path

Trade Promotion Planning Profiles

<*> = Generic EntryCONDITION = For Condition GenerationFUNDS = For FundsSOA_READ = For SOA Read Service (*)VOLUME = For Volume in the Spend Value Overview Assignment

Customer Relationship Management- Trade Promotion Management Key Figure Planning with the Planning Applications Kit Define Integrated Planning Profile Groups: Assign Read Queries

Integrated Marketing Calendar

Queries that retrieve the basic key figures to display in the Integrated Marketing Calendar views

Customer Relationship Management- Trade Promotion Management Key Figure Planning with the Planning Applications Kit Define Integrated Planning Profile Groups: Assign Read QueriesCustomer Relationship Management->Trade Promotion Management->Key Figure Planning with the Planning


8.13 Reporting Formulas

40/62 CUSTOMER 2013-05-13

Application Area Query Context Customizing PathApplications Kit->Integration with Integrated Marketing Calendar

Trade Promotion Totals assignment block

Query that retrieves the basic key figures to display in the Totals assignment block of a trade promotion.

Customer Relationship Management->Trade Promotion Management->Key Figure Planning with the Planning Applications Kit->Settings for Display of BW Key Figures->Define Query for Key Figures

(*) For the SOA_READ query context, all key figures should be read and therefore set with the property

Display-Hide = Always Show.

8.15 Planning Queries

Planning queries are used to access and update planning data from SAP NetWeaver BW. They are used

in the planning layout and only use dynamic filters (default values for the characteristics). SAP

Accelerated Trade Promotion Planning always changes the values of the characteristics dynamically

at runtime.

External hierarchies are not supported by the SAP Accelerated Trade Promotion Planning application.

SAP Accelerated Trade Promotion Planning supports universal display hierarchies.

Make the following settings for planning queries:

1. Make the following settings for all characteristics in the query:

■ Access Type for Result Values = Posted Values

■ Filter Value Selection at Query Execution = Posted Values

2. To make a query relevant for planning, select the Start Query in Change Mode checkbox, and set at

least one key figure as input-ready. The planning property “Aggregation” of the non-aggregating,

input-ready key figures should be set to value “Disaggregate” copy.

3. To display or hide a non-basic key figure (for example, a reporting formula) at runtime, enter a

technical name for it in the BEx Query Designer. For list price and net price list, the corresponding

reporting formulas must have the same technical name as the technical name for the basic key

figure. When you create the query for these key figures, the basic key figure must be below the

reporting formula in the key figure structure in the BEx Query Designer. A warning appears in

the BEx Query Designer that the same technical name is used twice. Ignore the warning and save

the query

If a basic key figure is used more than once in the BEx Query Designer and it is displayed or hidden

at runtime, it must have a BEx Query Designer technical name to uniquely identify it. If the basic

key figure is never displayed, it does not need a BEx Query Designer technical name.


8.15 Planning Queries

2013-05-13 CUSTOMER 41/62

8.16 Planning Function Types

Ensure that you have installed the following planning function types:

■ Deletion and Redistribution by Reference Data (0RSCRM_IMP_DEL_DISTR)

■ Set/Distribute Values (RSCRM_IMP_DIS_VALUE)

■ Time Shift (0RSCRM_IMP_TIMESHIFT)

■ Transfer DSO Data and Physically Delete Source Data (0RSPL_REPOST_DSO)

■ Repost (0RSPL_REPOST)

■ Set Key Figure Values (0RSPL_SET_VALUES)

■ Delete DSO Records (0RSPL_DELETE_DSO)

■ Delete (0RSPL_DELETE)

■ Generate Combinations (0RSPL_CREATE_CR)

■ Copy (Ignore Empty Records (0RSPL_COPY_NO_ZEROS)

■ Distribution by Reference Data (0RSPL_DISTR_REFDATA)

■ Distribution by Keys (0RSPL_DISTR_KEY)

NOTE

If you already have some of the above planning functions installed, re-install them to ensure that

you have the most recent version.

8.17 Planning Functions Based on Formula Extensions (FOX)

The planning functions based on FOX are of type Formula. They use regular FOX formulas or sequences

of FOX formulas based on the key figures that are available in the aggregation level on which the

planning functions are based. The step of the execution phase at runtime (for example, after

synchronization, after cell update, or before save) determines which formulas are executed. An eventing

mechanism is available, and the appropriate FOX formulas can be executed depending on the execution

phase. Using the Define Events for Query (RSCRM_EVENTCUST) transaction in SAP NetWeaver BW, you

can assign FOX formulas to events. For more information, see Customizing for Customer Relationship

Management under Trade Promotion Management Key Figure Planning with the Planning Applications Kit Define

Events for Queries .

8.18 Example Code for Simple Calculations with FOX

The following example shows code for a planning function of type FOX. Note that this code must be

adapted to correspond with your BI Content modeling.

This example code occurs after the synchronization of the planning layout with data from SAP

NetWeaver BW. It retrieves baseline data, performs calculations using data from the key figures, and

updates other relevant key figures accordingly.


8.16 Planning Function Types

42/62 CUSTOMER 2013-05-13

For example, you could include a calculation for total volume that adds the value of the uplift key

figure to the value of the base quantity key figure.

SYNTAX

DATA LV_PT TYPE 0PERIOD_TYP.

DATA L_BASE TYPE F.

DATA LV_INV_QTY TYPE F.

DATA LV_PRC_LST TYPE F.

DATA LV_PARVEN TYPE F.

DATA LV_PANETRV TYPE F.

DATA LV_BUDGET TYPE F.

LV_PT = OBJV().

* Only for Period Types Pre-Dip, Buying and Post-Dip

IF LV_PT = '30' OR LV_PT = '50' OR LV_PT = '70'.

LV_INV_QTY = { 0UPLI_QTYS } + { 0BASE_QTYS }.

{ 0INV_QTY } = LV_INV_QTY.

ENDIF.

LV_PRC_LST = { 0PRICELIST }.

{0CRM_OFFINV } = { 0BON_OIPSU } * LV_PRC_LST.

{0CRM_BONPRO } = { 0OFFR_DSCNT } + { 0CRM_OFFINV } + { 0EDLP_OINV }.

{0CRM_BBACK } = { 0BON_BBP } * LV_PRC_LST.

{0CRM_BONSAL } = { 0BON_SHSU } + { 0CRM_BBACK } + { 0EDLP_VARI }.

{0OFFR_DSCNT } = { 0CRM_BONPRO } * LV_INV_QTY.

{0BONUS_SHIP } = { 0CRM_BONSAL } * LV_INV_QTY.

{0BONUS_SCAN } = { 0BON_SCSU } * { 0SCAN_QTY }.

{0BUDGET } = { 0BONUS_DISP } + { 0BON_SCSU } * { 0SCAN_QTY }.

LV_BUDGET = { 0BUDGET }.

{0COPAREVEN } = LV_PRC_LST * LV_INV_QTY.

LV_PARVEN = { 0COPAREVEN }.

{0REG_REVE } = LV_PRC_LST * { 0BASE_QTYS }.

{0COPANETRV } = { 0REG_REVE } - LV_BUDGET.

LV_PANETRV = { 0COPANETRV } .

{0PROPUNIT } = { 0PROMPRICE } / { 0PROUNIT }.

{0CRM_ROIPER } = LV_PANETRV / LV_BUDGET.

{0CRM_CPC } = LV_BUDGET / LV_INV_QTY.

{0CRM_CPIC } = LV_BUDGET / { 0UPLI_QTYS }.


8.18 Example Code for Simple Calculations with FOX

2013-05-13 CUSTOMER 43/62

FOX is capable of combining all calculations in a single execution. We recommend that you put all

calculations in a single FOX execution to minimize the number of planning functions executed at

runtime and increase the performance throughput.

8.19 Baseline Data Retrieval Technology

Baseline is the volume of sales that a customer can expect during a period when no trade promotions

are running.

The baseline DSO contains granular data that can be retrieved using the dimensions (for example, time,

product, product hierarchy level, product group, business partner, business partner group level, or

unit of measure) available in the MultiProvider that contains the baseline DSO and the TPM planning

DSO.

Example 1

When planning by product at the business partner level, the FOX planning function uses the values of

the Product and the Business Partner characteristics to retrieve and aggregate the baseline data. This data is

then stored in the TPM planning DSO in a dedicated key figure for baseline data. To achieve this, the

technology used in based on Formula Extension (FOX) planning functions.

Example 2

When planning by product category at the business partner level, the application passes the category

levels of the products with data in the baseline DSO and uses the Product Hierarchy levels characteristics.

The FOX planning function reads and aggregates the baseline data for all products that belong to that

product category level and have data in the baseline DSO. The selection of the other characteristics

(for example, planning by time and unit of measure) applies to the FOX planning function.

Example 3

When planning by product category at the business partner hierarchy node level, the application passes

the business partner hierarchy node level of the business partners that have data in the baseline InfoCube

to the FOX planning function and uses the Business Partner Group levels characteristics. In the meantime,

the application passes the Product Hierarchy levels of the products with data in the baseline InfoCube using

the Product Hierarchylevels characteristics.

The FOX planning function reads and aggregates the baseline data for all business partners that belong

to the planning business partner hierarchy node level and have data in the baseline DSO, as well as the

baseline data for all products that belong to the planning product category level and have data in the

baseline DSO. The results will be aggregated by product and business partner hierarchy node.

The selection of other characteristics (for example, planning by time and unit of measure) applies to

the FOX planning function as well.

The figure below illustrates an account hierarchy (business partner hierarchy) with two levels:



44/62 CUSTOMER 2013-05-13

Figure 2: SAP CRM Account Hierarchy

SAP CRM Account Hierarchy

Account Hierarchy R3-CRM-01 Account Hierarchy Description

300010/30203000A REMA US Inc. / 1030 / BROOMALL PA 19008

300011/30203000A REMA DC West / 1030 / CARLSBAD CA 92008

300012/30203000A REMA DC East / 1030 / HOCKESSIN DE 19707

In SAP NetWeaver BW, account hierarchies can be modeled with the Business Partner Group (0BP_GRP)

InfoObject (business partner hierarchy node level) and its occurrences from level 1 to level 7

(0BP_GRP_A01, 0BP_GRP_A02, 0BP_GRP_A03) or the Business Partner (0BPARTNER) InfoObject.

The Business Partner Group (0BP_GRP) characteristic contains the master data that represents each node

and leaf of the account hierarchy (GUID and description).

InfoObject ‘0BP_GRP‘ – Master Data

BP: Group (Hierarchy) Description

46E028ED001A045BE10000000A421474 REMA US Inc. / PO Box 1030 / BROOMALL PA

46E028F0001A045BE10000000A421474 REMA DC West / PO Box 1030 / CARLSBAD CA

46E028F3001A045BE10000000A421474 REMA DC East / PO Box 1030 / HOCKESSIN D

The Business Partner Hierarchy Node levels are used to extract baseline data from the baseline InfoCube.

InfoObject ‘0BPARTNER‘ – Master Data (present here with 3 out of 3 levels):



2013-05-13 CUSTOMER 45/62

Business Partner (BP) BP Group Level 1 BP Group Level 2 BP Group Level 3 Description

300010 46E028ED001A045BE10000000A421474 00000000000000000000000000000000 00000000000000000000000000000000 REMA US Inc.

300011 46E028ED001A045BE10000000A421474 46E028F0001A045BE10000000A421474 00000000000000000000000000000000 REMA DC West

300012 46E028ED001A045BE10000000A421474 46E028F3001A045BE10000000A421474 00000000000000000000000000000000 REMA DC East

In the baseline DSO, the data is stored at the most granular level based on account (business partner),

account hierarchy level, product, product hierarchy level, sales unit of measure, and calendar day

characteristics. A user may want to plan at the account hierarchy node level (for example, to plan for

REMA US Inc. in the above example). To be able to execute joins between the planning DSO and the

baseline DSO, SAP NetWeaver BW needs data at the same granulation level from the application side.

Therefore, an application planning at account hierarchy node level has to send SAP NetWeaver BW

the selection filter filled with account hierarchy node level values along with the selection criteria (such

as product, product hierarchy level, unit of measure, or time). This filter is passed to a planning function

that reads baseline data from the baseline InfoCube, aggregating it at the application planning level,

and storing it in the dedicated key figure for baseline in the planning InfoCube.

Also, you may need to implement method IS_REFERENCE_DATA_ACTIVE of BAdI: Modification of

Planning Behavior (CRM_MKTPL_IMP_TPM) to enhance the query filter in order to select all the necessary

baseline data. For more information, see Customizing for Customer Relationship Management under

Trade Promotion Management Key Figure Planning with the Planning Applications Kit Business Add-Ins BAdI:

Modification of Planning Behavior .

In the current example, when the user plans at account hierarchy level 2 (REMA DC West), the

application has to send the following value in the query to the planning function:

Business Partner Node Level Value (GUID)

0BP_GRP_A02 46E028F0001A045BE10000000A421474

In the SAP NetWeaver BW system, you can use the transaction RSCRM_EVENTCUST to determine the

execution sequence for certain actions in SAP NetWeaver BW, depending on the leading SAP CRM

application events that can occur. Before the application executes a query against the SAP NetWeaver

BW system, the planning DSO baseline key figure has to be updated by the planning function with the

last available data from the baseline DSO. Therefore, the execution sequence is to trigger the planning

function that updates the baseline data in the planning DSO. The query is executed against the updated

planning DSO.

The following table identifies the InfoProviders provided with the standard BI Content.



46/62 CUSTOMER 2013-05-13

InfoProvider Name Description Type Source Data Targets

0TPM_DS01 Sales and Trade Promotions(This is the TPM Planning Cube.)

Data Store Object with direct-update setting

Planning 0TPM_AC040TPM_MC02

0TPM_DS02 TPM Base Sales Quantity(This is the baseline cube.)

Real Time Info Cube DSO 0TPM_MC02

0TPM_MC02 Baseline/TPM MultiProvider MultiProvider 0TPM_DS010TPM_DS02

0TPM_AC04

0TPM_AC04 Baseline for Prod-PCat@BPHN Aggregation Level 0TPM_MC02 Queries and Planning Functions

0TPM_AC03 Sales and TPM for Prod-PCat@BPHN

Aggregation Level 0TPM_DS01 Queries, Planning Functions, and Reports

Baseline Planning Scenario

Planning Scenario Master Query Planning Queries Read Query Planning Function

Planning on Product and Product Category at Business Partner Hierarchy Node Level

Master: BPHN and PCat. & Prod.0TPM_AC03_IRQ0001

Planning by Prod. Cat. & Prod.0TPM_AC03_IRQ00020TPM_AC03_IRQ0004(for CRM RATES)

TPM Read Query0TPM_DS01_Q0003

Execute All Formulas for Prod.Categ-Prod @BPHN0TPMIMP_PCPRD_BPHN_D

8.20 Example Code for Baseline Data Retrieval with FOX

This example code occurs after the synchronization of the planning layout with data from SAP

NetWeaver BW. It retrieves baseline data and updates the relevant baseline key figures accordingly.

The example code is an excerpt from the delivered planning function 0TPMIMP_PCPRD_BPHN_D and

illustrates the baseline retrieval. The code comments explain the technique used to retrieve the baseline

data in detail. Please note that every time the statement IN REFDATA is used, it refers to the baseline

DSO.

EXAMPLE

The following is an example of the logic behind the baseline data extraction process:

START PLANNING FUNCTION:

LOOP: Scan all Planning Products passed by the application

Finds the related planning period type and keeps only the planning DSO entries corresponding to three planning period types

(Buying, Pre-Dip and Post-Dip)



2013-05-13 CUSTOMER 47/62

IF the current Planning Product is initial (Not Assigned = ‘#’)

LOOP: Lookup for the baseline (reference) DSO entries grouped by characteristics 0BP_GRP_A01, 0BP_GRP_A02,

0BP_GRP_A03 and 0CRM_PR_A01, 0CRM_PR_A02, 0CRM_PR_A03, 0CRM_PR_A04,

0CRM_PR_A05.

Get the current planning product category from the planning DSO

IF the current planning product category is the same as one of the product category levels in the baseline(reference) DSO

for the current baseline entry

Get and aggregate the baseline data in a local variable.

ENDIF.

ENDLOOP.

ELSE the current planning product is NOT initial so the planning is done on product

LOOP: Lookup for the baseline (reference) DSO entries grouped by characteristics 0BP_GRP_A01, 0BP_GRP_A02,

0BP_GRP_A03 and 0CRM_PR_A01, 0CRM_PR_A02, 0CRM_PR_A03, 0CRM_PR_A04,

0CRM_PR_A05.

IF the current planning product has the same value as the product in the baseline(reference) DSO entry

Get and aggregate the baseline data in a local variable

ENDIF.

ENDLOOP.

ENDIF.

ENDLOOP.

At this point you have the aggregated baseline key figure values for all the planning data.

END PLANNING FUNCTION.

SYNTAX

DATA LV_PT TYPE 0PERIOD_TYP.

DATA LV_PROD TYPE 0CRM_PROD.

DATA LV_REF_PROD TYPE 0CRM_PROD.

DATA LV_REF_BP01 TYPE 0BP_GRP_A01.



DATA LV_PCAT TYPE 0PR_CAT_SAL.

DATA LV_REF_PR01 TYPE 0CRM_PR_A01.





DATA LV_TP_BASELINE TYPE I.

DATA L_BASE TYPE F.



48/62 CUSTOMER 2013-05-13

DATA LV_INV_QTY TYPE F.

DATA LV_PRC_LST TYPE F.

DATA LV_PARVEN TYPE F.

DATA LV_PANETRV TYPE F.

DATA LV_BUDGET TYPE F.

* In planning DSO (TPM)

FOREACH LV_PROD.

* Get the current Period Type (Planning DSO)

LV_PT = OBJV().

* Only retreiving Baseline data for following Period Types

IF LV_PT = '30' OR LV_PT = '50' OR LV_PT = '70'.

IF LV_PROD = #.

* Product is initial; Current planning data is Planning on PCat only

LV_TP_BASELINE = 0.

*Loop by Business Partner Hierarchy Nodes, Product and Product Hierarchy Levels (in Baseline

DSO)

FOREACH LV_REF_BP01, LV_REF_BP02, LV_REF_BP03, LV_REF_PROD, LV_REF_PR01,

LV_REF_PR02, LV_REF_PR03, LV_REF_PR04, LV_REF_PR05 IN REFDATA.

*Get the current Product Category (from planning DSO)

LV_PCAT = OBJV().

* Process only the current Product ( from Baseline DSO) if it is present on

* a Product Hierarchy level of the current Product Category (Planning DSO)

IF LV_PCAT = LV_REF_PR01 OR

LV_PCAT = LV_REF_PR02 OR



LV_PCAT = LV_REF_PR05.

* If the Product belongs to the planning PCat, add up the Baseline value

L_BASE = { 0BASE_QTYS, LV_REF_BP01, LV_REF_BP02, LV_REF_BP03, LV_REF_PROD,

LV_REF_PR01, LV_REF_PR02, LV_REF_PR03, LV_REF_PR04, LV_REF_PR05 | 0CALWEEK = #,

0BP_GRP = #, 0CRMVERSION = #, 0CRM_MKTELM = #, 0CRM_SALORG = #, 0CURRENCY

= #, 0DISTR_CHAN = #, 0DIVISION = #, 0INFOPROV = 0TPM_DS02, 0PERIOD_TYP = #,

0PR_CAT_SAL = #, 0FISCVARNT = #, 0FISCPER = # }.

LV_TP_BASELINE = LV_TP_BASELINE + L_BASE.

ENDIF.

ENDFOR.

ELSE.

LV_TP_BASELINE = 0.



2013-05-13 CUSTOMER 49/62

FOREACH LV_REF_BP01, LV_REF_BP02, LV_REF_BP03, LV_REF_PROD, LV_REF_PR01,

LV_REF_PR02, LV_REF_PR03, LV_REF_PR04, LV_REF_PR05 IN REFDATA.

IF LV_REF_PROD = LV_PROD.

* Product isn't initial; Planning on Product

L_BASE = { 0BASE_QTYS, LV_REF_BP01, LV_REF_BP02, LV_REF_BP03, LV_PROD,

LV_REF_PR01, LV_REF_PR02, LV_REF_PR03, LV_REF_PR04, LV_REF_PR05| 0CALWEEK = #,

0BP_GRP = #, 0CRMVERSION = #, 0CRM_MKTELM = #, 0CRM_SALORG = #, 0CURRENCY

= #, 0DISTR_CHAN = #, 0DIVISION = #, 0INFOPROV = 0TPM_DS02, 0PERIOD_TYP = #,

0PR_CAT_SAL = #, 0FISCVARNT = #, 0FISCPER = # }.

LV_TP_BASELINE = LV_TP_BASELINE + L_BASE.

ENDIF.

ENDFOR.

ENDIF.

* Using the calculated Baseline, coming from the given Baseline data(Planning on Product) * or

multiple reference Products( Planning on PCAT)

{ 0BASE_QTYS, #, #, #, LV_PROD, #, #, #, #, # } = LV_TP_BASELINE.

LV_INV_QTY = { 0UPLI_QTYS, #, #, #, LV_PROD, #, #, #, #, # } + LV_TP_BASELINE.

{ 0INV_QTY, #, #, #, LV_PROD, #, #, #, #, # } = LV_INV_QTY.

* Performing calculation for other keyfigures

LV_PRC_LST = { 0PRICELIST, #, #, #, LV_PROD, #, #, #, #, # }.

{ 0CRM_OFFINV, #, #, #, LV_PROD, #, #, #, #, # } = { 0BON_OIPSU, #, #, #, LV_PROD, #,

#, #, #, # } * LV_PRC_LST.

{ 0CRM_BONPRO, #, #, #, LV_PROD, #, #, #, #, # } = { 0OFFR_DSCNT, #, #, #, LV_PROD,

#, #, #, #, # } + { 0CRM_OFFINV, #, #, #, LV_PROD, #, #, #, #, # } + { 0EDLP_OINV, #, #,

#, LV_PROD, #, #, #, #, # }.

{ 0CRM_BBACK, #, #, #, LV_PROD, #, #, #, #, # } = { 0BON_BBP, #, #, #, LV_PROD, #, #,

#, #, # } * LV_PRC_LST.

{ 0CRM_BONSAL, #, #, #, LV_PROD, #, #, #, #, # } = { 0BON_SHSU, #, #, #, LV_PROD, #,

#, #, #, # } + { 0CRM_BBACK, #, #, #, LV_PROD, #, #, #, #, # } + { 0EDLP_VARI, #, #, #,

LV_PROD, #, #, #, #, # }.

{ 0OFFR_DSCNT, #, #, #, LV_PROD, #, #, #, #, # } = { 0CRM_BONPRO, #, #, #, LV_PROD,

#, #, #, #, # } * LV_INV_QTY.

{ 0BONUS_SHIP, #, #, #, LV_PROD, #, #, #, #, # } = { 0CRM_BONSAL, #, #, #, LV_PROD,

#, #, #, #, # } * LV_INV_QTY.

{0BONUS_SCAN, #, #, #, LV_PROD, #, #, #, #, # } = { 0BON_SCSU, #, #, #, LV_PROD, #,

#, #, #, # } * { 0SCAN_QTY, #, #, #, LV_PROD, #, #, #, #, # }.



50/62 CUSTOMER 2013-05-13

{0BUDGET, #, #, #, LV_PROD, #, #, #, #, # } = { 0BONUS_DISP, #, #, #, LV_PROD, #, #,

#, #, # } + { 0BON_SCSU, #, #, #, LV_PROD, #, #, #, #, # } * { 0SCAN_QTY, #, #, #,

LV_PROD, #, #, #, #, # }.

LV_BUDGET = { 0BUDGET, #, #, #, LV_PROD, #, #, #, #, # }.

{ 0COPAREVEN, #, #, #, LV_PROD, #, #, #, #, # } = LV_PRC_LST * LV_INV_QTY.

LV_PARVEN = { 0COPAREVEN, #, #, #, LV_PROD, #, #, #, #, # }.

{ 0REG_REVE, #, #, #, LV_PROD, #, #, #, #, # } = LV_PRC_LST * LV_TP_BASELINE.

{ 0COPANETRV, #, #, #, LV_PROD, #, #, #, #, # } = { 0REG_REVE, #, #, #, LV_PROD, #,

#, #, #, # } - LV_BUDGET.

LV_PANETRV = { 0COPANETRV, #, #, #, LV_PROD, #, #, #, #, # } .

{ 0PROPUNIT, #, #, #, LV_PROD, #, #, #, #, # } = { 0PROMPRICE, #, #, #, LV_PROD, #, #,

#, #, # } / { 0PROUNIT, #, #, #, LV_PROD, #, #, #, #, # }.

{ 0CRM_ROIPER, #, #, #, LV_PROD, #, #, #, #, # } = LV_PANETRV / LV_BUDGET.

{ 0CRM_CPC, #, #, #, LV_PROD, #, #, #, #, # } = LV_BUDGET / LV_INV_QTY.

{ 0CRM_CPIC, #, #, #, LV_PROD, #, #, #, #, # } = LV_BUDGET / { 0UPLI_QTYS, #, #, #,

LV_PROD, #, #, #, #, # }.

ENDIF.

ENDFOR.

8.21 BAdI’s in SAP NetWeaver BW

The following BAdI’s in SAP NetWeaver BW provide the ability to manipulate the filters associated with

each related process.

BAdI: Modification of Planning Functions (RSCRM_IMP_EVT_PLANNING_FUNCT)

Eventing allows the application to customize any planning function to be triggered during any of the

following execution points:

■ AFTER SYNCHRONIZE:

At the end of the synchronization, after all the standard logic is executed

■ BEFORE SAVE

Prior to saving the application data

■ AFTER UPDATE CELL

After a cell value is disaggregated

■ MANUAL EVENT

If triggered from the planning layout by selecting it from a drop down list box, this event executes

one or more planning functions. You can customize up to 10 different events.

Each event can execute more than one planning function. You must maintain a sequence number to

determine the sequence of this execution.



2013-05-13 CUSTOMER 51/62

For example, you can use the AFTER_SYNCHRONIZE event to execute a formula planning function

to read baseline data into the trade promotion InfoCube and use the AFTER UPDATE CELL event to

further perform simpler calculations only needed for the UI when entering values.

For more information, see the BAdI documentation assigned to the BAdI definition in the SAP

NetWeaver BW system.

BAdI: Determination of Values for Query Execution (RSCRM_IMP_QUERY)

Before executing the query, you can adjust the runtime filter sent by the application and add variables

or additional values.

For example, if your BI Content includes more than one planning InfoCube, you can use this BAdI to

specify, in the runtime filter, the InfoProvider to be used for a given trade promotion. For more

information, see the BAdI documentation assigned to the BAdI definition in the SAP NetWeaver BW

system.

BAdI: Filter for Standard Planning Functions (RSCRM_IMP_STD_PLANNING_FUNCT)

The following planning functions are executed by the system to process the application data:

■ Generate Combinations

Based on the characteristic relationships the application sets at runtime, this planning function

creates the relevant valid combinations of characteristics. These combinations will be processed by

subsequent planning functions.

■ Set Key Figure Values

This planning function sets the key figure layout indicator with the value of 1 to represent the set

of records that are valid when they are persisted in the InfoCube and to overcome the query record

suppression of deleted records.

For example, if the application wants to set a characteristic value of 100 for every record in SAP

NetWeaver BW, but the system does not do this automatically, the standard planning function

can be used to restrict this characteristic to a particular value. Generating combinations

automatically sets this value to every valid record the application creates at runtime. This

characteristic would not have to be part of the list of characteristics mapped by the application.

Another example scenario would be to restrict the InfoProvider characteristic0INFOPROV to the

application real-time InfoProvider that is currently being processed based on the filter information

sent by the application. This will prevent the generation of invalid combinations on an InfoProvider

that is not applicable. Two InfoProviders can be separated based on the sales organization: for

example, the planning data of one organization may be stored in the InfoProvider DSO1 while the

data of another sales organization is saved in the InfoProvider DSO2. When the application is

planning in the first sales organization, all the data should be saved in the InfoProvider DSO1 and

not DSO2. This can be achieved by restricting the InfoProvider characteristic.

For more information, see the BAdI documentation assigned to the BAdI definition in the SAP

NetWeaver BW system.



52/62 CUSTOMER 2013-05-13

8.22 Configuring Extensibility

For information about configuring extensibility, see SAP Help Portal at http://help.sap.com/

crmaddons SAP Accelerated Trade Promotion Planning . UnderApplication Help, open SAP Library and choose

SAP Accelerated Trade Promotion Planning Setting Up SAP Accelerated Trade Promotion Planning Configuring

Extensibility for SAP Accelerated Trade Promotion Planning .

8.23 Example of BI Content with BPS

The following is an example of BI Content you use for planning with BPS, followed by an example of

the BI Content you must use for planning with the planning applications kit if you want to achieve

the same planning use case.

InfoObjects Used for Key Figure Planning with BPS

Real-Time InfoCube PC1

InfoObject Type

CHA01 Characteristic


CHA03 Characteristic (has CHA05 as a navigation attribute)


CHA05 Characteristic (is a navigation attribute for CHA03)

KYF01 Key figure

KYF02 Key figure

KYF03 Key figure

KYF04 Key figure

KYF05 Key figure

InfoCube SC

The following table shows the InfoObjects of InfoCube SC (for the baseline data):

InfoObject Type




BKYF Key figure

Planning Areas

The following table shows the planning areas and their corresponding InfoCubes:

Planning Area InfoCube

PLA_PC PC1

PLA_SC SC


8.22 Configuring Extensibility

2013-05-13 CUSTOMER 53/62



Multi-Planning Area

The following table shows the planning areas of multi-planning area MPA_PC:

Multi-Planning Area Planning Areas

MPA_PC PLA_PCPLA_SC

Planning Levels

The following table shows the planning levels and their corresponding planning areas:

Planning Level Planning Area

PLL_PC PLA_PC

PLL_SC PLA_SC

Planning Level PLL_PC

The following table shows the InfoObjects of planning level PLL_PC:

InfoObject Type






KYF01 Key figure

KYF02 Key figure

KYF03 Key figure

KYF04 Key figure

KYF05 Key figure

Planning Level PLL_SC

The following table shows the InfoObjects of planning level PLL_SC:

InfoObject Type




BKYF Key figure

Ad Hok Package AHP_PC

Ad hoc package AHP_PC is based on planning level PLL_PC. The following table shows the InfoObjects

of ad hoc package AHP_PC:

InfoObject Type





54/62 CUSTOMER 2013-05-13

InfoObject Type




Planning Layout

Planning layout LAY_PC is based on planning level PLL_PC. The following table shows the InfoObjects

of planning layout LAY_PC:

InfoObject Type Position Display Mode

CHA01 Characteristic Lead column Displayed



CHA04 Characteristic Header Hidden

CHA05 Characteristic Header Hidden

KYF01 Key figure Data column Displayed





The following table shows the key figures of enhanced planning layout LAY_PC:

Row Key Figure Type Operand Operator Operand Details

10 BKYF Function 0 - 0 Uses a function module to retrieve data based on the join between planning area PLA_SC and planning level PLL_SC

20 KYF01 Basic key figure 0 - 0 -





70 CKYF01 Calculated key figure KYF02 * KYF03 -

80 CKYF02 Calculated key figure BKYF + KYF05 -

Planning Profile

The following table shows the planning areas of planning profile PPROF:

Planning Profile Planning Areas

PPROF PLA_PCPLA_SC



2013-05-13 CUSTOMER 55/62

8.24 Example of BI Content with the Planning Applications Kit

The following is an example of BI Content you use for planning with the planning applications kit if

you want to achieve the same planning use case as the previous example of BI Content used with BPS.

InfoObjects Used for Key Figure Planning with the Planning Applications Kit

Direct Update DSO PS2

The following table shows the InfoObjects of direct-update DSO PC2 (for the trade promotion planning

data):

InfoObject Type






KYF01 Aggregating key figure





NKYF01 Non-aggregating key figure

NKYF02 Non-aggregating key figure

The following table shows the InfoObjects of DSO PC3 (for the baseline data):

InfoObject Type




BKYF Key figure

MultiProvider MC

The following table shows the InfoProviders of MultiProvider MC:

InfoProvider Type

PC2 Direct-update DSO

PC3 DSO

The following table shows the InfoObjects and the DSOs the InfoObjects are assigned to:

InfoObject DSO

CHA01 PC2, PC3

CHA02 PC2, PC3

CHA03 PC2, PC3



56/62 CUSTOMER 2013-05-13

InfoObject DSO

CHA04 PC2

CHA05 PC2

BKYF PC3

KYF01 PC2

KYF02 PC2

KYF03 PC2

KYF04 PC2

KYF05 PC2

QKYF01 PC2

QKYF02 PC2

KKYF PC2

Aggregation Level AGG_MC

Aggregation level AGG_MC is based on InfoProvider MC. The following table shows the InfoObjects

of aggregation level AGG_MC:

InfoObject Type











NKYF01 Nog-aggregating key figure

NKYF02 Nog-aggregating key figure

BKYF Aggregating key figure

Query QRY01

Query QRY01 is based on aggregation level AGG_MC. The following table shows the InfoObjects of

query QRY01:

Area in the BEx Query Designer InfoObject Properties

Filter → Default Values CHA01 -







2013-05-13 CUSTOMER 57/62

Area in the BEx Query Designer InfoObject Properties

Free Characteristics CHA03 -



Rows CHA01 Drill down

Rows CHA02 -

Columns BKYF Not Input-Ready aggregating key-figure

Columns KYF01 Input-Ready aggregating key-figure





Columns NKYF01 Non-aggregating key-figure

Columns NKYF01 Non-aggregating key-figure

Planning Functions

Planning functions PLF_01 and PLF_02are based on aggregation level AGG_MC.

The following table shows the key figure of planning function PLF_01:

Type Key Figure Operand Operator Operand

Formula extension (FOX) KYF01 KYF02 * KYF03

The following table shows the key figure of planning function PLF_02:

Type Key Figure Operand Operator Operand

Formula extension FOX KYF02 BKYF + KYF05

NOTE

When you activate your BI Content, you must activate the following planning function types in

transaction Data Warehousing Workbench: BI Content (RSA1) in SAP NetWeaver BW:

■ Deletion and Redistribution by Reference Data (0RSCRM_IMP_DEL_DISTR)

■ Set/Distribute Values (0RSCRM_IMP_DIS_VALUE)

■ Time Shift (0RSCRM_IMP_TIMESHIFT)

To activate the planning function types in transaction RSA1, do the following:

1. In the left-hand pane, choose BI Content Object Type .

2. In middle pane, under All Objects According to Type, choose Planning Function Type for Planning Select

Objects .

3. Double-click on Select Objects to view the list of planning function types.

4. Select the planning functions to activate and choose the Transfer Selections pushbutton.



58/62 CUSTOMER 2013-05-13

Typographic Conventions

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>”.

ExampleExample

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

http://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

2013-05-13 CUSTOMER 59/62

http://www.sap.com



SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

© Copyright 2013 SAP AG. 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 AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the United States and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries.Oracle and Java are registered trademarks of Oracle and its affiliates.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems Inc.HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.IOS is a registered trademark of Cisco Systems Inc.RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited.Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc.INTERMEC is a registered trademark of Intermec Technologies Corporation.Wi-Fi is a registered trademark of Wi-Fi Alliance.Bluetooth is a registered trademark of Bluetooth SIG Inc.Motorola is a registered trademark of Motorola Trademark Holdings LLC.Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company.

60/62 CUSTOMER 2013-05-13

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company.All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components.Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.

Documentation in the SAP Service MarketplaceYou can find this document at the following address: http://service.sap.comhttp://service.sap.com/instguidesinstguides

2013-05-13 CUSTOMER 61/62

http://service.sap.comhttp://service.sap.com/instguidesinstguides

http://service.sap.comhttp://service.sap.com/instguidesinstguides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

© Copyright 2013 SAP AG. 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 AG. The information contained herein may be changed without prior notice.

sap accelerated tpm planning 2.0

Documents

key figure planning

planning queries

planning functions

planning layout

sap trade promotion

monitoring of trade

planning applications

planning function types