- 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
Purchase-to-Pay input fields
This section contains an overview of the fields for each of the input tables of Purchase-to-Pay. 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 Purchase-to-Pay 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 |
Table |
Mandatory Y/N |
---|---|---|
Purchase requisition |
|
N |
Purchase order |
|
Y |
Purchase order item |
|
Y |
Goods receipt |
|
N |
Invoice |
|
N |
Invoice item |
|
N |
Accounting |
|
N |
Payment |
|
N |
The illustration below displays the relations between entities of Purchase-to-Pay.
If you are extracting the data using CData Sync, `_raw` has to be added to the table names listed below, e.g. `Purchase_orders_base_raw`.
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 |
Purchase_requisitions_base
table.
Name |
Data type |
Mandatory Y/N |
Description |
---|---|---|---|
|
text |
Y |
The unique identifier of the purchase requisition. |
|
text |
N |
The status of the purchase requisition in the process. For example, ‘open’, ‘closed’, ‘pending’, ‘approved’, etc. |
|
text |
N |
The requested material. |
|
text |
N |
The categorization of the requested material. |
|
text |
N |
A user-friendly name to identify the purchase requisition. |
|
text |
N |
The categorization of purchase requisitions. |
|
text |
N |
The person who requested the purchase requisition |
|
double |
N |
A monetary value related to the purchase requisition |
Purchase_orders_base
table.
Name |
Data type |
Mandatory Y/N |
Description |
---|---|---|---|
|
text |
Y |
The unique identifier of the purchase order. |
|
date |
Y |
The date on which the purchase order is created. |
|
text |
N |
The status of the purchase order in the process. For example, ‘open’, ‘closed’, ‘pending’, ‘approved’, etc. |
|
text |
N |
The company for which the purchase order is created. |
|
text |
N |
A user-friendly name to identify the purchase order. |
|
text |
N |
The person who created the purchase order. |
|
text |
N |
The categorization of purchase orders. |
|
text |
N |
The purchasing group associated with the purchase order. |
|
text |
N |
The purchasing organization associated with the purchase order. |
|
text |
N |
The supplier associated with the purchase order. |
|
boolean |
N |
An indicator if the supplier is a one time supplier. |
|
text |
N |
The country associated to the supplier. |
|
text |
N |
The region associated to the supplier. |
Purchase_order_items_base
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
|
text |
Y |
The unique identifier of the purchase order item |
|
text |
Y |
The unique identifier of the purchase order |
|
text |
N* |
The unique identifier of the purchase requisition. |
|
text |
N |
The business area associated with the purchase order item. |
|
text |
N |
The cost center associated with the purchase order item. |
|
text |
N |
The customer on behalf of whom the purchase order item is created. |
|
text |
N |
The country associated to the customer. |
|
text |
N |
The region associated to the customer. |
|
boolean |
N |
Indicator if all ordered goods are received. |
|
date |
N |
The latest actual delivery date for the purchase order item. |
|
date |
N |
The latest originally confirmed delivery date for the purchase order item. |
|
text |
N |
The ordered materials. |
|
text |
N |
The categorization of the ordered materials. |
|
text |
N |
The plant associated to the purchase order item. |
|
text |
N |
A user-friendly name to identify the purchase order item. |
|
text |
N |
The quantity and the unit of measurement ordered. |
|
text |
N |
The storage location associated to the purchase order item. |
|
double |
N |
The monetary value related to the purchase order item. |
Purchase_requisition_id
field is mandatory.
Goods_receipt_base
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
|
text |
Y |
The unique identifier of the goods receipt. |
|
text |
N* |
The unique identifier of the purchase order item. |
purchase_order_item_id
field is mandatory.
Invoices_base
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
|
text |
Y |
The unique identifier of the invoice. |
|
text |
N* |
The unique identifier of the invoice as known in the accounting system. |
invoice_id
field is mandatory.
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 purchase order item. |
invoice_id
and purchase_ order_item_id
fields are 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 as known in the accounting system. |
accounting_document_id
and invoice_id
fields are 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 purchase requisition. |
|
text |
Y |
The unique identifier of the purchase order. |
|
text |
Y |
The unique identifier of the purchase order item. |
|
text |
Y |
The unique identifier of the goods receipt. |
|
text |
Y |
The unique identifier of the invoice. |
|
text |
Y |
The unique identifier of the invoice item. |
|
text |
Y |
The unique identifier of the accounting document. |
|
text |
Y |
The unique identifier of the payment. |
|
integer |
N |
The number that defines in which order activities are executed in case they have the same Event end. |
|
text |
N |
The department that executed the event. |
|
double |
N |
The costs for executing the event. |
|
text |
N |
Information related to the event. |
event_start *
|
datetime |
N |
The timestamp associated with the start of executing the event |
|
boolean |
N |
An indicator whether the event is manually executed or automated. |
|
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 Purchase-to-Pay, 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 Purchase-to-Pay.
- 10 fields of type text (5 fields for events);
- 10 fields of type double (5 fields 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 fields for events);
-
10 fields of type duration (5 fields for events).
Custom fields have generic names. Below is an overview of the custom fields that can be used in a Purchase-to-Pay process app.
.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.
Name |
Data type |
Mandatory Y/N |
---|---|---|
custom_purchase_order_item_text_{1...10} |
text |
N |
custom_purchase_order_item_number_{1...10} |
double |
N |
custom_purchase_order_item_datetime_{1...5} |
datetime |
N |
custom_purchase_order_item_boolean_{1...10} |
boolean |
N |
custom_purchase_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
- Purchase requisition
- Purchase_requisitions_base table
- Purchase Order
- Purchase_orders_base table
- Purchase_order_items_base table
- Goods_receipt_base
- Invoice
- Invoices_base table
- Invoice_items_base table
- Accounting
- Accounting_documents_base table
- Payment
- Payments_base table
- Events
- Events_base Table
- Custom fields