- Release notes
- Before you begin
- Getting started
- Managing access
- Working with process apps
- Creating process apps
- Loading data
- Customizing process apps
- Data transformations
- TemplateOne app template
- Purchase to Pay app template
- Order to Cash app template
- Basic troubleshooting guide
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.
When a table or field is not mandatory, it should be part of the input. Optional tables may contain no records and optional fields may contain empty values.
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.
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.
|
double |
Decimal separator:
. (dot)
Thousand separator: none |
integer |
Thousand separator: none |
text |
N/A |
Sales_orders_base
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 |
The sales order type of the sales order. |
|
text |
N |
The sales organization of the sales order. |
Sales_order_items_base
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
|
text |
Y |
The unique identifier of the sales order item. |
|
text |
Y |
The unique identifier of the sales order. |
|
date |
Y |
The date on which the sales order item is created. |
|
text |
N |
The category of sales order item. |
|
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 |
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
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
|
text |
Y |
The unique identifier of the delivery. |
Delivery_items_base
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. |
|
boolean |
N |
Indicates if the sales order item is released to invoicing. |
delivery_id
and sales_order_item_id
fields are mandatory.
Invoices_base
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
|
text |
Y |
The unique identifier of the invoice. |
Invoice_items_base
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
|
text |
Y |
The unique identifier of the invoice item. |
|
text |
N* |
The unique identifier of the invoice. |
|
text |
N* |
The unique identifier of the delivery item. |
|
boolean |
N |
Indicates if the invoice item is cancelled. |
|
boolean |
N |
Indicates if the invoice item is billable. |
invoice_id
and delivery_item_id
fields are mandatory.
Invoice_cancellations_base
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. |
invoice_id
field is mandatory.
Accounting_documents_base
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
|
text |
Y |
The unique identifier of the accounting document. |
|
text |
N* |
The unique identifier of the invoice. |
|
boolean |
N |
Indicates if the accounting document is cancelled. |
|
boolean |
N |
Indicates if the accounting document has been handled and is closed. |
invoice_id
field is mandatory.
Payments_base
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
|
text |
Y |
The unique identifier of the payment. |
|
text |
N* |
The unique identifier of the accounting document. |
accounting_document_id
field is mandatory.
Events_base
table contains all sub-event logs for all entities. Below is an overview of the fields of the Events_base
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
|
text |
Y |
The name of the event. This describes the step in the process. |
|
datetime |
Y |
The timestamp associated with the end of executing the event |
|
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. |
|
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 |
|
double |
N |
The costs of executing the event. |
|
text |
N |
Information related to the event. |
event_start *
|
datetime |
N | |
|
text |
N |
The user who executed the event. |
|
text |
N |
The function associated with the user. |
|
Text |
N |
The categorization of the user. |
event_start
and event_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
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 Purchase-to-Pay 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.
Additionally, custom case and event fields for both case and event properties are available for Order-to-Cash.
- 10 fields of type text (5 for events);
- 10 fields of type double (5 for events);
- 5 fields of type datetime; (These must be of the format yyyy-mm-dd hh:mm:ss[.ms], where [.ms] is optional.)
-
10 fields of type boolean (5 for events)
-
10 fields of type duration (5 for events).
.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.
Custom fields have generic names. Below is an overview of the custom fields that can be used in a Order-to-Cash process app.
Name |
Data type |
Mandatory Y/N |
---|---|---|
custom_sales_order_item_text_{1...10} |
text |
N |
custom_sales_order_item_number_{1...10} |
double |
N |
custom_sales_order_item_datetime_{1...5} |
datetime |
N |
custom_sales_order_item_boolean_{1...10} |
boolean |
N |
custom_sales_order_item_duration_{1...10 |
integer |
N |
custom_event_text_{1...5} |
text |
N |
custom_event_number_{1...5} |
double |
N |
custom_event_datetime_{1...5} |
datetime |
N |
custom_event_boolean_{1...5} |
boolean |
N |
custom_event_duration_{1...5} |
integer |
N |
When you use a custom field, you should rename the field in using Data manager to a name that matches the value. See Fields.
Custom fields that are empty in your dataset, are not displayed in Process Mining.
- Introduction
- Field types
- Sales order
- Sales_orders_base table
- Sales_order_items_base table
- Delivery
- Deliveries_base table
- Delivery_items_base table
- Invoice
- Invoices_base table
- Invoice_items_base table
- Invoice_cancellations_base table
- Accounting
- Accounting_documents_base table
- Payment
- Payments_base table
- Events
- Events_base table
- Custom fields