Incentive Administration by Vistex for SAPAn SAP Gateway (web) server is required to run the Fiori...

Vistex Rights and Royalties Documentati

Release Summary

Document Version: 1.0 – Final

Date: May 22, 2019

PUBLIC

Release Summary for:

Incentive Administration by Vistex for SAP

S/4HANA on 1809

Paybacks and Chargebacks by Vistex for SAP

S/4HANA on 1809

SAP Data Maintenance by Vistex, pricing option

for SAP S/4HANA on 1809

SAP Data Maintenance by Vistex, resource

option for SAP S/4HANA on 1809

Release Summary PUBLIC

SAP Incentive Administration by Vistex for SAP S/4HANA on 1809

SAP Paybacks and Chargebacks by Vistex for SAP S/4HANA on 1809

SAP Data Maintenance by Vistex, pricing option for SAP S/4HANA on 1809

SAP Data Maintenance by Vistex, resource option for SAP S/4HANA on 1809

Release Summary – Version: 1.0 – Final

May 22, 2019

© 2019 Vistex, Inc. All rights reserved.

© 2019 SAP SE or an SAP affiliate company. All rights reserved. 2

Table of Contents

1 Introduction ............................................................................................................... 4 1.1 More Information .............................................................................................................................. 4 1.2 Disclaimer and Liability Notice .......................................................................................................... 5

2 Prerequisites .............................................................................................................. 6 2.1 Technical Requirements for Release 1809 ....................................................................................... 6

2.1.1 Fiori Requirements ........................................................................................................... 6 2.1.2 ViZi® Analytics Requirements .......................................................................................... 6

3 Agreements ............................................................................................................... 7 3.1 Agreement Review Sheet ................................................................................................................. 7 3.2 Accounting ........................................................................................................................................ 7 3.3 Schedules ......................................................................................................................................... 7

4 Pricing and Planning ................................................................................................... 8 4.1 Price Review..................................................................................................................................... 8 4.2 Hybrid Configuration ......................................................................................................................... 8 4.3 ViZi as a Data Source ....................................................................................................................... 8

4.3.1 Statements ........................................................................................................................ 9 4.4 Fund Document ................................................................................................................................ 9 4.5 Live Planner...................................................................................................................................... 9

5 Core Functionality .................................................................................................... 10 5.1 Buckets ........................................................................................................................................... 10

5.1.1 Calculation Buckets ........................................................................................................ 10 5.1.2 Virtual Calculation Buckets ............................................................................................. 10 5.1.3 Bucket Simulation ........................................................................................................... 10

5.2 Transactional Calculation Run ........................................................................................................ 10 5.2.1 Group Pricing .................................................................................................................. 10 5.2.2 Scaling Scenario ............................................................................................................. 11 5.2.3 Frequency ....................................................................................................................... 11 5.2.4 Reconciliation ................................................................................................................. 11 5.2.5 Partner Communication for Transactional Calculation Run ............................................ 11 5.2.6 Payment Schedule for Transactional Calculation Run .................................................... 11

5.3 Ledger ............................................................................................................................................ 11

6 Data Objects ............................................................................................................ 13 6.1 Duplication Checks in Search Engine Services (SES) ................................................................... 13 6.2 Automatic Version Creation and Posting ........................................................................................ 13 6.3 Fuzzy Match on Any Field .............................................................................................................. 13 6.4 Derived Sections ............................................................................................................................ 14

7 Global ..................................................................................................................... 15 7.1 Global File Template ...................................................................................................................... 15







May 22, 2019



7.1.1 Agreements .................................................................................................................... 15 7.1.2 Pricing and Planning ....................................................................................................... 16

7.2 Status Engine 2.0 ........................................................................................................................... 16 7.3 Output Engine 2.0 ........................................................................................................................... 16

8 Fiori ......................................................................................................................... 17 8.1 Government Pricing ........................................................................................................................ 17

8.1.1 Reported Material ........................................................................................................... 17 8.1.2 Transaction Type Assignment ........................................................................................ 17 8.1.3 Price Type Tracking ........................................................................................................ 17

8.2 Hybrid Configuration ....................................................................................................................... 17 8.3 Membership .................................................................................................................................... 18 8.4 Customer List ................................................................................................................................. 18 8.5 Product List..................................................................................................................................... 18 8.6 Vendor List ..................................................................................................................................... 18 8.7 Territories ....................................................................................................................................... 19 8.8 Data Objects ................................................................................................................................... 19

8.8.1 UI Profile for Aggregation................................................................................................ 19 8.8.2 Fuzzy Match on Any Field............................................................................................... 20

8.9 Clauses and Templates .................................................................................................................. 20 8.10 Designer ......................................................................................................................................... 20

8.10.1 Watermark ...................................................................................................................... 20 8.10.2 Flexible Group Explode .................................................................................................. 20

8.11 Structural Pricing ............................................................................................................................ 20 8.12 New DMr Data Areas ...................................................................................................................... 21

8.12.1 Mass Hierarchy ............................................................................................................... 21







May 22, 2019



1 Introduction

This document provides an overview of the Vistex Solutions for SAP® Release 1809 S/4HANA new features and

enhancements. Vistex provides this release summary to Vistex provides this release summary to briefly explain new

features and changes included in the following Solutions for SAP® software:

• SAP Incentive Administration by Vistex for SAP S/4HANA on 1809

• SAP Paybacks and Chargebacks by Vistex for SAP S/4HANA on 1809

• SAP Data Maintenance by Vistex, pricing option for SAP S/4HANA on 1809

• SAP Data Maintenance by Vistex, resource option for SAP S/4HANA on 1809

1.1 More Information

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

https://www.vistex.com/services/customer-support/sap-support/.

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 https://www.vistex.com/help/.

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 available on SAP Service Marketplace.

You may also follow Vistex on a variety of social media:

https://www.vistex.com/services/customer-support/sap-support/

https://www.vistex.com/voice/

https://www.linkedin.com/

https://www.vistex.com/help

https://twitter.com/vistex

https://www.facebook.com/VistexInc

http://www.youtube.com/user/VistexTV

https://www.linkedin.com/company/vistex







May 22, 2019



1.2 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 their 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.







May 22, 2019



2 Prerequisites

2.1 Technical Requirements for Release 1809

The following minimums are required for running the Vistex V/4 1809 solution:

• SAP S/4HANA On Premise (OP) version 1809 system

• SPAM/SAINT update patch level 69

• A separate SAP Front-end Server based on SAP_UI 7.53 SP00 level (required for running Fiori apps on central HUB deployment scenario only).

If you have the software installed at the Vistex 60E level on the ECC system and are planning to migrate the ECC

system to S/4 1809, please refer to SAP Note 2738137 – Vistex IP and DM Module Conversion to Release V/4 1809

on S/4HANA OP 1809.

2.1.1 Fiori Requirements

An SAP Gateway (web) server is required to run the Fiori UI. You can choose to either deploy the web server on your

SAP S/4HANA application server OR create a separate, standalone web server to provide the Fiori UI.

2.1.2 ViZi® Analytics Requirements

The minimum requirements depend on the level of analytics being implemented.







May 22, 2019



3 Agreements

3.1 Agreement Review Sheet

As of Release 1809, the Review Sheet button in the Agreement Workbench generates the review sheet as a .PDF

file. Review sheets are no longer displayed in HTML.

To enable review sheets, template types must be flagged as Relevant to Review Sheet when configuring pricing

agreements. Review sheets are also configurable with respect to templates and clauses, as opposed to only

displaying configured tabs and rules in order.

3.2 Accounting

Release 1809 features the Vistex Accounting Engine, providing the necessary logic and advanced calculations for

accruals, reporting, subledgers, and allocation. The Vistex Accounting Engine is also utilized for new rules related to

deferrals, amortization, and revenue recognition. The Vistex Accounting Engine enables all these calculations to be

performed solely in Vistex.

Agreements now include an Accounting tab, which defines how the follow-on accounting processes should be

calculated and records all financial effects for the agreement. This enables all subsequent transactions for this

financial information to occur smoothly, and the information can be directly linked to all secondary transactions. The

data for agreement postings is pushed from accounting to improve system performance.

3.3 Schedules

In Release 1809, the Schedules tab in the Agreement Workbench has been enhanced. Information regarding dates,

consumption, payment amounts, and payments received is also shown in this tab. Events, Accounting, and the

Calculation engine have all been integrated into schedules to facilitate the allocation of products to a schedule line

item.







May 22, 2019



4 Pricing and Planning

4.1 Price Review

The price review application was introduced in Release 1809 to provide a user-friendly interface for pricing

management, and it also improves performance and removes dependencies on pre-built formulas. Similar to the

functionality in planning, price review can pull data from the source price sheets as well as other data sources, and

the changes made in price review update back to the source sheets.

The Mapping Profiles tab was removed from the pricing-object level and added to the price review template. Mapping

profiles configured in this tab generate proformas in the price review document.

4.2 Hybrid Configuration

Release 1809 introduced hybrid configuration, allowing matrix configuration activities to occur in a workbench instead

of SPRO. Some items offered through hybrid configuration include formulas, formula set up, creation of color map

templates, layouts, and the addition of new fields.

4.3 ViZi as a Data Source

Release 1809 allows ViZi to be used as a matrix data source. The Derivations tab defines ViZi as the data source

and the data source parameters are set up in the ViZi tab of the Data Source Workbench. This data can be obtained

from any of the areas listed below:

• Table

• View

• InfoSet Query

• Bex Query

• Data Model

• Data Store

• Data Store Object

• Function Module

• Report

• Procedure

• AMDP

• HANA view

• External view

• SDA view







May 22, 2019



Any of the fields included in the ViZi Data tab can be included in the ViZi data source, and period mapping can be set

to current period, specific period, or flexible period.

ViZi can also serve as the data source for attributes used in price review or price sheets. Also, when the Mapping for

Copy steps are defined in the review template, a ViZi data source must be selected when these steps are derived.

In order to use a ViZi report as a data source, users must create a ViZi report with the source type and table assigned

to derivations in the data source column. The source field, period mapping, source period, periodicity, target period,

and source map must also be assigned to derivations in the data source column. Once the derivation is assigned to

the layout, the data from the ViZi report is displayed in the created derivation.

4.3.1 Statements

In statement generation, users are able to create a statement using a period range or date range. Release ESP6 also

enables the generation of multiple files using the different file templates assigned to statement generation. The

Overwrite Statement flag was also introduced, and when flagged this prevents the creation of multiple statements for

one period by overwriting previous statements for the same time period. Finally, a statement’s context in statement

generation is established from either a ViZi data source or ViZi report.

4.4 Fund Document

Building on the Funds Engine released in 6.0 ESP5, fund documents appear in a grid view and can link to the

planning grid and planning documents.

4.5 Live Planner

Live Planner is now included in the UI Profile Workbench. Live planner maintains the rules and promotions whenever

a mapping profile is saved. The live planner is then automatically generated when the document is created. For the

$BB/unit to be displayed in the live planner, users must maintain the value and validity when mapping key figures in

the mapping profile. Additionally, users must flag the Anchor Rule field to combine $BB/unit based on the flexible

period to generate a cumulative record. When the Anchor Rule field is not flagged, the live planner will only display

the existing record.

After adding a promotion to a Master Agreement’s rule, when the live planner is refreshed in Fiori the grid will

regenerate to include the new rules.







May 22, 2019



5 Core Functionality

5.1 Buckets

5.1.1 Calculation Buckets

Calculation buckets aggregate and store information from the Agreement and Data Source (i.e. invoice, claim,

transaction) to be utilized in transactional calculation runs. This stores information in one place to improve system

performance and architecture.

Release 1809 introduced auto bucket creation for agreement and partner buckets, and accrual profile and settlement

profile are now available at the bucket document level. This offers greater flexibility, as different profiles can be used

with one bucket document.

5.1.2 Virtual Calculation Buckets

Rather than physically storing calculation data, Virtual Calculation Buckets dynamically access this information using

the HANA in-memory database. Virtual Calculation Buckets contain all the necessary calculation instructions and

formulas while offering greater efficiency and optimizing data storage.

5.1.3 Bucket Simulation

Release 1809 also includes two new data areas in the bucket data model: SI Simulation Items and SC Simulation

Calculations. First introduced in Release 1709, Bucket Simulation uses these data areas to analyze and simulate incentives,

paybacks, and rebates for any future period without storing the relevant information. While previously only available at the

bucket group level, Release 1809 offers Bucket Simulation at the individual bucket level, enabling accrual and settlement.

5.2 Transactional Calculation Run

5.2.1 Group Pricing

Group pricing determines the combined revenue for a set of line items or a material group and uses agreement

information to identify the scale pricing for those items. In prior releases, complete composite scenarios had to be

created for this functionality, which group pricing renders unnecessary.







May 22, 2019



5.2.2 Scaling Scenario

Scaling scenario collects the information necessary for group pricing and allows scaling to be determined on a

transactional level without creating a composite scenario.

5.2.3 Frequency

Two other new features in Release 1809 are Accrual Frequency and Settlement Frequency, both of which can be

assigned at the bucket group or bucket level. In Auto Bucket Creation, frequencies from the bucket group will

automatically populate in the bucket document, and these frequencies can be adjusted before the bucket is updated

in the Calculation Bucket Workbench. The Accrual and Settlement Frequencies can also be copied from the

Settlement Parameter Workbench, but the profiles assigned at the bucket level take priority.

5.2.4 Reconciliation

Using information obtained from the partner communication document in the transactional calculation run,

reconciliation uses this information to track the amounts asked for and received and performs the necessary

adjustments.

5.2.5 Partner Communication for Transactional

Calculation Run

Partner communication has been incorporated in transactional calculation run. Partner communication records claims

and claim responses to manage auditing trails, and when users receive partner communications, the calculation

buckets update to incorporate the new information.

5.2.6 Payment Schedule for Transactional Calculation

Run

Payment schedules have also been incorporated in transactional calculation run. Typically used for commissions,

payment schedules plan these payments based on when customers submit payments.

5.3 Ledger

The ledger contains all the detailed postings from claims, calculation buckets, and transactional tracking. All

transactions resulting in financial postings—including those from claims, composite tracking, and transactional







May 22, 2019



tracking—are recorded in the ledger. A high-level summary of these transactions can be posted in SAP, while a

detailed record is saved in Vistex. This granular calculation data may be aggregated for Vistex reporting while the

information required for the SAP posting is also collected. Utilizing the Vistex Accounting Engine and minimizing the

financial information stored in SAP improves system performance.

Different ledger views offer varying levels of transaction detail. This includes providing subsets of ledger information

through show ledger views of various items such as material group, sales organization, and material levels.







May 22, 2019



6 Data Objects

6.1 Duplication Checks in Search Engine Services

(SES)

Release 1809 features the same duplication engine functionality found in earlier releases, but it is no longer included

in a tab within the Data Model Workbench. Instead, this functionality is housed in the T-Code: /VTA/BDODPM, greatly

improving performance.

In this T-Code, the Fields tab dictates where the duplication will occur, and the Coverage tab determines the

duplication’s scope. The Display tab identifies the data areas, fields, and field position shown in the duplication, and

the Code tab details the validation codes for the duplication.

The header contains three possible values for the scope of the duplication:

• Within Object: Finds duplicates within one document

• Across Object: Finds duplicates in multiple documents

• Within & Across Objects: Finds duplicates within and across documents

Once the field groups and scope are defined, users must create a duplication profile. A duplication profile is a set of

field groups used for the duplication, and multiple field groups can be assigned to a duplication profile. The

duplication profile is then assigned to a data model.

6.2 Automatic Version Creation and Posting

In earlier releases, data objects were uploaded, an initial version was created, followed by the creation of a target

version. In Release 1809, the target version of an object is created immediately after the object is uploaded. In the

Mapping tab of the Data Model Workbench, the Auto Create field must be flagged for this to occur. The Definition tab

in this workbench contains an Auto Sublist Creation field. When flagged, all the errors in an uploaded object are

automatically compiled in a sublist. Also, users must define the target version as the reversal version, and the source

version defined as the initial version. This removes the need for the T-Code: /VTA/BDOTVC to create the target

version.

Release 1809 also removes the need for the T-Code: /VTA/BDOSOC. In the Postings tab of the Data Model

Workbench, after selecting the posting object type users can flag the Auto Post field to automatically create a posting

document from the target version.

6.3 Fuzzy Match on Any Field

Fuzzy matching accurately identifies the outgoing fields for a target version from a lower match percentage. This

feature was previously only available for address fields, but in Release 1809 it is available with any field.







May 22, 2019



6.4 Derived Sections

Derived Sections avoid storing unnecessary information within the data object. Instead, this information is only

derived when it is required, thus improving performance within data objects.







May 22, 2019



7 Global

7.1 Global File Template

The difference between file templates in earlier versions of Vistex and those in Release 1809 is that the new file

templates are no longer application specific, and all file templates are maintained in one global template engine.

Global file templates are available for the following:

• Billback Agreements

• Billback Agreement Requests

• Business Register Agreements

• Business Register Agreement Requests

• Chargeback Agreements

• Chargeback Agreement Requests

• Customer Rebate Agreements

• Customer Rebate Agreement Requests

• Master Agreements

• Master Agreement Requests

• Price Review

• Purchasing Rebate Agreements

• Purchasing Rebate Agreement Requests

• Sales Incentives Agreements

• Sales Incentives Agreement Requests

• Revisions

7.1.1 Agreements

In Release 1809, agreement file templates include a Qualifier tab, which includes Agreement Type as a mandatory

field. Agreement file templates have been updated to derive the appropriate data areas based on the agreement type

selected.

When uploading an agreement file template, if the File Source field is set to File Submission, users can define the

Commit Frequency. Commit Frequency limits the number of documents processed and saved at one time. When

Commit Frequency is not defined, all the submitted documents will be processed and saved simultaneously which

causes performance issues.

When the Transfer Error Flag is marked, users can download only the uploaded documents containing errors.







May 22, 2019



7.1.2 Pricing and Planning

Pricing file templates now include Section and Mapping tabs as well as the fields Processing Type and Skip Value

Conversion.

▪ Processing Type: shows whether the indicator refers to a specific row or column within the uploaded file template, or whether multiple data areas are included in a single row.

▪ Skip Value Conversion: when flagged, values will not be converted when uploading or downloading a file template to retain the internal data.

A price proposal, price review, or a variant can all be uploaded as a pricing file template. Old templates can still be

uploaded in Release 1809, but downloads are only available with new file templates.

7.2 Status Engine 2.0

The Vistex Status Engine has been updated for Release 1809. Users can now generate a statement in .PDF format

at any stage of the status flow to which it is assigned. This functionality requires users to maintain the Activity

Template and assign this template to the proper statement type.

7.3 Output Engine 2.0

Release 1809 introduced Output Engine 2.0, which allows users to generate a statement for a Claim/Transaction

Register document in .PDF format for different transmission medium, provided that the configuration for the

processing programs are maintained in the output type. Output types can be configured for respective applications

and application areas.

In the Claim/Transaction Register Workbench, when users create a Claim/Transaction Register document with the

document type assigned an output type, the output type will trigger based on the transmission medium. The output

type is then processed, and the statement is generated according to the transmission medium.

Note: The statement type should be assigned in the processing programs for output, while maintaining the output

type.







May 22, 2019



8 Fiori

8.1 Government Pricing

Release 1809 includes three Fiori screens for use with government pharmaceutical pricing.

8.1.1 Reported Material

The Reported Material screen displays a table of all of the NDC9 and NDC11 codes saved in the system. The

columns in the table include the NDC, description, validity dates, as well as information regarding when the record

was created or changed. By clicking on any of the rows in the table, a separate screen opens showing all of the

relevant information saved for that material. This screen also has a Hierarchy tab displaying the NDC11s associated

with an NDC9, or if you drilled down on an NDC11, the associated material IDs are displayed. Line extensions are

also available in NDC11 hierarchies.

8.1.2 Transaction Type Assignment

The Transaction Type Assignment screen allows users to manage price types and their assigned classifications.

Once each price type has a classification, transaction types are linked to the proper price type classifications.

8.1.3 Price Type Tracking

The Price Type Tracking screen is a search screen for the retrieval of price type tracking information. After selecting a

price type group from the dropdown menu. The next dropdown lists all of the price types defined in the system, such

as monthly AMP or quarterly AMP. After selecting price type and the price type version, a list of tracking screens

meeting the search criteria is shown.

8.2 Hybrid Configuration

As described above, hybrid configuration allows matrix configuration activities to occur in a workbench instead of

SPRO. This application is also available in Fiori. Some items offered through hybrid configuration include formulas,

formula set up, creation of color map templates, layouts, and the addition of new fields.







May 22, 2019



8.3 Membership

In Release ESP6, users can create and change membership data in the Fiori application. The membership Fiori

application is a web version of the standard membership transaction in the GUI.

8.4 Customer List

Release 1809 allows the creation of a search profile with assigned fields to search a customer list. The sections

included in this UI profile are variant, search, and worklist. In the Qualifiers tab in the GUI, Customer List Type serves

as the qualifier for the UI profile. The Sections tab supports five sections:

• Header

• Layout

• Notes

• Customer List Where Used

• Customer Where Used

In Fiori, this application includes a Quick Entry button to simultaneously add multiple child items to a parent. This

button is not available in the GUI.

8.5 Product List

For the Product List application, Product List Type and Product Type are the qualifiers used to create the UI profile for

a product list. The five sections supported in the UI profile are as follows:

• Header

• Layout

• Notes

• Product List Where Used

• Product Where Used

• The Product List application also includes a Quick Entry button in Fiori. This button is not available in the GUI.

8.6 Vendor List

For the Vendor List application, Vendor List Type is the sole qualifier used to create the UI profile for a vendor list.

The five sections supported in the UI profile are as follows:

• Header

• Layout

• Notes

• Vendor List Where Used

• Vendor Where Used







May 22, 2019



• Vendor List also includes a Quick Entry button in Fiori. This button is not available in the GUI.

8.7 Territories

Territory List can be used with the Territories and Assignment applications. There are five possible data areas for the

Territories application:

• Determination

• Header

• Notes

• Rules

• Structure

All relevant rules and rule sheets must be assigned to Territory UI profiles.

When editing territories in the GUI, the assignment type selected in the Determination tab defines the territory, while

the Structure tab defines the assigned territory’s structure. These tabs are both available in the Fiori Territories

application.

Information contained in the Territories application can be saved as a proposal. In Fiori, the Territories Proposal

application contains six tabs:

• Header

• Territory Structure

• Determination

• Status

• Notes

• Admin Data

Territory proposals can be deleted within the application, and new territory assignments can be created. In addition to

being available in the GUI, Fiori now offers mass determination and mass assignment for territories.

8.8 Data Objects

8.8.1 UI Profile for Aggregation

To enable search and process functionality in Fiori, this UI profile must have the UI Type set to List with Processing.

In the Sections tab, the default data area is Line Items. The search profile displayed in the header provides the

search data, and the search section fields are defined from the fields maintained in the search profile. In the

Functions tab the functions necessary for aggregation are already selected, and all the selected functions will be

displayed as buttons in Fiori.

When line items are selected in Fiori, the Assign button selects a processor for those lines.







May 22, 2019



8.8.2 Fuzzy Match on Any Field

In edit mode in Fiori, the match path for selected line items is displayed above the table. When configuring the match

patch, the selection operator is set to fuzzy search to identify the outgoing field from a lower match percentage. When

searching within the match path in Fiori, users can change the incoming field to obtain a different outgoing field.

8.9 Clauses and Templates

A new Qualifier section was added to the Clause UI profile transactions. Similar to the Qualifier section in the GUI,

this functionality allows users to easily reference information from a specified object type. The Qualifier section can

be added to any existing Clause UI profile.

When setting up the Clause tile in Fiori the workspace for clauses and templates (ZGBLWRKSP) must be selected.

The UI Type is defined as Document, and the Context is set to Object Type and Application.

8.10 Designer

Designer in Fiori includes two new features in Release 1809.

8.10.1 Watermark

Users can generate a customized watermark for their documentation. Using text or an uploaded image, users can

adjust the size, position, and rotation of the watermark.

8.10.2 Flexible Group Explode

• When viewing the Selected Fields for a clause in Fiori, there are two options for viewing the flexible groups:

• In Place – exploded flexible group appears within the same column of the initial table in the document, better

suited to smaller flexible groups

• Appendix – shows full flexible group appended to the end of the document

8.11 Structural Pricing

The Master Request UI Profile now features a Structural Pricing section. Structural Pricing can be displayed three

ways:

• Basic View







May 22, 2019



• Top Down View

• Bottom Up View

Other additions to the Master Request UI Profile include the Filter Change function as well as the Import and Delete

buttons. Manual BOM and variants can also be created in Fiori.

8.12 New DMr Data Areas

8.12.1 Mass Hierarchy

To use the Mass Hierarchy application in Fiori, both the search profile and UI profile must be set to Material Mass

Hierarchy. In the UI Profile Workbench, the hierarchy data area must be added to the Sections tab. Once the

application is set up, new parents can be created, child materials can be added or removed from parents, and

hierarchy nodes can be moved all within Fiori.

www.sap.com/contactsap

© 2019 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. The information contained herein may be

changed without prior notice.

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 or its affiliate companies shall not be liable for

errors or omissions with respect to the materials. The only warranties

for SAP 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.

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. All other product and service names mentioned are the

trademarks of their respective companies.

Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

https://www.sap.com/about/legal/trademark.html

Incentive Administration by Vistex for SAPAn SAP Gateway (web) server is required to run the Fiori...

Documents

Transcript of Incentive Administration by Vistex for SAPAn SAP Gateway (web) server is required to run the Fiori...