SAP Accelerated TPM Planning 2.0

Administrator's Guide SAP Accelerated Trade Promotion Planning 2.0 Using SAP Customer Relationship Management 7.0, Enhancement Packages 1 and 2 Target Audience Hßó0łP Consultants Hßó0łP Administrators Hßó0łP Others CUSTOMER HßóÔ¾lxUëö‘…~qɽÕ“OŽ®<†¾¼Ú'¦JíF¼ioé“þ2ý–Èé78Ì«YdA·šâµk
G†N 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 1.10 1.20 1.30 1.40 2012-09-19 2012-10-04 2012-12-06 2013-03-07 2013-05-13 Initial Version Included BI Content Migration Chapter Minor updates related to release of SP01 Minor updates related to release of SP02 Minor updates related to release of SP03 2/62 CUSTOMER 2013-05-13 Table of Contents Chapter 1 1.1 1.2 1.2.1 1.2.2 1.3 Chapter 2 2.1 2.2 Chapter 3 3.1 Chapter 4 4.1 Chapter 5 5.1 5.2 5.2.1 Chapter 6 6.1 6.1.1 6.1.2 6.1.3 6.2 6.3 6.4 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . References to Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Further Useful Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Important SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 7 8 8 9 9 System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 System Landscape Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Sizing Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Software Units of SAP Accelerated Trade Promotion Planning . . . . . . . . . . . . 13 Business Scenarios of SAP Accelerated Trade Promotion Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Trade Promotion Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Security Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fundamental Security Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security-Relevant Logging and Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security Breach Attempts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operations Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring of Trade Promotion Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trace and Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging of Critical Situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trace Tool Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Asynchronous Processing of Planning Requests . . . . . . . . . . . . . . . . . . . . . . . . Influencing Locking when Updating Master Data Records in SAP NetWeaver BW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Archiving Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 17 17 17 19 19 19 19 20 20 21 21 2013-05-13 CUSTOMER 3/62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 8. . . . . . . . . . . . . . . . . . . . . . . . . . Context to Use for Read Queries . . . . . . . Setting Restrictions to Period Types for Key Figures . . . . . . .4 8. .6. . . . . .3 6. . . . . . . . . . . . . .8 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Functional Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning Functions Based on Formula Extensions (FOX) . . . . . .6. . . . . . . . . . . . . . . . . . . . . . . . . . Thresholding . . . . . . . . . . . . . . . . . . . .7 6. . . . . . . . Objects Used for Key Figure Planning with BPS and Key Figure Planning with the Planning Applications Kit . . . . . . . . . . 28 BI Content Migration . . . .6. . . . . . . . . Accrual Calculation . . . . . . . . . . . . . . . . . . . . . . Key Figures Distribution Split . . . . . . . . . . . . . Time Dimension . . . . . . . . . 31 31 32 33 36 36 36 37 37 37 38 39 39 40 40 41 42 42 4/62 CUSTOMER 2013-05-13 . . . . . . . . . . . . Defining the Height of the Planning Layout . . . . . . . . . .4 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Non-Aggregating Key Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6.2 6. . . . . . . . . . . . . . . . . . . . . .6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5 8. . . . . . . . . . . .1 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16 8. . . 27 Functional Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activating Shared Memory . . . . . . . . . . .12 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Up Your Objects for Key Figure Planning with the Planning Applications Kit . . . . . . . . . . . . Setting the Buying Pattern Key Figure .7 8. . . . . . . . . . . . . . .3 8. . . . . . . . Read Queries . . . . . . . . . Prerequisites for Activating Shared Memory . . . . . . . . .13 8. . . . . . . . . . . . . . . . . . . . . . Define Cell Update Behavior . . . . . . Planning Function Types . . . . . . . . . . . . . . . . . . . . . . . . . . 21 22 22 22 23 23 24 24 24 24 25 Migration from SAP Trade Promotion Management to SAP Accelerated Trade Promotion Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 Chapter 8 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5 6. . . . .6 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deletion of Records . . . . . . Reporting Formulas . . . . . . . . .8 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . .6. . . . . . . . . . . . . . . . . . . . . . . . . . Using Optimized BI Content . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Up Your Queries for SAP Accelerated Trade Promotion Planning . . . . . . .6 6. .17 Reporting Problems . . .5 6. . . . . . . . . . . . . . . . . . Shared Memory . . . . . Load Balancing . . . . . . . . . . . . . . . .2 8. . . . . . . . . . .6 6. . . . . . Mapping Key Figures to Trade Spends .6. . . . . . . . . . . . . . . . . . .11 8. . . . . . . . . . . . . . . . . . . .1 6. . .10 8. .9 Chapter 7 7. . . . . .9 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activating Performance Improvements . . . . .6. . . . . . . .15 8. . . . . . . . . . . . . . . .6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6. . . . . . . . . . . . . . . . . . . . Suppression of Zero Rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14 8. . . . . . . . . . . . . . . . . Example of BI Content with the Planning Applications Kit . . . . . . . . . . . . . . . . . . . . . . . . .22 8. . . . . Configuring Extensibility . . .24 Example Code for Simple Calculations with FOX . . . . . .20 8. . . Example Code for Baseline Data Retrieval with FOX . . . . . . . . .19 8. . Example of BI Content with BPS . . . . . . . . 42 44 47 51 53 53 56 2013-05-13 CUSTOMER 5/62 . . . . . . . Baseline Data Retrieval Technology . . . . . . . . . . . . . . . . . . . . . . . . . . BAdI’s in SAP NetWeaver BW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23 8. . . . . . . . . . . . . . . . . . . . . .8. . . . .21 8. . . . . . . . . . . . . . . . . . . . . . . . . .18 8. . . . . . . . . . . . . . . . . . . . . . . . This page is left blank for documents that are printed on both sides. . 1 Introduction About this Document 1 Introduction 1. c<¾ï˛Á Business Scenarios This section identifies the business processes that you can benefit from using SAP Accelerated Trade Promotion Planning. c<¾ï˛Á BI Content Migration Information This section provides you with a comparison of the objects used with BPS and with the planning applications kit. The guide will be updated according to updates of the software. and is divided into the following main sections: c<¾ï˛Á Introduction References to related documents and relevant SAP notes c<¾ï˛Á System Landscape The first section provides a high-level architecture diagram of the system landscape and sizing recommendations. c<¾ï˛Á Operation Information This section provides you with the most relevant information needed for the operation of SAP Accelerated Trade Promotion Planning. as well as security and operation information. It then explains how to set up the new objects to use for planning. c<¾ï˛Á Installation Information This section identifies the software units required for SAP Accelerated Trade Promotion Planning. It contains implementation information. NOTE You can find the most current version of this document on SAP Service Marketplace at http:// service. c<¾ï˛Á 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. We strongly recommend that you use the document available there.1 1.com/instguides. c<¾ï˛Á Security Information This section provides you with the information that you require to securely operate SAP Accelerated Trade Promotion Planning.1 About this Document This document is a single source of information for the implementation of SAP Accelerated Trade Promotion Planning. 2013-05-13 CUSTOMER 7/62 .sap. sap. see http://service.sap. and memory resource categories. strategies and language support Network security http://service.2 References to Related Information For more information about implementation topics not covered in this guide.sap. 8/62 CUSTOMER 2013-05-13 .sap. You can find more information on component-specific software dependencies in the corresponding installation guides. with the Quick Sizer tool Released platforms and technology.sap. Some sections have been deliberately excluded from this guide since the information is already included in the guides for SAP CRM 7.sdn.0 enhancement packages.1 Further Useful Links The following table lists further useful links on SAP Service Marketplace. operation.com/performance Information about support package http://service. 1. latest software versions.com/instguides upgrade guides General information about SAP http://service. see the following content on SAP Service Marketplace: Content Location on SAP Service Marketplace Latest versions of installation and http://service.sdn.com/platformsTo access the Product Availability related topics. rather than its subordinate components. This means that additional software dependencies can exist without being mentioned explicitly in this document. installation.com/pam.com/crm Customer Relationship Management (SAP CRM) Sizing and calculation of hardware http://service.com/sp-stacks stacks.com/securityguide High Availability http://www.sap.2.0 enhancement packages.sap. such as CPU.sap.2 Introduction References to Related Information Constraints ?üfió_o This administrator’s guide discusses the overall technical implementation of SAP Accelerated Trade Promotion Planning.sap.sap.com/irj/sdn/ha Performance http://service. such as maintenance Matrix directly. and security) for SAP CRM 7.com/irj/sdn/i18n technology 1.com/quicksizer requirements.http://service. disk. and patch level requirements Information about Unicode http://www.1 1. ?üfió_o This administrator’s guide only provides information for SAP Accelerated Trade Promotion Planning that is different from the information included in the guides (master. 3 Upgrade Master http://service.3 Master Guide for SAP http://service.sap.3 NetWeaver Business Installation Warehouse 7.sap.. These SAP Notes contain the most recent information on the installation. 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.2.com/instguides SAP NetWeaver SAP NetWeaver 7.sap. Make sure that you have the up-to-date version of each SAP Note.com/instguides SAP In-Memory Computing SAP In-Memory In-Memory Appliance (SAP HANA) Appliance (SAP HANA) 1.com/instguides SAP NetWeaver SAP NetWeaver 7.com/instguides SAP Business Suite Applications SAP CRM SAP CRM 7.com/notes.com/message http://service.sap. which you can find on SAP Service Marketplace at http://service.0.sap.sap.sap.com/notes http://service. Support Package SP03 2013-05-13 CUSTOMER 9/62 .3 Important SAP Notes You must read the following SAP Notes before you start the installation of SAP Accelerated Trade Promotion Planning.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 http://service.1 1.3 Introduction Important SAP Notes Location on SAP Service Marketplace http://service.com/securityguide SAP Business Suite Applications SAP CRM SAP CRM Master Guide for SAP http://service.sap.com/rkt 1.0 enhancement packages Security Guides for http://service.sap. as well as corrections to the installation documentation.com/swdc Content Information about creating error messages SAP Notes search SAP Software Distribution Center (software download and ordering of software) SAP Online Knowledge Products (OKPs) –role-specific learning maps http://service.3 Guide for SAP Upgrade NetWeaver Business Warehouse 7.sap. 3 Introduction Important SAP Notes Title Description SAP Note Number 1796581 1735590 1637199 1765693 Support Packages for TPM_IMP 200 Information about support packages for SAP Accelerated Trade Promotion Planning 2. Using the ABAP planning SAP Note provided by SAP applications KIT NetWeaver Business Warehouse (SAP NetWeaver BW) to identify any functional restrictions when planning with the planning applications kit BI_CONT 707/737/747: Information Contains information about on Add-On Support support packages for Add-ons. 10/62 CUSTOMER 2013-05-13 .0. Q&A on DSO Planning Information on how to leverage the new DSO planning feature in SAP NetWeaver NW.1 1. scalability. Use the Quicksizer tool to size the SAP NetWeaver BW system and the SAP HANA database. do not use a minimal system landscape as your production landscape.2 2. 2013-05-13 CUSTOMER 11/62 . 2.]WUaô€-ÿUÒHigh-Level System Landscape CAUTION We strongly recommend that you use a minimal system landscape for test and demo purposes only.2 Sizing Recommendations We recommend using the existing sizing guide for trade promotion management to size the trade promotion object. For performance.1 System Landscape System Landscape Overview 2 System Landscape 2. high availability.1 System Landscape Overview The following diagram provides a high-level architectural overview of the system landscape for SAP Accelerated Trade Promotion Planning: …ÿ$b”4F−. and security reasons. This page is left blank for documents that are printed on both sides. . Product version SAP NetWeaver 7.0.47/7.1 or To display Adobe Flex-based planning higher layouts in SAP CRM The following components apply if you are installing SAP Accelerated Trade Promotion Planning on SAP CRM 7.47/7. version 10. NOTE Note: To use the SAP Accelerated Trade Promotion Planning application.47/7.0) SP01 Software component version BI CONT EXT FOR BI CONT 7.02 Software component version Product version SAP CRM ABAP Server Component SAP CRM ABAP 7.0. Type of Component Software Unit Description Software component version SAP CRM ABAP 7.1 Software Units of SAP Accelerated Trade Promotion Planning The following software units are required for SAP Accelerated Trade Promotion Planning. you must install SAP Accelerated Trade Promotion Planning 2.47/7.3 SAP NetWeaver BW 7. External product Adobe Flash Player.37 7.0 with Enhancement Package 1.3 (SP08) with SAP HANA PLATFORM EDIT 1.01 SAP CRM ABAP Server Component SAP CRM ABAP 7. Type of Component Software Unit Description Software component version Software component version SAP CRM ABAP 7.3 SAP NetWeaver BW 7.3 3. The following components apply if you are installing SAP Accelerated Trade Promotion Planning on SAP CRM 7.02 (SP05) TPM IN MEMORY PLANNING 200 TPM In Memory Planning 200 (SAP Accelerated Trade Promotion Planning 2.37 (SP03).3 (SP08) with SAP HANA PLATFORM EDIT 1.0 SP01.37 BI Content extension for BI Content 7.37 (SP03). SAP NetWeaver 7.1 Installation Software Units of SAP Accelerated Trade Promotion Planning 3 Installation 3. 2013-05-13 CUSTOMER 13/62 .01 (SP09) Software component version TPM IN MEMORY PLANNING 200 TPM In Memory Planning 200 (SAP Accelerated Trade Promotion Planning 2.0 with Enhancement Package 2.0) SP01 BI CONT EXT FOR BI CONT BI Content extension for BI Content 7. version 10.3 3.1 Installation Software Units of SAP Accelerated Trade Promotion Planning Software Unit Description Type of Component External product Adobe Flash Player.1 or To display Adobe Flex-based higher planning layouts in SAP CRM 14/62 CUSTOMER 2013-05-13 . com/instguides SAP Business Suite Applications SAP CRM .1 Trade Promotion Management You use SAP Accelerated Trade Promotion Planning with the Trade Promotion Management business scenario and its related business processes. 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. 2013-05-13 CUSTOMER 15/62 . Under Application Help.com/crmaddons SAP Accelerated Trade Promotion Planning .0 Including SAP Enhancement Packages 1 and 2 at http://service.4 4. For more information see SAP Library on SAP Help Portal athttp://help. refer to the master guides for SAP Customer Relationship Management 7.1 Business Scenarios of SAP Accelerated Trade Promotion Planning Trade Promotion Management 4 Business Scenarios of SAP Accelerated Trade Promotion Planning 4. open SAP Library and choose SAP Accelerated Trade Promotion Planning Setting up SAP Accelerated Trade Promotion Planning . For more information about the trade promotion management business scenario.sap.sap. .This page is left blank for documents that are printed on both sides. 5. For more information.1 Security Information Fundamental Security Guides 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 Security Breach Attempts If any tampering with the XML content sent from the WebClient UI to the BI Consumer Services (BICS) is detected. see SAP Note 1757230. a security breach attempt has occurred. all security information for SAP Customer Relationship Management (SAP CRM) applies to SAP Accelerated Trade Promotion Planning.5 5.2. see the security guides for SAP enhancement packages 1 and 2 for SAP CRM 7. it is recorded in the central application log. If any logs exist for this object type and subobject type. To search for security breach attempts search for object type CRM_IMP and subobject type CRM_IMP_SECURITY in transaction SLG1.0 on SAP Service Marketplace at http://service. 2013-05-13 CUSTOMER 17/62 .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.1 Fundamental Security Guides Unless specifically mentioned here. For more information.com/security SAP Security Guides SAP CRM Security Guides .sap. 5. .This page is left blank for documents that are printed on both sides. created by/on. and so on). you save some data in SAP CRM that does not appear in the SAP NetWeaver BW system. the master data is saved and activated in SAP NetWeaver BW. and the user to correct or reprocess the affected objects. Each log in the database also has the attributes Object and Sub-object.1.1 Monitoring of Trade Promotion Planning 6. Logging and tracing for ABAP components is done using transaction SLG1.1. 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. This helps an administrator to analyze the issue that caused the error. subobject = CRM_IMP_CONNECTOR). The central application log indicates the time of the action.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. These attributes describe and classify the application that wrote the log. 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 BAL can be accessed through transaction SLG1 (object = CRM_IMP.1 Operations Information Monitoring of Trade Promotion Planning 6 Operations Information 6.1 Trace and Log Files Trace files and log files are essential for analyzing problems.6 6. then SAP 2013-05-13 CUSTOMER 19/62 . 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). Data Inconsistencies are stored in the object CRM_MKT in the subobjects COMMIT and ROLLBACK. 6. The log header contains general data (type. but a system administrator must then check the system log for more details. An application log is comprised of a log header and a set of messages. If the master data activation fails. you can check the central application log by using the transaction Application Log: Display Logs (SLG1). go to the trace tool environment (transaction RSTT).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. Asynchronous processing is used to reduce the navigation time from the Trade Promotion overview page on the WebClient UI to the planning layout. More Information For more information about asynchronous RFCs.sap. 3. 6.0 Including Enhancement Package 2 .com/netweaver SAP NetWeaver 7. In SAP NetWeaver BW. NOTE Any other users who are logged in to the SAP CRM system and are using planning data will affect the trace. see SAP Library for SAP NetWeaver on SAP Help Portal at http://help.2 Operations Information Asynchronous Processing of Planning Requests 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. Under Application Help. This can be used when you encounter an error and wish to send SAP a recording of the trace.6 6.com/netweaver SAP NetWeaver 7. As an alternative.1.sap. analyze performance. Asynchronous processing is the default mode when a planning session is created from SAP Accelerated Trade Promotion Planning.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.3 Including Enhancement Package 1 -> Under Application Help. open SAP Library and choose SAP NetWeaver SAP NetWeaver Library: FunctionOriented View Business Warehouse Generic Tools and Services Test and Trace Tools Trace Tool Environment . Check which user is defined for this RFC connection. 6. This environment contains tools that allow you to log and play back traces. ensure that you have set up a remote function call (RFC) connection so you can access the SAP NetWeaver BW system from SAP CRM. More Information For more information about the trace tool environment. you must first make the following user settings: 1. process automatic regression tests. see SAP Library for SAP NetWeaver on SAP Help Portal at http://help. In SAP CRM. 2. Under User Activation. open SAP Library and choose SAP NetWeaver SAP NetWeaver by Key Capability 20/62 CUSTOMER 2013-05-13 . and so on. you can also set up a RFC connection with a trusted user. Procedure To use the trace tool environment. enter the user name defined in the RFC connection to activate the trace. you can use the following message components to report problem messages on the SAP Support Portal at http://service.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 . You can use the new archiving table CRMD_MKTPL_PSM for the planning synchronization manager for SAP Accelerated Trade Promotion Planning. there can be delays. To determine how many times you want the system to request a lock and to determine the interval between attempts.6 6.4 Archiving Objects The archiving object CRM_MKTPL is used to archive information for trade promotions created using SAP Accelerated Trade Promotion Planning.com/message: fiW–pÀ± CRM-ANA-IMP Used to report issues related to planning fiW–pÀ± CRM-MKT-MPL-TPM-IMP Used to report issues related to the application fiW–pÀ± BW-BCT-IMP-TPM Used to report issues related to the standard BI Content for SAP Accelerated Trade Promotion Planning. If the records are locked when the system is trying to save or activate the modified master data in SAP NetWeaver BW.5 Reporting Problems For SAP Accelerated Trade Promotion Planning.sap.3 Operations Information Influencing Locking when Updating Master Data Records in SAP NetWeaver BW 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 . see SAP Notes 421419 and 954346. 6. 2013-05-13 CUSTOMER 21/62 . 6. 6. 6 6.6 Operations Information Activating Performance Improvements 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 Accelerated Trade Promotion Planning. The shared area buffers the following query-dependent metadata from SAP NetWeaver BW: Þ³†Bì query descriptions Þ³†Bì query key figures Þ³†Bì query characteristics Þ³†Bì aggregation level characteristics Þ³†Bì aggregation level key figures Þ³†Bì 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: Þ³†Bì Attributes: Aut. Area Creation Þ³†Bì Runtime Setting – Area Structure: Autostart for Read Request and Every Invalidation Þ³†Bì 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 (BCABA) 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 6 6.6 Operations Information Activating Performance Improvements 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 (BCABA) 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 6 6.6 Operations Information Activating Performance Improvements 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 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.6. for a given characteristic. all queries should be based on a single provider. For example.9 Using Optimized BI Content To optimize performance. your BI Content model should follow that of the example BI Content delivered by SAP. 2013-05-13 CUSTOMER 25/62 . For more information about this restriction. see SAP Note 1637199. If it is necessary for operations to occur on a MultiProvider.6 Operations Information Activating Performance Improvements 6. such as several single values or intervals. Disaggregation in the query should not be executed in the database if a key figure is restricted to multiple values.6 6. This page is left blank for documents that are printed on both sides. . Feature SAP Trade Promotion Management SAP Accelerated Trade Promotion Planning Performance and database Standard performance and database connection.1 Functional Enhancements The following table explains the functional enhancements in SAP Accelerated Trade Promotion Planning compared with SAP Trade Promotion Management. campaigns. or Enhanced performance and integration with SAP in-memory computing technology using the SAP HANA appliance software. 2013-05-13 CUSTOMER 27/62 . This controls which layouts and key figures will appear in your planning layouts. 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. account plans. Multiple remote All planningfunction call (RFC) relevant data for destinations trade promotions. deals. if you . live rates.1 Migration from SAP Trade Promotion Management to SAP Accelerated Trade Promotion Planning Functional Enhancements 7 Migration from SAP Trade Promotion Management to SAP Accelerated Trade Promotion Planning 7. 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. Time dimension Planning is done according to calendar month. calendar week. Planning is done according to calendar day or calendar week. For example.7 7. Planning data is always stored at the level you are planning on but can be displayed in different time dimensions. Planning profile A planning profile group group contains a grouping of profiles that are defined in SAP NetWeaver Business Warehouse (SAP NetWeaver BW). or day level. week. goods receipt dates. 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 . Eventing You can use a small set of BPS-based events and planning sequences. and other additional date ranges. or day level. You can synchronize multiple date ranges to the planning layout. You can use an eventing mechanism that offers increased flexibility in manipulating your planning data with the use of planning functions.7 7. If you plan by day. including the following: ÊD}ÇÉG Take rates ÊD}ÇÉG Off-invoice caps ÊD}ÇÉG Tiered growth rebates ÊD}ÇÉG Critical changes based on changes to spend values ÊD}ÇÉG Trade promotion guidelines based on spend values ÊD}ÇÉ( Free goods ÊD}ÇÉ( Indirect trade promotions ÊD}ÇÉ( Creating a trade promotion from a deal ÊD}ÇÉ( Reverse key figure schemes ÊD}ÇÉ( Product segment as product planning basis ÊD}ÇÉ( Creating a trade promotion element from a trade promotion ÊD}ÇÉ( Building a hierarchy of trade promotions ÊD}ÇÉ( 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 .2 Functional Restrictions The following features are not supported in SAP Accelerated Trade Promotion Planning 2. For more information.0 compared with SAP Trade Promotion Management: ÊD}ÇÉ( Certain functions when using rates in SAP CRM.2 Migration from SAP Trade Promotion Management to SAP Accelerated Trade Promotion Planning Functional Restrictions SAP Trade Promotion Management Feature SAP Accelerated Trade Promotion Planning calendar day. including buying dates. Some planning-related BAdIs are obsolete or have been replaced with a new BAdI definition or method. you can display your planning information at the calendar month. Planning data can be stored and displayed at the calendar month. Business Add-Ins Planning-related (BAdIs) BAdIs are available. 7. week. Multiple date ranges You can only synchronize one date range to the planning layout. 2 Migration from SAP Trade Promotion Management to SAP Accelerated Trade Promotion Planning Functional Restrictions f×™š` Some features used to set up enhanced layouts with the Settings for Planning Services (UPX_MNTN) transaction f×™š` Target group promotions with business partner hierarchy node explosion f×™š` Integration with deal planning f×™š` Integration with validation sheet f×™š` Integration with live rates f×™š` Integration with workflow f×™š` Integration with SAP Supply Chain Management (SAP SCM) f×™š` Integration with the Marketing Calendar NOTE f×™š` f×™š` f×™š` f×™š` f×™š` f×™š` f×™š` f×™š` f×™š` f×™š` f×™š` f×™š` f×™š` f×™š` f×™š` f×™š` 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. 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 .7 7. Product Categories. .This page is left blank for documents that are printed on both sides. Aggregation levels are used for the selection of InfoObjects to be included in restrictions on data sets. InfoCubes are used for storing baseline data. 8. and for the definition of planning functions and filters. DataStoreObjects are used for storing baseline data.1 BI Content Migration Objects Used for Key Figure Planning with BPS and Key Figure Planning with the Planning Applications Kit 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. Multiplanning 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. Aggregation levels are used to set restrictions on data sets that are used by queries or planning functions. 2013-05-13 CUSTOMER 31/62 .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. Planning levels are used to set restrictions DataStoreObjects(DSO) are used for storing trade promotion planning data. Planning areas based on InfoCubes are used to define data slices and characteristic relationships.8 8. and for the definition of planning functions and planning packages. Planning levels are used for the selection of InfoObjects to be included in restrictions on data sets.0. 2 BI Content Migration Setting Up Your Objects for Key Figure Planning with the Planning Applications Kit Key Figure Planning with BPS Key Figure Planning with the Planning Applications Kit on data sets that are used by the planning layouts or planning functions. multiple values. In SAP Library. 8. Planning layouts can be enhanced to add calculation formulas. Planning packages are used to set further restrictions on data sets that are already restricted by planning levels. or intervals of values. More Information For more information about BPS and the planning applications kit. functions. To make queries or planning functions reusable. Filters are used to set further restrictions on data sets that are already restricted by aggregation levels by setting values for characteristics. Variables can have single values. A filter (restriction) defined on an aggregation level applies to all InfoObjects based on this aggregation level. Planning layouts are based on planning levels and planning packages.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. you can use variables in filters to restrict characteristics instead of fixed values. choose SAP NetWeaver Library: Function-Oriented View Business Warehouse Analytic Engine Planning Engine .8 8.sap. A filter (restriction) defined on an aggregation level can be applied for different use cases. 32/62 CUSTOMER 2013-05-13 . Planning profiles are used to set up userspecific selections of planning objects.com/netweaver. based on different data sets. Planning layouts are used for providing data records from InfoCubes for manual planning or data entry. and other features for presenting data. Queries are used instead of planning layouts and enhanced planning layouts. see SAP Library for SAP NetWeaver on SAP Help Portal at http://help. 2013-05-13 CUSTOMER 33/62 . when creating a DataStoreObject (DSO). indexes can be created over a DSO in order to increase the speed of data access. run transaction Planning-Specific Properties of an InfoProvider (RSPLAN). 8. in the SAP NetWeaver BW system used for planning with the planning applications kit. execute the following reports: „På…ã½ „På…ã½ RSDDB_LOGINDEX_CREATE RSDRI_CONVERT_CUBE_TO_INMEMORY Setting Up MultiProviders 1. DataStore Object Key Field Ordering and Indexes For performance reasons.3 BI Content Migration Setting Up Your Queries for SAP Accelerated Trade Promotion Planning 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. Moreover. Ensure that the RSADMINparameter RSPLS_DSO_PLANNING has value X. Create a new DSO with the following settings : „På…ã½ Type of DataStore Object = Direct Update or Standard „På…ã½ Plan Flag = X To enable the DSO for SAP Accelerated Trade Promotion Planning. 2.3 Setting Up Your Queries for SAP Accelerated Trade Promotion Planning You can use the query Master: BPHN and PCat. For the TPM planning DSO. Create a MultiProvider based on the following InfoProviders: „På…ã½ DSO for trade promotion planning data „På…ã½ DSO for baseline data To define data slices and characteristic relationships. Ensure that the RSADMIN parameter RSPLS_DSO_PLANNING has value X. 2. The most selected characteristics should be on the top of DSO key fields characteristics list. 1. 2. Create a DSO with the following settings : „På…ã½ Type of DataStore Object = Direct Update „På…ã½ Plan Flag = X Setting up DataStore Objects for Baseline Data 1.3 SP08.8 8. Be aware that indexes increase the performance for reading the data but decrease the performance when writing in a DSO. therefore it is placed as the first field in the key fields list. 3. the most selected characteristic is CRM Marketing Element (Campaign and Marketing Plan) (0CRM_MKTELM). the physical order of its key fields should be ordered based on the selectivity of the characteristics being part of DSO key fields. Indexes are also based on the most selected characteristics as part of a DSO key fields. & Prod(0TPM_AC03_IRQ0001) as a reference. but can be displayed at runtime. EUR or USD) to the query. You can use. If you will use trade spend combinations with Percentage as the discount method. Every new query that is created on the same InfoProvider will contain the same restricted key figures. the characteristic Currency as a free characteristic in your planning. Default Values for Characteristics In the BEx Query Designer. and the sign for the value of a key figure. you can specify if a key figure is displayed in the planning layout. You can specify the number of decimal places for the value of a key figure. 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. the scaling factor. Key Figures In the BEx Query Designer. multiple single values. A variable can have a single value. 34/62 CUSTOMER 2013-05-13 . you must model a unique key figure for each trade spend combination Restricted Key Figures In the BEx Query Designer. Variables allow you to reuse query objects. Defaulting values for characteristics is the default behavior when working with queries online (through APIs). you can define restricted key figures at the aggregation level that can be used across all queries defined on the same aggregation level. you can choose certain characteristics to behave as default characteristics (part of the query dynamic filter). You can choose from the following options: ]÷nßàÿ Always Show The key figure is always displayed in the planning layout. or a range of single values. for example.8 8. ]÷nßàÿ Hide (Can Be Shown) The key figure is hidden at design time. When you are setting up your queries for SAP Accelerated Trade Promotion Planning. and you can define a variable that acts as a placeholder for this characteristic value. The SAP Accelerated Trade Promotion Planning application provides the corresponding characteristic values before the execution of the query. The query restricts the data set and returns the combinations. You can define variables in the Data Warehousing Workbench (RSA1) or in the BEx Query Designer. taking into account only the expected currency. The planning application can transfer an appropriate value for the Currency variable (for example. right-click the Key Figures structure and select New Restricted Key Figure. From the InfoProvider.3 BI Content Migration Setting Up Your Queries for SAP Accelerated Trade Promotion Planning Variables You can restrict the use of characteristics by using variables. ]÷nßàÿ Always Hide The key figure is always hidden in the planning layout. you can use a variable for the Trade Promotion ID characteristic to perform a lock on the data combinations related to this promotion. then the BEx Query Designer default values are read to determine if the characteristic value is available. For example. you can see the relationship between parent and child compound characteristics. In addition. 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.com/nw. 2. The parent characteristic values are always single values for each trade promotion. The values for the parent characteristics are automatically filled from the runtime query filter and from the default values of the BEx Query Designer. BEx Query Designer Default Values If the runtime query filter does not contain the compounded parent value. On the Compounding tab.8 8. If the characteristic 0FISCVARNT is found in the filter sent by the application. see SAP Library for SAP NetWeaver on SAP Help Portal at http:// help. If neither the runtime query filter nor the BEx Query Designer contain the characteristic value.sap.3 BI Content Migration Setting Up Your Queries for SAP Accelerated Trade Promotion Planning 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. if the characteristic 0FISCVARNT is defined in the BEx query designer with a default value of “K4”. The same is true if more than one parent characteristic value is maintained for a single parent characteristic. you can specify different types of distribution for the values of different key figures. 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. The parent characteristic value(s) are unique for each child characteristic value(s). an exception will occur. Distribution of Key Figure Values When you are setting up your queries for SAP Accelerated Trade Promotion Planning. In SAP Library. this value will be added to the filter sent by the application if 0FISCVARNT cannot be found within the filter. You can choose from the following types of distribution: 2013-05-13 CUSTOMER 35/62 . it will not be added at runtime. For information about compounding. 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. There cannot be a child characteristic with a different parent characteristic value(s) within the same trade promotion. 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. In the Query Designer. characteristics with or without display hierarchies) are displayed as individual hierarchies. open a query and then click on the RowsI[?‘^âÚA£d«ColumnsI[?−ìÚQ£•dûM
€+Í”´ô¼.4 BI Content Migration Time Dimension I[?-^ Equal distribution I[?-^ Analog distribution with a self-reference I[?-^ Analog distribution with a reference to a given object Display as Hierarchy In the Query Designer.8 8. you can specify for each axis whether all objects on an axis (structures. Þž°È}Úz?‘ÉGëKÓ#MÇiÓ+pOO”5+éÞ9 I[?ß„âÚC£ÅdùM€%Í”´©¼. With SAP Accelerated Trade Promotion Planning. No automatic calculations for percentages will be carried out. 8. under Rows/Columns.5 Mapping Key Figures to Trade Spends When using BPS. 8. This is useful for removing deleted records. you must map trade spend combinations with the Percentage discount method to a unique key figure for percentages. The SAP NetWeaver BW system derives the time dimensions Calendar Week (0CALWEEK) and Calendar Month (0CALMONTH) from Calendar Day (0CALDAY).6 Suppression of Zero Rows For planning and read queries. choose the following settings: I[?-^ Suppress Zeros: Active (All Values = 0) I[?-^ Effect on: Rows This setting does not affect master queries. In the BEx Query Designer. 8. ensure that the effect on rows is set to active so that zeros are suppressed for all values. planning operations using SAP NetWeaver BW cannot be executed.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. you must ensure that the time interval used for trade promotion planning is within the time interval defined in transaction RSRHIERARCHYVIRT. Also.Þ®±ÈyŒzs7‘łGÿKÙ#LÇ[iÈ+vON”|+õÞ1Ÿ¥v$‚³h‡ºXûfiÚfiúKà˘·iו|ÂŽx⁄’Ó˚KæÑ™à©DÌÜäÑ|(4ßï ¸·žREν˙ÔÛ‹\ZT8Â"ÓPropertiesI[?‘^þÚP£ÒdîM€"ÍË´»¼^Þ¯¹È6ÚzS>‘łGíKÞ#[ÇÛiœGeneralI[?‘^ùÚR£Â I[?ßêÚV£„d«M€)Í⁄´¿¼OÞ¾xÈ8ActiveI[?‘^øÚ]£ÄdîM€ìÍËDisplay As HierarchyI[?†ÞØÚ]£ÄdîM€ìÍËExpand to. 36/62 CUSTOMER 2013-05-13 .I[?‘^ôÚ\£Õd«M€-Í–´ú¼OÞ¢·Èw›zyp‘ÎGéKŒ#JÇiœ+iOC”5+äÞ6Ÿòv?‚úh‹ºXûÒÚfi˜úOà level the hierarchy is to drilled down in the initial view. you were able to map two trade spend combinations with different discount methods to a single key figure.Otherwise. 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. If More Than One Value Occurs)and the Aggregation property set to value No aggregation (X. A non-aggregating key figure must have the Exception Aggregation property set to value No aggregation (X. see Customizing for Customer Relationship Management under Trade Promotion Management Trade Promotions Trade Spends Define Trade Spends for Values . the cost. 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. all corresponding planning records are removed from the DSO. for example. In SAP NetWeaver BW. in SAP Accelerated Trade Promotion Planning. 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 . 8. when products are removed from a trade promotion. which is used as a restriction for the key figures that depend on specific date ranges.8 8. 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. You use the Period Type characteristic (0PERIOD_TYP).3. Note that for trade spend key figures. For example. The minimum technological requirement to implement non-aggregating key figures with DataStoreObjects is SAP NetWeaver BW 7.7 BI Content Migration Deletion of Records 8. and variable trade spends key figures must be defined as non-aggregating key figures. if more than one value occurs) that can be defined in Characteristic Maintenance (RSD1). or header attributes of a trade promotion are changed. For more information. SP 08. The following table shows an example of the master data associated with the Period Type characteristic: Period Type Period Type Description 50 95 Buying Goods Receipt 2013-05-13 CUSTOMER 37/62 .7 Deletion of Records During a deletion.8 Non-Aggregating Key Figures The planning applications kit supports the non-aggregating key figures by using DataStore Objects (DSO) as InfoProviders. price. you must restrict the values of the period types for the key figures. You create restricted key figures that are dependent on a date range characteristic. The key figure value is equally distributed at the most granular time unit level. 2012 10. 2012 31 30 August 3rd. 2012-August 140 16th. The key figure values are aggregated at the next time unit level.10 BI Content Migration Key Figures Distribution Split For example. set the characteristic 0PERIOD_TYP to 95 (Goods Receipt) 8. the application applies a top-down distribution. Week 32 and Week 33. 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. 2012 10.10 Key Figures Distribution Split During the planning process. 2. This planning period spans 3 calendar weeks : Week 31. and Rebate_KYFkey figures for your planning.00 August 4th. 2012 10. 2012 until Thursday August 16. 2012. In this case. 1. 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. when you enter a cumulative key figure value in the highest level aggregation position. set the characteristic 0PERIOD_TYP to 50 (Buying) H°iøþ For the Goods_Receipt_KYF key figure.00 August 5th. It is possible that the business weeks you are planning on do not have the same number of days. The distribution is performed in two steps. you are using the Buying_KYF. Goods_Receipt_KYF. and you want the following conditions to apply: H°iøþ 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 H°iøþ 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 H°iøþ 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. This is the expected behavior of the application.8 8. you must restrict the three key figures as follows: H°iøþ For the Buying_KYF key figure. Planning Period KYF Value KYF Value (Top Aggregated Level) Calendar Week (Subtotal 1) Calendar Day KYF Value (Subtotal 2) August 3rd. by calendar day. by calendar week. Example The following example illustrates the expected behavior of the top-down distribution of a cumulative key figure value. To achieve this in the BEx Query Designer. the key figure value aggregation by calendar week can show different values for different calendar weeks in the planning period.00 38/62 CUSTOMER 2013-05-13 . Consider the planning period from Friday August 3. 2012 August 13th. 2012 August 16th. you must define a key figure that represents the buying pattern percentage in the planning DSO.00 10. except for the Trade Promotion ID (0CRM_MKTELM) characteristic that is used to get the highest aggregated view on the data. 2012 August 8th. The buying pattern key figure is of type Amount. 2012 August 10th. 2012 August 14th. 2012 August 11th. Filter Value Selection at Query Execution = Only Posted Values for Navigation 3.00 10.00 8.00 10.00 10. 2012 August 12th.8 8.00 10. the percentage values for distribution are assigned to the buying pattern key figure. You define this key figure using transaction RSA1 (Data Warehousing Workbench: Modeling). 2012 August 15th. 2012 August 7th. Set all characteristics that are used in the query as free characteristics. The buying pattern key figure is not displayed in the planning layout.00 10. 8.11 Setting the Buying Pattern Key Figure If you are using buying patterns.00 10. Make the following settings for all key figures in the query: 1. 2. The buying pattern key figure is a placeholder for the percentage distribution of other key figures that represent business data. 2012 August 9th. The data that read queries retrieve is then used for other purposes. such as for condition generation.12 Read Queries Read queries are used to retrieve planning data from SAP NetWeaver BW. Change Data = Not Input-Ready (Not Relevant for Locking) 2. 2012 10. 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 .11 BI Content Migration Setting the Buying Pattern Key Figure KYF Value KYF Value (Top Aggregated Level) Calendar Week (Subtotal 1) Calendar Day KYF Value (Subtotal 2) Planning Period 32 70 33 40 August 6th. Ensure that all characteristics in the query have the following default settings: 1.00 10. Make the following settings for read queries: 1. At runtime. Access Type for Result Values = Posted Values 2. Hide=Hide (Can Be Shown) 2013-05-13 CUSTOMER 39/62 .00 10.00 10. For those query contexts. different read queries can be defined and used depending on the context. or they can allow you to change the operands in the formula.Trade Promotion Management Key Figure Planning with the Planning Applications Kit Define Integrated Planning Profile Groups: Assign Read Queries Customer Relationship Management>Trade Promotion Management->Key Figure Planning with the Planning 40/62 CUSTOMER 2013-05-13 . only the key figures should be added and those key figures should have the Hide setting set to Always Shown. Therefore. and the reporting formulas show the results of the calculations. different settings are required. and not for processing on the WebClient UI. because the data is only used for backend processing. Reporting formulas can either only display the result of key figure calculations as defined in the formula.Trade Promotion Management Key Figure Planning with the Planning Applications Kit Define Integrated Planning Profile Groups: Assign Read Queries Customer Relationship Management.13 BI Content Migration Reporting Formulas The query properties Universal Display Hierarchy and External Hierarchy are not supported by the SAP Accelerated Trade Promotion Planning application. Read queries for all other query contexts should be defined as described above.13 Reporting Formulas Reporting formulas in queries represent calculated key figures based on calculations involving persisted key figures or other calculated key figures. and they are processed in ABAP. no data drilldown is supported. NOTE When using the SOA read service or integrated marketing calendar query context for read queries. The results of reporting formulas are not persisted in the database. 8. SAP HANA does not support reporting formulas. You define key figure calculations. but their use is determined using Customizing settings. Currently. 8. We recommend that you use planning functions instead. The read queries are developed with the Business Explorer Query Designer.14 Context to Use for Read Queries The planning data can be used for different purposes.8 8. For this reason. The use of read queries is summarized in the following table: Application Area Query Context Customizing Path Trade Promotion Planning Profiles <*> = Generic Entry CONDITION = For Condition Generation FUNDS = For Funds SOA_READ = For SOA Read Service (*) VOLUME = For Volume in the Spend Value Overview Assignment Integrated Marketing Queries that retrieve the basic key figures Calendar to display in the Integrated Marketing Calendar views Customer Relationship Management. input-ready key figures should be set to value “Disaggregate” copy. 8. External hierarchies are not supported by the SAP Accelerated Trade Promotion Planning application. The planning property “Aggregation” of the non-aggregating. Applications Kit->Settings for Display of BW Key Figures->Define Query for Key Figures (*) For the SOA_READ query context. If the basic key figure is never displayed. select the Start Query in Change Mode checkbox. all key figures should be read and therefore set with the property Display-Hide = Always Show. 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. a reporting formula) at runtime. it must have a BEx Query Designer technical name to uniquely identify it. the corresponding reporting formulas must have the same technical name as the technical name for the basic key figure. To display or hide a non-basic key figure (for example.15 BI Content Migration Planning Queries Query Context Customizing Path Application Area Trade Promotion Totals assignment block Applications Kit->Integration with Integrated Marketing Calendar Query that retrieves the basic key figures Customer Relationship Managementto display in the Totals assignment block >Trade Promotion Management->Key Figure Planning with the Planning of a trade promotion. 3.P Filter Value Selection at Query Execution = Posted Values 2. To make a query relevant for planning. the basic key figure must be below the reporting formula in the key figure structure in the BEx Query Designer. Make the following settings for all characteristics in the query: !|. enter a technical name for it in the BEx Query Designer. and set at least one key figure as input-ready. For list price and net price list. A warning appears in the BEx Query Designer that the same technical name is used twice.8 8. They are used in the planning layout and only use dynamic filters (default values for the characteristics). SAP Accelerated Trade Promotion Planning supports universal display hierarchies.P Access Type for Result Values = Posted Values !|. When you create the query for these key figures. SAP Accelerated Trade Promotion Planning always changes the values of the characteristics dynamically at runtime. Make the following settings for planning queries: 1. 2013-05-13 CUSTOMER 41/62 .15 Planning Queries Planning queries are used to access and update planning data from SAP NetWeaver BW. it does not need a BEx Query Designer technical name. This example code occurs after the synchronization of the planning layout with data from SAP NetWeaver BW.16 Planning Function Types Ensure that you have installed the following planning function types: ßł—óX‹ Deletion and Redistribution by Reference Data (0RSCRM_IMP_DEL_DISTR) ßł—óX‹ Set/Distribute Values (RSCRM_IMP_DIS_VALUE) ßł—óX‹ Time Shift (0RSCRM_IMP_TIMESHIFT) ßł—óX‹ Transfer DSO Data and Physically Delete Source Data (0RSPL_REPOST_DSO) ßł—óX‹ Repost (0RSPL_REPOST) ßł—óX‹ Set Key Figure Values (0RSPL_SET_VALUES) ßł—óX‹ Delete DSO Records (0RSPL_DELETE_DSO) ßł—óX‹ Delete (0RSPL_DELETE) ßł—óX‹ Generate Combinations (0RSPL_CREATE_CR) ßł—óX‹ Copy (Ignore Empty Records (0RSPL_COPY_NO_ZEROS) ßł—óX‹ Distribution by Reference Data (0RSPL_DISTR_REFDATA) ßł—óX‹ Distribution by Keys (0RSPL_DISTR_KEY) NOTE If you already have some of the above planning functions installed. An eventing mechanism is available. after cell update. The step of the execution phase at runtime (for example. It retrieves baseline data. For more information. performs calculations using data from the key figures.18 Example Code for Simple Calculations with FOX The following example shows code for a planning function of type FOX. 8. Note that this code must be adapted to correspond with your BI Content modeling.17 Planning Functions Based on Formula Extensions (FOX) The planning functions based on FOX are of type Formula. and updates other relevant key figures accordingly. 8. 42/62 CUSTOMER 2013-05-13 . you can assign FOX formulas to events.8 8.16 BI Content Migration Planning Function Types 8. see Customizing for Customer Relationship Management under Trade Promotion Management Key Figure Planning with the Planning Applications Kit Define Events for Queries . after synchronization. Using the Define Events for Query (RSCRM_EVENTCUST) transaction in SAP NetWeaver BW. re-install them to ensure that you have the most recent version. and the appropriate FOX formulas can be executed depending on the execution phase. 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. or before save) determines which formulas are executed. DATA LV_PARVEN TYPE F. SYNTAX DATA LV_PT TYPE 0PERIOD_TYP. {0BONUS_SHIP } = { 0CRM_BONSAL } * LV_INV_QTY. DATA LV_PRC_LST TYPE F. LV_PARVEN = { 0COPAREVEN }. LV_PANETRV = { 0COPANETRV } . 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. LV_INV_QTY = { 0UPLI_QTYS } + { 0BASE_QTYS }. {0BONUS_SCAN } = { 0BON_SCSU } * { 0SCAN_QTY }.LV_BUDGET. {0CRM_CPIC } = LV_BUDGET / { 0UPLI_QTYS }. {0CRM_CPC } = LV_BUDGET / LV_INV_QTY. {0CRM_BONPRO } = { 0OFFR_DSCNT } + { 0CRM_OFFINV } + { 0EDLP_OINV }. {0COPANETRV } = { 0REG_REVE } .18 BI Content Migration Example Code for Simple Calculations with FOX For example. {0CRM_ROIPER } = LV_PANETRV / LV_BUDGET. DATA LV_BUDGET TYPE F. LV_PT = OBJV(). {0COPAREVEN } = LV_PRC_LST * LV_INV_QTY. {0OFFR_DSCNT } = { 0CRM_BONPRO } * LV_INV_QTY. {0BUDGET } = { 0BONUS_DISP } + { 0BON_SCSU } * { 0SCAN_QTY }. {0PROPUNIT } = { 0PROMPRICE } / { 0PROUNIT }. 2013-05-13 CUSTOMER 43/62 . ENDIF.8 8. {0CRM_BBACK } = { 0BON_BBP } * LV_PRC_LST. DATA LV_PANETRV TYPE F. Buying and Post-Dip IF LV_PT = '30' OR LV_PT = '50' OR LV_PT = '70'. LV_PRC_LST = { 0PRICELIST }. LV_BUDGET = { 0BUDGET }. {0CRM_OFFINV } = { 0BON_OIPSU } * LV_PRC_LST. * Only for Period Types Pre-Dip. DATA LV_INV_QTY TYPE F. {0CRM_BONSAL } = { 0BON_SHSU } + { 0CRM_BBACK } + { 0EDLP_VARI }. {0REG_REVE } = LV_PRC_LST * { 0BASE_QTYS }. DATA L_BASE TYPE F. { 0INV_QTY } = LV_INV_QTY. 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. product. or unit of measure) available in the MultiProvider that contains the baseline DSO and the TPM planning DSO. the FOX planning function uses the values of the Product and the Business Partner characteristics to retrieve and aggregate the baseline data. business partner group level. 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. business partner. planning by time and unit of measure) applies to the FOX planning function as well. time.8 8. To achieve this. The figure below illustrates an account hierarchy (business partner hierarchy) with two levels: 44/62 CUSTOMER 2013-05-13 . 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. 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. Example 1 When planning by product at the business partner level. This data is then stored in the TPM planning DSO in a dedicated key figure for baseline data. The selection of the other characteristics (for example. The baseline DSO contains granular data that can be retrieved using the dimensions (for example. the application passes the Product Hierarchy levels of the products with data in the baseline InfoCube using the Product Hierarchylevels characteristics. the technology used in based on Formula Extension (FOX) planning functions. The selection of other characteristics (for example. Example 3 When planning by product category at the business partner hierarchy node level. Example 2 When planning by product category at the business partner level. The results will be aggregated by product and business partner hierarchy node. product group. product hierarchy level.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.19 BI Content Migration Baseline Data Retrieval Technology FOX is capable of combining all calculations in a single execution. 8. planning by time and unit of measure) applies to the FOX planning function. the application passes the category levels of the products with data in the baseline DSO and uses the Product Hierarchy levels characteristics. In the meantime. InfoObject ‘0BPARTNER‘ – Master Data (present here with 3 out of 3 levels): 2013-05-13 CUSTOMER 45/62 . InfoObject ‘0BP_GRP‘ – Master Data BP: Group (Hierarchy) Description 46E028ED001A045BE10000000A421474 46E028F0001A045BE10000000A421474 46E028F3001A045BE10000000A421474 REMA US Inc. 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.19 BI Content Migration Baseline Data Retrieval Technology °zc“Õhà³N¢ôˆ|•¶¬C&pWSAP CRM Account Hierarchy SAP CRM Account Hierarchy Account Hierarchy R3-CRM-01 Account Hierarchy Description 300010/30203000A 300011/30203000A 300012/30203000A REMA US Inc. / 1030 / BROOMALL PA 19008 REMA DC West / 1030 / CARLSBAD CA 92008 REMA DC East / 1030 / HOCKESSIN DE 19707 In SAP NetWeaver BW.8 8. 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). / PO Box 1030 / BROOMALL PA REMA DC West / PO Box 1030 / CARLSBAD CA REMA DC East / PO Box 1030 / HOCKESSIN D The Business Partner Hierarchy Node levels are used to extract baseline data from the baseline InfoCube. A user may want to plan at the account hierarchy node level (for example. and calendar day characteristics. to plan for REMA US Inc. For more information. and storing it in the dedicated key figure for baseline in the planning InfoCube. The query is executed against the updated planning DSO. The following table identifies the InfoProviders provided with the standard BI Content. 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. unit of measure. Also. aggregating it at the application planning level. Therefore. sales unit of measure. depending on the leading SAP CRM application events that can occur. product hierarchy level. 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. 46E028ED001A045BE10000000A421474 46E028F0001A045BE10000000A421474 00000000000000000000000000000000 REMA DC West 46E028ED001A045BE10000000A421474 46E028F3001A045BE10000000A421474 00000000000000000000000000000000 REMA DC East In the baseline DSO. 46/62 CUSTOMER 2013-05-13 . the execution sequence is to trigger the planning function that updates the baseline data in the planning DSO. the data is stored at the most granular level based on account (business partner). product. account hierarchy level. the planning DSO baseline key figure has to be updated by the planning function with the last available data from the baseline DSO. SAP NetWeaver BW needs data at the same granulation level from the application side. Therefore. In the current example. in the above example). 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 .8 8. To be able to execute joins between the planning DSO and the baseline DSO. 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.19 BI Content Migration Baseline Data Retrieval Technology Business Partner (BP) BP Group Level 1 BP Group Level 2 BP Group Level 3 Description 300010 300011 300012 46E028ED001A045BE10000000A421474 00000000000000000000000000000000 00000000000000000000000000000000 REMA US Inc. when the user plans at account hierarchy level 2 (REMA DC West). Before the application executes a query against the SAP NetWeaver BW system. or time). This filter is passed to a planning function that reads baseline data from the baseline InfoCube. you can use the transaction RSCRM_EVENTCUST to determine the execution sequence for certain actions in SAP NetWeaver BW. product hierarchy level. 0TPM_DS01_Q0003 Prod.) TPM Base Sales Quantity (This is the baseline cube.) Baseline/TPM MultiProvider Data Store Object Planning with direct-update setting Real Time Info Cube DSO MultiProvider 0TPM_AC04 0TPM_MC02 0TPM_MC02 Baseline for Prod-PCat@BPHN Aggregation Level Sales and TPM for ProdPCat@BPHN Aggregation Level 0TPM_DS01 0TPM_AC04 0TPM_DS02 0TPM_MC02 Queries and Planning Functions 0TPM_DS01 Queries.20 BI Content Migration Example Code for Baseline Data Retrieval with FOX Type Source Data Targets InfoProvider Name Description 0TPM_DS01 0TPM_DS02 0TPM_MC02 0TPM_AC04 0TPM_AC03 Sales and Trade Promotions (This is the TPM Planning Cube. Product 0TPM_AC03_IRQ0001 and Product Category at Business Partner Hierarchy Node Level Planning by Prod. It retrieves baseline data and updates the relevant baseline key figures accordingly. The code comments explain the technique used to retrieve the baseline data in detail. Planning Functions. it refers to the baseline DSO. & Prod. Cat.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. Pre-Dip and Post-Dip) 2013-05-13 CUSTOMER 47/62 .8 8. 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. Please note that every time the statement IN REFDATA is used.Categ-Prod @BPHN 0TPM_AC03_IRQ0002 0TPMIMP_PCPRD_BPHN_D 0TPM_AC03_IRQ0004 (for CRM RATES) 8. The example code is an excerpt from the delivered planning function 0TPMIMP_PCPRD_BPHN_D and illustrates the baseline retrieval. TPM Read Query Execute All Formulas for & Prod. and Reports Baseline Planning Scenario Planning Scenario Master Query Planning Queries Read Query Planning Function Planning Master: BPHN and on PCat. 0CRM_PR_A05. DATA LV_REF_PR02 TYPE 0CRM_PR_A02. DATA LV_REF_PROD TYPE 0CRM_PROD. DATA LV_REF_BP02 TYPE 0BP_GRP_A02. SYNTAX DATA LV_PT TYPE 0PERIOD_TYP. 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. 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. DATA LV_PROD TYPE 0CRM_PROD. DATA LV_TP_BASELINE TYPE I. ENDLOOP. 0CRM_PR_A05. DATA LV_REF_PR05 TYPE 0CRM_PR_A05. 0BP_GRP_A03 and 0CRM_PR_A01. 0CRM_PR_A02.20 BI Content Migration Example Code for Baseline Data Retrieval with FOX IF the current Planning Product is initial (Not Assigned = ‘#’) LOOP: Lookup for the baseline (reference) DSO entries grouped by characteristics 0BP_GRP_A01. DATA LV_REF_BP01 TYPE 0BP_GRP_A01. 0CRM_PR_A04. ENDLOOP. DATA LV_REF_BP03 TYPE 0BP_GRP_A03. DATA LV_REF_PR03 TYPE 0CRM_PR_A03.8 8. DATA LV_REF_PR01 TYPE 0CRM_PR_A01. ENDIF. 0CRM_PR_A03. ENDIF. DATA L_BASE TYPE F. At this point you have the aggregated baseline key figure values for all the planning data. DATA LV_PCAT TYPE 0PR_CAT_SAL. END PLANNING FUNCTION. 0BP_GRP_A03 and 0CRM_PR_A01. 0BP_GRP_A02. 0BP_GRP_A02. 0CRM_PR_A03. DATA LV_REF_PR04 TYPE 0CRM_PR_A04. 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. 0CRM_PR_A04. 48/62 CUSTOMER 2013-05-13 . ENDLOOP. 0CRM_PR_A02. LV_REF_PR01. LV_REF_BP02. * If the Product belongs to the planning PCat. * Product is initial. LV_REF_BP01. LV_REF_PR03. 2013-05-13 CUSTOMER 49/62 . * Only retreiving Baseline data for following Period Types IF LV_PT = '30' OR LV_PT = '50' OR LV_PT = '70'. 0FISCPER = # }. DATA LV_BUDGET TYPE F.20 BI Content Migration Example Code for Baseline Data Retrieval with FOX DATA LV_INV_QTY TYPE F. 0CURRENCY = #. LV_REF_BP03. 0DISTR_CHAN = #. LV_REF_PROD. LV_REF_PR01. Current planning data is Planning on PCat only LV_TP_BASELINE = 0. 0FISCVARNT = #. ENDFOR. DATA LV_PARVEN TYPE F. DATA LV_PRC_LST TYPE F. 0INFOPROV = 0TPM_DS02. LV_REF_PR03. LV_TP_BASELINE = LV_TP_BASELINE + L_BASE. Product and Product Hierarchy Levels (in Baseline DSO) FOREACH LV_REF_BP01. LV_REF_PR05 | 0CALWEEK = #. 0CRM_SALORG = #. LV_REF_BP02. LV_REF_PR05 IN REFDATA. 0CRMVERSION = #. * Get the current Period Type (Planning DSO) LV_PT = OBJV(). LV_REF_PROD. ELSE. 0PR_CAT_SAL = #. 0BP_GRP = #.8 8. LV_REF_PR02. DATA LV_PANETRV TYPE F. LV_REF_PR04. LV_REF_PR04. 0CRM_MKTELM = #. *Get the current Product Category (from planning DSO) LV_PCAT = OBJV(). 0PERIOD_TYP = #. IF LV_PROD = #. LV_TP_BASELINE = 0. * 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_PR03 OR LV_PCAT = LV_REF_PR04 OR LV_PCAT = LV_REF_PR05. LV_REF_BP03. LV_REF_PR02. * In planning DSO (TPM) FOREACH LV_PROD. ENDIF. *Loop by Business Partner Hierarchy Nodes. 0DIVISION = #. add up the Baseline value L_BASE = { 0BASE_QTYS. ENDIF. #. #. #. LV_REF_BP03. 0DISTR_CHAN = #. #. #. #. #. #. #. LV_PROD. #. #. 0CRM_SALORG = #. #. LV_REF_PR03. #. #. Planning on Product L_BASE = { 0BASE_QTYS. #. #. #. #. #. #. #. # } = { 0CRM_BONSAL.20 BI Content Migration Example Code for Baseline Data Retrieval with FOX FOREACH LV_REF_BP01. #. #. #. #. #. LV_PROD. #. #. #. #. #. #. #. * Product isn't initial. #. #. #. LV_REF_PR05 IN REFDATA. #. LV_REF_PR01. #. #. #. #. # }. # } * LV_PRC_LST. #. #. #. # } * LV_PRC_LST. LV_PROD. 0CRMVERSION = #. { 0INV_QTY.8 8. #. #. IF LV_REF_PROD = LV_PROD. # } = { 0BON_SCSU. #. LV_REF_BP01. #. LV_REF_BP03. #. #. #. #. 0FISCVARNT = #. #. #. # } = LV_INV_QTY. #. LV_PROD. #. #. LV_REF_PR05| 0CALWEEK = #. 0CRM_MKTELM = #. #. LV_REF_BP02. #. {0BONUS_SCAN. #. #. #. 0PERIOD_TYP = #. # } = { 0BON_OIPSU. { 0CRM_BONPRO. LV_PROD. # }. #. # } = { 0BON_SHSU. LV_REF_PR03. #. { 0OFFR_DSCNT. # } + LV_TP_BASELINE. #. #. #. #. #. 0FISCPER = # }. #. 0DIVISION = #. { 0BONUS_SHIP. #. LV_PROD. #. { 0CRM_OFFINV. ENDFOR. #. #. #. LV_PROD. #. # } + { 0CRM_OFFINV. #. LV_PROD. #. #. LV_PROD. #. #. #. #. #. #. #. LV_INV_QTY = { 0UPLI_QTYS. ENDIF. #. #. LV_TP_BASELINE = LV_TP_BASELINE + L_BASE. #. #. #. #. #. LV_PROD. #. #. #. LV_PROD. #. LV_PROD. #. LV_PROD. #. #. LV_REF_PR02. * Using the calculated Baseline. LV_PROD. #. LV_REF_BP02. #. #. #. #. # } * LV_INV_QTY. #. #. #. # } + { 0CRM_BBACK. #. #. LV_REF_PR01. LV_PROD. #. 0INFOPROV = 0TPM_DS02. { 0CRM_BBACK. # } = LV_TP_BASELINE. #. #. LV_PROD. # } = { 0CRM_BONPRO. { 0CRM_BONSAL. # } = { 0BON_BBP. #. 0PR_CAT_SAL = #. #. #. 0BP_GRP = #. #. #. #. #. #. #. #. coming from the given Baseline data(Planning on Product) * or multiple reference Products( Planning on PCAT) { 0BASE_QTYS. #. # }. #. #. 0CURRENCY = #. #. #. LV_PROD. #. #. LV_PROD. #. #. #. #. #. LV_PROD. #. #. #. # }. #. LV_REF_PR02. #. #. #. #. #. #. #. LV_PROD. #. LV_REF_PROD. LV_PROD. LV_REF_PR04. LV_REF_PR04. #. #. #. #. #. LV_PROD. #. # } + { 0EDLP_VARI. #. #. # } + { 0EDLP_OINV. # } * { 0SCAN_QTY. LV_PROD. LV_PROD. #. #. #. #. * Performing calculation for other keyfigures LV_PRC_LST = { 0PRICELIST. 50/62 CUSTOMER 2013-05-13 . # } * LV_INV_QTY. #. #. # } = { 0OFFR_DSCNT. #. # } = LV_BUDGET / LV_INV_QTY. #. 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: @ıƒTŽ× AFTER SYNCHRONIZE: At the end of the synchronization. #. #. #. #. #. #. #. LV_PROD. #. #. #. # } = { 0PROMPRICE. #. #. #. #. # }. #. #. { 0CRM_ROIPER. # } / { 0PROUNIT. #. LV_PROD. LV_PROD. #. #. #. #. ENDIF. #. # } = LV_PRC_LST * LV_INV_QTY. #. { 0CRM_CPC. #. #. #. LV_BUDGET = { 0BUDGET. #. #. #. You can customize up to 10 different events. #. #. #. #. { 0CRM_CPIC. #. #. # } = LV_BUDGET / { 0UPLI_QTYS. #. #. #. #. # } = { 0REG_REVE. #. #. LV_PROD. #. # }. #.8 8. #. #. #. #. LV_PARVEN = { 0COPAREVEN. Each event can execute more than one planning function. #. #. # } = { 0BONUS_DISP. #. #. #. # }. LV_PROD. LV_PANETRV = { 0COPANETRV. #. #. #. #. #. #. #. #. #. #. #. #. #. #. #. # } + { 0BON_SCSU. #. #. #. #.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. LV_PROD. after all the standard logic is executed @ıƒTŽ× BEFORE SAVE Prior to saving the application data @ıƒTŽ× AFTER UPDATE CELL After a cell value is disaggregated @ıƒTŽ× MANUAL EVENT If triggered from the planning layout by selecting it from a drop down list box. #. #. LV_PROD. #. #. #. #. #. #. { 0COPANETRV. #. #. this event executes one or more planning functions. #. #. #. You must maintain a sequence number to determine the sequence of this execution. #. LV_PROD. #. LV_PROD. #. LV_PROD. #. #. #. #. 8. # } . #. ENDFOR.21 BI Content Migration BAdI’s in SAP NetWeaver BW {0BUDGET. #. LV_PROD. #. #. LV_PROD. LV_PROD. #. #. LV_PROD. #. #. #. #. # } = LV_PRC_LST * LV_TP_BASELINE. #. #. # }. { 0REG_REVE. #. # }. #. #. #. #. #. #. # } = LV_PANETRV / LV_BUDGET. #. #. #. #. { 0PROPUNIT. { 0COPAREVEN. # } * { 0SCAN_QTY. #. LV_PROD. #. LV_PROD. #. #. LV_PROD. # } . #. #. #.LV_BUDGET. LV_PROD. 2013-05-13 CUSTOMER 51/62 . #. #. #. For more information. the InfoProvider to be used for a given trade promotion. this planning function creates the relevant valid combinations of characteristics. if your BI Content includes more than one planning InfoCube. in the runtime filter.8 8. 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. For example. see the BAdI documentation assigned to the BAdI definition in the SAP NetWeaver BW system. For example. This can be achieved by restricting the InfoProvider characteristic. For more information. 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.21 BI Content Migration BAdI’s in SAP NetWeaver BW For example. but the system does not do this automatically. you can use this BAdI to specify. This will prevent the generation of invalid combinations on an InfoProvider that is not applicable. if the application wants to set a characteristic value of 100 for every record in SAP NetWeaver BW. For more information. . see the BAdI documentation assigned to the BAdI definition in the SAP NetWeaver BW system. Two InfoProviders can be separated based on the sales organization: for example. you can adjust the runtime filter sent by the application and add variables or additional values.z^%3Ç Generate Combinations Based on the characteristic relationships the application sets at runtime. all the data should be saved in the InfoProvider DSO1 and not DSO2. When the application is planning in the first sales organization. BAdI: Determination of Values for Query Execution (RSCRM_IMP_QUERY) Before executing the query. Generating combinations automatically sets this value to every valid record the application creates at runtime. 52/62 CUSTOMER 2013-05-13 . the standard planning function can be used to restrict this characteristic to a particular value. 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: . 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. These combinations will be processed by subsequent planning functions. This characteristic would not have to be part of the list of characteristics mapped by the application. see the BAdI documentation assigned to the BAdI definition in the SAP NetWeaver BW system.z^%3Ç 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. 8 8. UnderApplication Help.22 Configuring Extensibility For information about configuring extensibility. 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.com/ crmaddons SAP Accelerated Trade Promotion Planning . 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 .22 BI Content Migration Configuring Extensibility 8. see SAP Help Portal at http://help.23 Example of BI Content with BPS The following is an example of BI Content you use for planning with BPS. 8. InfoObjects Used for Key Figure Planning with BPS Real-Time InfoCube PC1 InfoObject Type CHA01 CHA02 CHA03 CHA04 CHA05 KYF01 KYF02 KYF03 KYF04 KYF05 InfoCube SC Characteristic Characteristic Characteristic (has CHA05 as a navigation attribute) Characteristic Characteristic (is a navigation attribute for CHA03) Key figure Key figure Key figure Key figure Key figure The following table shows the InfoObjects of InfoCube SC (for the baseline data): InfoObject Type CHA01 CHA02 CHA03 BKYF Planning Areas Characteristic Characteristic Characteristic Key figure The following table shows the planning areas and their corresponding InfoCubes: Planning Area InfoCube PLA_PC PLA_SC PC1 SC 2013-05-13 CUSTOMER 53/62 .sap. 23 BI Content Migration Example of BI Content with BPS Multi-Planning Area The following table shows the planning areas of multi-planning area MPA_PC: Multi-Planning Area Planning Areas MPA_PC PLA_PC PLA_SC Planning Levels The following table shows the planning levels and their corresponding planning areas: Planning Level Planning Area PLL_PC PLL_SC Planning Level PLL_PC PLA_PC PLA_SC The following table shows the InfoObjects of planning level PLL_PC: InfoObject Type CHA01 CHA02 CHA03 CHA04 CHA05 KYF01 KYF02 KYF03 KYF04 KYF05 Planning Level PLL_SC Characteristic Characteristic Characteristic Characteristic Characteristic Key figure Key figure Key figure Key figure Key figure The following table shows the InfoObjects of planning level PLL_SC: InfoObject Type CHA01 CHA02 CHA03 BKYF Ad Hok Package AHP_PC Characteristic Characteristic Characteristic Key figure Ad hoc package AHP_PC is based on planning level PLL_PC.8 8. The following table shows the InfoObjects of ad hoc package AHP_PC: InfoObject Type CHA01 CHA02 Characteristic Characteristic 54/62 CUSTOMER 2013-05-13 . 8 8.23 BI Content Migration Example of BI Content with BPS Type InfoObject CHA03 CHA04 CHA05 Planning Layout Characteristic Characteristic Characteristic 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 CHA02 CHA03 CHA04 CHA05 KYF01 KYF02 KYF03 KYF04 KYF05 Characteristic Characteristic Characteristic Characteristic Characteristic Key figure Key figure Key figure Key figure Key figure Lead column Lead column Lead column Header Header Data column Data column Data column Data column Data column Displayed Displayed Displayed Hidden Hidden Displayed Displayed Displayed Displayed 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 20 30 40 50 60 70 80 KYF01 KYF02 KYF03 KYF04 KYF05 CKYF01 CKYF02 Basic key figure Basic key figure Basic key figure Basic key figure Basic key figure Calculated key figure Calculated key figure 0 0 0 0 0 KYF02 BKYF * + 0 0 0 0 0 KYF03 KYF05 Uses a function module to retrieve data based on the join between planning area PLA_SC and planning level PLL_SC - Planning Profile The following table shows the planning areas of planning profile PPROF: Planning Profile Planning Areas PPROF PLA_PC PLA_SC 2013-05-13 CUSTOMER 55/62 . PC3 56/62 CUSTOMER 2013-05-13 . PC3 PC2.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.8 8. PC3 PC2. 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 CHA01 CHA02 CHA03 CHA04 CHA05 KYF01 KYF02 KYF03 KYF04 KYF05 NKYF01 NKYF02 Characteristic Characteristic Characteristic Characteristic Characteristic Aggregating key figure Aggregating key figure Aggregating key figure Aggregating key figure Aggregating key figure Non-aggregating key figure Non-aggregating key figure The following table shows the InfoObjects of DSO PC3 (for the baseline data): InfoObject CHA01 CHA02 CHA03 BKYF MultiProvider MC Type Characteristic Characteristic Characteristic Key figure The following table shows the InfoProviders of MultiProvider MC: InfoProvider Type PC2 PC3 Direct-update DSO DSO The following table shows the InfoObjects and the DSOs the InfoObjects are assigned to: InfoObject DSO CHA01 CHA02 CHA03 PC2.24 BI Content Migration Example of BI Content with the Planning Applications Kit 8. 8 8. The following table shows the InfoObjects of query QRY01: Area in the BEx Query Designer InfoObject Properties Filter → Default Values Filter → Default Values Filter → Default Values Filter → Default Values Filter → Default Values CHA01 CHA02 CHA03 CHA04 CHA05 - 2013-05-13 CUSTOMER 57/62 . The following table shows the InfoObjects of aggregation level AGG_MC: InfoObject Type CHA01 CHA02 CHA03 CHA04 CHA05 KYF01 KYF02 KYF03 KYF04 KYF05 NKYF01 NKYF02 BKYF Query QRY01 Characteristic Characteristic Characteristic Characteristic Characteristic Aggregating key figure Aggregating key figure Aggregating key figure Aggregating key figure Aggregating key figure Nog-aggregating key figure Nog-aggregating key figure Aggregating key figure Query QRY01 is based on aggregation level AGG_MC.24 BI Content Migration Example of BI Content with the Planning Applications Kit DSO InfoObject CHA04 CHA05 BKYF KYF01 KYF02 KYF03 KYF04 KYF05 QKYF01 QKYF02 KKYF Aggregation Level AGG_MC PC2 PC2 PC3 PC2 PC2 PC2 PC2 PC2 PC2 PC2 PC2 Aggregation level AGG_MC is based on InfoProvider MC. 3. 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 NOTE KYF02 BKYF + KYF05 When you activate your BI Content. choose BI Content Object Type . In middle pane.24 BI Content Migration Example of BI Content with the Planning Applications Kit InfoObject Properties Area in the BEx Query Designer Free Characteristics Free Characteristics Free Characteristics Rows Rows Columns Columns Columns Columns Columns Columns Columns Columns Planning Functions CHA03 CHA04 CHA05 CHA01 CHA02 BKYF KYF01 KYF02 KYF03 KYF04 KYF05 NKYF01 NKYF01 Drill down Not Input-Ready aggregating key-figure Input-Ready aggregating key-figure Input-Ready aggregating key-figure Input-Ready aggregating key-figure Input-Ready aggregating key-figure Input-Ready aggregating key-figure Non-aggregating key-figure Non-aggregating key-figure Planning functions PLF_01 and PLF_02are based on aggregation level AGG_MC. 58/62 CUSTOMER 2013-05-13 . 4. Double-click on Select Objects to view the list of planning function types. under All Objects According to Type. you must activate the following planning function types in transaction Data Warehousing Workbench: BI Content (RSA1) in SAP NetWeaver BW: &˙3´ıí Deletion and Redistribution by Reference Data (0RSCRM_IMP_DEL_DISTR) &˙3´ıí Set/Distribute Values (0RSCRM_IMP_DIS_VALUE) &˙3´ıí Time Shift (0RSCRM_IMP_TIMESHIFT) To activate the planning function types in transaction RSA1. 2. Select the planning functions to activate and choose the Transfer Selections pushbutton. choose Planning Function Type for Planning Select Objects .8 8. In the left-hand pane. do the following: 1. for example. for example. for example. program names. names of variables and parameters.Typographic Conventions Example <Example> Description Example Example Example Example Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system. database table names. messages ¬−´Žq Source code or syntax quoted directly from a program ¬−´Žq File and directory names and their paths. menu names. These include field labels. and names of installation. and menu options.sap. “Enter your <User Name>”. These include report names. SELECT and INCLUDE Keys on the keyboard http://www. upgrade. and database tools Technical names of system objects. menu options Emphasized words or expressions Words or characters that you enter in the system exactly as they appear in the documentation Textual cross-references to an internet address Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web Hyperlink to an SAP Note. ¬−´Žq Cross-references to other documentation or published works ¬−´Žq Output on the screen following a user action. Arrows separating the parts of a navigation path. for example. pushbutton labels. and key concepts of a programming language when they are surrounded by body text. SAP Note 123456 ¬−´Žq Words or characters quoted from the screen. screen titles.com /example 123456 Example Example EXAMPLE EXAMPLE 2013-05-13 CUSTOMER 59/62 . transaction codes. for example. Microsoft. INTERMEC is a registered trademark of Intermec Technologies Corporation. POWER7. BlackBerry PlayBook. PostScript. UNIX. z/ OS. Program Neighborhood. PowerHA. Multi-Touch. Google Mobile. SAP. iPad. ICA. Crystal Decisions. Acrobat. and Motif are registered trademarks of the Open Group. Gmail. Citrix. Crystal Reports. Google Checkout. Google Apps. zEnterprise. POWER6. IOS is a registered trademark of Cisco Systems Inc. Excel. PowerPoint. z10. 60/62 CUSTOMER 2013-05-13 . Google Voice.com © Copyright 2013 SAP AG. Power Architecture. Sybase 365. z/VM. XML. Outlook.sap. Linux is the registered trademark of Linus Torvalds in the United States and other countries. System i5. Safari. iBooks. Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH. OS/390. BlackBerry. 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. Sybase and Adaptive Server. Google Mobile Updater. Retina. and W3C are trademarks or registered trademarks of W3C®. Objective-C. Google Maps. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. GPFS. DB2. POWER6+. POWER. System i. R/3. BBM. Storwize. RETAIN. Google Sync. and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries. Sybase is an SAP company. Redbooks. PartnerEdge. OS/2. DB2 Connect. Web Intelligence. App Store. System x.SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www. and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited. Apple. Motorola is a registered trademark of Motorola Trademark Holdings LLC. BusinessObjects. System Storage. World Wide Web Consortium. Tivoli. ByDesign. Intelligent Miner. iTunes. System p. System z10. iPhone. SAP BusinessObjects Explorer. Xcelsius. Siri. BlackBerry Storm. pureScale. Windows. System z. BlackBerry Bold. Oracle and Java are registered trademarks of Oracle and its affiliates. BlackBerry Torch. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. SAP HANA. PowerVM. BlackBerry Pearl. XIV. WinFrame. and Xcode are trademarks or registered trademarks of Apple Inc. Business Objects is an SAP company. and Smarter Planet are trademarks or registered trademarks of IBM Corporation. Power Systems. BlackBerry Storm2. RIM. Duet. OSF/1. Google Data API. iAnywhere. System p5. Bluetooth is a registered trademark of Bluetooth SIG Inc. BladeCenter. iPhoto. PowerPC. VideoFrame. Adobe. Business Objects and the Business Objects logo. iPod. Google Store. YouTube. and Visual Studio are registered trademarks of Microsoft Corporation. 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. Wi-Fi is a registered trademark of Wi-Fi Alliance. The information contained herein may be changed without prior notice. RACF. Massachusetts Institute of Technology. MetaFrame. HTML. Google Mobile Ads. IBM. WebSphere. AIX. DB2 Universal Database. Dalvik and Android are trademarks or registered trademarks of Google Inc. HACMP. SQL Anywhere. Informix. the Adobe logo. BlackBerry Curve. Google Mail. StreamWork. X/Open. Google Updater. XHTML. Silverlight. and MultiWin are trademarks or registered trademarks of Citrix Systems Inc. SAP NetWeaver. All rights reserved. Google App Engine. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only.comhttp://service. National product specifications may vary.sap. These materials are subject to change without notice. if any. 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. Crossgate is an SAP company. and SAP Group shall not be liable for errors or omissions with respect to the materials. m@gic EDDY. Documentation in the SAP Service Marketplace You can find this document at the following address: http://service. and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries.sap.Crossgate. B2B 360°. without representation or warranty of any kind. Disclaimer Some components of this product are based on Java™. Nothing herein should be construed as constituting an additional warranty. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited. as is any decompilation of these components.com/ instguidesinstguides 2013-05-13 CUSTOMER 61/62 . 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. All rights reserved. . The information contained herein may be changed without prior notice.com © Copyright 2013 SAP AG.sap.SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.