The SAP Purchase-to-Pay Connector for AppOne needs UiPath Process Mining version 2021.4 or higher.
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.
The tables in the SAP Purchase-to-Pay Connector for AppOne are ordered in a structured way and consists of the following groups:
- Event log creation
- Business data input
Below is a description of the table groups that contain specific tables for the SAP Purchase-to-Pay Connector.
|1. Input||Tables that contain SAP input data.|
|2. Entities||Tables 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 creation||Tables 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
|4. Business data input||Contains 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.
|5. Preprocessing||Tables for adding business logic.|
|6. Output||Tables for creating a dataset that can be used in AppOne.|
Updated 2 months ago