Skip to main content

Celonis Product Documentation

Open Order Processing Getting Started Guide

With Business Applications it is easier to deliver insights into your processes and drive actions that resolve inefficiencies and increase efficiency. The whole installation process for Open Order Processing takes just a few steps if you have your SAP ECC Order-to-Cash Data Model already installed.

Notice

To learn more about setting up the Open Order Processing app, please have a look at the technical enablement in the academy. Alternatively, this page guides you through all the steps.

To use the Open Order Processing application, an SAP ECC Order-to-Cash data model must be in place. Please use this flow chart to find out if you still need to act or if you can proceed with Step 2.

DataModelFlow.png
  • If you have no data model in place you can either create a custom one or install the SAP ECC connector for the O2C process. We would recommend this second option. You can find more information on this step here.

  • To enable augmentation of the order status and tasks, the VBAK is limited to 30M entries. If your data model exceeds this, please create an operational data model. This is explained in the Add-Ons Guide for Data Engineers in the section for a fast-loading data model.

Follow these steps in the video to get your Open Order Processing application running. You can also review the steps in detail after the video.

 
  1. Search for the App on the Marketplace: Enter “Open Order Processing” in the search bar to locate the app. Open the App and then click the “Request Access” or “Install” button to begin the installation.

  2. Choose a Space: During the initial installation of the App from the Marketplace, you can either create a new “Space” into which the App is downloaded (e.g. Order Management) or use a pre-existing space. Click “Confirm” to proceed.

  3. Connect Data Model: After downloading the application you must assign a data model to the package. In the package settings, your data model must be assigned to the variable 'sap-ecc-order-to-cash-data-model'. If you open your view now you will receive the error 'Table could not be found. Table with name ORDER_CEL_TASK cannot be found.' Therefore, continue with step 4 to resolve this issue.

  4. Enter Knowledge Model Key: To ensure correct mapping of task augmentation for inefficiencies, the knowledge model key must be maintained in the knowledge model. Copy the knowledge model key and paste it into the VARIABLE_KNOWLEDGE_MODEL_KEY.

  5. Publish the App: You can now publish the app which triggers the creation of inefficiency tasks and enables access for users in Celonis Apps.

  6. After the first adjustments, it is still possible that there are some errors shown. Therefore, it is necessary to validate certain variables and KPIs. Please continue with the Configuration and Validation this should resolve all errors. For further explanations of the Knowledge Model and Views, and how to customize certain parts, please review the separate sections.

The validation of certain variables in the Knowledge Model is obligatory to ensure correct mapping and calculation of dates and inefficiencies.

Filter Variables

Variable ID

Default Value

Description

VARIABLE_OPEN_ORDER_ITEM

((PU_LAST(VBAP,VBUP.GBSTA) NOT IN ( 'C') 
    AND (VBAP.ABGRU IS NULL OR
    RTRIM(LTRIM(VBAP.ABGRU)) = '' ))
OR (PROCESS ON "_CEL_O2C_ACTIVITIES"."ACTIVITY_EN" NOT EQUALS 
    ('${VARIABLE_ACTIVITY_CREATE_INVOICE}',
     '${VARIABLE_ACTIVITY_RECORD_GOODS_ISSUE}')
    AND PU_LAST(VBAP,VBUP.GBSTA) = 'C' 
    AND (VBAP.ABGRU IS NULL 
         OR RTRIM(LTRIM(VBAP.ABGRU)) = '' )))

Open order item filter used globally in the app to only show relevant order items.

This variable is used in FILTER_OPEN_ORDER_ITEM. There it is also possible to adjust the sales document type (VBTYP) filtering. By default, this is set to the sales document type 'C'.

To include other SD document categories like quotations (B), Orders w/o charge/Free of charge orders (I), and Scheduling agreements (E) you have to adjust this filter.

VARIABLE_AUTO_TYPES

"'B','S'"

SAP user types that are considered to be automated and not relevant for manual touches

Activity Variables

Whenever an activity variable is used, the surrounding formula includes the outer quotation marks. Therefore, you must not add them at the start or end, but between two activities for the same variable (e.g. VARIABLE_ACTIVITY_SET_DELIVERY_BLOCK )

Variable ID

Default Value

Description

VARIABLE_ACTIVITY_CHANGE_CONFIRMED_DELIVERY_DATE

Change Confirmed Delivery Date

Inefficiency indicator and used in task attributes

VARIABLE_ACTIVITY_RECORD_GOODS_ISSUE

Record Goods Issue

Inefficiency indicator and condition for other formulas

VARIABLE_ACTIVITY_CREATE_DELIVERY

Create Delivery

Inefficiency indicator

VARIABLE_ACTIVITY_CREATE_INVOICE

Create Invoice

Inefficiency indicator and open order item filter

VARIABLE_ACTIVITY_SET_DELIVERY_BLOCK

Set Delivery Block','Set Initial Delivery Block

Task attributes

VARIABLE_ACTIVITY_CHANGE_DELIVERY_BLOCK

Change Delivery Block

Task attributes

VARIABLE_ACTIVITY_SET_BILLING_BLOCK

Set Billing Block','Set Initial Billing Block

Task attributes

VARIABLE_ACTIVITY_CHANGE_BILLING_BLOCK

Change Billing Block

Task attributes

VARIABLE_ACTIVITY_SET_CREDIT_BLOCK

Set Credit Hold','Set Initial Credit Block

Task attributes

Date Variables

VARIABLE_DATE_DUE_DATE_TEXT

CASE WHEN 1=1 THEN 'Next Material Availability Date' ELSE 'Next Material Availability Date' END

Stores title for the defined delivery date. This is used in the app to make the currently defined due-date visible to the business users. Please adjust this if you customize the delivery date.

MBDAT = Material Availability Date

VARIABLE_DATE_DELIVERY_DATE

PU_MIN(VBAP, VBEP.MBDAT ,"VBEP"."BMENG">0 AND (VBAP.ABGRU IS NULL OR RTRIM(LTRIM(VBAP.ABGRU)) = ''))

There are different options to use for the desired delivery/due date. Please adjust this according to business definitions.

Examples are: Transportation Planning Date (TDDAT) or Goods Issue Date (WADAT)

  1. Identify if any errors are generated for:

    • Components

    • Fields in tables

    • KPIs

    • Attributes.

  2. Identify if any implausibilities are generated such as values, KPIs or execution gaps not making sense.

  3. Resolve any errors.

  4. Resolve any implausibilities.

The actions used in this section are predefined and included with the Order Management Execution App. To get started with extending these or building custom actions, see:

Validation - Update Order Status

 
  1. Select an order in the table.

  2. Click Update Order Status.

  3. Add a custom comment or note in the Order Status field.

  4. Click Execute.

  5. Check the comment displays for the order in the Order Status column.

Validation - Create Task

 
  1. Select an order in the table.

  2. Click Create New Task To User.

  3. Add your colleague's email address in the Assignee field.

  4. Click Execute.

  5. Check the newly-created task displays when clicking on the KPI tile "Orders with Tasks".

Validation - Send Email

 
  1. Select an order with an open task.

  2. Click Send Email.

  3. Check if the pre-populated email opens in your mail client.

After finishing the basic validation, you may have found some views, filters or KPIs that do not completely match your business needs. All parts of the App can be fully customized but you should avoid customizations to ensure:

  • Simple maintenance

  • Easier updates of future versions

  • Increased stability of future versions

If you still want to customize your App, use these tutorials which will show you, for example, how to overwrite the base within your extension:

Additionally, we recommend doing the technical enablement that guides through some customization examples.

Notice

If you have any questions, feedback or suggestions, get in touch with Celonis support.