You are on page 1of 5


Document: Xcelsius Dashboards for Sales and Distribution URL: Date created: August 12, 2013

© 2013 SAP AG or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP 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. Please see for additional trademark information and notices.

Note This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

PUBLIC © 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 1 of 5

com SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability ABAP Technology UI Technology Launchpads . are available here. net values. So that performance is not compromised unneccessarily at runtime.30 BI JAVA For more information. for example. the pricing procedure RVAA04 is configured in such a way that it can be used as the basis for evaluations on the structure of the base values. A BEx query is assigned to each connection. see Adjust Pricing Procedure. The visualization layout settings are tailored to the respective analytics objective. You can use these dashboards with the defined BEx queries as a template. You have done the following to develop your own dashboards. which are delivered with this business function. In Customizing for Sales and Distribution under Basic Functions Pricing Pricing Control Define and Assign Pricing Procedures . are also the template for the queries used in the dashboard. and to include a dashboard you have developed yourself. Adjust Pricing Procedure You have to adjust your pricing procedure for price determination so that the evaluation Discounts (As a Percentage of the Base Value) can determine the discounts correctly in the dashboard Performance in Sales and Distribution. Prerequisites You are familiar with pricing control. you can use pricing procedure RVAA04 as an example.20 Patch Level 2.0 EhP 1 BI JAVA Support package 03 for SAP NW 7. The unrestricted subtotal fields KZWI1 to KZWI6 are available for this purpose. Generally. or to edit the dashboards provided by SAP: You have installed Xcelsius 2008 SP3 Fixpack 4. For more information. Integration You use SAP BusinessObjects Xcelsius to create and edit dashboards. You have adjusted your pricing procedure for price determination so that the evaluation Discounts (As a Percentage of the Base Value) can determine the discounts correctly in the dashboard Performance in Sales and Distribution. several data connections of the type SAP NetWeaver BW are set up. To make this adjustment. Example Based on the condition types. and tailor them to your enterprise-specific analytics objectives using the functions in the SAP BusinessObjects Xcelsius application. You can integrate the settings for the condition types into your customer-defined pricing procedures. For more information. whereas the billing document contains actual PUBLIC © 2013 SAP AG or an SAP affiliate company. Alternatively. You have installed SAP GUI 7.Xcelsius Dashboards for Sales and Distribution You are provided with three Xcelsius Dashboards which enable your managers and employees in Sales and Distribution to perform adhoc analyses. Defining Condition Types Reporting and statistics are generally not used at document condition level. Page 2 of 5 . see SAP note 1526708. The following Xcelsius Dashboards for Sales and Distribution are available: For managers: Quote and Order Progress Performance in Sales and Distribution For internal sales representatives: Day-to-Day Activities Prerequisites You have activated the content bundle Content Activation for Logistical Sales for Dashboards (LOG_SD_ANALYTICS_DASHBOARD). subsequent compensation. You have done the following to configure the launchpad (transaction LPD_CUST). all values in the order are plan values (planned revenue. All rights reserved. for example: You have created a type H RFC connection (HTTP to ABAP) to the OLTP system (transaction SM59). The net value (NETWR) and the cost (WAVWR).10 Patch Level 12 or SAP GUI 7. discounts granted by sales employees. The role SAP_QAP_BW_DASHBOARDS is assigned to your user. The BEx queries used. You use the ZWISCHENSUMME indicator to assign the condition types. You have installed one of the following support packages: Support package 09 for SAP NW BI7. another way of determining the pricing result is necessary. and standard discounts). planned costs). see Creating a Technical User. For more information. To enable communication for the backend system and the web client. For more information about configuring the launchpad. you can install Java patch SP07. see SAP Help Portal at To evaluate how the discounts are distributed. for example data is presented as a line graph or pie chart. You have entered the name of the RFC connection as a system alias (transaction LPD_CUST). and especially discounts (customer-specific discounts. planned revenue deductions. the queries defined for the dashboard only evaluate data for a particular analytics objective. see Pricing and Conditions (SD-BF-PR). but at document item level. your user is assigned a technical user role. you have selected the Maintain Pricing Procedures activity and opened pricing procedure RVAA04. For each dashboard. for example.

are stored in the fields NETWR and WAVWR. The standard price PR00 is defined as the base value. the customer-specific price is calculated as the delta for the base price. 3. With this condition type. These two conditions are the only condition types in the procedure that are not static and are defined with condition class B (= price). move xkwert to komp-kzw1. they must contain the value formula 006 (base price) or 906 (base price PR02). At the end of the pricing procedure. you have to create a new value formula (value formula 931 in the example pricing procedure) in order to fill the subtotal 1 (KZWI1). Key figure 4 – Manual conditions (KZWI4) To ensure that key figures 3 (customer-specific conditions) and 4 (conditions which a sales employee has entered manually in the document) can be kept PUBLIC © 2013 SAP AG or an SAP affiliate company. Reason: If these conditions were defined as prices. Each condition has to be assigned to one of these key figures. Condition type PR0B (customer-specific price) is new. You use the ZWISCHENSUMME indicator to assign the condition types. you can add a formula which compares the sum of the subtotals 1 to 4 with the net value. they would deactivate all previous conditions and therefore also the base value. you have to differentiate between customer-specific discounts that are determined automatically. either as condition EK01 or condition PR0A. that is. 2. Determination of Key Figures Key figure 1 . it should be assigned to the subtotal 1. Exceptions to this are the conditions EK01 and PR0A. This ensures that the value of the price conditions is defined as the delta for the net value developed previously. The base value must always be available. 100% discount) are assigned to key figure 2. You can use this information to check whether the settings are correct.values. This includes customer-hierarchy conditions. All rights reserved. An appropriate message may also still be issued if a result is incorrect. However. One of these conditions must always be determined during pricing. to ensure that these conditions act like a price. Key figures 1-5 are stored in the subtotal fields KZW1 to KZW5. A new exclusive access sequence PR0B is set up. this would lead to incorrect results. All other price conditions must be defined as surcharges or discounts with condition class A . PR0A is initially created as a copy of PR00 but with access sequence PR0A and reference condition type PR00. The key figures are determined as follows: Key figure 1: Base value (value resulting from a basic price to be defined) Key figure 2: Standard conditions: (all general conditions which are found automatically and are not customer-specific) Key figure 3: Customer-specific conditions (sum of all conditions that are found automatically. The condition type has condition class A = Surcharge/Discount. Customer-specific prices are stored in the new condition type PR0B. The following prices must be removed from the condition and added to a different condition type: Article prices and price list prices are stored in the new condition type PR0A (general price). If you want to evaluate discounts. This means that this condition usually has priority. Therefore. The sum of the condition subtotals 1-4 results in the net value ((KZWI1 to KZWI4) = NETWR).Spec. form frm_kondi_wert_931 2. Page 3 of 5 . You can use the following template to create the value formula. Key figure 3 – Customer-specific conditions (KZWI3) All automatically determined conditions that are in any way customer-specific are assigned to key figure 3. Condition type PR0B (Customer-specific price): This new condition type “cuts” the customer-specific parts out of condition type PR00. Condition type EK01 (actual costs) As this condition primarily provides actual costs.Standard conditions (KZWI2) All automatically determined conditions that are not customer-specific (such as minimum price. net value and cost. The access sequence is set up in such a way that after the access to the customer-specific price. Price As the condition type PR0A needs to be cumulated for key figure 1. for example. external services (vendor invoices) are billed during the settlement of expences.Base value (KZWI1) 1. for example. the customer hierarchy is also searched. and manual discounts granted by sales employees. However. endform Key figure 2 . it is assigned the subtotal = B (cost) indicator. if condition EK01 is also available at the same time. This condition has priority if. The following table shows how to use the new condition types PR0A und PR0B in the pricing procedure: Step Count er 8 9 0 0 EK01 PR0A CTyp Descr iption Actual Costs Gener al Price 10 16 0 0 PR0B Base Price Cust. Condition type PR0A (general price) A new and exclusive access sequence has been configured for PR0A. This means that the prices under condition type PR00 can be maintained for all nodes of the customer hierarchy. 0 0 3 2 6 0 ERL 0 0 1 0 2 0 0 0 2 0 0 ERL 0 0 From To Manua l x Requi red Statist ics 8 2 Print SuTot Reqt CalTy pe 0 BasTy pe 0 AccKe y ERL Accru als Syntax 1. customer-specific contractual agreements) Key figure 4: Conditions which a sales employee has entered manually in the document Key figure 5: Expected expenditure for subsequent compensation paid out during rebate processing Key figure 6: Net value Key figure 7: Cost (cost of sales transaction) Key figures 6 and 7. 3.

you use this Xcelsius dashboard to call up an overview of the progress of quotation and order processing. Structure View Fulfillment rate of sales orders Description You check the degree of processing for the orders as well as the net value of the orders that are still open. in the simplest of cases. Any intermediate step in the pricing procedure can be used as the reference step. Key figure 6 . which. the value formulas used previously 011 (contribution margin) and 018 (contribution margin in %) were replaced by two new value formulas 911 and 918. In this case. It is then not possible to change automatically determined conditions that already exist. These conditions are generally statistical in the documents and represent an estimated value.apart. however. also possible to take the expected expenditure into account for subsequent compensation (rebate conditions). you use this Xcelsius dashboard to call up an overview of the performance of your sales team. You check. which means that the contribution margin represents the value DB2. If you do want to manually change automatically determined conditions.Rebate conditions (KZWI5) Here you can find all condition types that are set up as subsequent compensation and therefore have condition class C. The actual value is only available later. you have to group together key figures 3 and 4.Net value (NETWR) Field NETWR is hard-coded and contains the sum of all conditions that are not statistical but active and that are not taxes (indicator inactive = field is empty). but set up with condition class A (surcharge/discount). Returns rate Quantity and value trends in quotations and orders You check the development of the returns rate and the net value of incoming returns. The condition type PB01 (gross price) is a copy of condition type PB00. Key figure 7 . This key figure is used to display a contribution margin. all automatic condition types have to be set to “Cannot Be Changed Manually”. is calculated as follows: Contribution margin (DB1) = NETWR . across the quarters. The pricing procedure is set up in such a way that reference step 908 is defined for both of the subtotals. Quote and Order Progress Xcelsius Dashboard: 0XC_ERP_SLS_MGR_QUOTE_ORDER As a sales manager. Structure PUBLIC © 2013 SAP AG or an SAP affiliate company. The only manual changes that can be made are if conditions are added manually during order processing.WAVWR It is. Filter Number of orders Sales organization Sales office Sales group Sales employee 0OPS_11_HDR_Q0009 0SALESOFFICE_Q0002 0SALESOFFICE_Q0003 0SALESOFFICE_Q0004 0SALESOFFICE_Q0005 0OPS_11_ITM_Q0006. the average development in terms of quantity or value of orders and quotations and you check which trends appear. Key figure 5 . All rights reserved. The corresponding condition types are assigned to subtotal B. the following applies: Contribution margin (DB2) = NETWR + KZWI5 – WAVWR The contribution margin is represented in two subtotals in the pricing procedure: Step 950: Contribution margin as price Step 951: Contribution margin as percentage The reference step is used as the basis for calculating the contribution margin. To enable this level of flexibility. Page 4 of 5 . 0OPS_11_HDR_Q0003 0OPS_11_HDR_Q0005 Query Used 0OPs_11_HDR_Q0004 Performance in Sales and Distribution Xcelsius Dashboard: 0XC_ERP_SLS_MGR_PERFORMANCE As a sales manager.Cost (WAVWR) The cost conditions are stored in field WAVWR.

0OPS_11_HDR_Q0010 PUBLIC © 2013 SAP AG or an SAP affiliate company. 0OPS_11_ITM_Q0004 Discounts Filter You check the discounts granted to the 20 most important customers (according to the base value). You check which quotations currently have the status “open”. Structure View My top 10 / bottom 10 customers (in terms of incoming orders) Top 10 materials My open quotations Description You check which customers are currently at the top with regard to incoming orders. My current sales documents (quotations. orders. and you check the respective proportion of the base value. and those granted by sales employees are. you use this Xcelsius dashboard to call up an overview of the progress of quotation and order processing. You check which materials are selling particularly well at the moment. returns) You check which sales documents you have been working on in the last few days. and where additional activities are necessary. billing documents. 0OPS_13_ITM_Q0003 Discounts as a percentage of the base value You check how high the general and customerspecific discounts. Query Used 0OPS_11_ITM_Q0016 Revenue growth You check how revenue has developed in the current and past quarters and how revenue growth compares to the previous year. All rights reserved. and which are at the bottom. Sales organization Sales office Sales group Sales employee 0OPS_11_ITM_Q0011 0SALESOFFICE_Q0002 0SALESOFFICE_Q0003 0SALESOFFICE_Q0004 0SALESOFFICE_Q0005 Day-to-Day Activities Xcelsius Dashboard: 0XC_ERP_SLS_REP_MY_WORK As an internal sales representative.View Quotation conversion rate/quotation success rate Description You check how many quotations result in an order and thus determine how successful your team or employee is at creating quotations. Page 5 of 5 . according to incoming orders. 0OPS_11_ITM_Q0010 0OPS_11_ITM_Q0009 0OPS_11_ITM_Q0008 Query Used 0OPS_11_HDR_Q0006.