- 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
- App templates
- Additional resources
- Out-of-the-box Tags and Due dates
- Editing data transformations in a local environment
- Setting up a local test environment
- Designing an event log
- Extending the SAP Ariba extraction tool
- Performance characteristics
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.
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 |
Purchase_requisitions_base_raw
table.
Name |
Data type |
Mandatory Y/N |
Description |
---|---|---|---|
|
text |
Y |
The unique identifier of the purchase requisition. |
|
text |
N | |
|
text |
N | The requested material. |
Material_group |
text |
N | The categorization of the requested material. |
Purchase_requisition |
text |
N | A user-friendly name to identify the purchase requisition. |
|
text |
N |
The status of the purchase requisition in the process. For example, ‘open’, ‘closed’, ‘pending’, ‘approved’, etc. |
|
text |
N |
The categorization of purchase requisitions. |
|
text |
N | |
|
text |
N |
The person who requested the purchase requisition. |
|
double |
N |
A monetary value related to the purchase requisition. |
Purchase_orders_base_raw
table.
Name |
Data type |
Mandatory Y/N |
Description |
---|---|---|---|
|
text |
Y |
The unique identifier of the purchase order. |
Company |
text |
N | The company for which the purchase order is created. |
|
date |
N |
The date on which the purchase order is created. |
One_time_supplier |
boolean |
N | An indicator if the supplier is a one time supplier. |
Purchase_order |
text |
N | A user-friendly name to identify the purchase order
. |
|
text |
N |
The status of the purchase order in the process. For example, ‘open’, ‘closed’, ‘pending’, ‘approved’, etc. |
|
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. |
|
text |
N |
The country associated to the supplier. |
|
text |
N |
The region associated to the supplier. |
Purchase_order_items_base_raw
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
|
text |
Y |
The unique identifier of the purchase order item |
|
text |
N |
The unique identifier of the purchase order |
|
text |
N* |
The unique identifier of the purchase requisition. |
|
text |
N | |
|
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 storage location associated to the purchase order item. |
|
text |
N | The quantity and the unit of measurement ordered. |
|
double |
N |
The monetary value related to the purchase order item. |
- If you want to include purchase requisition events in the process graphs, the
Purchase_requisition_ID
field is mandatory.
Goods_receipt_base_raw
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. |
|
text |
N | |
|
boolean |
N | |
|
text |
N | |
|
text |
N | |
|
text |
N | |
|
text |
N | |
|
text |
N | |
|
double |
N |
- If you want to include goods receipt events in the process graphs, the
Purchase_order_item_ID
field is mandatory.
Invoices_base_raw
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
|
text |
Y |
The unique identifier of the invoice. |
|
text |
N | |
|
date |
N | |
|
text |
N | |
|
double |
N | |
|
double |
N | |
|
double |
N | |
|
integer |
N | |
|
integer |
N | |
|
text |
N | |
|
date |
N | |
|
text |
N | |
|
integer |
N | Net payment period of the invoice in days. |
|
text |
N | |
|
text |
N | |
|
date |
N |
- If you want to include accounts payable events in the process graphs, the
Invoice_ID
field is mandatory.
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 invoice. |
|
text |
N* |
The unique identifier of the purchase order item. |
|
text |
N | |
|
text |
N | |
|
text |
N | |
|
text |
N | |
|
text |
N | |
|
double |
N |
- If you want to include events related to accounts payable in the process graphs, the
Invoice_ID
andPurchase_ order_item_ID
fields are 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 as known in the accounting system. |
|
text |
N | |
|
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 | |
|
date |
N | |
|
text |
N | |
|
double |
N |
- If you want to include events related to accounts payable in the process graphs, both the
Accounting_document_ID
andInvoice_ID
fields are 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 payment events 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. |
|
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. |
| boolean |
N | An 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. |
User | text | N | The user who executed the event. |
User_function | text | N | The function associated with the user. |
User_type | text | N | The categorization of the user. |
|
double |
N |
The costs for executing the event. |
Event_start *
|
datetime |
N |
The timestamp associated with the start of executing the event |
-
If both
Event_start
andEvent_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 onlyEvent_end
end is defined, the throughput time will be calculated as the difference between previousEvent_end
and theEvent_end
.Event_start
is only taken into account if every record in the dataset contains a not-null value.Important:If you want to useEvent_cost
and/orEvent_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. See Loading data using DataBridgeAgent.Make sure you add the connector to DataBridgeAgent. See Adding a custom connector to DataBridgeAgent.
Note:It is expected that for each record exactly one of theID
fields is filled in, which is the one of the entity on which the event takes place. The otherID
fields may be empty.Next to the standard mandatory fields (Activity
andEvent_end
), oneEntity_ID
is mandatory. This field depends on the entity the event is part of.