Subscribe

UiPath Process Mining

The UiPath Process Mining Guide

Introduction to SAP Purchase-to-Pay Connector for AppOne

📘

Note:

The SAP Purchase-to-Pay Connector for AppOne needs UiPath Process Mining version 2021.4 or higher.

Introduction

UiPath Process Mining uses event logs as input data. SAP does not output one event log which can be used in UiPath Process Mining, rather it stores data about the different artifacts and their activities in several tables. These SAP tables must be combined and transformed to an event log. The main purpose of the SAP Purchase-to-Pay connector is to convert SAP data to an event log that can be used by UiPath Process Mining.

Table structure of the SAP Purchase-to-Pay Connector for AppOne

The tables in the SAP Purchase-to-Pay Connector for AppOne are ordered in a structured way and consists of the following groups:

  1. Input
  2. Entities
  3. Event log creation
  4. Business data input
  5. Preprocessing
  6. Output

Below is a description of the table groups that contain specific tables for the SAP Purchase-to-Pay Connector.

Table groupDescription
1. InputTables that contain SAP input data.
2. EntitiesTables that represent entities in the Purchase-to-Pay process, for example, Purchase order. These tables are often created by combining header and item data.
3. Event log creationTables for event generation.
- Entity relations tables define how the entity documents in the Purchase-to-Pay process are linked together.
- Events tables define the events based on Activity and Event end attributes.
4. Business data inputContains the input tables for Tags, Due dates and Reference models.

After the event log is created, the Business data input tables are ready. From this part on the data creation process is similar to the Basic Connector.

Table groupDescription
5. PreprocessingTables for adding business logic.
6. OutputTables for creating a dataset that can be used in AppOne.

Updated 2 months ago

Introduction to SAP Purchase-to-Pay Connector for AppOne


Suggested Edits are limited on API Reference Pages

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