Subscribe

UiPath Process Mining

The UiPath Process Mining Guide

SAP Input

Suggest Edits

Introduction

The input tables are the tables from the SAP database which are used as the input tables for the SAP Connector. These tables are loaded either directly from the SAP database using the SAP or ODBC connection string type or with .csv files uploaded to the UiPath Process Mining server using the Files connection string type.

Input Table types

There are two types of input tables:

  • Transactional data is data relating to the day-to-day transactions in the process.
  • Transactional data is used to create the event log, including cases, events, and attributes.
  • Most of the transactional data is required to get a complete event log.

  • Master data is data that remains unchanged over a period of time.
  • Master data contains characteristics of an object, such as for example the name of a company.
  • Without master data, the event log would only contain, for example, the attribute company code and not the corresponding company name.
  • Master data is optional to get more understandable case and event attributes.

    • Data restriction

    Fields used in Process Mining

    For most of the input tables, only a subset of the available fields is used as datasource attributes in Process Mining.
    When loading data directly from the SAP database, a query is used to load only the fields that are used in Process Mining. When loading data via .csv files, you must make sure that all fields that are used in Process Mining are available in the .csv files.

    📘

    Note

    When loading data via .csv files, it is strongly recommended that you only extract the fields that are required in Process Mining. Loading data that is not used in Process Mining will slow down the data load.

    Filtering

    For some of the input tables, only a subset of the available records is used for Process Mining.
    When loading data directly from the SAP database, a filter is applied to load only the records that are used in Process Mining. When loading data via .csv files, it is advised to apply the filtering on the input tables, to limit the size of the input .csv files. If this filtering is not applied at the moment of the data extraction, the required filtering will be applied in the connector in the first joins where the input tables are used.

    📘

    Note

    If this filtering is not applied at the moment of the data extraction, the required filtering will be applied in the SAP Connector in the first joins where the input tables are used.

    Trim input

    By default, input trimming is enabled for all attributes in all document tables and master data tables to avoid arbitrarily or unintended different events. This means that any leading or trailing blank spaces will be removed when the data is loaded. If needed you can disable the input trimming for individual datasource attributes.

    Follow these steps to disable the input trimming for a datasource attribute.

    Step

    Action

    1

    Open the SAP Connector in your development environment.

    2

    Go to the Data tab and locate the 1. Input section.

    3

    Click on the input table that contains the attribute for which you want to disable the input trimming.

    4

    In the table items list on the right, double click on the appropriate datasource attribute.

    5

    In the Edit Datasource Attribute dialog disable the Trim input check box in the Parse format panel.

    See illustration below for an example.

    Updated 11 days ago

    SAP Input

    Suggested Edits are limited on API Reference Pages

    You can only suggest edits to Markdown body content, but not to the API spec.