Installing the object-centric Shipped Not Invoiced app
The object-centric version of the Shipped Not Invoiced app works with objects and events created for object-centric process mining. Before you set up the object-centric version of the Shipped Not Invoiced app, you’ll need to enable and configure the Order Management process from the Celonis catalog, load the object-centric data model with your data, and validate the standard Order Management perspective. See Prerequisites for the object-centric Shipped Not Invoiced app.
You can download the Shipped Not Invoiced app from the Celonis Marketplace. When you link the Shipped Not Invoiced app to the perspective you're using with the app, it uses the objects and events that you’ve already built from your source system data and stored in the OCPM Data Pool.
Here’s how to install the Shipped Not Invoiced app:
Open the Celonis Marketplace from the Celonis navigation menu, and search for all or part of the app’s name. You’ll probably see an original case-centric version of the app as well as the object-centric version. Only the object-centric version is suitable for object-centric process mining.
Select the Shipped Not Invoiced (object-centric) app to see its information page.
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 object-centric Shipped Not Invoiced app.
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.
In the Studio overview, find the Shipped Not Invoiced app package in the space where you installed it, and click its tile to go to the app package.
Click the Package Settings icon (the box) and select Variables.
Select the Assign Data Model button, then search or browse for the Order Management perspective you're using with the app, and click to select it. Click Save to set the Data Model variable.
The Shipped Not Invoiced app needs publishing before configuration because publishing triggers the creation of augmented attributes and makes profile views available. 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.
Open the Action View and validate that your data is shown. If there are any errors, you can address them during app setup.
Use the Setup and Validation view to set up the variables for the app. See Configuring settings for the object-centric Shipped Not Invoiced app.
Tip
Because the Shipped Not Invoiced 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.
After you’ve worked through the Setup and Validation and Value Framing views, 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 object-centric Shipped Not Invoiced app explains the process.
If you want to add custom values for the status of delivery items (besides the supplied values "New", "In Progress", and "Rejected"), configure the augmented attributes to add these. Configuring augmented attributes for the object-centric Shipped Not Invoiced app has instructions to do this.
Configure the tasks and actions for the app. Configuring tasks and actions for the object-centric Shipped Not Invoiced app tells you how, and explains what needs configuring.
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 object-centric Shipped Not Invoiced 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.
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.
When you publish the Shipped Not Invoiced app for the first time, it creates a number of augmented tables in the data model. You’ll see these in the app’s Knowledge Model as autogenerated KPIs and records, and they are used in the calculations for some of the KPIs. The tables are:
O_CELONIS_DELIVERYITEM_AUG_UNBILLED_STATUS
O_CELONIS_DELIVERY_AUG_COMMENT
O_CELONIS_SALESORDERITEM_AUG_COMMENT
O_CELONIS_SALESORDER_AUG_COMMENT
O_CELONIS_CUSTOMER_AUG_COMMENT