process-mining
2021.10
true
Process Mining user guide
- Release notes
- Getting started
- Installation
- Configuration
- Integrations
- Authentication
- Working with Apps and Discovery Accelerators
- AppOne menus and dashboards
- AppOne setup
- Input tables of AppOne
- TemplateOne 1.0.0 menus and dashboards
- TemplateOne 1.0.0 setup
- TemplateOne menus and dashboards
- TemplateOne 2021.4.0 setup
- Purchase to Pay Discovery Accelerator menus and dashboards
- Purchase to Pay Discovery Accelerator Setup
- Order to Cash Discovery Accelerator menus and dashboards
- Order to Cash Discovery Accelerator Setup
- Basic Connector for AppOne
- SAP Connectors
- Introduction to SAP Connector
- SAP input
- Checking the data in the SAP Connector
- Adding process specific tags to the SAP Connector for AppOne
- Adding process specific Due dates to the SAP Connector for AppOne
- Adding automation estimates to the SAP Connector for AppOne
- Adding attributes to the SAP Connector for AppOne
- Adding activities to the SAP Connector for AppOne
- Adding entities to the SAP Connector for AppOne
- SAP Order to Cash Connector for AppOne
- SAP Purchase to Pay Connector for AppOne
- SAP Connector for Purchase to Pay Discovery Accelerator
- SAP Connector for Order-to-Cash Discovery Accelerator
- Superadmin
- Dashboards and charts
- Tables and table items
- Application integrity
- How to ....
- Working with SQL connectors
- Introduction to SQL connectors
- Setting up a SQL connector
- CData Sync extractions
- Running a SQL connector
- Editing transformations
- Releasing a SQL Connector
- Scheduling data extraction
- Structure of transformations
- Using SQL connectors for released apps
- Generating a cache with scripts
- Setting up a local test environment
- Separate development and production environments
- Useful resources
Input tables of AppOne in standalone Process Mining and their relationship to the output tables produced by the Basic Connector.
Introduction
This pages gives an overview of the input tables of AppOne.
Note:
The output tables of the Basic Connector are the same as the input tables of AppOne.
Cases_base
| Name | Data type | Mandatory Y/N | Description |
|---|---|---|---|
| Case ID | Text | Y | A unique internal identifier of the case. |
| Amount | Double | N | A numeric value (Liters, Euro’s, Weight, etc.). |
| Amount group | Text | N | Group to which the amounts belong (High, Med, Low). |
| Case | Text | N | While Case ID is the case number, Case can designate a more user-friendly name of a case. |
| Case department | Text | N | The department of a case. |
| Case owner | Text | N | The owner of a case (User name, ID, department). |
| Case type | Text | N | Categorization of a case (Simple case, Complex Case, Case department). |
| Customer | Text | N | Descriptive field about a case customer (Customer, Brand, Relationship nr, company). |
| Customer type | Text | N | Group of customers. |
| Supplier | Text | N | Descriptive field about a supplier (Company, Brand, Relation). |
| Supplier type | Text | N | Group of suppliers. |
| Variant type | Text | N | Group of variants. |
| Case URL | Text | N | URL where more info about each case can be found. |
Generic items
| Name | Data type | Mandatory Y/N |
|---|---|---|
| Generic_case_1 | Text | N |
| Generic_case_2 | Text | N |
| Generic_case_3 | Text | N |
| Generic_case_4 | Text | N |
| Generic_case_5 | Text | N |
| Generic_case_6 | Text | N |
| Generic_case_6 | Text | N |
| Generic_case_7 | Text | N |
| Generic_case_8 | Text | N |
| Generic_case_9 | Text | N |
| Generic_case_10 | Text | N |
Events_base
| Name | Data type | Mandatory Y/N | Description |
|---|---|---|---|
| Activity | Text | Y | The events in a case (Open, Close, Screen X, Document created, etc.) |
| Case ID | Text | Y | Reference to the unique Case ID in Cases_base. |
| Event end | Datetime | Y | Format: YYYY-M-D h [.zzz] |
| Activity order | Integer | N | If activities take place on the same time (in parallel), you can define their order here. |
| Activity type | Text | N | Grouping of activities (Finance steps, Payments, etc.). |
| Activity type order | Integer | N | Order of activity type in the legend. |
| Country | Text | N | Country where the event(activity) took place. |
| Event cost | Double | N | Cost involved in the execution of the event. For example, employee wages. |
| Event processing time | Duration | N | Time that is actually worked on the event without taking into account any waiting time. |
| Event detail | Text | N | Information related to the event. |
| Event ID | Text | N | Unique identifier of the event. |
| Event start | Datetime | N | Format: YYYY-M-D h [.zzz] |
| Event URL | Text | N | URL where more info about each event can be found. |
| Is automated | Boolean | N | Define if the event is automated or not. |
| Is close activity | Boolean | N | Define if this is an (expected) end/close activity to define the end of a process. |
| Is open activity | Boolean | N | Define if this is an (expected) start/open activity to define the start of a process. |
| Team | Text | N | Team which executed the activity. |
| User | Text | N | User which executed the activity. |
Generic items
| Name | Data type | Mandatory Y/N |
|---|---|---|
| Generic_event_1 | Text | N |
| Generic_event_2 | Text | N |
| Generic_event_3 | Text | N |
| Generic_event_4 | Text | N |
| Generic_event_5 | Text | N |
| Generic_event_6 | Text | N |
| Generic_event_6 | Text | N |
| Generic_event_7 | Text | N |
| Generic_event_8 | Text | N |
| Generic_event_9 | Text | N |
| Generic_event_10 | Text | N |
Tags_base
| Name | Data type | Mandatory Y/N | Description |
|---|---|---|---|
| Case ID | Text | Y | Reference to the unique Case ID in Cases_base. |
| Comment | Text | N | Description of the tag. |
| Tag | Text | N | Name of the tag. |
| Tag score | Text | N | A tag score. |
| Tag type | Text | N | Tag type (Rework, Inefficiency, Violation, etc). |
Due_dates_base
| Name | Data type | Mandatory Y/N | Description |
|---|---|---|---|
| Actual date | Datetime | Y | Format: YYYY-M-D h [.zzz] |
| Due date | Text | Y | Name of the Due date. |
| Event ID | Text | Y | Reference to the unique Event ID in Events_base. |
| Expected date | Datetime | Y | Format: YYYY-M-D h [.zzz] |
| Due date amount | Currency | N | Amount related to the Due date, often this will be a penalty or a discount. |
| Time bin | Text | N | Description of the bin depending if the activity took place on time or not, e.g. “More than two weeks late”, “One week ahead”. |
Reference_models_base
| Name | Data type | Mandatory Y/N | Description |
|---|---|---|---|
| Activity | Text | Y | The events of a case. |
| Reference model | Text | Y | Name of the Reference model. |
| Trace ID | Text | Y | Numeric value to indicate the order of the activities. |
Global_settings
| Name | Data type | Mandatory Y/N | Description |
|---|---|---|---|
| Default period | Text | N | Default period for the period filter. If not set, the default will be All. |
| Dashboard item is expanded by default | Text | N | The History and/or Distribution charts are collapsed by default. |
| Welcome screen | Text | N | HTML text to be used for the welcome dashboard. |