Skip to main content

Configuring settings for the SAP - Payment Terms Harmonizer (Catalog 3) app

Use the Setup and Validation view to configure the app’s runtime variables and validate the business logic. This view is split into three different tabs: Settings and Scope, Validating VAT Codes and Exploring Benefit Calculations.

There you can define:

  • Settings and Scope: Currency settings for KPI calculations, the Payment Terms Documents Selection for the Best Payment Terms calculation, the relevant Spend Threshold for a Payment Term to be relevant in the harmonization use case as well as the Priority Definition which helps identify which Suppliers need most attention first

  • Validate VAT Codes: you can exclude specific VAT Codes from your calculation as well as standardizing Vendor Names for effective clustering.

  • Explore Benefit Calculations: you can define your WACC factor, the default value is set at 100%.

The settings in this view control the underlying Knowledge Model variables and directly influence KPI calculations and prioritization in the operational app views. After publishing, variable changes must be made in the Apps environment to take effect for end users.

Important

After you publish an app for the first time, changing runtime variable values in the Setup and Validation view or Value Framing view in Studio doesn’t change their values in Apps. The Payment Terms Harmonizer app needs to be published right away to initialize to values, tasks and augmented attributes. So you’ll need to work with the views in the Apps area in order for the values of the settings to be applied for end users. It’s best to keep the two sets of variable values in sync so that your results in Studio match those in Apps.

Here’s how to work with the Validation and Value Assessment view Setup and Validation view in Apps:

  1. In the Celonis navigation menu, select Apps.

  2. Find the SAP - Payment Terms Harmonizer (Catalog 3) app in the space where you installed it, and click its tile.

  3. Select the Setup and Validation view if you know what you want to change default variable values.

  4. When you’ve finished configuring the settings, make the same changes to the settings in the Studio package for the app, to keep them in sync.

Tip

When you’ve finished setup and the app is in use by business users, to avoid accidental changes, consider limiting the availability of the Setup and Validation view and the Value Framing view. You could restrict these to a specific group of business users who are responsible for making adjustments to the variable values.