Inventory Management App Configuration
In order to correctly apply the logic that defines the content of the Starter Kit, different variables, the KPIs, and filters need to be configured and validated. The following section will guide you through the app configuration process, with a main focus on the KM configuration.
Variable Configuration
To start the variable configuration, please go to the Knowledge Model (KM). Go through the variables section in the view mode and validate whether the input used for the variables is correct for your business needs. To view all variables in use, you can navigate to the variables section of the KM.
For the apps, only non-auto-generated configurations are used, so you can disable the auto-generated definitions. In some cases, variables are used for storing values (strings, integers, etc.) that are used inside of KPIs and inefficiencies, such as the Planned Lead Time, for storing target and benchmark values of KPIs and frequently used activity names like the Goods Issue activity.
Some variables are more important than others to update, since the business logic of the app will not work if they are not set correctly. An example are the variables that reference different fields and activity names, e.g. the "Record Goods Issue" activity.
On the other hand, all variables are set with a default value and, in some cases, the app will still function properly if they are not updated, such as the "Desired Service Level". If you identify the variables that need to be adjusted, you can easily update them directly from inside of the variable part of the KM visual editor. Other variables are stored in the plain text variables section of the package settings. These variables can also be changed if needed and are only affecting the package in which they are defined.
Important Variables to Validate and Update
Below is a list of variables that should be validated during the App configuration. These variables can only be updated from the runtime variable editor or KM editor with ANALYST or ADMIN permissions.
Variable ID | Type of variable | Variable name/description |
|---|---|---|
toCurrency | Runtime variable | Currency to be displayed in app |
fromCurrency | Runtime variable | Original currency |
currencyConversionType | Runtime variable | Currency conversion type |
PARAMETER_ACTIVITY_PURCHASE_ORDER_ITEM_CREATED | KM | Purchase Order Item Start Activity |
PARAMETER_ACTIVITY_PURCHASE_ORDER_ITEM_GOODS_RECEIPT | KM | Purchase Order Item Goods Receipt Activity |
PARAMETER_ACTIVITY_PRODUCTION_ORDER_ITEM_START | KM | Production Order Item Start Activity |
PARAMETER_ACTIVITY_PRODUCTION_ORDER_ITEM_COMPLETED | KM | Production Order Item Completed Activity |
Note
The variables not listed here can be changed from the UI with a dropdown or an input box and will be part of the KPI validation of the Validation Cockpit.
Updating the Business Logic
The business logic is packaged into formulae (KM KPIs) to reuse in the different parts of the app or inside of other KPIs/formulae to make the setup more concise. These PQL-statements define the calculations of KPIs, filter statements on your data, and inefficiencies. Hence they are one of the most important parts of the app.
For example, the formula KPI_MATERIAL_PUSUM_EXCESS_INVENTORY_RATE is used for all excess inventory KPIs (e.g. Obsolete Stock, Excess Stock, etc.). By adjusting the underlying business logic in that one place, you adjust the business logic for all KPIs and related definitions simultaneously.
This list is not exhaustive and should be checked inside of the Knowledge Model. Make sure to also check nested formulas that might be used within the KPIs listed below. You can identify by the prefix whether it’s defined as KPI or formula.
KPI ID | Formula description |
|---|---|
FORMULA_MATERIAL_INDICATOR_STOCK_OUT | Business Logic for Stockouts |
FORMULA_MATERIAL_INDICATOR_STOCK_UNDER | Business Logic for Under Stock |
FORMULA_MATERIAL_INDICATOR_STOCK_EXCESS | Business Logic for Excess Stock |
FORMULA_MATERIAL_INDICATOR_STOCK_OBSOLETE | Business Logic for Obsolete Stock |
FORMULA_MATERIAL_INDICATOR_STOCK_UNTOUCHED | Business Logic for Untouched Stock |
FORMULA_MATERIAL_INDICATOR_STOCK_OUT_DURING_REPLENISHMENT | Business Logic for Stockout during Replenishment Period |
FORMULA_MATERIAL_INDICATOR_SERVICE_LEVEL_STOCKOUT_SALES_ORDER | Business Logic for Upcoming Demand without Supply |
If you update the underlying business logic or used variables, make sure to also update the documentation for the business users in the Documentation folder.
Updating the Runtime Variables
Next, configure the following runtime variables to your specifications.
Variable ID | Variable Description | Default Value |
|---|---|---|
initialStockFloor | Minimum value for a material's Initial Stock | MARC.BSTMI |
materialAvailabilityMRPType | MRP types to be considered for Material Availability | 'PD', 'R1', 'VM', 'VB', 'VV' |
plannedLeadTime | Planned Purchasing Lead Time | MARC.PLIFZ+MARC.WEBAZ |
plannedProductionLeadTime | Planned Production Lead Time | MARC.DZEIT |
planningStrategy | Planning strategies to be excluded from Material Availability | ‘20' |
recordGoodsIssueActivity | Goods Issue activity | ‘Record Goods Issue' |
Important
For the app to work properly, publish the app by clicking the Publish button in the upper right corner.