Skip to main content

Installing the SAP - Payment Terms Harmonizer (Catalog 3) app

The SAP - Payment Terms Harmonizer (Catalog 3) app works with objects and events created for object-centric process mining. Before you set up the Payment Terms Harmonizer app, you’ll need to enable and configure the Procurement process from the Celonis catalog, load the object-centric data model with your data, and validate the standard Procurement perspective. You’ll also need to create custom items and extend the perspective. Prerequisites for the SAP - Payment Terms Harmonizer (Catalog 3) app tells you what to do.

You can download the SAP - Payment Terms Harmonizer (Catalog 3) app from the Celonis Marketplace. When you link the SAP - Payment Terms Harmonizer (Catalog 3) app to your extended perspective, it uses the objects and events that you’ve built from your source system data for the Procurement process and stored in the OCPM Data Pool.

Here’s how to install the SAP - Payment Terms Harmonizer (Catalog 3) app:

  1. Open the Celonis Marketplace from the Celonis navigation menu, and search for all or part of the app’s name. You’ll see multiple versions of this app. You want to install the one named SAP - Payment Terms Harmonizer (Catalog 3).

  2. Select Get it now to install the app. If you see Request Access instead, click this to request the app, and check the other prerequisite steps in Prerequisites for the SAP - Payment Terms Harmonizer (Catalog 3) app .

  3. In Celonis, choose a Studio space to install the app in. You can use an existing Studio space or create a new one. (You can move the app after installation.) Click Confirm to proceed with the installation.

  4. In the Studio overview, find the SAP - Payment Terms Harmonizer (Catalog 3) app package in the space where you installed it, and click its tile to go to the app package.

  5. Click the Package Settings icon (the box) and select Variables.

  6. Select the Assign Data Model button, then search or browse for the extended perspective perspective_custom_PaymentTermsHarmonizer (or your chosen name for the custom perspective you set up in Prerequisites for the SAP - Payment Terms Harmonizer (Catalog 3) app ). Click to select it, then click Save to set the Data Model variable.

    Tip

    Use the version of the perspective with the prefix test: if you're working in the development environment, and the version without the prefix if you're working in the production environment.

  7. Set the Knowledge Model key for your local app installation, as the value of the Knowledge Model Key variable in the app’s Knowledge Model. Setting the Knowledge Model Key variable for the object-centric Payment Term Checker app explains how.Setting the Knowledge Model Key variable for the object-centric Payment Term Checker app

  8. The SAP - Payment Terms Harmonizer (Catalog 3) app needs publishing before configuration because publishing initializes the augmented attribute (Update Negotiation Status for a Supplier, Update Negotiation Status for a VAT, Term Validity for PO, Term Validity for VendorContract, Term Validity for VendorMasterData, Term Validity for Invoice MM, Term Validity for Invoice FI. Select the Publish button to publish a version of the app.

    Tip

    To prevent business users from accessing the app while you’re working on setup, set the package permissions to hide it from them. Click the Package Settings icon (the box), and select Permissions. Set “No Permissions” to stop a user or group from seeing the app. You can also hide the view in the Apps Perspective tab in the package settings, but then you won’t see it either, so you won’t be able to check your settings in Apps.

  9. Open the SAP - Payment Terms Harmonizer (Catalog 3) app and validate that your data is shown. It might take a few seconds before all the tables are created. If you see “Table could not be found” errors, wait for a short time and then reload the page to see if they disappear. If they remain, you’ll need to fix this during app setup.

  10. Use the Setup & Validation view to set up the variables for the app. Configuring settings for the SAP - Payment Terms Harmonizer (Catalog 3) app tells you how.

    Tip

    Because the SAP - Payment Terms Harmonizer (Catalog 3) app needs to be published right away, you’ll need to change the settings in these views in Apps as well as in Studio. Changing the settings in Studio after publishing doesn’t affect the values in Apps.

  11. Work through the steps in the Setup & Validation view to change the default parameters from the Knowledge Model to align with how things are done in your organization. If anything is still not the way you want it, you can make further adjustments to the KPIs and calculated attributes directly in the app’s Knowledge Model. Validating KPIs for the SAP - Payment Terms Harmonizer (Catalog 3) app explains the process.

  12. If you want to add custom values for the Update Negotiation Status for a Supplier, Update Negotiation Status for a VAT, Term Validity for PO, Term Validity for VendorContract, Term Validity for VendorMasterData, Term Validity for Invoice MM, Term Validity for Invoice FI fields, configure the augmented attributes to add these. Configuring augmented attributes for the SAP - Payment Terms Harmonizer (Catalog 3) app tells you how.

  13. Configure the tasks and actions for the app. Configuring tasks and actions for the SAP - Payment Terms Harmonizer (Catalog 3) app tells you how, and explains what needs configuring.

  14. If you want to customize the app’s views to change their look, fit your business process, or include custom items, edit them in Studio. Editing views for the SAP - Payment Terms Harmonizer (Catalog 3) app explains the process. You’ll need Analyst permissions for Studio and the views to modify them. If you make any changes to view components that involve the calculated attributes from the Knowledge Model, we’ll automatically update the calculated attributes in the Knowledge Model.

  15. When you’re happy with your results, publish a version of the app. There's a Publish button at the top of all the screens in your Studio space.

    Tip

    After publishing the package, if you make any further changes to variables in the Setup & Validation view, make sure you set these in both Studio and Apps. Changing the settings in Studio after publishing doesn’t affect the values in Apps.