Skip to main content

Order-to-Cash input fields

Introduction

This section contains an overview of the fields for each of the input tables of Order-to-Cash. For each object 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 object is included in the Order-to-Cash process.

note

Optional tables should be part of the input, but may contain no records. When a field is mandatory, it should not contain NULL values.

ObjectTablesMandatory Y/N
Sales orderSales_orders Sales_order_itemsY
DeliveriesDeliveries Delivery_itemsN
InvoiceInvoices Invoice_items Invoide_cancellationsN
AccountingAccounting_documentsN
PaymentPaymentsN
Events*EventY

*) Events is not an object of the Order-to-Cash process, but an events table is mandatory for a correct working of the Order-to-Cash process app.

The following illustration shows the relations between objects of Order-to-Cash.

docs image

important

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 following tables and that the file names match the table names.

Field types

The following table describes the different field types and their default format settings.

Field typeFormat
booleantrue, false, 1, 0
dateyyyy-mm-dd
datetimeyyyy-mm-dd hh:mm:ss[.ms], where [.ms] is optional. Refer to the official Microsoft documentation if you want to change the date format.
doubleDecimal separator: . (dot) Thousand separator: none
integerThousand separator: none
textN/A

Sales order

Sales_orders

The following table describes the fields of the Sales_orders table.

NameTypeMandatory Y/NDescription
Sales_order_IDtextYThe unique identifier of the sales order.
CompanytextNThe company for which the sales order is created.
CustomertextNThe customer for whom the sales order is created.
Customer_countrytextNThe country associated to the customer.
Customer_regiontextNThe region associated to the customer.
Distribution_channeltextNThe distribution channel associated to the sales order.
DivisiontextNThe division associated to the sales order.
Requested_delivery_datedateNThe customer’s requested delivery date for the sales order.
Sales_grouptextNThe sales group associated to the sales order.
Sales_officetextNThe sales office associated to the sales order.
Sales_order_creatortextN
Sales_order_typetextNThe sales order type of the sales order.
Sales_organizationtextNThe sales organization of the sales order.

Sales_order_items

The following table describes the fields of the Sales_order_items table.

NameTypeMandatory Y/NDescription
Sales_order_item_IDtextYThe unique identifier of the sales order item.
Sales_order_IDtextNThe unique identifier of the sales order.
CategorytextNThe category of sales order item.
Creation_datedateNThe date on which the sales order item is created.
IncotermstextNThe incoterms associated to the sales order item.
Latest_expected_delivery_datedateNThe latest expected delivery date of (parts of) the sales order item.
MaterialtextNThe material sold.
Material_grouptextNThe categorization of the material sold.
Payment_termstextNThe terms of payment associated to the sales order item.
PlanttextNThe plant associated to the sales order item.
Profit_centertextNThe profit center associated to the sales order item.
QuantitytextNThe quantity and unit of measurement sold.
Sales_order_itemtextNA user-friendly name to identify the sales order item
Sales_order_item_creatortextN
Shipping_point_countrytextNThe country where the goods are delivered associated to the sales order item.
Storage_locationtextNStorage location associated to the sales order item.
ValuedoubleNA monetary value related to the sales order item.

Delivery

Deliveries

The following table describesthe fields of the Deliveries table.

NameTypeMandatory Y/NDescription
Delivery_IDtextYThe unique identifier of the delivery.
CompanytextN
Delivery_creatortextN
Delivery_datedateN
Delivery_typetextN
IncotermstextN
Planned_delivery_datedateN
Sales_organizationtextN
Shipping_conditionstextN
Staging_areatextN
Warehouse_numbertextN

Delivery_items

The following table describes the fields of the Delivery_items table.

NameTypeMandatory Y/NDescription
Delivery_item_IDtextYThe unique identifier of the delivery item.
Delivery_IDtextN*The unique identifier of the delivery.
Sales_order_item_IDtextN*The unique identifier of the sales order item.
Delivery_item_creatortextN
CategorytextN
Delivery_item_is_invoicedbooleanNIndicates if the sales order item is released to invoicing.
Delivered_quantitytextN
MaterialtextN
Material_grouptextN
PlanttextN
Storage_locationtextN
ValuedoubleN
  • If you want to include events related to other objects than the sales order in the process graphs, the Delivery_ID and Sales_order_item_ID fields are mandatory.

Invoice

Invoices

The following table describes the fields of the Invoices table.

NameTypeMandatory Y/NDescription
Invoice_IDtextYThe unique identifier of the invoice.
Baseline_datedateN
CompanytextN
DiscountdoubleN
Discount_percentage_1doubleN
Discount_percentage_2doubleN
Discount_period_1integerN
Discount_period_2integerN
Fiscal_yeartextN
IncotermstextN
Invoice_creatortextN
Invoice_datedateN
Invoice_typetextN
Net_payment_periodintegerNNet payment period of the invoice in days.
Payment_methodtextN
Payment_termstextN
Posting_datedateN
Sales_organizationtextN
Shipping_conditionstextN

Invoice_items

The following table describes the fields of the Invoice_items table.

NameTypeMandatory Y/NDescription
Invoice_item_IDtextYThe unique identifier of the invoice item.
Delivery_item_IDtextN*The unique identifier of the delivery item.
Invoice_IDtextN*The unique identifier of the invoice.
CategorytextN
Invoice_item_creatortextN
Invoice_item_is_cancelledbooleanNIndicates if the invoice item is cancelled.
Invoice_item_is_released_into_accountingbooleanNIndicates if the invoice item is billable.
Invoiced_quantitytextN
MaterialtextN
Material_grouptextN
PlanttextN
ValuedoubleN
  • If you want to include events related to other objects than the sales order in the process graphs, the Invoice_ID and Delivery_item_ID fields are mandatory.

Invoice_cancellations

The following table describes the fields of the Invoice_cancellations table.

NameTypeMandatory Y/NDescription
Invoice_cancellation_IDtextYThe unique identifier of the invoice cancellation.
Invoice_IDtextN*The unique identifier of the invoice that is cancelled.
CompanytextN
Fiscal_yeartextN
IncotermstextN
Invoice_cancellation_creatortextN
Invoice_datedateN
Invoice_typetextN
Sales_organizationtextN
Shipping_conditionstextN
  • If you want to include events related to other objects than the sales order in the process graphs, the Invoice_ID field is mandatory.

Accounting

Accounting_documents

The following table describes the fields of the Accounting_documents table.

NameTypeMandatory Y/NDescription
Accounting_document_IDtextYThe unique identifier of the accounting document.
Invoice_IDtextN*The unique identifier of the invoice.
Accounting_document_creatortextN
Accounting_document_is _cancelledbooleanNIndicates if the accounting document is cancelled.
Accounting_document_is _clearedbooleanNIndicates if the accounting document has been handled and is closed.
Baseline_datedateN
CompanytextN
DiscountdoubleN
Discount_percentage_1doubleN
Discount_percentage_2doubleN
Discount_period_1integerN
Discount_period_2integerN
Document_datedateN
Document_typetextN
Fiscal_yeartextN
Net_payment_periodintegerN
Payment_datedateN
Payment_methodtextN
Payment_statustextN
Payment_termstextN
Posting_datedateN
Transaction_typetextN
ValuedoubleN
  • If you want to include events related to other objects than the sales order in the process graphs, the Invoice_ID field is mandatory.

Payment

Payments

The following table describes the fields of the Payments table.

NameTypeMandatory Y/NDescription
Payment_IDtextYThe unique identifier of the payment.
Accounting_document_IDtextN*The unique identifier of the accounting document.
CompanytextN
Fiscal_yeartextN
Payment_creatortextN
Payment_is_completebooleanN
Payment_is_debitbooleanN
ValuedoubleN
  • If you want to include events related to other objects than the sales order in the process graphs, the Accounting_document_ID field is mandatory.

Events

Events

The Events table contains all sub-event logs for all objects. The following table describes the fields of the Events table.

NameTypeMandatory Y/NDescription
ActivitytextYThe name of the event. This describes the step in the process.
Accounting_document_IDtextYThe unique identifier of the accounting document.
Delivery_IDtextYThe unique identifier of the delivery.
Delivery_item_IDtextYThe unique identifier of the delivery item.
Event_enddatetimeYThe timestamp associated with the end of executing the event .
Invoice_IDtextYThe unique identifier of the invoice.
Invoice_item_IDtextYThe unique identifier of the invoice item.
Invoice_cancellation_IDtextYThe unique identifier of the invoice cancellation.
Payment_IDtextYThe unique identifier of the payment.
Sales_order_IDtextYThe unique identifier of the sales order.
Sales_order_item_IDtextYThe unique identifier of the sales order item.
Activity_categorytextNThe type of activity that takes place (e.g. change, set/remove block)
Activity_orderintegerNThe number that defines in which order activities are executed in case they have the same Event end.
Activity_triggertextNField describing the reason for the executed activity
AutomatedbooleanNIndicator whether the event is manually executed or automated.
DepartmenttextNThe department that executed the event
Event_detailtextNInformation related to the event.
UsertextNThe user who executed the event.
User_functiontextNThe function associated with the user.
User_typetextNThe categorization of the user.
Event_costdoubleNThe costs of executing the event.
Event_start *datetimeNThe timestamp associated with the start of executing the event.
Event_processing_timeintegerNThe time for executing the event (in milliseconds).

If both 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 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.

note

It is expected that for each record exactly one of the ID fields is filled in, which is the one of the object on which the event takes place. The other ID fields may be empty. Next to the standard mandatory fields (Activity and Event_end), one object ID is mandatory. This field depends on the object the event is part of. If your dataset contains events where Event_start occurs after Event_end, Event_start is automatically set to the Event_end date, as this would otherwise result in a negative cycle time. A warning message is displayed in the ingestion log.