Installing the case-centric Shipped Not Invoiced app
You can download the Shipped Not Invoiced app from the Celonis Marketplace. Before you install the app, you’ll need to set up the appropriate Data Connection and Process Connector and load the Data Model, as explained in Prerequisites for the case-centric Shipped Not Invoiced app. When you’ve done that, follow these steps to install the Shipped Not Invoiced app:
Open the Celonis Marketplace from the Celonis navigation menu, and enter "Shipped Not Invoiced" in the Marketplace search.
Select the Shipped Not Invoiced app to see its information page.
Select Get it now to install the 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.
Click Assign Data Model when the app prompts you. This takes you to the Variables tab in the Settings view.
Select the Assign Data Model button, then search or browse for the Data Model “Order-to-Cash for SAP ECC”, or your Data Model copy for the Shipped Not Invoiced app if you needed to reduce the VBAP table, and click to select it. Click Save to set the Data Model variable.
Set the Knowledge Model key for your local app installation, as the value of the Knowledge Model Key variable in the app’s Knowledge Model. Setting the Knowledge Model Key variable for the case-centric Shipped Not Invoiced app explains how.
The Shipped Not Invoiced app needs publishing before configuration because publishing triggers task creation, displays augmented attributes, and makes profile views available. Select the Publish Package 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. The Permissions settings are available from the package’s context menu (the three vertical dots by the package name). 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 the User Guide view and validate that your data is shown. It might take a few seconds before all the tables are created. If you see “Table could not be found” errors, wait for a short time and then reload the page to see if they disappear. If they remain, you’ll need to fix this during app setup.
Use the Validation and Value Assessment view and the Settings view to set up the runtime variables for the app. See Configuring settings for the case-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.
Check that the business logic used by the KPIs in the app’s Knowledge Model is correct for your business. Start with the Validation and Value Assessment view, which guides you through setup for key KPIs. Validating KPIs for the case-centric Shipped Not Invoiced app explains how to check the KPIs that can only be managed in the Knowledge Model. You’ll need Analyst permissions for Studio and the Knowledge Model to modify any of the KPIs and their calculations.
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 case-centric Shipped Not Invoiced app has instructions to do this.
Configure the tasks and actions for the app. Configuring tasks and actions for the case-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 properties, edit them in Studio. Editing views for the case-centric Shipped Not Invoiced app explains the process. You’ll need Analyst permissions for Studio and the views to modify them.
When you’re happy with your results, publish a version of the app. There's a Publish Package button at the top of all the screens in your Studio space. If you made any further changes to runtime variables in the Validation and Value Assessment view or the Settings view, make sure you set these in both Studio and Apps.
Augmented Tables
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.
Tasks:
SALES_ORDER_CEL_TASK
SALES_ORDER_ITEM_CEL_TASK
CUSTOMER_CEL_TASK
Augmented attributes:
SALES_ORDER_ITEM_AUGMENTED_UNBILLED_COMMENTS
SALES_ORDER_ITEM_AUGMENTED_UNBILLED_STATUS
If you see errors in the views because one or more of the augmented tables isn’t found, make sure that you’ve published the app package, and that your settings for the runtime variables are the same in both Studio and Apps. If those weren't the problem:
Check the Sensor Logs and the Execution Logs for the skills with Smart Sensors for any problems - there might be a PQL error related to a filter used by the app.
Enter each skill with a Smart Sensor in edit mode and click the step “Create Task”. If you don’t see the configuration panel on the right side, raise a support ticket (Support tells you how) to get the backend feature flag enabled.
If none of these solutions work, raise a support ticket (Support tells you how) to check if there’s an infrastructure issue.