Procurement Starter Kit
Note
To successfully install the App, please check with product management that accesses to the app has been granted, and all required features have been enabled in the backend. The list of required features is found in the Appendix.
Please find in the following a general overview of the App and a guide on how to set it up.
Here's a short briefing on the most essential points to consider.
Data Model, transformations, and extractions
The Process Data Model should be based on the current SAP ECC Purchase-to-Pay process connector from the Marketplace. This is very important as the data extractions, data sharing between pools & transformations can have a lot of variety as well as the data model configuration (tables configurations/alias, activity & case table configuration, and key-relationships). If you can not use the standard, you can always compare your setting to the standard setting to identify deviations.
The PR Connector uses the ‘Transfer Data Between Data Pools’ functionality, allowing it to pull data from the O2C, IM, and PP pools if necessary.
Package variables
On installation of the App from the Marketplace, it is important that you set up the different package variables. These are:
sap-ecc-purchase-to-pay-data-model
Currency (the currency in which you would like to display the app)
Variables
The Knowledge Model is built using variables in the PQL statements for the tables, filter objects (gaps and filters), thresholds, and often used dates, activities, and fields. So, your first point when making adjustments or customizations is to change the variable once, and all related definitions will also be updated. If you find that a variable is missing or a KPI is hardcoded with something that should be variable, please provide feedback to the product team.
Filters
To minimize the adjustments needed, the App is built in a way that is often enough to change the PQL once to update all related definitions of the execution gap. To do so, we have implemented all logic using variables. For example, the filter 3_YTD allows a user to filter three years' worth of data to date, which can then be leveraged across views and components in a repeatable fashion.
Others: All other dependent areas (e.g., KPI definitions, time-series filters) aim to use variables or formulas (KPIs) where possible.
PQL-based
In the end - everything is still based on PQL and the process data model. If you get any error messages, you can always narrow it down to the respective pql-statement (be it a selection, KPI, or filter statement) and test your code in an analysis to see if you might have any syntax errors. Such errors can occur when using Pull Up (PU) functions with incorrect dimensions.
High-level process
Below are the high-level steps to get started Procurement app.
Set up a Connection to an SAP system from Celonis
Set up extractor server
Configure Connection
Install the SAP- ECC Purchase-to-Pay Process connector
Select the element in the Marketplace
Reuse your existing connection
Update the Data Pool Parameters
Export the Data Connections from your O2C, PP, and P2P pools and import them into the MM pool
Execute the data extraction as full load (only the first time needed)
Execute the full transformations (in the order that the connector provides)
Install the Starter Kit App
Select the app in the Marketplace
Assign your SAP ECC Purchase to Pay Data Model
Finish setup
Validate and customize the Knowledge Model and runtime variables
Implement KPI customization in KM
Implement customizations in Views