SAP Hybris Billing, Pricing Simulation Extended Functions Release 2.0, SP03

Transcription

1 SAP Hybris Billing, Pricing Simulation Extended Functions Release 2.0, SP03 Document Version

2 TABLE OF CONTENTS EXTENDED FUNCTIONS IN SAP HYBRIS BILLING, PRICING SIMULATION... 3 Using Alternative Sort Sequences When Selecting Data to Be Used to Execute a Simulation... 3 Technical Information... 3 Procedure... 3 Using a Simulation Result as a Data Basis for Additional Simulations... 4 Prerequisites in the Tariff... 4 Technical Information... 4 Procedure... 5 Points to Observe When Creating a Price Model... 5 Configure the Mapping of the Chargeable Item Classes... 5 Using the Simulation Result in a Follow-up Simulation... 5 Query Viewer... 6 Availability

3 EXTENDED FUNCTIONS IN SAP HYBRIS BILLING, PRICING SIMULATION Using Alternative Sort Sequences When Selecting Data to Be Used to Execute a Simulation Usage data is transferred in order according as the time at which the events were created by the service user. The sort sequence is defined by the contract for a service user (subscriber) and the consumption date (date on which the event was generated by the subscriber) and is therefore strictly chronological. The default sort sequence proposed in the standard system can however be changed, so that the events to be rated are transferred to the simulation in a different grouping. This is always advisable if pricing is extremely context-dependent This means you can perform a rating according as various criteria, such as: Subscriber groups Document or service type groups Grouping of specific transactions (such as specific purchasing transactions) A modified sort sequence can only be defined for one sort criterion. This overrides the chronological sorting defined for each contract. Any of the available fields from the usage data (CDR) can be used as a sort criterion. The usage date is used to sort within the sort criterion. Note: Changing the default sorting can have a significant influence on performance when the simulation is executed. Recurring basic charges or resetting counters using defined events (such as the start or end of the month) can produce inaccurate results. Technical Information Usage data in the pricing simulation is available in a generic format. The chargeable item class used defines the content of the respective usage data fields. To define a modified sort sequence, you must therefore define which of the generic fields is to be used for an alternative sorting in relation to the chargeable item class. As result of this, a defined grouping field must be suitable for the chargeable item class and the associated charge. To be able to define a modified sort sequence, the chargeable item class must therefore be known, which is in turn used by the price models that are based on a modified sort sequence. Procedure To change the sort sequence, you can proceed as follows: 1. Access the SAP Implementation Guide to configure the pricing simulation (transaction PSIIMG). 2. The modified sort sequence can be defined in Customizing of the Pricing Simulation under Scenarios Define Rating Scenarios. a. Create the scenario you require or select an existing scenario. b. Select a field for which sorting is to be performed from the generic usage data structure in the Group Field field. c. Access the Chargeable Item Class submenu to define the chargeable item class, which establishes the connection between the generic field and the field structure of the chargeable item class. You can specify several classes here. 3. To be able to use a modified sort sequence in a simulation, the rating scenario must be combined with an aggregation group as an overall scenario. The selection of usage data is then restricted to the predefined chargeable item classes when the simulation is executed. If the user has made a restriction to different chargeable item classes, the system overrides this selection. 3

4 Using a Simulation Result as a Data Basis for Additional Simulations Usage data that is based on a simulation could previously be historical usage data or modeled usage data. A simulation result can now be used as a data basis for a subsequent simulation. This means that dependent calculations can be performed in several simulation steps. This has the additional advantage that individual simulations can be used to display interim results. To make a distinction between the different types of data basis used, a new data source type has been introduced in the simulation, which specifies the usage data on which the simulation is based. Possible usage data sources are: Historical Modeled Simulation result Starting from an initial simulation (basic simulation), any number of simulations can be created, which are each based on the preceding simulation. Any simulation (historical, modeled, simulation result) can be used as the initial simulation. The basic prerequisite for using a simulation result in a subsequent simulation is that the result of the initial simulation is not summarized using aggregation groups (overall scenario and aggregation groups), but is saved at individual record level. Note: If a basic simulation is already used in a follow-up simulation, its assigned scenario can no longer be modified. A follow-up simulation is possible for a single tariff from the basic simulation. Simulation results are saved in the tariffs found in a simulation. If an initial simulation has several tariffs, and therefore result areas, you must define which tariff-based result is to be used as the data basis for the follow-up simulation. Note: A basic simulation used cannot be deleted as long as its result is used in another simulation. Note: Dependent charges are not currently supported. This means that the system can only subsequently process the price of an event if it is determined from a master charge. Prerequisites in the Tariff Previously, a tariff could only be applied to historical or modeled usage data. If a tariff also exists in the historical usage data, it is defined as such and as being productive. This indicator is selected automatically by the system. The options for editing a productive tariff are limited. You require specific authorizations to edit this type of tariff. A new product type, which explicitly defines that a tariff uses a simulation result for the subsequent calculation is available. Product types: Productive: (generated by the system) Usage data: To be used for historical and modeled usage data Simulation result: To be used for simulation results Tariffs with the simulation result type can only be used in a simulation that also has the simulation result type. Tariffs with a different type cannot be used in a simulation of this type to configure simulation tariffs. It is important that this type of tariff uses the same reference charge plan as the tariff that is used for the initial basic simulation. Technical Information If a simulation accesses the result of another simulation, the data field that contains the results field for the usage data must be identified. The results field from a basic simulation run is used in the follow-up simulation 4

5 in one of the generic numerical fields (PN_01 40) in the usage data structure (CDR). You can configure the position of the field in the usage data, and this is recorded in the chargeable item class. Performing a configuration between the basic and follow-up simulation serves two purposes: It defines the field in the usage data that contains the result of the basic simulation. It defines how the price model for the follow-up simulation can be used to access the result of the initial simulation. Procedure Points to Observe When Creating a Price Model Note that the price models for the follow-up simulation contain a field in which the result field of the basic simulation is entered when the follow-up simulation is executed. This field must also be used for the calculations required in the follow-up simulation. Configure the Mapping of the Chargeable Item Classes Configuration between the chargeable item class for the price model used in the basic simulation and the chargeable item class for the price model used in the follow-up simulation. Note: You must know which chargeable item class is used by the charge plans for the tariffs that are used in the basic and follow-up simulations. A chargeable item class can only be defined once as an initial structure (source). To define the configuration for simulations that are based on one another, you can proceed as follows: Access the SAP Implementation Guide to configure the pricing simulation (transaction PSIIMG). You can define the assignment of the chargeable item classes and their fields in Customizing of the Pricing Simulation under Basic Simulation Chargeable Item Class Mapping (view cluster PSIVC_CIT_MAP_SIM). Mapping must be performed within a catalog. Assignment between the chargeable item classes, which are used by the basic simulation tariffs (source) and the chargeable item classes, which are used by the follow-up simulation tariffs (target). Within the chargeable item class mapping, you can define the way in which fields in the basic simulation (source) are to be used in the follow-up simulation (target). The contents of the basic simulation are transferred to the generic fields in the usage data (CDR) according as the assignment made when executing a follow-up simulation. To be able to access the results field for the basic simulation Price excl. Dependent Charge (PRICE_EXCL_DP) in the follow-up simulation, this must be mapped to one of the generic numerical fields (PN_01 PN_40), which is accessed in the price model for the follow-up simulation for subsequent processing. If no field assignment is made, the system transfers the field content without modification from the initial structure to the target structure. Using the Simulation Result in a Follow-up Simulation A simulation that is to access the result of a previously executed simulation requires the Simulation Result data source type. This can only be assigned when the simulation is entered. It can no longer be modified subsequently. Any simulation whose result has been saved without being summarized can be used as a basic simulation. Note that the tariffs used in the initial simulation are based on charge plans whose associated chargeable item class was maintained in the configuration for the basic simulation. The simulation result of the basic simulation does not otherwise affect the follow-up simulation. The follow-up simulation therefore only observes usage data that is based on a chargeable item class for which a mapping exists. This means that if 5

6 no mapping is available for any chargeable item class in a basic simulation, the follow-up simulation terminates with an error. If a basic simulation contains several tariffs and therefore results, you must define a tariff whose result is to be used for subsequent processing. The simulation tariff, which is to be applied to the result of the basic simulation must be configured in the follow-up simulation. Summary A follow-up simulation must have the Simulation Result data source type. One basic simulation must be defined. A basic simulation can be any simulation whose result has not been saved in a summarized format. If the basic simulation contains several tariffs, one of these must be selected for the follow-up simulation. The follow-up simulation must be configured with a tariff that is suitable for the basis simulation. A mapping of the chargeable item classes must be available When analyzing the simulation, the Follow-Up Simulation function can be used to easily create a follow-up simulation, which uses the current simulation as a basic simulation. Query Viewer In the Query Viewer, the Auto Start On/Off function can be used to specify for each user whether a query is to be executed again when it is accessed, and if dimensions or key figures are changed, or whether execution is only to be defined manually using the Start function. The setting made here applies to all queries. Availability The enhancements to the simulation described in this document are available in the following notes for the SAP Hybris Billing, Pricing Simulation 2.0 SP03: API: UI:

7 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see for additional trademark information and notices. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE s or its affiliated companies strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.