Skip to main content

Celonis Product Documentation

Prerequisites for the case-centric Shipped Not Invoiced app

Before you set up the case-centric version of the Shipped Not Invoiced app, you’ll need to complete these prerequisite steps:

  1. Install and configure a Data Connection between Celonis and your source system.

    If you’ve already set up a Data Connection to this source system, you can reuse it. If not, you'll need to install the Celonis components in your source system, set up the extractor server, and configure a Data Connection in the Celonis platform. Data Connections has the instructions to do this.

  2. Install and configure the newest version of the Process Connector that the Shipped Not Invoiced app works with.

    This is the one shown on the app’s Celonis Marketplace listing page as the required connector. The Data Model “Order-to-Cash for SAP ECC” that you’ll use with the app comes with the Process Connector. The easiest way to get the connector is through the Process Connector library - Process Connector Installation tells you how to do this.  If you’ve already set up this Process Connector for a different app, you can reuse it.

  3. Load the Data Model “Order-to-Cash for SAP ECC” with your data.

    Required tables and columns lists the tables and columns you’ll need from SAP ECC.

    Important

    The VBAP table, which contains sales order items, must have fewer than 30 million rows for the Shipped Not Invoiced app’s augmentation functionality to work. If yours is larger, see Reducing the VBAP (sales order item) table size for how to work around this.

When the Data Connection and Process Connector are in place and you’ve loaded the Data Model, follow the steps in Installing the case-centric Shipped Not Invoiced app.

If you need to get help with any of the app’s prerequisites or setup steps, Support tells you how.

Required tables and columns

Here’s the reference list of the SAP ECC tables and columns that the Shipped Not Invoiced app needs data from:

Table

Columns

KNA1

FAKSD, KUNNR, MANDT, NAME1, VBUND

VBAK

AUART, AUART_TEXT, BUKRS_TEXT, BUKRS_VF, ERNAM, FAKSK, KUNNR, MANDT, TS_ERDAT, VBELN, VKGRP, VKGRP_TEXT, VKORG, VKORG_TEXT, VKWEG, VTWEG_TEXT, WAERK

VBAP

ABGRU, FAKSP, FKREL, MANDT, MATKL, MATKL_TEXT, MATNR, MATNR_TEXT, NETWR, NETWR_CONVERTED, POSNR, PSTYV, PSTYV_TEXT, TS_ERDAT, VBELN, WAERK, WERKS, WERKS_TEXT, WADAT

Reducing the VBAP (sales order item) table size

If the VBAP table, which contains sales order items, exceeds 30 million rows, you’ll need to reduce its size so that the app can create augmented attributes. The Shipped Not Invoiced app doesn’t need to look at sales document types for which no invoice is expected, so you can safely exclude these.

Here’s how to create and use a reduced VBAP table:

  1. Create a copy of the Data Model for the Shipped Not Invoiced app. Copy the original “Order-to-Cash for SAP ECC” Data Model, but you’ll be replacing the VBAP table with your reduced table.

    Tip

    If you want to reduce the reload time for your Data Model copy for the Shipped Not Invoiced app, you can remove tables that aren’t required for the Shipped Not Invoiced use case.

  2. In the Data Pool that the Shipped Not Invoiced app is using, create a new transformation in a new or existing data job. In the transformation, paste in the following statements to create a reduced version of the VBAP table named O2C_VBAP_SNI_REDUCED, that excludes sales document types for which no invoice is expected.

    -- Option 1 (preferred)
-- O2C_VBAP_SNI_REDUCED is a reduced version of VBAP
-- with only order items for which an invoice is expected
-- to allow for augmentation (requirement < 30M rows in table with aug. attributes)

DROP VIEW IF EXISTS O2C_VBAP_SNI_REDUCED;

CREATE VIEW O2C_VBAP_SNI_REDUCED AS (
  SELECT *
  FROM "O2C_VBAP"
  WHERE (
    EXISTS (SELECT 1
            FROM "O2C_VBAK"
            WHERE 1=1
              AND "O2C_VBAK"."MANDT" = "O2C_VBAP"."MANDT"
              AND "O2C_VBAK"."VBELN" = "O2C_VBAP"."VBELN"
              AND "O2C_VBAK"."AUART" NOT IN ('RE', 'KB'))-- To Do: add here the sales document types for which no invoice is expected
  )
);

  3. In your Data Model copy for the Shipped Not Invoiced app, select the reduced table O2C_VBAP_SNI_REDUCED as VBAP.

    shippednotinvoiced_cc_vbap.png

  4. Load your Data Model copy for the Shipped Not Invoiced app to verify that the number of rows in the VBAP table has been reduced below 30 million.

  5. If the first suggested transformation doesn’t reduce the number of rows in VBAP below 30 million, swap it for the following transformation. This one only includes items that have a goods issue or equivalent activity, such as "Supplier Invoice Receipt" for drop shipments, but don’t have an invoice creation activity. This reduction limits the historical billing performance insights available in the Shipped Not Invoiced app, so you should avoid it if the necessary reduction can be achieved with the first suggested transformation.

    -- Option 2-- O2C_VBAP_SNI_REDUCED is a preliminary reduced version of VBAP with unbilled order items to allow for
-- augmentation (requirement < 30M rows in table with aug. attributes)

DROP VIEW IF EXISTS O2C_VBAP_SNI_REDUCED;
CREATE VIEW O2C_VBAP_SNI_REDUCED AS (
   SELECT *
   FROM "O2C_VBAP"
   WHERE (
    EXISTS (SELECT 1
         FROM "_CEL_O2C_ACTIVITIES"
         WHERE 1=1
           AND "O2C_VBAP"."MANDT" = "_CEL_O2C_ACTIVITIES"."MANDT"
           AND "O2C_VBAP"."VBELN" = "_CEL_O2C_ACTIVITIES"."VBELN"
           AND "O2C_VBAP"."POSNR" = "_CEL_O2C_ACTIVITIES"."POSNR"
           AND "_CEL_O2C_ACTIVITIES"."ACTIVITY_EN" = 'Record Goods Issue')
    AND NOT EXISTS (SELECT 1
         FROM "_CEL_O2C_ACTIVITIES"
         WHERE 1=1
           AND "O2C_VBAP"."MANDT" = "_CEL_O2C_ACTIVITIES"."MANDT"
           AND "O2C_VBAP"."VBELN" = "_CEL_O2C_ACTIVITIES"."VBELN"
           AND "O2C_VBAP"."POSNR" = "_CEL_O2C_ACTIVITIES"."POSNR"
           AND "_CEL_O2C_ACTIVITIES"."ACTIVITY_EN" = 'Create Invoice')
   )
);

  6. Load your Data Model copy for the Shipped Not Invoiced app to verify that the number of rows in the VBAP table has now been reduced below 30 million.