- Release notes
- Getting started
- Installation
- Configuration
- Integrations
- Authentication
- Working with Apps and Discovery Accelerators
- AppOne menus and dashboards
- AppOne setup
- TemplateOne 1.0.0 menus and dashboards
- TemplateOne 1.0.0 setup
- TemplateOne menus and fashboards
- TemplateOne 2021.4.0 setup
- Purchase to Pay Discovery Accelerator menus and dashboards
- Purchase to Pay Discovery Accelerator Setup
- Order to Cash Discovery Accelerator menus and dashboards
- Order to Cash Discovery Accelerator Setup
- Input tables of the Order-to-Cash Discovery Accelerator V21.4.1
- Input tables of the Order-to-Cash Discovery Accelerator 21.4
- Adding automation estimates
- Basic Connector for AppOne
- SAP Connectors
- Introduction to SAP Connector
- SAP input
- Checking the data in the SAP Connector
- Adding process specific tags to the SAP Connector for AppOne
- Adding process specific Due dates to the SAP Connector for AppOne
- Adding automation estimates to the SAP Connector for AppOne
- Adding attributes to the SAP Connector for AppOne
- Adding activities to the SAP Connector for AppOne
- Adding entities to the SAP Connector for AppOne
- SAP Order to Cash Connector for AppOne
- SAP Purchase to Pay Connector for AppOne
- SAP Connector for Purchase to Pay Discovery Accelerator
- SAP Connector for Order-to-Cash Discovery Accelerator
- Superadmin
- Dashboards and charts
- Tables and table items
- Application integrity
- How to ....
- Working with SQL connectors
- Introduction to SQL connectors
- Setting up a SQL connector
- CData Sync extractions
- Running a SQL connector
- Editing transformations
- Releasing a SQL Connector
- Scheduling data extraction
- Structure of transformations
- Using SQL connectors for released apps
- Generating a cache with scripts
- Setting up a local test environment
- Separate development and production environments
- Useful resources
Input tables of the Order-to-Cash Discovery Accelerator V21.4.1
This section contains an overview of the attributes for each of the input tables of the Order-to-Cash Discovery Accelerator. For each entity the attributes are listed. For each attribute, the name and a data type are displayed. Apart from that, it is indicated whether the attribute is mandatory if the entity is included in the Order-to-Cash process.
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 the Order-to-Cash Discovery Accelerator.
Sales_orders_base
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
Sales order ID |
Text |
Y |
The unique identifier of the sales order. |
Company |
Text |
N |
The company for which the sales order is created. |
Customer |
Text |
N |
The customer for whom the sales order is created. |
Customer country |
Text |
N |
The country associated to the customer. |
Customer region |
Text |
N |
The region associated to the customer. |
Distribution channel |
Text |
N |
The distribution channel associated to the sales order. |
Division |
Text |
N |
The division associated to the sales order. |
Requested delivery date |
Date |
N |
The customer’s requested delivery date for the sales order. |
Sales group |
Text |
N |
The sales group associated to the sales order. |
Sales office |
Text |
N |
The sales office associated to the sales order. |
Sales order type |
Text |
N |
The sales order type of the sales order. |
Sales organization |
Text |
N |
The sales organization of the sales order. |
Sales_order_items_base
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
Sales order item ID |
Text |
Y |
The unique identifier of the sales order item. |
Sales order ID |
Text |
Y |
The unique identifier of the sales order. |
Creation date |
Date |
Y |
The date on which the sales order item is created. |
Category |
Text |
N |
The category of sales order item. |
Incoterms |
Text |
N |
The incoterms associated to the sales order item. |
Latest expected delivery date |
Date |
N |
The latest expected delivery date of (parts of) the sales order item. |
Material |
Text |
N |
The material sold. |
Material group |
Text |
N |
The categorization of the material sold. |
Payment terms |
Text |
N |
The terms of payment associated to the sales order item. |
Plant |
Text |
N |
The plant associated to the sales order item. |
Profit center |
Text |
N |
The profit center associated to the sales order item. |
Quantity |
Text |
N |
The quantity and unit of measurement sold. |
Sales order item |
Text |
N |
A user-friendly name to identify the sales order item |
Shipping point country |
Text |
N |
The country where the goods are delivered associated to the sales order item. |
Storage location |
Text |
N |
Storage location associated to the sales order item. |
Value |
Double |
N |
A monetary value related to the sales order item. |
Deliveries_base
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
Delivery ID |
Text |
Y |
The unique identifier of the delivery. |
Delivery_items_base
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
Delivery item ID |
Text |
Y |
The unique identifier of the delivery item. |
Delivery ID |
Text |
N* |
The unique identifier of the delivery. |
Sales order items ID |
Text |
N* |
The unique identifier of the sales order item. |
Delivery items is invoiced |
Boolean |
N |
Indicates if the sales order item is released to invoicing. |
\* If you want to include events related to other entities than the sales order in the process graphs, the Delivery ID and Sales order items ID fields are mandatory.
Invoices_base
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
Invoice ID |
Text |
Y |
The unique identifier of the invoice. |
Invoice_items_base
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
Invoice item ID |
Text |
Y |
The unique identifier of the invoice item. |
Invoice ID |
Text |
N* |
The unique identifier of the invoice. |
Delivery item ID |
Text |
N* |
The unique identifier of the delivery item. |
Invoice item is cancelled |
Boolean |
N |
Indicates if the invoice item is cancelled. |
Invoice item is released into accounting |
Boolean |
N |
Indicates if the invoice item is billable. |
* If you want to include events related to other entities than the sales order in the process graphs, the Invoice ID and Delivery item ID fields are mandatory.
Invoice_cancellations_base
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
Invoice cancellation ID |
Text |
Y |
The unique identifier of the invoice cancellation. |
Invoice ID |
Text |
N* |
The unique identifier of the invoice that is cancelled. |
* 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
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
Accounting document ID |
Text |
Y |
The unique identifier of the accounting document. |
Invoice ID |
Text |
N* |
The unique identifier of the invoice. |
Accounting document is cleared |
Boolean |
N |
Indicates if the accounting document has been handled and is closed. |
* 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
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
Payment ID |
Text |
Y |
The unique identifier of the payment. |
Accounting document ID |
Text |
N* |
The unique identifier of the accounting document. |
* 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
table contains all sub-event logs for all entities. Below is an overview of the attributes of the Events_base
table.
Name |
Type |
Mandatory Y/N |
Description |
---|---|---|---|
Activity |
Text |
Y |
The name of the event. This describes the step in the process. |
Event end |
DateTime |
Y |
The timestamp associated with the end of executing the event |
Accounting document ID |
Text |
Y |
The unique identifier of the accounting document. |
Delivery ID |
Text |
Y |
The unique identifier of the delivery. |
Delivery item ID |
Text |
Y |
The unique identifier of the delivery item. |
Invoice ID |
Text |
Y |
The unique identifier of the invoice. |
Invoice item ID |
Text |
Y |
The unique identifier of the invoice item. |
Invoice cancellation ID |
Text |
Y |
The unique identifier of the invoice cancellation. |
Payment ID |
Text |
Y |
The unique identifier of the payment. |
Sales order ID |
Text |
Y |
The unique identifier of the sales order. |
Sales order item ID |
Text |
Y |
The unique identifier of the sales order item. |
Activity category |
Text |
N |
The type of activity that takes place (e.g. change, set/remove block) |
Activity order |
Integer |
N |
The number that defines in which order activities are executed in case they have the same Event end. |
Activity trigger |
Text |
N |
Attribute describing the reason for the executed activity |
Automated |
Boolean |
N |
Indicator whether the event is manually executed or automated. |
Department |
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. |
It is expected that for each record exactly one of the 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.
Below is an overview of the different attribute types and their default format settings.
Attribute type |
Specification |
---|---|
Boolean |
n/a |
Date |
Format: YYYY-M-D |
DateTime |
Date format: YYYY-M-D Time format: h:mm[:ss[[.zzz]]] |
Double |
Decimal separator: . (dot) Thousand separator: none |
Integer |
Thousand separator: none |
Text |
n/a. |
Some of the attribute types of the input attributes can have multiple format settings which can differ. For example, two attributes can be both of type Date, but they can each have a specific format.
If your input data is of a different format than the default format in the Order-to-Cash Discovery Accelerator, you can edit the format settings for all the input attributes of that type in the Edit Datasource Attribute dialog in the Order-to-Cash Discovery Accelerator to match the format of your input data. See the illustration below for an example.
Changing the display format
If you want to use different display formats in the Order-to-Cash Discovery Accelerator than the default format that is set for the attribute type, you can change the display format settings in Order-to-Cash Discovery Accelerator. For example, if you want to use a different currency string you can change the settings in the Display Format dialog.
Follow these steps to open the Display Format dialog.
Step |
Action |
---|---|
1 |
Click on the Home icon and select Settings.... |
2 |
Click on DISPLAY FORMAT.... |
See the illustration below.
In a similar way, you can change the decimal separator or thousand separator for specific attributes.
For more information see Display Format.
- Introduction
- 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
- Attribute type
- Input format