- Release notes
- Before you begin
- Getting started
- Integrations
- Working with process apps
- Working with dashboards and charts
- Working with process graphs
- Working with Discover process models and Import BPMN models
- Showing or hiding the menu
- Context information
- Export
- Filters
- Sending automation ideas to UiPath® Automation Hub
- Tags
- Due dates
- Compare
- Conformance checking
- Root cause analysis
- Simulating automation potential
- Triggering an automation from a process app
- Viewing Process data
- Creating apps
- Loading data
- Customizing process apps
- Publishing Dashboards
- App templates
- Additional resources
Process Mining
Out-of-the-box Tags and Due dates
This page contains an overview of the Tags that are available for Order-to-Cash related app templates.
The Sales order item with late payments tag identifies Sales order items that have an invoice linked to them which in turn was paid late.
Actual date or Expected date cannot be determined, the Expected payment due date will not show up in the Due dates dashboard.
Payments.Payment_is_complete = true) are taken into account.
The Sales order item with late payments tag is not available for the SAP Order-to-Cash app template.
This page contains an overview of the Due dates that are available for Purchase-to-Pay related app templates.
Actual date is based on moment of the Create payment or Create outgoing payment event. The Expected date for the due date is defined based on the Invoices_base.Baseline_date with the Invoices_base.Net_payment_period added to it.
Actual date or Expected date cannot be determined, the Expected payment due date will not show up in the Due dates dashboard.
Payments.Payment_is_complete = true) are taken into account.
The Expected payment due date is not available for the SAP Purchase-to-Pay app template.
The PR to PO throughput time due date allows you to analyze the time it takes to between creating a purchase requisition and the creation of the purchase order item. Reducing this throughput time can lead to improved efficiency in the Purchase-to-Pay process.
Actual date is the Create purchase order item event. The Expected date is based on the variation for the throughput times between the Create purchase requisition event and the Create purchase order item event. When the throughput time of the Purchase requisition creation to the Purchase Order creation is more than a standard
deviation of all known throughput times between PR creation and PO creation different from the expected throughput time, the
case is considered overdue.
This means that the Expected date is derived using the following computations:
-
The expected throughput time is the average of all throughput times PR creation to PO creation.
-
The standard deviation is computed based on these throughput times.
-
Expected datefor the due date is the PR creation time + average throughput time + standard deviation.
This page contains an overview of the Due dates that are available for Order-to-Cash related app templates.
Actual date is based on moment of the Create incoming payment event. The Expected date for the due date is defined based on the Invoices_base.Baseline_date with the Invoices_base.Net_payment_period added to it.
Actual date or Expected date cannot be determined, the Expected payment due date will not show up in the Due dates dashboard.
Payments.Payment_is_complete = true) are taken into account.
The Expected payment due date is not available for the SAP Order-to-Cash app template.
The Expected delivery due date allows you to analyze whether deliveries are done in time or not.
Actual date is based on the Deliveries.Delivery_date and the expected date is the Deliveries.Planned_delivery_date.
Actual date or Expected date cannot be determined, the Expected delivery due date will not show up in the Due dates dashboard.
The Expected delivery due date is not available for the SAP Order-to-Cash app template.
