Release 6.0E. Support Package 4. Summary of New Features and Enhancements

Transcription

1 Release 6.0E Support Package 4 Summary of New Features and Enhancements

2 Contents Introduction... 5 Information Sources... 5 Social Media... 5 Disclaimer and Liability Notice... 6 SAP ECC Version Requirements... 6 User Interface... 7 SAP Fiori... 7 UI Application Setup (for SAP Fiori)... 7 Launchpad... 8 Additional Link Types in Launchpad Workspaces... 8 Copy Existing Launchpad Profile... 8 Status Flow (for SAP Fiori)... 8 Level Description Added to Status Flow Steps... 8 Agreements... 8 Electronic/Digital Signature... 8 Trade Calendar... 9 Composite Model... 9 Evaluations... 9 Status Flow Support in Evaluations... 9 Matrix... 9 Character Type and Date Type Added as Key Figure Fields... 9 HANA Structure Workbench Revamp... 9 Layout Function Categories Matrix Closed Periods Procedures Assigned to Subset Usage Procedures in Copy Management Utilities Source Unit in Copy Management Utilities Subset Usage Data Sources Displayed on Demand Unique Function Type for Custom Functions Tracking Filtering Bucket Line Items by Driver in Tracking Planning Planning Grid Assumptions Color Maps Document Level Notes External Description Field Copyright 2016 Vistex, Inc. All rights reserved. 2

3 Mass Posting Planning Documents Snapshots of Changes to the Planning Document Matrix Planning Member Selection Enhancement Refresh Derivation Values Summary Functions Uploading and Downloading Planning Data Wildcards Allowed for Scenario Selection Proforma Planning Promotion Based Planning Transactional Model Buckets Virtual Buckets in a HANA Database Claims and Transaction Documents Paging in Claims and Transactions Inventory Pools Multiple Currency Support Pool Reservation Parameter Group in Claim Type Partner Communication Upload/Download Multiple Partner Communication Documents Data Maintenance Pricing Price Book Price Book Pricing Procedure at Sales Area Level Price Catalog Price Catalog Outbound IDoc Structural Pricing Expand/Collapse Nodes Added to Structural Pricing Rules Data Maintenance Resources Data Flow Domains Domain Identification Domain IDoc Info Records Composite Attributes for Info Records Info Record IDoc Vendor Info Record for Material Group Structures BOM Structures Change Log Copyright 2016 Vistex, Inc. All rights reserved. 3

4 Technical Archiving Archiving Buckets Data Maintenance Resources Archiving Business Script Buckets Conditional Update Function Pop-up Display Improvement Field Definitions Removed from Script Trace Results Data Objects Address Match Field Values Overwrite in Current Version Automatic Sublist Creation Data Model Copy Version Functionality Document Map Enhancements Duplication Checks Using a TREX Server File Template Processing Type HANA Database Section Table on Demand Navigation from Data Model to Rule Profile and Rule Parallel Processing Option for Upload Partial Transfer to Create a Target Version TREX Update Performance Improvement Validation Error Code Color Coding Copyright 2016 Vistex, Inc. All rights reserved. 4

5 6.0E SP4 Release Summary Introduction This document provides an overview of the Vistex Solutions for SAP Release 6.0E Support Package 4 new features and enhancements. Vistex provides this release summary to briefly explain new features and changes included in the following Solutions for SAP software: SAP Incentive Administration SAP Paybacks and Chargebacks SAP Data Maintenance Resources SAP Data Maintenance Pricing Information Sources 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 Marketplace and the Vistex support page Vistex maintains a discussion forum on LinkedIn where our customers are welcome to post questions about Vistex solutions, learn company news or network with other Vistex users, and share knowledge and best practices for using Vistex solutions in the business processes that Vistex solutions support. This forum 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. Social Media You may follow Vistex on a variety of social media: Copyright 2016 Vistex, Inc. All rights reserved. 5

6 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 Release 6.0E Support Package 1 required SAP ECC 6.0 Enhancement Package 5 or newer with no requirement on the SAP Support Package level. Vistex Release 6.0E Support Package 2, Release 6.0E Support Package 3, and Release 6.0E Support Package 4 require the following minimum SAP Support Package levels to ensure proper installation and feature function: SAP ECC 6.0, Enhancement Package 5, Support Package Stack 11 SAP ECC 6.0, Enhancement Package 6, Support Package Stack 09 SAP ECC 6.0, Enhancement Package 7, Support Package Stack 02 Copyright 2016 Vistex, Inc. All rights reserved. 6

7 User Interface SAP Fiori Vistex has selected SAP Fiori as the design paradigm for its standard user interface. Existing web interface (_WS) transactions, which are Business Server Pages, are being replaced by SAP Fiori. The following web interface transactions have been redesigned as SAP Fiori in Release 6.0E SP4. Remaining web interface transactions (including Deals and Data Maintenance Resources transactions) will be replaced in future support packages. Also, functionality not added to the SAP Fiori screens in SP4, such as flexible groups, will be included as part of future support packages. Master Request Agreement (all IP applications) Agreement Request Claim Document Claim Validation Transaction Document Transaction Validation Calculation Run Individual Tracking (Includes participant tracking functionality) Launchpad for Fiori Similar to the SAP Fiori Launchpad; certain functionality in the existing Launchpad, such as Process Observer counts, will be added with future support packages Planning/Matrix/Proforma (Web Dynpro screens with an SAP Fiori wrapper) Price Proposal (Data Maintenance Pricing) UI Application Setup (for SAP Fiori) The following new workbenches are used to set up the SAP Fiori applications for 6.0E SP4: UI Profile Workbench, which replaces the BSP block profile configuration, to explicitly set the fields to be displayed in the Fiori applications. No default layout is provided. Search Profile Workbench, to restrict the searchable fields and control how the search results are displayed. No default layout is provided. Role Workbench, to determine who can access the UI applications. The role restricts which workspaces a user can enter. When the user navigates to an application in the UI, the system displays the search profile and UI profile for the application, based on the active role that the user is assigned to. Copyright 2016 Vistex, Inc. All rights reserved. 7

8 Launchpad Additional Link Types in Launchpad Workspaces All types of Launchpad links can be created in the Workspace Workbench for 6.0E SP4: GUI transactions, Web (BSP) applications, UI (SAP Fiori) applications, URL s, Vistex reports, business processes (Process Observer), and activities (actions, alerts, and notifications). Copy Existing Launchpad Profile New functionality in 6.0E SP4 provides the ability to copy an existing Launchpad profile, in the Launchpad Profile configuration. Status Flow (for SAP Fiori) Level Description Added to Status Flow Steps Status flow levels are used when multiple concurrent approvals are required. Previously, only a level number field was available for each step. A field has been added to accept a description of the level for 6.0E SP4. NOTE: The description field is editable only for the first entry; it is not editable for subsequent entries for a level. Agreements Electronic/Digital Signature As of Release 6.0E SP4, Vistex supports the use of DocuSign to electronically initial and sign agreements, agreement requests, and master requests. NOTE: Digital signature functionality requires the purchase of a separate DocuSign license. This functionality is an extension of contract authoring during which: A legal document is generated. Signature and initials fields are identified in the clauses tag detail. The generated document is ed to users to review, initial, and sign in DocuSign. The signed document is retrieved and stored as an attachment to the legal document. An entry is added to a signature log to indicate the status of the document, and a background job can be executed to update the signature data in the system document. From either SAP GUI or Fiori, a separate copy of the document can be ed to individual users, or the same document can be routed from one user to another. s can be sent to multiple groups of users at a time. Copyright 2016 Vistex, Inc. All rights reserved. 8

9 Trade Calendar The Trade Calendar, introduced in Release 6.0E SP3 as a UI alternative to the agreement/agreement request (display only) Calendar View, allows a non-technical person (sales rep or marketing person, for example) to review and maintain validity periods for all the programs that the person is running, without logging onto SAP GUI. For example, the sales rep might compare current programs with those being planned, and then use drag and drop capability to adjust specific dates as needed. Two types of documents can be visualized next to each other, such as agreements and agreement requests. Trade Calendar functionality has been enhanced for Release 6.0E SP4. To improve the Search, the use of period profiles has been integrated into the trade calendar s time scale. Within the calendar display, the position of the documents can easily be switched, or one document type can be hidden. Double clicking on a row provides a pop-up that can be used to review, maintain, and change document data. New documents, such as new agreements, can be created directly from the Trade Calendar. Composite Model Evaluations Evaluation is a data collection tool similar to a survey or census. Each evaluation consists of a set of fields and/or grids used to record and track data. Status Flow Support in Evaluations For 6.0E SP4, status flow functionality is supported in evaluations. Evaluation approvals can be performed from the evaluation document, , or activities prior to the evaluation data being accepted. Matrix Character Type and Date Type Added as Key Figure Fields For Release 6.0E SP4, character type and date type fields are available at the key figure level. Prior to SP4 only currency, quantity, and adjustment fields were available as key figure fields. HANA Structure Workbench Revamp A HANA database can be used as a data source for the matrix. For Release 6.0E SP4, the HANA Structure Workbench was revamped. Previously, information entered in the workbench was used to generate structures for the following purposes: to pull HANA view data into a matrix, as a source for matrix explosions, and as a source for matrix derivations that pull HANA view information into Matrix Planning on-the-fly. Copyright 2016 Vistex, Inc. All rights reserved. 9

10 For SP4, the new HANA Source Workbench is used to define HANA views or procedures, to pull HANA data into the matrix, using a HANA data update transaction. The HANA source data also can be used either in matrix derivations or explosions to pull data into Matrix Planning at run time. Layout Function Categories As of 6.0E SP4, layout functions are classified into the following types: Calculations, which support simple calculations used only for Fiori applications. Business Script functionality used to create the calculations is limited to basic functions. Derivations, which derive data from other sources, such as matrices and pricing. Prior to SP4, all layout functions were classified as Derivations. Matrix Closed Periods A new workbench was created for Release 6.0E SP4 to track which periods are closed and, therefore, cannot be edited in Matrix Planning. Periods open/closed assignment is maintained by matrix/subset/usage/year. NOTE: The list of closed periods does not apply to Proforma Planning. Procedures Assigned to Subset Usage As of 6.0E SP4 a list of procedures can be assigned at the subset usage level, for a specific layout. Each procedure can include any of the following types of steps: Create Records Copy Records Search and Replace Set Values Execute Functions, to execute the list of functions defined in the procedure step Procedures are executed on demand in Matrix Planning. Procedures in Copy Management Utilities In Copy Management for Release 6.0E SP4, a predefined list of procedures can be processed over the source data. For each procedure, default values can be specified for any variables assigned to the procedure. Procedures will be run before any functions assigned to the utility are processed. Source Unit in Copy Management Utilities Prior to 6.0E SP4, before the source was copied using the Copy Management utility the key figure data was converted to the default currency/unit of measure. For SP4, the user now controls whether to perform utility operations with or without the Source Unit. The source can either be copied as is or converted to the default currency/unit. Copyright 2016 Vistex, Inc. All rights reserved. 10

11 Subset Usage Data Sources Displayed on Demand In the Subset Workbench, source data tabs were displayed for all usages, regardless of whether or not sources were entered for a usage. For 6.0E SP4, an icon indicates when source data exists for a usage, allowing the user to display the tabs of source data on demand. Unique Function Type for Custom Functions For Release 6.0E SP4, a new function type (Variation) was created explicitly for user-created functions. Previously, custom functions were grouped with delivered functions. Tracking Filtering Bucket Line Items by Driver in Tracking Drivers allow you to dynamically determine how to calculate and track information in the composite model. For example, information can be tracked in different ways for different customers. Prior to 6.0E SP4, filtering in tracking was based on the agreement/partner and the bucket header. For SP4, if a driver is used for tracking, the system will filter the bucket line items based on the driver and show the source documents (line items) as subcomponent characteristics. Planning Planning Grid Prior to Release 6.0E SP4, planning data was displayed in a Web Dynpro-based planning tool used to maintain the matrix for a selected version of a subset. A proforma, triggered from objects such as agreements, agreement requests, price proposals, was used to snapshot the data, make adjustments, and then post those changes back to the matrix. To provide a modern UI for all planning activities, in Release 6.0E SP4 Vistex is introducing the Planning Grid app. The Vistex Planning Grid is built on top of the following: IP Matrix, which stores planned data, such as quotas for commission structures Planning Object, to define what you are going to plan for/manage by assigning a matrix and specifying the data to be planned. Territory Management is leveraged to control the selection process and data access. Planning Scenario, to create a search used to access the specific data to be planned Planning Document, the result of the planning scenario Planning documents provide a way to control access to certain matrix data. Rather than having access to an entire matrix, planning can be restricted to selected matrix data that is pulled into a planning document. For example, the data can be limited to a particular sales representative's data; only that data will be visible and maintainable on the Planning Grid. Copyright 2016 Vistex, Inc. All rights reserved. 11

12 A planning document supports all the functionality of the existing Web Dynpro planning tool. For example, proformas can be created directly from a planning document. Data in the planning document will not be updated to the matrix unless explicitly posted to that matrix. Planning data can be downloaded to maintain it offline and then the changed data can be uploaded to the planning document. The Planning Grid includes navigation buttons to move around the screen, Quick Hints button to view a list of keyboard shortcuts, and an application toolbar to perform checks, select a different layout, and save changes. A separate pane provides a settings toolbar to adjust numerous grid settings such as layout, variables, paging, filters, functions, and procedures. Following are descriptions of functionality added to 6.0E SP4 specifically for the Planning Grid: Assumptions For use in the Planning Grid in Release 6.0E SP4, Vistex has introduced Assumptions, which are flexible, member-dependent variables that can be used in function formulas and color maps. Assumptions operations are performed in the Planning Grid at run time, which allows you to change the default values in the fields assigned to the assumption and then re-run the formulas, to immediately see the effects of the new values. Color Maps In the Planning Grid for 6.0E SP4, color can be used to highlight individual cells, based on the values in the cells. Color maps indicate the range of cell values that correspond to each color. Color maps are defined at the matrix level and can be assigned to fields in a layout and to summary fields. Document Level Notes Notes can be added and maintained at the planning document level as of 6.0E SP4, using the standard Notes tab. External Description Field An (optional) external description field is available in the planning document in 6.0E SP4. NOTE: The external description field also was added to the proforma document. Mass Posting Planning Documents A new transaction was created for 6.0E SP4 to mass post planning documents. Documents can be selected for mass posting by planning document number, external description, planning object, planning scenario, and planning status, as well as created by and changed by user and date. Snapshots of Changes to the Planning Document Snapshots can be created for 6.0E SP4 to review data maintained in the planning document. In the GUI version of the planning document workbench, the tab used to store a list snapshots created from the planning document was renamed as the Snapshots tab. Copyright 2016 Vistex, Inc. All rights reserved. 12

13 Matrix Planning The following functionality was added to the Web Dynpro planning tool for Release 6.0E SP4. This same functionality exists in the Planning Grid: Member Selection Enhancement Adding members to Matrix Planning is easier due to functionality added to member selection. Prior to 6.0E SP4, the user had to enter specific criteria for each member. Now the user executes a search over selected criteria to view a list of members that meet that criteria. Members chosen from the list are added to the screen. Refresh Derivation Values A Refresh button can be used to update the derivation values to the latest values from the source data. Summary Functions The Matrix Planning screen is organized into two areas of data: Grid, the main display Summary, which provides access to user-defined sets of data defined at the usage level, either a grid of fields or an overall total. For summaries displayed in a grid, user-defined functions can be executed over the summary data either on load (executed before the summary data is displayed) or on demand (executed from a dropdown list). In 6.0E SP4, simple calculations created in Business Script are supported at the summary level. No complex lookups are supported at this level. Uploading and Downloading Planning Data Upload and download functions were added to the Web Dynpro planning document for 6.0E SP4. Wildcards Allowed for Scenario Selection In Matrix Planning, the Selection tab is used to filter the displayed information, to plan only a specific customer or material group, for example. For 6.0E SP4, the use of wildcards (generic selections) is now supported on the Selection tab. Proforma Planning Promotion Based Planning Promotion data can be displayed on the Proforma Planning screen for promotion based plans in 6.0E SP4. The promotions are assigned to the master request at the price sheet level, then the proforma is created using the price sheet as the data source. Copyright 2016 Vistex, Inc. All rights reserved. 13

14 Transactional Model Buckets Virtual Buckets in a HANA Database To improve performance, in Release 6.0e SP4, virtual buckets can be created in a HANA database to read bucket aggregation data at run time on-the-fly, without storing any data in the bucket table. Virtual bucket functionality is provided for all IP applications, claims, transactions, and data objects. Claims and Transaction Documents Paging in Claims and Transactions Paging is a global function available for ALV grids on certain GUI screens, such as Claim Validation and the Rules tab in the Agreement Workbench. Use paging to limit the grid's page size, that is, the number of lines displayed at one time. Paging was developed to replace scrolling through a large number of line items. For certain transactions, paging also helps improve performance by loading only the needed page. For Release 6.0E SP4, paging functionality was added to claims and transaction documents. Inventory Pools Inventory pools can be used by manufacturers to track inventory at the distribution channel, and to validate the inventory as claims are received in from distributors. Pools also can be used for price protection estimations. Multiple Currency Support Prior to 6.0E SP4, pool documents supported only a single currency. Users in different regions/countries need the ability to create pool documents in different/local currencies, therefore, multiple currency support was added for SP4. Pool values now can be defined to appear in the appropriate sales organization currency. Pool Reservation Parameter Group in Claim Type To help manage pool reservations, 6.0E SP4 includes functionality to assign a different parameter group to each claim type. This enhancement, which is similar to settlement parameter management, allows different claim types that have the same submitter to use different pool parameters. Partner Communication Upload/Download Multiple Partner Communication Documents Before 6.0E SP4, only one partner communication document could be uploaded/downloaded at a time. For SP4, the upload and download functions have been enhanced to allow multiple communication documents to be uploaded/downloaded at one time. Copyright 2016 Vistex, Inc. All rights reserved. 14

15 Data Maintenance Pricing Price Book Price Book Pricing Procedure at Sales Area Level Previously, the pricing procedure was assigned directly at price book type level. For 6.0E SP4, the pricing procedure can be assigned at the sales area level of the price book type. Price Catalog Price Catalog Outbound IDoc A price catalog contains prices of multiple products for multiple customers. For 6.0E SP4, a new transaction can be used to create the outbound price catalog IDoc. Structural Pricing Expand/Collapse Nodes Added to Structural Pricing Rules Controls were added in 6.0E SP4 to expand and collapse the bill of material levels on the Structural Pricing rules sheet in the master request. By default, the structure is collapsed at the top level. Data Maintenance Resources Data Flow A data flow can be integrated into a customer, material, or vendor list to trigger a series of steps that allow data maintenance to occur simultaneously in multiple departments. For example, when a new customer is created, Sales can work on entering the sales data while Finance enters the financial data. Each set of data has its own life cycle. For 6.0E SP4, the following functionality has been added to data flows: Business Script Business Script can be used for rule-based triggering of subsequent steps or marking the current list as complete. Sub-flows Another data flow can be initiated within the main data flow as a sub-flow. Termination The data flow, sub-flow, or any individual step in the flow can be terminated. Locking A particular list created during the data flow can be locked after a certain user status of the list is reached. Copyright 2016 Vistex, Inc. All rights reserved. 15

16 Intermediate Posting Prior to SP4, any list in the flow could be posted only when the entire flow was complete. Now posting of list from dataflow is possible even if the entire data flow is not complete, provided all the lists created as a part of data flow are complete. Domains Domain Identification For 6.0E SP4, functionality is introduced to define identification types at the domain level, to identify partners using a unique ID, such as HIN number. A format template can be assigned to each identification type, to check that values are entered properly. Searches by identification type can be performed in the customer and vendor domain workbenches, domain list workbenches, and domain dashboards. Changes made to the identification type in the workbenches and dashboards are recorded in the changes log. Domain IDoc As of Release 6.0E SP4, inbound IDocs can be used to create and change customer, material, and vendor domains. Info Records Composite Attributes for Info Records For 6.0E SP4, composite attributes are supported for customer and vendor info records. Info Record IDoc For Release 6.0E SP4, inbound and outbound IDoc functionality is provided to create and change customer and vendor info records. Vendor Info Record for Material Group Previously, vendor info records only could be created using the vendor and material. For 6.0E SP4, vendor info records can be created either with vendor and material or vendor and material group. Structures BOM Structures Change Log For Release 6.0E SP4, changes to fields in BOM structures are recorded in a change log that can be displayed either in Document View or Package View. The following types of changes are recorded: Structure Header Data Structure BOM Items Structure Text Maintenance Structure Attribute Values Copyright 2016 Vistex, Inc. All rights reserved. 16

17 Technical Archiving Archiving Buckets Release 6.0E SP4 provides functionality to archive buckets. Data Maintenance Resources Archiving For additional attributes stored only in Vistex, 6.0E SP4 provides functionality to archive the following Vistex objects stored only in Data Maintenance Resources: Customer Lists Material Lists Structures Vendor Lists Business Script Business Script is a business user scripting language created by Vistex. It contains pre-populated functions to perform calculations and lookups. Introduced in Release 6.0E SP2, the use of business scripts replaces the use of BRF+, Measures, Condition Editor, and SAP Formula Builder. For 6.0E SP4, the following enhancements have been made to Business Script: Buckets Conditional Update By default, creating/maintaining an IP document will always update the bucket. To restrict when a selected bucket type will be updated, Business Scripts can be created for execution at the bucket line item level. For example, you might restrict the bucket update to occur only when IP document line items have action code 001. Function Pop-up Display Improvement When adding a function to a script, the function pop-up guides the user through entering data for the function. Initially, the pop-up displays the description for each field. If the user hovers over the description, field details appear in a tooltip. The pop-up can be changed to instead display the field s technical name. If the user hovers over the technical name, the system displays a tooltip that contains the description and data type. Prior to 6. 0E SP4, this functionality added a column to the pop-up. The functionality was changed to improve the display. Copyright 2016 Vistex, Inc. All rights reserved. 17

18 Field Definitions Removed from Script Trace Results A script can be run in simulation mode to test the script s functionality without executing it in the application. All steps in the script can be traced to help determine whether they are acting as desired. Results of the trace can be viewed for each function. Previously, field definitions were included in both the definition area and in the results. For SP4, the field definitions were removed from the trace results to make them easier to read. Data Objects The purpose of data objects is to have an intermediate step between receiving a submission of raw data from external sources and loading that data into the appropriate Vistex application files. Rather than sending the raw data directly into system files, the data will first be processed based on a predefined data model. Clean data then can be sent to the application in a format that the application can understand and use. Data Objects was introduced in Release 6.0E SP1 and has been enhanced in subsequent support packages. For 6.0E SP4, the following enhancements have been made: Address Match Field Values Overwrite in Current Version Previously, when the user chose a qualified entry from address matching, that entry was used only in the target version of the data object; the user could not overwrite the current version. In Release 6.0E SP4 an overwrite flag is provided in Match configuration to overwrite the current version section data with its match record. NOTE: The overwrite functionality currently is only available as an online process. Automatic Sublist Creation Sublists created for a version are used to perform partial postings of version data to an object type, such as claims. For example, a sublist might contain claim line items for a certain product. Only the line items for that product will be posted to the claims files. Prior to 6.0E SP4, the creation of sublists was a manual process. For SP4, sublists can be created automatically when a data model version is created. Newly created sublists entries can be flagged for posting either manually in the data object or using business rules. If any items were not flagged for posting, the system creates a separate sublist containing those unposted items. The partial posting statuses are: Ready for posting Flags the entry for posting to the object. Not yet posted Blocked for posting Prevents an entry from being posted to any object. Copyright 2016 Vistex, Inc. All rights reserved. 18

19 Partially posted Assigned by the system to a header entry when certain item entries were not posted to the object. The user cannot assign this status. Posted Assigned by the system to entries after they are posted to the object. The user cannot assign this status. Data Model Copy Version Functionality A new data model version can be created by copying an existing version of that data model. The new version then can be changed, as needed. Document Map Enhancements Document maps are used to map data from the data model to application files, such as claims files. The system follows the mapping to create documents from the source data model. For Release 6.0E SP4, the following functionality was added to document maps: Data object header fields, for example sales organization and admin data fields, are available to include in the document map. If the section data is organized into packages, functionality can be enabled to create a document for each package. Duplication Checks Using a TREX Server Duplication checks can be performed for defined groups of fields, within a data object and across data objects, using either a separate TREX server (new for 6.0E SP4) or index tables (existing functionality prior to SP4). File Template Processing Type A new processing type field in the data object file template controls how the data is processed internally. Prior to Release 6.0E SP4, the only processing option was to use an indicator (defined for each section) to format the data. Two additional options have been added for SP4: Only Column (format data starting with a user-specified start row number) and Row and Column. HANA Database Section Table on Demand By default, section data is indexed in TREX. For Release 6.0E SP4, a version can be flagged to generate a transparent table to also store the section data in HANA. For example, the user might want to report over the stored section data in HANA. Navigation from Data Model to Rule Profile and Rule Hot links were added to allow navigation from a data model section to the rule profile, and from the rule profile to the rule. Parallel Processing Option for Upload To minimize the processing time for upload, target version creation, and posting to objects (such as claims), parallel processing was added as a processing option. Copyright 2016 Vistex, Inc. All rights reserved. 19

20 Partial Transfer to Create a Target Version Prior to 6.0E SP4, when creating the target version all entries from the source version were included. For SP4, the target version can be created from only selected entries that are assigned a certain status, such as clean data that does not require further work. Remaining entries stay in the source version unless a version update is performed at a later time. The partial transfer statuses are: Ready for transfer Flags the entry for transfer to the target version. Not yet transferred Blocked for transferring Prevents an entry from being transferred to any target version. Partially transferred Assigned by the system to a header entry when certain item entries were not transferred to the target version. The user cannot assign this status. Transferred Assigned by the system to entries after they are transferred to the target version. The user cannot assign this status. The transfer status can be updated either manually or by using business rules. TREX Update Performance Improvement If using a TREX server, to improve performance during update of records from the Search and Process (Dashboard), during TREX processing the system will lock the objects being processed. A refresh option is available to process the update immediately and unlock the objects. Validation Error Code Color Coding Validation error codes can be color-coded in the data object detail, to highlight entries assigned a certain validation error. For example, all non-standard provider error entries might be highlighted in yellow. Copyright 2016 Vistex, Inc. All rights reserved. 20