RELEASE 6.0E Support Package 2. Summary of New Features and Enhancements

Transcription

1 RELEASE 6.0E Support Package 2 Summary of New Features and Enhancements

2 Contents Contents... 2 Introduction... 5 About This Document... 5 Disclaimer and Liability Notice... 5 SAP ECC Version Requirements... 5 Feature Name Changes... 6 Global... 7 Business Script... 7 Business Script Definition... 7 Business Script Integration for Matrix... 7 Process Observer... 8 New Generation Launchpad... 8 Data Objects... 9 Duplicate Check Improvements... 9 Reprocess Data Object... 9 File Templates... 9 Business Script Integration... 9 Serial Number Integration... 9 Offline Maintenance Incidents Direct Agreements SEPA Compatibility with SAP SD Agreement Multi-Use Agreements Agreement Schedules Schedule Definition Claim Creation from Agreement Schedule Campaigns Agreement Postings Agreement Postings Removed Dependency with IP type Agreement Group Postings Derivation Postings in the Agreements Agreement Close-Out Follow-On Functions Other Bucket Type Automatic Truncation in Membership Periods Tab in Agreements Dimension Scales in Agreement Review Sheet Territory Locking Territory Assignment Structure Upload Agreement Log Improvement Creating Master Request Using Reference Tracking Tab and Proforma Tab in BSP Hide Summary Price Sheet Proforma Proforma Models Proforma Pushback Recreate and Refresh Proforma Background Processing Summary of New Features and Enhancements

3 Proforma Notes Any Value Description Proforma URL Characteristic Explosion Settlement New Bucket Types Simulation Bucket Usage Quantities and Amounts Bucket Usage Bucket Upgrades Dynamic Header Criteria Creating Dynamic Buckets from Settlement Parameters Priority for Updating Dynamic Buckets Creating Dynamic Buckets during Agreement Creation Agreement at the Bucket Item Level Processing Status on Bucket Header HR Settlement Posting to INFOTYPEs Claims Serial Number Integration in Claims Serial Number Integration in Pools Pools Submitter Settlement Parameter for Claims Pools Condition Type Sales Areas in Claims IP Document Reverse Cancellation Selective Claims Locking in Claims Validation Report Claims Output in IDoc Format Composite Processing Matrix Key Figure Grouping Characteristic Value Controls Material Based Conversion Definition for Quantity Usage as a Characteristic Reference Usage for Members Computation and Formula Functions Merged Scenarios (formerly Matrix Variant/Planning Area) Staging Data for Matrix Updating Matri x from Calculation Run Matrix Explosion Sweep Function BI Query as Usage Function Composite IP Modeling for Planning Reason Codes for Editable Eligible Amounts Deployment Code Participants Type Changes Derived Participation Postings Options for Components and Subcomponents Subcomponent Sequencing to Fetch Characteristics from Multiple Sources Key Figure Descriptions for Components and Subcomponent Store Exploded Hierarchy Summarization in Report Definition Line Items Display in BSP Call Back for Customer Search Help Summary of New Features and Enhancements

4 Calculation Run Extended Options in Reports Drivers (a.k.a. Express Rebates) Roster Redemption of Awards Pricing Lookup Other IP Enhancements Fund Hierarchy Improved Performance of Reconciliation Report BOM Explosion in Purchase Rebates Variants Authorization Workbench Data Maintenance - Pricing Deals On Demand Deals Deal API Pricing Pricing Area Workbench Pricing Workbench Maintenance Request Workbench Virtual Tables in Master Request Price Method Price Monitor Workbench Communication Segment in Catalogs Flexible Group as a Source to Catalogs Price Simulation Enhancements Price Source Explosion Profile in Structural Pricing Supporting Condition Class D for Taxes Data Maintenance Resources Domains Facets Data Flow Other Enhancements File Template for Info Records Creation of Multiple Info Records from Material List Integration of Product/Customer/Vendor List in Segments String Data Type for Attributes Propose Class when Relevant Attributes are entered INFO Records in the Material Dashboard Global / Maintenance Level Post from List User Maintenance Level Structure Assignment Structure Upload/Download using File template and BOM assignment Business Script for Attribute Rules Usage of the Attribute Set Separate List Type Authority Check for Items Support of Standard SAP Features Joint Production Vendor Sub-Range Summary of New Features and Enhancements

5 Introduction About This Document This document provides an overview of the Vistex Release 6.0E Support Package 2 new features and enhancements. Vistex provides this release summary to briefly explain new features and changes included the software. To ensure our customers benefit from new developments and improvements, Vistex offers a variety of sources of information about Vistex solutions. Vistex publishes release notes both on SAP Service Market Place and on Vistex VOICE at VOICE is a customer media channel for learning about Vistex solutions, networking with other Vistex users, and sharing knowledge and best practices for using Vistex solutions in the business processes that Vistex solutions support. VOICE provides an excellent vehicle for discussing new business trends, new features and enhancements, and engaging with the Vistex community about any topic that has piqued your interest. Further information about Vistex features can also be found in the Vistex Help Portal at This website provides extensive documentation from the Vistex Library on Vistex solutions, organized by release number, product and application. Vistex software releases, support packages and SAP Notes are all available on SAP Service Marketplace. Disclaimer and Liability Notice Changes made based on this information are not supported and can be overwritten during an upgrade. Vistex will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. Vistex offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this article including any liability resulting from incompatibility between the content within this document and the materials and services offered by Vistex. You agree that you will not hold, or seek to hold, Vistex responsible or liable with respect to the content of this document. SAP ECC Version Requirements Vistex Release 6.0E and 6.0E Support Pack 1 required SAP ECC 6.0 Enhancement Pack 5 with no requirement on the SAP Support Pack level. Vistex Release 6.0E Support Pack 2 introduces minimum SAP Support Pack levels to ensure proper installation and feature function, as follows: SAP ECC 6.0, Enhancement Pack 5, Support Pack Stack 11 SAP ECC 6.0, Enhancement Pack 6, Support Pack Stack 09 SAP ECC 6.0, Enhancement Pack 7, Support Pack Stack 02 5 Summary of New Features and Enhancements

6 Feature Name Changes As a result of continuing improvement and reviews, Vistex has decided to rename certain existing features beginning with this release: Price Request renamed to Master Request Matrix Scenario renamed to Subset Scenario Group renamed to Matrix Group Matrix Variant/Planning Area renamed to Scenario 6 Summary of New Features and Enhancements

7 Global Business Script SAP Solution Extensions by Vistex, as embedded components of the overall SAP ECC instance, offer a number of methods some native to SAP ECC and others developed by Vistex to construct rules and formulas for determining pricing and incentives. As a result, the implementation of calculation logic can be inconsistent and difficult to maintain. To streamline the definition and maintenance of calculation logic, and to improve the user experience of such activities, Vistex introduces Business Script. Business Script allows users to define calculation logic using language that is more human than computer. Business Script eliminates the need for the Formula Builder, Condition Editor and BRF+ features as well as Measures definitions. You may still use these tools, but Business Script will be default for all new implementations by Vistex. Business Script Definition The new Measure Workbench will hold all of the formulas and measures in one centralized area. Instead of separately using formula builder and measure features, all formulas and all of the measures are now maintained in one single area. In addition, it supports new functionalities. The workbench has three tabs: General Tab identify incoming and outgoing parameters that process data and produce results Fields Tab define the parameter name, description, variable type and references Steps Tab define logic and formulas used to produce results Business Script Integration for Matrix The new Business Script functionality has been implemented to replace the old formula functionality. Business scripts have been implemented into the functionality of the formula transaction and impacts all of the applications where formulas may be created. Existing formulas can be edited in the Formula Workbench. When creating a new formula, the users have an option to either use the old formula functionality or the new business script functionality. Users can maintain either existing formulas or business script. 7 Summary of New Features and Enhancements

8 Process Observer Process Observer is a new feature that enables the solution to efficiently provide business metrics for dashboard purposes, such as the Vistex LaunchPad. Process Observer can be used to count the number of new claims submitted each day, the total number of contracts that are active, the number of open requests at any given time, etc. This new functionality is incredibly valuable because it displays a comprehensive snapshot of real-time status of any process performed on an item. Process Observer serves as an activity auditor during the various lifecycle stages of agreements, agreement requests, claims and transaction register documents and IP documents. It can also provide tracking of the duration of an item between any stages in its lifecycle. Examples: Users can determine the number of items in the specific system status (e.g. started, running, finished, restarted) Users can determine end-to-end process visibility Number of items that have been created/posted/released during any specific time frame Number of agreements created from agreement requests Users can determine how long a process ran by linking the process creation event to the process final event Track how long it takes an agreement request to post Track how long it takes between creation of an agreement request and the creation of the subsequent agreement KPI information can be bucketed for easier display (e.g. each week, last 30 days, etc.) New Generation Launchpad The original Launchpad was introduced in Release D to provide customers with fully configurable landing page. The earlier generation Launchpad allowed users to configure organized lists of SAP or Vistex transactions or links to pre-defined reports. The original version of Launchpad is still available in this release. The next generation of Launchpad allows dashboard concepts to be introduced to the landing page, including KPI metrics, charts and other information in addition to links to SAP transactions, Vistex transactions or BCAs, reports and other web content. New Generation Launchpad is now in a Web view and fully customizable. The screen is only available in a web-based tile view (no SAP GUI option), and allows the user to log on to the SAP system when directly launching the Launchpad from a browser window. Vistex provides the Launchpad Builder to customize the Launchpad view, number of tiles, tile size, tile image and image carousel. The layout of the Launchpad can be configured: 8 Summary of New Features and Enhancements

9 Any number of tiles Multiple pages (up to 5 total) Number of columns of tiles per page Gap spacing size between tiles Each tile has settings to adjust: Size a mixture of small, medium and large tile sizes can be displayed Font font type, size and color of each tile is individually set Image background image with adjustable width, height Alignment slide tile left/bottom/top/right Visibility -- can choose to display or hide the tile Animation -- details scroll right/left/up/down and percentage scale Links a tile may have multiple links; links may be transaction or report The new Launchpad web view also provides flexibility to add multiple links to each tile from a Workspace or Process Observer. Users may drag-n-drop links from the workspace or may assign a Process Observer process ID. Runtime variables can be added to tile links, either in the tile or in a pop-up window. In order to add a chart to a tile, the IP report link has to be added to the workspace. Data Objects Data Objects was introduced in Release E-SP1 and has received minor enhancements to functionality in addition to a significantly improved user experience in Release E-SP2. Duplicate Check Improvements Potential duplicates found by Data Objects will now show the context of the possible duplicate within the document data. Previously, the potential duplicates were identified with an error message on the row. Reprocess Data Object Users can re-run the data validations on corrected data to determine if errors and duplicates have been properly resolved. Reprocessing can also be performed if the data validation configuration has changed since the prior validation process was completed. File Templates The File Template feature (available previously in other areas of the solution) has been introduced within Data Objects. Business Script Integration The new Business Script feature is available in Data Objects. For more information on Business Script, see the related topic in this document. Serial Number Integration Serial number tracking and validation has been integrated into Data Objects. For more information on the new treatment of serial numbers, see the related topic in this document. 9 Summary of New Features and Enhancements

10 Offline Maintenance Any version of data in Data Objects can be downloaded into a spreadsheet file, changed offline and uploaded into Data Objects again as a new version. Incidents The Incident management functionality enables users to record, manage and track concerns about data within the Vistex solution. A user may record an Incident for any Vistex data object type: customer, material, vendor, catalog, rule (condition), deal, agreement, clause, claim and any IP document. A user can record multiple issues per incident; each issue is a separate line item of the incident. Multiple objects can be assigned to an issue. The Incident Workbench consolidates and tracks incidents. The workbench has several tabs containing issue details, resolutions, related partners and document attachments. Examples of possible business scenarios: 1. The expected employee commission for a transaction was calculated as 4%, but employee believes that 5% is correct. Employee can create an incident to identify this issue and track its resolution. 2. A distributer s claim was adjusted by the manufacturer, and the distributor disagrees with the adjustment. The distributer can view the claim in the Vistex portal and file an incident for the claim. Direct Agreements This new concept allows users to define sales order pricing agreements without regard to a specific Vistex application. No subsequent IP document processing is expected with Direct Agreements, i.e. no billback, rebate or other subsequent documents are necessary. Direct agreements offer a similar header, rules sheet and other agreement elements as other agreement types. A direct agreement is an IP application but acts as a global agreement which is not specific to any application. Direct agreements provide sales order pricing similar to billback agreements but no subsequent IP documents (e.g. billback documents) are created. Direct Agreements can be created directly or via an Agreement Request. 10 Summary of New Features and Enhancements

11 SEPA Compatibility with SAP SD The Single Euro Payments Area (SEPA) is an initiative of the EU governments, the European Commission and the European Central Bank (ECB), to create an integrated payments market across Europe for any organization or individual making or receiving payments in euros. Vistex has integrated the SEPA (Single Euro Payments Area) compliant functionality into the appropriate Vistex IP documents. The SAP Sales and Distribution (SD) as well as the Agency Business (AB) components support the processing of direct debits within the Single Euro Payments Area (SEPA) in compliance with legal requirements. SD provides the SEPA-specific functions for processing sales documents and billing documents using Terms of Payment or Payment Methods. Vistex has extended this methodology to IP documents settled through the SD method. Mandates assigned to the Sales document (Sales Order and Invoice) are copied over to the IP documents, and during SD and/or AB settlement process, the mandates are passed to the respective Billing item. 11 Summary of New Features and Enhancements

12 Agreement Multi-Use Agreements The purpose of this new functionality is to use the same agreement in multiple Vistex applications without having to recreate the agreement. A Multi-Use Agreement is created from a Direct Agreement source, and may appear in multiple Vistex applications. This allows users to define billbacks, rebates and/or deals in a global agreement framework that can be extended into each relevant Vistex application from a central agreement object. For example, using this functionality a company may offer both rebates and deals to the same customers on a single agreement, or create a chargeback to a supplier for the cost associated with a deal offered to an end-customer. In previous releases, agreements and agreement numbers were specific to each Vistex application. This new functionality allows users to create an agreement that exists in multiple Vistex applications with the same agreement number. This extension of an agreement is supported in multiple scenarios: Extend Direct Agreement to IP Agreement/Deal Extend IP Agreement to IP Agreement Extend Direct/IP Agreement to IP/Direct Agreement Request Extend Direct/IP Agreement Request to IP/Direct Agreement Request Extend Deal to Direct/IP Agreement The agreement is created from the Direct Agreement Workbench using Multi-Use Agreement function. The Direct Agreement extension source has to be maintained in the application to extend the agreement to a different application. An extension source number is listed in the agreement header of the new agreement when an agreement is extended to a new agreement. Condition type group contains common condition types in the condition type group to extend the agreement; the same agreement number from the original agreement will be kept in the new agreement. Although the agreement is extended, the parameters of the agreement, including rules, can be specific to each instance of an agreement in a Vistex application to allow agreement rules to vary by Vistex application. Rules that should be common to all instances of the agreement, such as eligible customer or vendor, can be extended to the multiple agreements when maintained in Additional Price Sheets. Agreement Schedules Schedule Definition This new functionality allows users to determine when amounts are paid from an agreement. The amounts may be a fixed amount or calculated percentage, and may occur periodically. 12 Summary of New Features and Enhancements

13 A new Schedule tab is introduced in the Agreement Workbench for Release E- SP2. Schedule functionality allows users to allocate amount by payment period dates using agreement parameters. Each line item of the schedule defines a schedule type, start date and total amount which is allocated based on payment period schedule. Agreement schedules can be based on a specific date, a milestone (as defined) or periodic. When a scheduled amount is allocated, it is automatically and equally distributed among the periods if schedule type is periodic. provides flexibility to remove periods from the schedule by simply deleting the timelines and the amount is automatically recalculated and equally re-distributed based on the validity dates. Schedules appear in the Agreement Review Sheet and are fully supported in Agreement Upload/Download. Claim Creation from Agreement Schedule From the Schedules tab the total amount per line item can be allocated based on the schedule dates and special promotion running at the time. The expense for the promotion is distributed and the amount is allocated to the final materials. In order to allocate the expense the claim document is created from the item source. Once the claim is created and the amount is allocated, changes are no longer allowed. Schedule expense amounts can also be tracked from composite when defined in the subcomponent formula. Campaigns Campaigns are a new concept that exists above the agreement level. Campaigns are defined to plan marketing campaigns for new product launches or promoting existing products in one or more markets. After a campaign is defined and planned, one or more agreements can be generated from the campaign. This functionality allows users to plan, analyze, execute and measure promotional campaign activities through all Vistex applications (e.g. pricing, billbacks, deals, rebates, etc.) before creating any resulting agreements or deals. Each campaign is defined using a number of elements that are included in KPI metrics and used for profitability analyses. Elements are the pertinent information in the campaign (dates of the campaign, target market, type of campaign, etc.). Element details include dates, locations, evaluation criteria and day-to-day agenda. Agreements can be created from the campaigns. When agreement is created from a campaign, the campaign number is displayed on the agreement. 13 Summary of New Features and Enhancements

14 Agreement Postings Agreement Postings Removed Dependency with IP type The new nodes have been added for the postings to the agreement configuration and eliminated dependency on IP type. Agreement Group Postings Agreement Group is a new workbench for enabling Agreement postings. Agreement group is designed for user-friendly maintenance of postings data in Composite IP, Bucket and Transaction IP. The user is able to select either a single agreement or multiple agreements. The user has to maintain postings at the agreement type level. With this new functionality users will be able to check posting amounts. Derivation Postings in the Agreements Derivation Postings are the postings that the user can maintain on the agreement posting fields for Outstanding Settlement, Total Spend, Average Spend, and Close-out. Derivation Contribution is set up at the agreement type level. Users can assign a derivation of their choice and define their own formula. Agreement Close-Out Agreement closeout functionality is utilized when the agreement is about to be retired and when there will be no further activity related to the agreement. Prior to Release E-SP2, Close out agreement was selected from the edit menu, and once the agreement was closed it could not be re-opened again. With Release E-SP2, a new Close out tab is available from the Agreement Workbench, and the agreement can be closed-out for all periods or based on the user s selection of a specific period. After the agreement is closed, a claim document is created displaying the close-out amount. Each close out document can be cancelled from the Close-out tab. Mass agreement close-out functionality is also introduced. When a difference exists between the Actual Accrual and Expected Accrual, the solution creates a claim document with the adjustment amount, and the new Derivation For Postings logic is introduced for posting purposes. The close-out derivation steps can be assigned to the derivation postings to identify the distribution of the amount. Follow-On Functions Follow-On Functions is a mass report. Follow-On Functions is performed with the following options: Schedule this option has to be selected in combination with schedule type, usage and periodicity timeframe. Proforma the report can be created in correlation with Proforma profile for the agreement type Close Out this option can complete a mass close-out or individual, the follow on function is selected in combination with close-out type and reason, dates. Follow-on functions report can be executed in real-time or as a background job. 14 Summary of New Features and Enhancements

15 Other Bucket Type To create Buckets, the Bucket type can now be maintained at the Agreement type level. Buckets can be created manually, automatically and automatically using a scheduled job. Bucket validity dates can be derived from agreement header dates, settlement calendar or period profile. Bucket type can also be maintained at the Deployment Code level in the Agreement type maintenance. Automatic Truncation in Membership At times, users may want to replace existing membership data with an entirely new and updated membership list. Instead of having to determine the records that are to be added, changed or deleted, an exhaustive list of members can be imported to replace all existing data with new data. Replacing all existing data can ensure that unmentioned members in the new file are properly terminated. All existing membership records in the system for a given organization can be truncated, i.e. deleted, before loading the newly submitted membership records. A new membership submission category Replace is used in combination with the Revision date and submission date to replace existing membership data. Periods Tab in Agreements Prior to Release E-SP2, the periods were maintained under the Tracking tab with the respective deployment code and only one version could be maintained. Multiple agreement-specific periods are now possible in an Agreement using the new Periods tab. The new Periods tab is now available within an agreement; there is no need to maintain periods for the deployment code at the agreement level. Similar to the layout of periods under the former Tracking tab, periods can be set up in the new Periods tab. Periods can be defined with a predefined period profile or a document- or participant-specific period profile. Posting periods can be reviewed in the Agreement Overview screen. Dimension Scales in Agreement Review Sheet Scales Dimensions are now available for review in the Agreement Review Sheet from the Agreement Workbench. Territory Locking In the Territory Workbench under the Determination tab, if the assignment type of the territory was open in Change Mode, it prohibited other users from opening the same territory assignment type in any other 15 Summary of New Features and Enhancements

16 territory. With Release E-SP2, this has been enhanced to allow other territories to be changed simultaneously. Territory Assignment Structure Upload Release E-SP2 allows a user to upload a territory assignment structure from a file. Agreement Log Improvement The Agreement Log has a new look, which is similar to the Deal Log. Administrators can choose to revert back to the previous version of the Agreement Log. Creating Master Request Using Reference In any Agreement Workbench, a Master Request can be created using an agreement as a reference from the edit menu. The functionality will provide a pop-up window. Tracking Tab and Proforma Tab in BSP Now users can maintain Tracking tab and Proforma tab in the BSP screen as well as traditional SAP GUI screen. Hide Summary Price Sheet The Summary Price Sheet will not be displayed if there is only one price sheet being used. 16 Summary of New Features and Enhancements

17 Proforma Proforma Models Proforma is used to simulate the effect of changes to rule parameters of one or more agreements for a segment of customers and/or materials. Proforma can be used for budgeting, account planning, incentive simulations, accrual modeling, etc. Proformas can be created from multiple source types, including tracking documents, calculation runs, and price simulations and proposals. Proforma Profile has a new Proforma Model concept that categorizes the type of Proforma and its source. Proforma Model field allows the user to choose one of the following types: Rule-based model for a Proforma created from deals, deal requests, agreements, agreement requests, direct agreements, and direct agreement requests. Tracking model for a Proforma created from a calculation run for composite (versus transactional) sources. Simulation model for a Proforma created from price simulations. This model is useful for upfront planning purposes prior to the existence of any agreement or price request. Price model for a Proforma created from price proposals. Proforma Pushback Proforma is used to simulate the effect of changes to rule parameters of one or more agreements for a segment of customers and/or materials. This is accomplished in Proforma by copying the rules and parameters from the source(s) and allowing the user to modify the parameter values within the Proforma. Once the desired effects are realized in the Proforma, the user needs to apply these changes to the source(s). The values transferred into Proforma from the source documents can be updated and sent back to the source document. Only those fields that directly have been sourced from the rule can be updated in the Proforma and pushed back to the source document. In the Proforma profile for key figures, the pushback can be configured to update source fields on save or on post. If configured to pushback on save, the source document is updated when the Proforma is saved; if pushback is on post, the source document is updated when the changes in the Proforma are posted. Recreate and Refresh Proforma After creating a Proforma with any of the models described above, a user may recreate the Proforma or refresh the data within the Proforma. These functions are enabled in the Proforma Profile. Recreate Proforma function recreates the Proforma data from the source document. All manual adjustments not 17 Summary of New Features and Enhancements

18 part of the source documents will be lost. Refresh All function refreshes the Proforma data from source document, except changed values in the Proforma will remain the same. Background Processing Proformas can now be created in the background. Proforma Notes Notes can be maintained for Proforma from the Note tab. Notes may also be changed in the Planning Workbench. Any Value Description There is a new field at the Usage level called Characteristic Usage Description. In this field the user can enter a new value, and any characteristic at the level will be overridden to display the value entered. Proforma URL Now Proforma URL is available from any application. Characteristic Explosion The Proforma can be exploded based on a selected field, e.g. material, need to enter the field and select a function module to utilize the explosion. 18 Summary of New Features and Enhancements

19 Settlement New Bucket Types Release E-SP2 introduces new types of Buckets. The original single usage of Buckets indexed settlements by customer, period, etc. for transactional and composite scenarios. In addition to the original usage, two new usages are introduced: (1) Simulation Buckets and (2) Quantities and Amounts Buckets. These new usages are further described below. Simulation Bucket Usage Simulation Buckets allow users to apply existing (historical) data to proposed agreements without duplicating the historical IP document data. The amounts are calculated in the simulation buckets for analysis. The functionality allows users to estimate the outcome of incentives, paybacks or rebates for the upcoming periods using existing sales orders or billing documents without needing any subsequent IP documents. Source documents are used by the Bucket Simulation Report to create virtual IP document items that populate the bucket. Quantities and Amounts Bucket Usage Quantities and Amounts Buckets store quantities and values from line item key figures in the bucket itself. This condition-level bucket type is intended for composite processing. The advantage of this new functionality is retrieving quantity and amount data from the bucket while using buckets. The quantity and amount bucket created directly in the Bucket Workbench. The Bucket is updated when IP document(s) is created. Bucket Upgrades Dynamic Header Criteria Previously, buckets were created based on a few header criteria: material, partner and agreement. This release allows a user to use a wider range of criteria to define buckets. 19 Summary of New Features and Enhancements

20 Starting in Release E-SP2 users have the flexibility to define a wider variety of anchors for buckets, such as IP type, plant, settlement profile, etc. The new Criteria node field has been added to the configuration of the Bucket Types. It provides a field catalog to allow users the flexibility to maintain their own values or records in the bucket. Bucket Type can be assigned to the Bucket Profile, and the Bucket Profile is assigned to the item level at the IP type configuration. Specifically for using material as a header criterion in buckets, a new option has been introduced for retrieving the necessary data for performing Individual and Collective tracking for Government Pricing [life sciences industry] purposes. For Business Register, either the SAP Material or the Reported Material may be used in the Bucket criteria. For all other applications (Billbacks, Rebates, etc.) only the SAP Material may be used. Creating Dynamic Buckets from Settlement Parameters This new feature will help users to auto-create buckets from customer/vendor/employee settlement parameters to make tracking user-friendly and update buckets based on settlement parameter changes. Buckets can now be created automatically from customer/vendor/employee settlement parameters. This feature offers a Create Bucket configuration window for users to maintain behavior for bucket types created from customer, vendor and employee settlement parameters. For each bucket type, users can choose to create buckets from the settlement parameters automatically, manually, or not at all (do not create using settlement parameters). Buckets are recreated or deleted based on validity date changes in the associated settlement parameters. Priority for Updating Dynamic Buckets This updated functionality indicates the priority for updating the dynamic buckets with IP documents items. The settlement parameters flag at the header control for sales documents indicates the priority and updates the buckets based on the selection made. Options include using partner only, partner and parameter group, and parameter group only. The company code is used with each option, unless no buckets are found. Creating Dynamic Buckets during Agreement Creation This functionality will automatically create a bucket after an agreement is created. The attributes of the bucket, such as validity timeframe, will match the corresponding agreement. The buckets will be deleted if the corresponding agreement is deleted. Agreement at the Bucket Item Level The agreement associated with each condition in the Bucket item-level fields is captured to provide flexibility for further Composite processing. The solution will retain and display agreements fetched by the conditions in a bucket. 20 Summary of New Features and Enhancements

21 Processing Status on Bucket Header Users would like to know if a bucket is already fully settled or partially settled before the next settlement job is executed. In this release, tracking tables are introduced to avoid confusion on partially processed buckets. The Status tab in the Bucket Workbench displays the status of the bucket. HR Settlement Posting to INFOTYPEs Prior to Release E-SP2, HR postings were allowed only to INFOTYPE 15. Now users will be able to configure HR settlement postings to any INFOTYPE in the Payroll Profiles using the new Infotype field. 21 Summary of New Features and Enhancements

22 Claims Serial Number Integration in Claims Prior to Release E-SP2, standard SAP screens and functionality were utilized to process serial numbers in claims, and serial numbers were stored in SAP tables. As of Release E-SP2, serial numbers submitted in claims will be stored in Vistex tables. Serial numbers can be viewed in a new screen introduced at the item detail level in a Claim document. Claim validations can use serial number data to determine if a submitted serial number is valid (i.e. exists in tracking table) and whether the serial number pre-dates the claim (i.e. valid serial number but invalid claim). There is a refresh option to update the existence status of the serial number on the Claim item. Serial Number Integration in Pools The system will now allow tracking of serial numbers in supply chain inventory using Pools and Reservation documents. Pools Submitter Settlement Parameter for Claims In Release E-SP1 the Pools Submitter Parameters were defined and assigned in the Define Submitter Parameters node in the configuration. Starting with Release E-SP2, the Pools Submitter Parameters can be maintained from Customer/Vendor Settlement Parameters. The new Pool Parameters fields (Price Type, Reservation Type, Past Offset Periods and Future Offset Periods) can now be maintained in Customer/Vendor Settlement parameters. In addition, the new Pool Partner Role field has been added at the claim type configuration under Partners header. It allows users to assign a partner role of customer or vendor. Pools Condition Type Pools Condition Types are can now be maintained from the Claim Types Pricing element and can be calculated for the claim type. If the settlement parameters specify than a pools price should be calculated, the condition type should be included against which the price calculated for pools will be stored. Sales Areas in Claims In the prior releases the sales area in claims was determined from the sales order type. In Release E-SP2 the sales area can be determined from the claim type. Under the Claims Type, the new Sales Area field has been added to indicate the priority for using settlement partners. When creating a claim, the user may choose from the combination of the master sales area and the reference sales area of the customer, or select only from the master sales area of the customer. 22 Summary of New Features and Enhancements

23 IP Document Reverse Cancellation The system should allow the user to reverse the cancellation process in order to use the IP document for further processing. This feature provides efficiency and effective way of utilizing the same IP document and avoids the need to create a replica of the IP document. In the IP application workbench, select the required document and choose to reverse cancellation. After the cancellation of the IP document is reverse, the OP document can be utilized for further processing. The system logs the cancellation of the IP document in the audit trail of the cancelled document. Selective Claims Locking in Claims Validation Report Selective locking will help users to lock only those claims which are being processed in the Claim Validation Workbench. Even if the claims are selected by the Claim Validation report, by using the newlyintroduced selective locking concept the users gain the ability to work on these documents from various other workbenches simultaneously if it is not locked from the Claim Validation Workbench. In the Claim Validation Workbench there a Change Claims button that allows a user to lock claims. If any user is working on the claims from any other workbench at the same time they will receive a message stating that the claim is locked. Claims Output in IDoc Format IDocs are used in most SAP applications to transfer data among SAP applications and external systems. When generating claims within the solution to send to a supplier, the solution is now able to create these claims as outbound IDocs. In order to create an IDoc from Claim the user will run the Create Output IDoc for Claim report. 23 Summary of New Features and Enhancements

24 Composite Processing Matrix Key Figure Grouping Key figures now can be defined as a group in the Matrix Workbench for layout, and they can be viewed in the Planning Workbench in collapsed mode or expanded to see all of the data of individual key figures. Characteristic Value Controls Characteristics in the Matrix can now be controlled for blank values and non-specific values (similar to wildcard search). Release E-SP2 provides four options for Characteristic values: Can be blank Cannot be blank Can be any value and can be blank (i.e. can be wildcard/non-specific value or be blank) Can be any and cannot be blank (i.e. can be wildcard/non-specific value and cannot be blank) Material Based Conversion Definition for Quantity In prior releases, there was no option to convert the quantity based on material. A new material field is now available at the key figure level. When the MATNR is selected in the field it considers materials during the quantity conversion process in the Matrix characteristics. Usage as a Characteristic Prior to Release E-SP2, only one Usage could be selected for planning purposes. This feature allows multiple Usages in planning by introducing Usages as a part of the characteristic hierarchy in the planning process. There is no limit to the number of Usages that can be selected and compared. In the Layout tab, Usage is listed as a characteristic and part of the hierarchy. Only Anchor Usage can be maintained, the other Usages are display only. Reference Usage for Members Reference Usage can be assigned to a Usage to retrieve the members from that referred usage into the actual or anchor usage. The members of a usage can be used in the supplemental usage of the same scenario with this reference usage. When the usage is referred to an actual usage all the members from referred usage will be displayed or added to the actual usage. Then the actual or anchor usage cannot be edited to add the members, but the members can normally be added for the referred usage. For example, Plan Usage 001 may utilize Reference Usage 004, and therefore Plan Usage 001 may use members from Reference Usage 004. Computation and Formula Functions Merged Computation and Formula functions are merged in to a single function which is named Computation Function. 24 Summary of New Features and Enhancements

25 A function may be assigned to one or more categories. Load functions can be called when any data in the Planning Workbench is saved. Check functions are called when the Check and Complete feature is executed. Demand functions are called in planning features. A function may be categorized for Load and another type at the same time. Check and Demand categories are mutually exclusive; only one of these categories can be flagged for a function at one time. Scenarios (formerly Matrix Variant/Planning Area) This new functionality allows users to create variants for Matrices for planning purposes. A variant for the Planning screen is created in the new Variant Workbench and is used in the Planning Workbench. The variant stores selection criteria for the Planning screen fields in the Scenario Workbench. User-specific fields can also be flagged and saved, but user-specific fields can only be flagged during the creation of variant; once the variant is created, the user-specific fields become non-editable. Staging Data for Matrix Prior this release the IP document data was stored in the Matrix directly. This may not be desirable due to possible process issues. Starting with Release E-SP2, a staging area is introduced. While updating Matrix from a source document (IP document), the data will be stored in a staging area and a job may be run to update the Matrix from the staging area. Updating Matri x from Calculation Run A new Matrix Group field is introduced to determine which Matrix to update. The Matrix Group field is introduced at the Calculation Run level in the Deployment Code configuration to identify fields mapped to the Matrix. The conditions that evaluate the Matrix are also assigned in the dataset. Matrix Explosion The Derivation tab of the Matrix now has an additional derivation type called Explosion. Explosion can also be automatically added via the Add Explosion button on the header menu. Only a single Explosion ID can be used in derivation. In order to syndicate the data from different Matrices, the Explosion ID, key figures and characteristics values are maintained in the Matrix derivation type. The Explosion values are maintained in the Scenario Workbench at the Usage level. Users have flexibility to add multiple Matrix Explosion IDs for each Usage type and map each Matrix to the specific key figures and characteristics using source map along with target period and period mapping. The key figures indicate the placement target of the data in the Matrix. Characteristics provide ability to control the way data is pulled. Once Explosion ID is maintained with the key figures and characteristics, it is added to the column hierarchy in the layout of the Matrix setup and can be compared to the other Usage types side-by-side. While the values in the Matrix may be changed, changed values are not stored in the Matrix where the source data was pulled; these changes are for analyses exclusively. While creating a Proforma the data can be created and stored in the Proforma for analytical purposes. 25 Summary of New Features and Enhancements

26 Sweep Function The main purpose of this functionality is to reflect a higher-level value to all the lower-level fields equally. When a Matrix is created, the Sweep function is automatically defined for the Matrix. BI Query as Usage Function In the Matrix Workbench, BI query can now be selected as a part of the Usage function. The query is defined in combination with period profile with the mapping of the corresponding fields. Based on the mapping, the system selects data and stores it in the Matrix. Composite IP Modeling for Planning To allow modeling of planning data without posting to Matrix. The Deployment Code configuration now contains a new Modeling flag that can prohibit any postings for the Deployment Code. Every modeling scenario is mapped to a reference version (e.g. A000, A001, etc.). A new Reference Version field is added to the Deployment Code configuration to map to the modeling version. Central components and formulas are utilized in the Reference Version to adjust values of the modeling, thus, all of the values for modeling derive from a specific reference version. Formulas from the reference version can be overwritten with the key figures from modeling. The Proforma tab is now available in the Calculation Run Workbench. The Proforma can now be created in the calculation run using tracking and Matrix function. When Proforma data is created the data is derived from modeling version utilizing Proforma Profile which is determined based on the configuration of the Calculation Run type assigned to the Deployment Code and version. Reason Codes for Editable Eligible Amounts To provide a reason code when eligible accrual amount has been changed or modified. When the Eligible Amounts is changed or modified in the Calculation Run, the Assign Reason Code popup window will appear to allow the user to assign an Accrual Reason Code. The Accrual Reason Code is used for tracking only and has no impact on financial area. 26 Summary of New Features and Enhancements

27 Deployment Code Participants Type Changes Vistex Release 6.0E Support Package 2 To support Plant, Agreement Group, Agreement Request, Company Code and Organization Unit in the Deployment Code Participants node. Participation Types (e.g. Plant, Agreement Group, Company Code, and Organization Unit) are now available from the Deployment Code configuration in the Participants node to auto-assign them at the Deployment Code level in the tracking. Derived Participation To assign multiple settlement partners directly in the Participation to create collective tracking with a single agreement but multiple participants. The existing Dynamic Participation functionality has been extended to support multiple settlement partners. An agreement with Dynamic Participation is now able to include multiple participants. In the configuration of the Deployment Code, the Virtual Participation flag has been replaced with the Virtual/Dynamic Participation field offering Derived Participation and Virtual Participation participation category options. In Derived Participation, the agreement acts as a participant with each settlement partner acting as a sub-participants. Plan Tracking will now have a new Sub-Participant field to select the sub-participant; only those sub-participants that belong to the specific agreement will be displayed. Users can track multiple sub-participants at a time. Postings Options for Components and Subcomponents In prior releases, there was only the ability to create a Calculation Run from a report; now the solution provides an option to directly post approvals/settlements. Vistex is now proving an option to post Calculation Run after it has been created. In the Create Calculation Run transaction there is a new Select a Function window that provides several options: None will only create the Calculation Run Accrue Calculation Run will be created as well as an accrual document for the same amount Settlement Interim settlement Settlement Adjustment Post All If the Calculation Run is relevant for creation of a Claim, it will create a Claim document. 27 Summary of New Features and Enhancements