Celonis Product Documentation

The architecture diagram below shows what views exist and how those component specific views are embedded in the Parked & Blocked Action View. The gray boxes indicate the different tabs of the Action View. The blue “Component Base Views” are separately defined Base Views that are embedded in the Action View at multiple places.

The yellow components are directly defined in the Action View.

The app comes with four central components: the KPI list, a KPI List for Parked & Blocked invoices only, a Breakdown Table and an Action Table that are used in multiple tabs as depicted in the diagram above. The standard configuration is located in the folder Bases/Components.

This means in case you want to adjust the tables in the invoice table in the Parked & Blocked View, the update needs to be done in the “Action Table” view.

The App comes with two layers of profile views - the Action View is connected with the Invoice Details Profile View using the “KnowledgeObjectID“ INVOICE_CASE and showing contextual information of the invoice. From this View, linked Purchase Orders and Purchase Order Items can be opened using the “KnowledgeObjectID“ PURCHASE_ORDER and PURCHASE_ORDER_ITEM.

This approach is also used for the invoice details view. By default, the app comes with three different “issue views”: one for price-quantity variance, one for a vendor block and a default one in case the underlying issue is unclear. Depending on the recognized problem, only one of those views is shown in the Overview tab. Section Adding an issue details view describes how additional views for customer specific problems can be added (e.g. non-PO invoices, invoices in a workflow). While the components illustrated by the blue boxes are embedded in the invoice details view, the components illustrated in yellow are directly defined in the invoice details view.

From the Invoice Details Profile View, the App allows access to Purchase Orders connected with the invoices by clicking on either the purchase order number or the purchase order item number.

The layout and all components for both views are defined in the view called “Purchase Order & Goods Receipt”. The views “Purchase Order” and “Purchase Order Item” embed the “Purchase Order & Goods Receipt” view and have a dynamic filter on top of it using the record variable. This setup allows you to use the same underlying view but dynamically filter on either the PO (EBELN) or on the PO ITEM (EBELN & EBELP), depending on the user’s click.