Validating KPIs for the object-centric Open Purchase Requisition Processing app
Work with the Setup and Validation view to change the default parameters for the Open Purchase Requisition Processing app. We explain how we calculate each KPI, and what parameters the app uses by default. You can change their values to align with how things are done in your organization.
The Setup and Validation view is the best way to validate and adjust the KPIs in the Open Purchase Requisition Processing app’s Knowledge Model. If you’ve worked through your use case there but something is still not the way you want it, you can make further adjustments directly in the Knowledge Model in Studio.
The Knowledge Model for the Open Purchase Requisition Processing app is called “Knowledge Model”. You’ll need Analyst permissions on Studio and the Knowledge Model to update it. Each KPI contains a PQL (Process Query Language) formula which you can change in our editor to change how the KPI behaves. Your changes are applied when you publish a new version of the app.
The Knowledge Model also includes calculated attributes that contain the business logic to classify and provide metadata about objects. You can use them in PQL queries as if they were another column in the database table for the object type. They appear in the Knowledge Model as attributes of relevant records. If you make any edits to view components that involve the calculated attributes from the Knowledge Model, we’ll automatically update the calculated attributes in the Knowledge Model to match your edits. You can also adjust them directly in the Knowledge Model before or after editing the views.
Calculated attributes and PQL formulas might be reused in the calculations for several KPIs across the Knowledge Model. If you change the business logic in one location and save your change, all of the KPIs that reuse the calculated attribute or PQL formula will reflect your changes.
Here’s how to work with the KPIs and calculated attributes in the app’s Knowledge Model. If you need training, check out the training track “Build Knowledge Models and Views” on the Celonis Academy.
In the Celonis navigation menu, select Studio.
In the Studio overview, find the Open Purchase Requisition Processing app in the space where you installed it, and click its tile.
Select the Knowledge Model from the app navigation.
Select the KPIs section of the Knowledge Model to work with KPIs, or the Records section to work with calculated attributes.To see only the records with calculated attributes, and see only the calculated attributes on those records, click the Hide Autogenerated Definitions icon by the search bar.
To see and edit the full PQL formula and other settings for a KPI, click its row to open an editor. The editor automatically validates any changes that you make in the PQL formula.
If you want a fuller-featured PQL editor that lets you select from the tables and columns in your data, click on the pen icon next to the PQL formula.
If you need to disable a KPI or formula, click the three vertical dots at the top of the editor, and select Disable Scope, then click Disable to confirm. When you do this, the object can't be accessed or used anywhere in the package, including by other apps that depend on it.
When you’ve made changes to the KPIs and calculated attributes, use the Publish button at the top of the screen in your Studio space to publish a new version of the app.
For the Open Purchase Requisition Processing app, you can manage the settings for most of the important KPIs using the Setup and Validation view and Settings view. The important KPIs that you can only manage in the Knowledge Model are:
KPI Detail | Name | Record ID |
|---|---|---|
Total number of Purchase Requisition Lines for the selected time period. | Requisition Lines | P2P_Metric_PurchaseRequisitionLine_COUNT__PurchaseRequisitionLine |
Total net purchase requisition line value for the selected time period. | Requisition lValue | P2P_Metric_PurchaseRequisitionLine_SUM__PurchaseRequisitionLineValue |
Total net document line value for the selected time period. | Purchase value | P2P_Metric_PurchaseRequisitionLine_SUM__PurchaseRequisitionLineValue |
If the PR Line Value is higher than defined in the Setup it gets marked as “Ishigh” | IsHighValue | IsHighValue |
Percentage of purchase document lines where a vendor contract was used when the document lines were created. | HasVendorContract | P2P_Metric_PurchaseDocumentLine_AVG__VendorContractUsage |
Percentage of purchase document lines where at least one line item was added as free text | FreeText rate | P2P_Metric_PurchaseDocumentLine_AVG__FreeTextOrder |