- 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
- Starting a Task Mining project from Process Mining
- Triggering an automation from a process app
- Viewing Process data
- Creating apps
- Loading data
- Customizing process apps
- Publishing process apps
- App templates
- Additional resources
Order-to-Cash input fields
This section contains an overview of the fields for each of the input tables of Order-to-Cash. For each entity the fields are listed. For each field, the name and a data type are displayed. Apart from that, it is indicated whether the field is mandatory if the entity is included in the Order-to-Cash process.
Optional tables should be part of the input, but may contain no records.
NULL
values.
Entity |
Tables |
Mandatory Y/N |
---|---|---|
Sales order |
|
Y |
Deliveries |
|
N |
Invoice |
|
N |
Accounting |
|
N |
Payment |
|
N |
The illustration below displays the relations between entities of Order-to-Cash.
Table names and field names are case-sensitive. Always make sure that the field names (column headers) in your dataset match the field names (in English) in the tables below and that the file names match the table names.
Below is an overview of the different field types and their default format settings.
Field type |
Format |
---|---|
boolean |
true , false , 1 , 0 |
date |
|
datetime |
yyyy-mm-dd hh:mm:ss[.ms] , where [.ms] is optional.
Refer to the official Microsoft documentation if you want to change the date format. |
double |
Decimal separator:
. (dot)
Thousand separator: none |
integer |
Thousand separator: none |
text |
N/A |
Sales_orders_base_raw
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
|
text |
Y |
The unique identifier of the sales order. |
|
text |
N |
The company for which the sales order is created. |
|
text |
N |
The customer for whom the sales order is created. |
|
text |
N |
The country associated to the customer. |
|
text |
N |
The region associated to the customer. |
|
text |
N |
The distribution channel associated to the sales order. |
|
text |
N |
The division associated to the sales order. |
|
date |
N |
The customer’s requested delivery date for the sales order. |
|
text |
N |
The sales group associated to the sales order. |
|
text |
N |
The sales office associated to the sales order. |
|
text |
N | |
|
text |
N |
The sales order type of the sales order. |
|
text |
N |
The sales organization of the sales order. |
Sales_order_items_base_raw
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
|
text |
Y |
The unique identifier of the sales order item. |
|
text |
N |
The unique identifier of the sales order. |
Category | text |
N | The category of sales order item. |
|
date |
N |
The date on which the sales order item is created. |
|
text |
N |
The incoterms associated to the sales order item. |
|
date |
N |
The latest expected delivery date of (parts of) the sales order item. |
|
text |
N |
The material sold. |
|
text |
N |
The categorization of the material sold. |
|
text |
N |
The terms of payment associated to the sales order item. |
|
text |
N |
The plant associated to the sales order item. |
|
text |
N |
The profit center associated to the sales order item. |
|
text |
N |
The quantity and unit of measurement sold. |
|
text |
N |
A user-friendly name to identify the sales order item |
|
text |
N |
|
|
text |
N |
The country where the goods are delivered associated to the sales order item. |
|
text |
N |
Storage location associated to the sales order item. |
|
double |
N |
A monetary value related to the sales order item. |
Deliveries_base_raw
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
|
text |
Y |
The unique identifier of the delivery. |
|
text |
N | |
|
text |
N | |
|
date |
N | |
|
text |
N | |
|
text |
N | |
|
date |
N | |
|
text |
N | |
|
text |
N | |
|
text |
N | |
|
text |
N |
Delivery_items_base_raw
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
|
text |
Y |
The unique identifier of the delivery item. |
|
text |
N* |
The unique identifier of the delivery. |
|
text |
N* |
The unique identifier of the sales order item. |
|
text |
N | |
|
text |
N | |
|
boolean |
N |
Indicates if the sales order item is released to invoicing. |
|
text |
N | |
|
text |
N | |
|
text |
N | |
|
text |
N | |
|
text |
N | |
|
double |
N |
- If you want to include events related to other entities than the sales order in the process graphs, the
Delivery_ID
andSales_order_item_ID
fields are mandatory.
Invoices_base_raw
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
|
text |
Y |
The unique identifier of the invoice. |
|
date |
N | |
|
text |
N | |
|
double |
N | |
|
double |
N | |
|
double |
N | |
|
integer |
N | |
|
integer |
N | |
|
text |
N | |
|
text |
N | |
|
text |
N | |
|
date |
N | |
|
text |
N | |
|
integer |
N | Net payment period of the invoice in days. |
|
text |
N | |
|
text |
N | |
|
date |
N | |
|
text |
N | |
|
text |
N |
Invoice_items_base_raw
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
|
text |
Y |
The unique identifier of the invoice item. |
|
text |
N* | The unique identifier of the delivery item. |
|
text |
N* |
The unique identifier of the invoice. |
|
text |
N | |
|
text |
N | |
|
boolean |
N |
Indicates if the invoice item is cancelled. |
|
boolean |
N |
Indicates if the invoice item is billable. |
|
text |
N | |
|
text |
N | |
|
text |
N | |
|
text |
N | |
|
double |
N |
- If you want to include events related to other entities than the sales order in the process graphs, the
Invoice_ID
andDelivery_item_ID
fields are mandatory.
Invoice_cancellations_base_raw
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
|
text |
Y |
The unique identifier of the invoice cancellation. |
|
text |
N* |
The unique identifier of the invoice that is cancelled. |
|
text |
N | |
|
text |
N | |
|
text |
N | |
|
text |
N | |
|
date |
N | |
|
text |
N | |
|
text |
N | |
|
text |
N |
- If you want to include events related to other entities than the sales order in the process graphs, the
Invoice_ID
field is mandatory.
Accounting_documents_base_raw
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
|
text |
Y |
The unique identifier of the accounting document. |
|
text |
N* |
The unique identifier of the invoice. |
|
text |
N | |
|
boolean |
N |
Indicates if the accounting document is cancelled. |
|
boolean |
N |
Indicates if the accounting document has been handled and is closed. |
|
date |
N | |
|
text |
N | |
|
double |
N | |
|
double |
N | |
|
double |
N | |
|
integer |
N | |
|
integer |
N | |
|
date |
N | |
|
text |
N | |
|
text |
N | |
|
integer |
N | |
|
date |
N | |
|
text |
N | |
|
text |
N | |
|
text |
N | |
|
date |
N | |
|
text |
N | |
|
double |
N |
- If you want to include events related to other entities than the sales order in the process graphs, the
Invoice_ID
field is mandatory.
Payments_base_raw
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
|
text |
Y |
The unique identifier of the payment. |
|
text |
N* |
The unique identifier of the accounting document. |
|
text |
N | |
|
text |
N | |
|
text |
N | |
|
boolean |
N | |
|
boolean |
N | |
|
double |
N |
- If you want to include events related to other entities than the sales order in the process graphs, the
Accounting_document_ID
field is mandatory.
Events_base_raw
table contains all sub-event logs for all entities. Below is an overview of the fields of the Events_base_raw
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
|
text |
Y |
The name of the event. This describes the step in the process. |
|
text |
Y |
The unique identifier of the accounting document. |
|
text |
Y |
The unique identifier of the delivery. |
|
text |
Y |
The unique identifier of the delivery item. |
Event_end | datetime | Y | The timestamp associated with the end of executing the event
. |
|
text |
Y |
The unique identifier of the invoice. |
|
text |
Y |
The unique identifier of the invoice item. |
|
text |
Y |
The unique identifier of the invoice cancellation. |
|
text |
Y |
The unique identifier of the payment. |
|
text |
Y |
The unique identifier of the sales order. |
|
text |
Y |
The unique identifier of the sales order item. |
|
text |
N |
The type of activity that takes place (e.g. change, set/remove block) |
|
integer |
N |
The number that defines in which order activities are executed in case they have the same Event end. |
|
text |
N |
Field describing the reason for the executed activity |
|
boolean |
N |
Indicator whether the event is manually executed or automated. |
|
text |
N |
The department that executed the event |
Event_detail | text |
N | Information related to the event. |
|
text |
N |
The user who executed the event. |
|
text |
N |
The function associated with the user. |
|
Text |
N |
The categorization of the user. |
|
double |
N |
The costs of executing the event. |
Event_start *
| datetime |
N |
The timestamp associated with the start of executing the event. |
Event_processing_time |
integer |
N | The time for executing the event (in milliseconds). |
Event_start and E
vent_end
are defined in your dataset, the duration of the event is known. This will be used to calculate the throughput time of events. If only Event_end
end is defined, the throughput time will be calculated as the difference between previous Event_end
and the Event_end
. Event_start
is only taken into account if every record in the dataset contains a not-null value.
Event_cost
and/or Event_start
in Order-to-Cash, you must add these fields to your .mvp
connector and use DataBridgeAgent to load the data in your Order-to-Cash process app.
Make sure you add the connector to DataBridgeAgent. See Adding a custom connector to DataBridgeAgent.
ID
fields is filled in, which is the one of the entity on which the event takes place. The other ID
fields may be empty.
Activity
and Event_end
), one entity ID
is mandatory. This field depends on the entity the event is part of.