Skip to main content

Celonis Product Documentation

Activating the Value Discovery App

In order for the Value Discovery App to work with the Starter Kit, modifications have to be made to the Data Model.

Modifications to the Data Model

The Value Discovery App needs a new table added in the Data Model using the following steps:

  1. Go to the Data Integration section of Celonis and select the Data Pool that you are using for the Starter Kit.

  2. Click Data Jobs and then click on New Data Job with the option to add it as a Global (no data connection). We recommend naming it "Create Inefficiency Table".

  3. Click on New Transformation. We recommend naming it "Create Inefficiency Table" and without any task template.

  4. Paste the code provided below.

  5. Select all code and click the Execute button.

  6. Go to the Data Model that you are using for the Starter Kit. Add the INEFFICIENCIES table via the Add Tables button and then click Finish.

  7. Reload the Data Model.

DROP TABLE IF EXISTS INEFFICIENCIES;
CREATE TABLE INEFFICIENCIES (
  INEFFICIENCY_NAME VARCHAR(100),  
  TIME_TO_VALUE VARCHAR(100),  
  BUSINESS_OBJECTIVE VARCHAR(100))
;

INSERT INTO INEFFICIENCIES
  (INEFFICIENCY_NAME,TIME_TO_VALUE,BUSINESS_OBJECTIVE)
  SELECT 'Duplicate Invoices','A - Low','Spend' UNION
  SELECT 'Lost Cash Discount','A - Low','Spend' UNION
  SELECT 'Early Payments','B - Medium','Working Capital' UNION
  SELECT 'Late Payments','A - Low','Labor Productivity' UNION
  SELECT 'Manual Invoice Posting','C - High','Labor Productivity' UNION
  SELECT 'Short Payment Terms','B - Medium','Working Capital' UNION
  SELECT 'Manual Payment Block Changes','B - Medium','Labor Productivity' UNION
  SELECT 'Manual Invoice Clearing','C - High','Labor Productivity' UNION
  SELECT 'Manual Payment Term Changes','B - Medium','Labor Productivity' UNION
  SELECT 'Invoices w/ Retrospective POs','A - Low','Spend' UNION
  SELECT 'Invoices without Purchase Order','A - Low','Spend' UNION
  SELECT 'Manual Baseline Date Changes','B - Medium','Labor Productivity' UNION
  SELECT 'Baseline Date Decreases','B - Medium','Working Capital' UNION
  SELECT 'Payment Term Decreases','B - Medium','Working Capital' UNION
  SELECT 'Unfavorable Payment Terms','B - Medium','Working Capital' UNION
  SELECT 'Multiple Payment Terms per Vendor','B - Medium','Working Capital'

Value Discovery App Runtime Variables

The runtime variables for the Value Discovery App are listed in the Variables tab of the Starter Kit settings. Here are some important runtime variables that you might need to configure to match your Data Model and your SAP system.

Variable ID

Variable Description

Default Value

userTypesAutomated

Include all user types that are considered Automated

'B', 'S'

PostingActivity

Posting Activity

'Enter in SAP'

setPaymentBlockActivity

Payment Block Activity Field

'Set Payment Block'

BaselineDateField

Baseline Date Field

'ZFBDT'

PaymentTermField

Payment Term Field

'ZTERM','ZBD1T','ZBD2T','ZBD3T','ZBD1P','ZBD2P'

InvoiceClearingActivity

Invoice Clearing Activity

'Clear Invoice', 'Clear Invoice with Payment Run'

ReferenceTransactionField

Field to identify a reference transaction

‘RMRP’

PaymentBlockActivity

Payment Block Activity

'ZLSPR'

Important

After updating Value Discovery App settings, publish the package that contains the app. There's a Publish button at the top of all the screens in your Studio Space.

After you publish an app for the first time, changing runtime variable values in the Validation and Value Assessment view or Settings view in Studio doesn’t change their values in Apps. After publishing, 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.