Skip to main content

Celonis Product Documentation

Table MATERIAL_PLANT_CEL_TASK not found in Knowledge Model

Error Message: … has PQL errors. Table not found: “MATERIAL_PLANT_CEL_TASK”


Solution: The table doesn’t exist in the selected data model. This could be because:

  1. It does not fulfill the requirements for task augmentation.

  2. No skill was executed yet to ‘create’ any task. (This table stores the created tasks, if there are none created yet - the table doesn’t exist yet.) Make sure to check the skill logs to see if - for the record MATERIAL_PLANT any skill was executed yet.

  3. If no tasks were created and you don’t want to use tasks, you can ignore this error.

Table OR Columns not found in Views

If the error message “Table X cannot be found” or “Column Y cannot be found” is present inside of a table in a view, very likely inside of the Master Data Improvements App main view, then it is likely caused by the issues described in section 9.1 or 9.2. To resolve this issue in the app, the most pragmatic approach is to set the column to "Scope: Hidden", which will remove it from appearing inside of the table, and the error message should disappear. See the screenshot below of how that looks like in the YAML.


The trick to this solution is that you need to find the ID of the column, which is sometimes only possible inside of the ‘Preview final’ component, inside of the full YAML editor. This is because the table is defined in the base view, which is not ‘fully visible’ in the extension that’s installed on your team. To see the column ID, follow the steps below.

  1. Click Switch to Code Editor.

  2. Click Preview Final.

  3. Find the table in the right hand section of the editor.

  4. Find the specific ID of the column you wish to overwrite. For this example, let’s take the ID: MATERIAL_PLANT.MATERIAL_NUMBER.

  5. You can then go back to the visual editor, navigate to the table, and then set that ID to “Scope: hidden”.

Installing new apps and updating existing apps

Q: I just updated to the latest version of the Control Center App, and suddenly there is an error on the KPI List component. I found that the issue is with the KPI Material Availability, as the error message for this kpi displays: “column ‘STOCK_HISTORY.DAYS_MAT_AVAILABLE’ is missing”. See the example screenshot below from a table component that references a field that does not exist in the data model.


Answer 1:

This error is likely due to the Inventory Management Connector having added in a new field to the Stock History Table, namely ‘DAYS_MAT_AVAILABLE’ (in January 2022 this field was added in, with the name ‘DAYS_MAT_AVAIL’, which stores the number of days the stock level was greater than zero per month per material. Depending on when you initially installed the connector will influence whether or not that field is available for use inside of the Inventory Management data model. In order to rectify this issue, there are a couple of ways forward.

  1. Update the connector to the latest version by either copying in the new additions to your existing data pool, and copying your customizations into the latest version of the connector

  2. Revert the App to the older version prior to your update (in the event that it was an App update that causes this issue). This would mean you cannot leverage any of the other new features that might have been released inside of this version of the App.

  3. Try to ‘hide’ the missing column from the app, utilizing the “scope: hidden” functionality inside of the App UI. For example, editing the table with the error, and setting that KPI reference to “scope: hidden”, which will remove this KPI from the App’s UI. (least advised, as this process is not always straightforward, and can cause other issues along the way)

I installed the inventory management connector some months ago, and have just tried to install the Inventory Projections App from the Marketplace. After installing the app, I get the following error: “Table with name PLAF cannot be found.” See the screenshot below.


Answer 2:

This error is likely caused by the fact that the version of the connector you installed in the past did not include the PLAF table in the data model, as it was not required by the earlier Inventory Management Apps. However, since the Inventory Projection app required the Planned Orders from PLAF, it had to be transformed and added to the data model. There are a few ways to resolve this issue.

  1. The advised approach is to install the latest version of the connector, copy the PLAF extractions and transformations into your productive connector, and then add the transformed table into the data model.

  2. If for any reason this table is not used by your company, a second approach would be to create a ‘dummy’ PLAF table. Whereby, you simply create the table with the necessary fields, but don’t load any data into it. You can then join this empty table to the data model.

  3. If the first and second options are not possible, the last suggestion is to modify the KM formulas that reference the PLAF table, whereby you would comment out or delete any reference to PLAF fields. These changes would be stored in your ‘extension’ of the Knowledge model, and can be easily removed in the future if you ever wanted to use the fields again.

    1. This approach is not advised, as it can be very effortful to modify each of the PQL formulas referencing this table (and other tables), especially in the case of PLAF as it is present in a lot of UNION_ALL based functions.