Skip to main content

Celonis Product Documentation

IM Master Data Improvement FAQ

Here are some most commonly asked questions regarding the Master Data Improvement App.

In case you have identified a bug (e.g. PQL incorrect, UI not working properly) or have a feature request (e.g. new KPI, additional component, new use case), please feel free to create a ticket with our customer support or contact us using the built-in feedback icon in the app.

  • To what extent are Scheduling Agreements considered? Scheduling Agreements are currently already part of the Purchase to Pay (P2P) connector and are therefore considered in Inventory Management as well.

    The default SAP data does not allow for a straightforward mapping between Purchase Order Items and Goods Receipts for Scheduling Agreements. While this does not impact purchase quantities or values, it does affect lead time considerations which can be alleviated by introducing a mapping between both data objects. This mapping is done in a separate connector which you can find in the Marketplace:

    image6.png

    If installing an additional connector as suggested above is not feasible, consider sticking to the default of determining actual lead times from the first deliveries only.

  • My dependency does not get set up correctly. How can I fix this? If both the IM Starter Kit and the IM Master Data Improvement packages are installed but setting up the dependency still leaves an error message, the following solution typically works:

    1. Select IM Master Data Improvement Package (or other app).

    2. Create a new Knowledge Model in the package as an extension. Select the relevant Master Knowledge Model as the base (for IM Master Data Improvement this would be the IM Master Knowledge Model).

      image10.png
    3. Open the new Knowledge Model and copy the Base header. It should look like this: base: key: im-starter-kit.im-master-knowledge-model version: 1.0.156 dataModelId: ${{inventory-management-data-model}}

    4. Overwrite the base header in the actual knowledge model of the app (if you only work with the newly created knowledge model, you would have to change each view individually).

    5. Save and publish the package.

    6. KPIs, records, etc. should be available. Further, it should now be safe to remove reference to version shown above (“version : 1.0.156”).

  • I want to customize or create additional KPIs for past/ future consumption using UNION_ALL. What do I need to look out for?

    Currently you can at most connect eight tables using the UNION_ALL operator. In order to have any new or customized objects work with the existing logic, the used tables must be listed in the same order. They must have the same Common Table.

    The following combination will cause an error since there is no Common Table due to different ordering and different number of tables involved:

    image1.png

    A Common Table in UNION_ALL requires that both the number and the ordering of the tables involved are the same:

    image2.png

    In case a table is not required for the KPI you are trying to create, such as if you want to compute purchase value a sales table is irrelevant, you can give an empty reference for the sales table to the UNION_ALL operator by including BIND(“VBEP”, NULL).

    If you require fields or values which are not part of the considered tables but can be referenced via joined tables in the data model, you can use pull up function or the BIND operator just as with regular KPIs.