The objects that are involved in the Q2C process are: quote items, sales order items, delivery items, invoice items, and payments.
A user creates a quote with a series of quote items, which are converted into a sales order with a series of sales order items that are being purchased by a customer. Once approved, these sales orders are sent to order fulfillment, where delivery of the items is planned, scheduled, and executed. These items are then invoiced to the customer, with payments then collected around pre-defined payment terms.
The below is an object relationship diagram of the objects used in the creation of the events for the Q2C process.
The following tags are available by default.
| Tag | Description |
|---|---|
| Throughput time more than 30 days | max(event_end) - (min event_end) > 30 per object |
| Quote item value differs from sales order item value | quote_item."value" != sales_order_item."value" |
| Total invoice item values differs from sales order item value | sales_order_item."value" != sum(invoice_item."Value") |
| Change in sales order item value | Quote_item_event_log."Activity" = 'Change sales order item value' |
| Change in sales order item quantity | Quote_item_event_log."Activity" = 'Change sales order item quantity' |
| Partial goods delivery | sales_order_item."Quantity" > sum(delivery_item."Quantity") |
The following due dates are available by default.
| Due Date | Description |
|---|---|
| Payment due date | Difference between invoice item due date and create payment date |
This app template uses Netsuite version 2021.2 or higher as source system. NetSuite has two data model configurations: SuiteTalk and SuiteQL. Both SuiteTalk and SuiteQL schemas are used in this app template.
Extraction for the system is done using CData Sync. To set-up the extraction, make sure you have a valid license for CData Sync and have installed CData Sync.
To be able to connect to Netsuite, certain features need to be enabled in Netsuite and a role should be created with the correct access. Furthermore a custom saved search needs to be created in Netsuite.
In NetSuite, go to Setup -> Company -> Enable Features and enable the following in the SuiteCloud tab:
A role should be created for connecting to NetSuite to extract the data. This role must have the permissions that are listed in CData's documentation for their NetSuite connector. Use a naming convention for the role that would be memorable, like CData Extractor. Create a token for this role to use in the extraction and note down the details.
One of the tables that the app template requires must be created in NetSuite as a custom saved search. The custom saved search titled transaction item change log utilizes the Line System Notes Fields... in order to bring in line item level changes into the app template. Follow these steps in order to create the necessary saved search in NetSuite:
Go to Lists -> Search -> Saved Searches -> New. Choose Transaction for the Search Type. Under Search Title type in transaction item change log.
Line System Notes: Context. Choose none of and -None-.Under the Results tab, add the following fields:
| Field |
|---|
| Line Unique Key |
| Transaction Number |
| Line System Notes: Context |
| Line System Notes: Date |
| Line System Notes: Field |
| Line System Notes: New Value |
| Line System Notes: Old Value |
| Line System Notes: Record |
| Line System Notes: Record ID |
| Line System Notes: Record Type |
| Line System Notes: Role |
| Line System Notes: Set by |
| Line System Notes: Type |
| Department |
| Status |
| Vendor: Country |
| Vendor: Company Name |
| User: Internal ID |
Click Save & Run to save the search and look at the results.
A JavaScript file, called search_script.js, must be added to NetSuite in order for RESTlet Saved Search Queries to work. Follow the steps from the CData documentation to set this up to be able to query the transaction item change log Saved Search. After following the steps, note down the SearchId, ScriptId, and DeploymentNum. These are necessary to set up the extraction connection for SuiteTalk.
In order for filtering on dates to work, the date format in NetSuite should be used in the extraction configuration. Go to NetSuite -> SetUp -> Company -> General Preferences and make note of the date format (MM/DD/YYYY for instance). When configuring the data extraction job in CData, the dates in the date extraction range need to be specified in the same format.
To be able to extract data from NetSuite, two source connections need to be created in CData Sync, one for SuiteTalk and one for SuiteQL.
To set up the destination connection, follow the steps as defined in Create a destination connection (Automation Cloud). Note: If you are using Automation Suite, make sure to select AUTOMATION SUITE as the DELIVERY option and select the correct version of Automation Suite you are using.
To be able to extract the data from NetSuite, two jobs need to be set up in CData Sync, one using SuiteTalk as source and one using SuiteQL. Both will use the same destination connection.
In the Advanced tab in the Job Settings panel, define the following settings:
Important: Make sure you edit the Pre-job Event.
CData Sync allows the use of environment variables in order to drive specific extraction logic in each query.
| Variable | Description | Comment |
|---|---|---|
| start_extraction_date | Defines first date for which data will be extracted. | Mandatory |
| end_extraction_date | Last date for which data will be extracted. |
Be mindful of choosing a start_extraction_date that encompasses the data that you want to capture, as orders are the starting point of the quote to cash process.
In order to setup the environment variables:
| Step | Action |
|---|---|
| 1 | Go to the Events tab in the Job Settings panel of the job you are creating |
| 2 | Edit the Pre-Job Event section to add the code displayed below after <!-- Code goes here -- >. Do not modify the api:info details that are shown by default. |
| 3 | Make sure the date format matches the date format of NetSuite as noted down in the system configuration. |
| 4 | Click on Save Changes. |
<!-- Modify environment variables here. -->
<!-- Variable start_extraction_date must be populated.-->
<api:set attr="out.env:start_extraction_date" value="01/01/2022" />
<!-- In case a specific end date is needed, replace the value string with the required date in the Date format listed in NetSuite. -->
<!-- i.e api:set attr="out.env:end_extraction_date" value="01/01/2022" -->
<api:set attr="out.env:end_extraction_date" value= '12/31/3000' />
<api:push item="out" />
By default, end_extraction_date will default to today's date. start_extraction_date must always be populated.
Once the job is correctly setup, click on Add Custom Query under the Tasks tab and paste the following queries (each query needs to maintain the semicolon at the end). Make sure you save all changes.
Use the following custom query for SuiteQL when creating the job:
REPLICATE [Employee] WITH TruncateTableData = 'True' SELECT [id], [department], [employeetype], [entityid], [title] FROM [employee];
REPLICATE [Entity] WITH TruncateTableData = 'True' SELECT [id], [entityid], [vendor] FROM [entity];
REPLICATE [Item] WITH TruncateTableData = 'True' SELECT [id], [department], [fullname], [itemid], [itemtype], [subtype] FROM [item];
REPLICATE [Previoustransactionlinelink] WITH TruncateTableData = 'True' SELECT [linktype], [nextdoc], [nextline], [nexttype], [previousdoc], [previousline] FROM [previoustransactionlinelink] WHERE [nexttype] IN ('Estimate', 'SalesOrd', 'CustPymt', 'ItemShip', 'Deposit', 'CustInvc', 'RtnAuth', 'CashSale');
REPLICATE [Systemnote] WITH TruncateTableData = 'True' SELECT * FROM [systemnote] WHERE [field] IN ('TRANDOC.KSTATUS', 'TRANLINE.MESTAMOUNT', 'TRANDOC.BPAYMENTHOLD', 'TRANDOC.STRANTYPE', 'TRANLINE.RITEMCOUNT', 'TRANLINE.MAMOUNT', 'TRANDOC.MAMOUNTMAIN', 'TRANLINE.RUNITPRICE', 'TRANDOC.DSHIP', 'CUSTBODY_REPORT_TIMESTAMP', 'TRANDOC.KFORMTEMPLATE') AND ([recordtypeid] = -30) AND ([date] >= '{env:start_extraction_date}') AND ([date] <= '{env:end_extraction_date}');
REPLICATE [Transaction] WITH TruncateTableData = 'True' SELECT [id], [approvalstatus], [billingaddress], [billingstatus], [closedate], [createdby], [createddate], [currency], [daysopen], [daysoverduesearch], [duedate], [employee], [entity], [exchangerate], [externalid], [foreigntotal], [paymentmethod], [postingperiod], [status], [terms], [trandate], [trandisplayname], [type], [void], [voided] FROM [transaction] WHERE [type] IN ('Estimate', 'SalesOrd', 'CustPymt', 'ItemShip', 'Deposit', 'CustInvc', 'RtnAuth', 'CashSale') AND ([createddate] >= '{env:start_extraction_date}') AND ([createddate] <= '{env:end_extraction_date}');
REPLICATE [Transactionline] WITH TruncateTableData = 'True' SELECT DISTINCT TL.[id], [uniquekey], TL.[linelastmodifieddate], TL.[createdfrom], [department], TL.[entity], [expenseaccount], [inventorylocation], [isclosed], [item], [itemtype], [linesequencenumber], [location], [netamount], [quantity], [subsidiary], [taxline], [transaction], [units] FROM [transactionline] AS TL JOIN [transaction] as T ON TL.[transaction] = t.[id] WHERE [type] IN ('Estimate', 'SalesOrd', 'CustPymt', 'ItemShip', 'Deposit', 'CustInvc', 'RtnAuth', 'CashSale');
REPLICATE [Unitstypeuom] WITH TruncateTableData = 'True' SELECT [internalid], [unitname] FROM [unitstypeuom];
Make sure that the query for transactionline works, as it is a custom case where it is joined to the transaction table in order to filter to only include transaction lines for transactions in the quote to cash process.
In the Advanced tab in the Job Settings panel, define the following settings:
Important: Make sure you edit the Pre-job Event.
CData Sync allows the use of environment variables in order to drive specific extraction logic in each query.
| Variable | Description | Comment |
|---|---|---|
| start_extraction_date | Defines first date for which data will be extracted. | Mandatory |
| end_extraction_date | Last date for which data will be extracted. |
Be mindful of choosing a start_extraction_date that encompasses the data that you want to capture, as orders are the starting point of the quote to cash process.
In order to setup the environment variables:
| Step | Action |
|---|---|
| 1 | Go to the Events tab in the Job Settings panel of the job you are creating |
| 2 | Edit the Pre-Job Event section to add the code displayed below after <!-- Code goes here -- >. Do not modify the api:info details that are shown by default. |
| 3 | Make sure the date format matches the date format of NetSuite as noted down in the system configuration. |
| 4 | Click on Save Changes. |
<!-- Modify environment variables here. -->
<!-- Variable start_extraction_date must be populated.-->
<api:set attr="out.env:start_extraction_date" value="01/01/2022" />
<!-- In case a specific end date is needed, replace the value string with the required date in the Date format listed in NetSuite. -->
<!-- i.e api:set attr="out.env:end_extraction_date" value="01/01/2022" -->
<api:set attr="out.env:end_extraction_date" value= '12/31/3000' />
<api:push item="out" />
By default, end_extraction_date will default to today's date. start_extraction_date must always be populated.
After the data has been successfully loaded, the Process Mining platform needs to start the data ingestion process. This is done by calling the End of Upload API. In order to set this up, follow the steps below:
| Step | Action |
|---|---|
| 1 | Go to the Events tab in the Job Settings panel of the job you are creating |
| 2 | Edit the Post-Job Event section to add the code displayed below after <!-- Code goes here -- >. Do not modify the api:info details that are shown by default. |
| 3 | Fill out the End of Upload API with the value provided. |
| 4 | In case you need a debugging log for this call, uncomment the two lines provided in the code below and provide a location for the log file. |
| 5 | Click on Save Changes. |
<api:set attr="http.url" value="END_OF_UPLOAD_API"/>
<!-- <api:set attr="http.verbosity" value="5"/> -->
<!-- <api:set attr="http.logfile" value="D:/mydir/cdata_log.txt"/> -->
<api:call op="httpPost" in="http"/>
Once the job is correctly setup, click on Add Custom Query under the Tasks tab and paste the following query. Make sure you save all changes.
Use the following custom query for SuiteTalk when creating the job:
REPLICATE [Transaction_item_change_log] WITH TruncateTableData = 'True' SELECT [Line_Unique_Key], [Transaction_Number], [Context], [Date], [Field_text] as [Field], [New_Value], [Old_Value], [Record], [Record_ID], [Record_Type], [Role_text] as [Role], [Set_by_text] as [Set_by], [Type], [Department_text] as [Department], [Status_text] as [Status], [Country_text] as [Country], [Company_Name], [Internal_ID_text] as [Internal_ID] FROM [transaction_item_change_log] WHERE ([Date] >= '{env:start_extraction_date}') AND ([Date] <= '{env:end_extraction_date}');
This section contains an overview of the fields for each of the input tables of the Oracle NetSuite Quote to Cash app template. For each table the fields are listed.
Below is a list of tables that are brought in with the NetSuite SuiteQL Schema specified:
The following is a list of tables that are brought in with the NetSuite SuiteTalk Schema specified:
The transaction_item_change_log table is a custom saved search that has been created for the purpose of bringing line item change history into the transformations.
More information can be found on these tables in the NetSuite help center. The Analytics Browser tab is for SuiteQL tables.
| Field | Data type | Label | Filtering |
|---|---|---|---|
| id | Text | Internal ID | |
| department | Text | Department | |
| employeetype | Text | Type | |
| entityid | Text | Entity ID | |
| title | Text | Job Title |
| Field | Data type | Label | Filtering |
|---|---|---|---|
| id | Text | Internal ID | |
| entityid | Text | Entity name | |
| vendor | Text | Vendor ID |
| Field | Data type | Label | Filtering |
|---|---|---|---|
| id | Text | Internal ID | |
| cost | Double | Cost | |
| department | Text | Department | |
| fullname | Text | Internal ID | |
| itemid | Text | Full Name | |
| itemtype | Text | Address | |
| subtype | Text | Sublocation of |
| Field | Data type | Label | Filtering |
|---|---|---|---|
| linktype | Text | Link Type | |
| nextdoc | Text | Transaction ID of next document | |
| nextline | Text | Line ID of the next document line | |
| nexttype | Text | Next document type | in ('Estimate', 'SalesOrd', 'CustPymt', 'ItemShip', 'Deposit', 'CustInvc', 'RtnAuth', 'CashSale') |
| previousdoc | Text | Transaction ID of previous document | |
| previousline | Text | Line ID of the previous document line |
| Field | Data type | Label | Filtering |
|---|---|---|---|
| id | Text | Internal ID | |
| date | date | Country | |
| field | Text | Currency | in ('TRANDOC.KSTATUS', 'TRANLINE.MESTAMOUNT', 'TRANDOC.BPAYMENTHOLD', 'TRANDOC.STRANTYPE', 'TRANLINE.RITEMCOUNT', 'TRANLINE.MAMOUNT', 'TRANDOC.MAMOUNTMAIN', 'TRANLINE.RUNITPRICE', 'TRANDOC.DSHIP', 'CUSTBODY_REPORT_TIMESTAMP') |
| name | Text | Full Name | |
| newvalue | Text | Address | |
| oldvalue | Text | SubSubsidiary of | |
| record | Text | Return Address | |
| recordid | Text | Shipping Address | |
| recordtypeid | Text | State | -30 |
| role | Text | Address |
| Field | Data type | Label | Filtering |
|---|---|---|---|
| id | Text | Internal ID | |
| lastmodifieddate | Date | Date Last Modified | |
| approvalstatus | Text | Approval Status | |
| billingaddress | Text | Billing Address | |
| billingstatus | Text | Billing Status | |
| closedate | Text | Date Closed | |
| createdby | Text | Created By | |
| createddate | Text | Date Created | |
| currency | Text | Currency | |
| daysopen | Text | Days Open | |
| daysoverduesearch | Text | Days Overdue | |
| duedate | Text | Due Date | |
| employee | Text | Sales Rep | |
| entity | Text | Entity | |
| exchangerate | Text | Exchange Rate | |
| externalid | Text | External ID | |
| foreigntotal | Text | Total Amount (Transaction Currency) | |
| paymentmethod | Text | Payment Method | |
| postingperiod | Text | Posting Period | |
| status | Text | Status | |
| terms | Text | Terms | |
| trandate | Date | Date | |
| trandisplayname | Text | Transaction | |
| type | Text | Type | in ('Estimate', 'SalesOrd', 'CustPymt', 'ItemShip', 'Deposit', 'CustInvc', 'RtnAuth', 'CashSale') |
| void | Text | Void | |
| voided | Text | Voided |
This table is joined to the transaction table in order to filter on transaction."type"
| Field | Data type | Label | Filtering |
|---|---|---|---|
| id | Text | Internal ID | |
| uniquekey | Text | Unique Key | |
| linelastmodifieddate | Text | Line Last Modified Date | |
| createdfrom | Text | Created From | |
| department | Text | Department | |
| entity | Text | Entity | |
| expenseaccount | Text | Expense Account | |
| inventorylocation | Text | Storage location | |
| isclosed | Text | Closed | |
| item | Text | Item | |
| itemtype | Text | Item Type | |
| linesequencenumber | Text | Line Number | |
| location | Text | Location | |
| netamount | Text | Amount (Net) (Transaction Currency) | |
| quantity | Text | Quantity | |
| subsidiary | Text | Subsidiary | |
| taxline | Text | Tax Line | |
| transaction | Text | Transaction ID | |
| units | Text | Unit ID |
| Field | Data type | Label | Filtering |
|---|---|---|---|
| internalid | Text | Internal ID | |
| unitname | Text | Name of the measuring unit |
This is the table created as a custom saved search and connected through the SuiteTalk RESTlet Saved Search Schema.
| Field | Data type | Label | Filtering |
|---|---|---|---|
| Line_Unique_Key | Text | Unique ID of the line item | |
| Transaction_Number | Text | Transaction document number | |
| Context | Text | Execution context of the change | |
| Date | Datetime | Datetime | |
| Field_text | Text | Field of change | |
| New_Value | Text | New value | |
| Old_Value | Text | Old value | |
| Record | Text | Record type | |
| Record_ID | Text | Transaction ID | |
| Record_Type | Text | One word record type | |
| Role_text | Text | Name of the role making the change | |
| Set_by_text | Text | Name of user making the change | |
| Set_by_value | Text | User ID of person making the change | |
| Status_text | Text | Status of the transaction | |
| Type | Text | Change log action type | |
| Department_text | Text | Name of the department |
Below is an overview of the objects, and their attributes, of the Oracle NetSuite Quote to Cash app template.
| Name | Attribute | Data type | Mandatory Y/N | Description |
|---|---|---|---|---|
| Quote_item_ID | Quote_items."Quote_item_ID" |
Text | Y | Unique identifier of quote item |
| Quote_item | concat(transactions."Tran_display_name", '-', transactionlines."Line_id") |
Text | N | Display name of quote item |
| Status | transaction_item_change_log."Status" |
Text | N | Quote item status |
| Type | systemnote_order_types_input."New_value" |
Text | N | Quote item order type |
| Value | Quote_items."Value" |
Integer | N | Quote item value |
| Quantity | concat(abs(transactionlines."Quantity"), ' ', coalesce(unitstypeuom."Unit_name", 'Units')) |
Text | N | Quote item quantity and unit type |
| Created_by | Quote_items."Creator" |
Text | N | Quote item creator |
| Name | Attribute | Data type | Mandatory Y/N | Description |
|---|---|---|---|---|
| Quote_item_ID | transactionlines."Unique_key" |
Text | Y | Unique identifier of the quote item |
| Line_id | transactionlines."Line_id" |
Text | Y | Identifier of the line in the quote transaction |
| Quote_ID | transactionlines."Transaction" |
Text | Y | Unique identifier of the quote |
| Created_at | transactions."Created_date" |
Date | Y | Creation date |
| Creator | employee."Entity_id" |
Text | Y | Employee name |
| Value | abs(transactionlines."Net_amount") |
Double | Y | Value of the quote item |
| Quantity | concat(abs(transactionlines."Quantity"), ' ', coalesce(unitstypeuom."Unit_name", 'Units')) |
Text | Y | Quote item quantity and unit |
| Status | transaction_item_change_log."Status" |
Text | Y | Quote status |
| Team | employee."Department" |
Text | Y | Employee team |
| Name | Attribute | Data type | Mandatory Y/N | Description |
|---|---|---|---|---|
| Quote_item_ID | transactionlines."Unique_key" |
Text | Y | Unique identifier of the quote item |
| Line_id | transactionlines."Line_id" |
Text | Y | Identifier of the line in the quote transaction |
| Quote_ID | transactionlines."Transaction" |
Text | Y | Unique identifier of the quote |
| Created_at | transactions."Created_date" |
Date | Y | Creation date |
| Creator | employee."Entity_id" |
Text | Y | Employee name |
| Value | abs(transactionlines."Net_amount") |
Double | Y | Value of the quote item |
| Quantity | concat(abs(transactionlines."Quantity"), ' ', coalesce(unitstypeuom."Unit_name", 'Units')) |
Text | Y | Quote item quantity and unit |
| Status | transaction_item_change_log."Status" |
Text | Y | Quote status |
| Team | employee."Department" |
Text | Y | Employee team |
| Name | Attribute | Data type | Mandatory Y/N | Description |
|---|---|---|---|---|
| Quote_item_ID | transactionlines."Unique_key" |
Text | Y | Unique identifier of the quote item |
| Line_id | transactionlines."Line_id" |
Text | Y | Identifier of the line in the quote transaction |
| Quote_ID | transactionlines."Transaction" |
Text | Y | Unique identifier of the quote |
| Created_at | transactions."Created_date" |
Date | Y | Creation date |
| Creator | employee."Entity_id" |
Text | Y | Employee name |
| Value | abs(transactionlines."Net_amount") |
Double | Y | Value of the quote item |
| Quantity | concat(abs(transactionlines."Quantity"), ' ', coalesce(unitstypeuom."Unit_name", 'Units')) |
Text | Y | Quote item quantity and unit |
| Status | transaction_item_change_log."Status" |
Text | Y | Quote status |
| Team | employee."Department" |
Text | Y | Employee team |
| Name | Attribute | Data type | Mandatory Y/N | Description |
|---|---|---|---|---|
| Quote_item_ID | transactionlines."Unique_key" |
Text | Y | Unique identifier of the quote item |
| Line_id | transactionlines."Line_id" |
Text | Y | Identifier of the line in the quote transaction |
| Quote_ID | transactionlines."Transaction" |
Text | Y | Unique identifier of the quote |
| Created_at | transactions."Created_date" |
Date | Y | Creation date |
| Creator | employee."Entity_id" |
Text | Y | Employee name |
| Value | abs(transactionlines."Net_amount") |
Double | Y | Value of the quote item |
| Quantity | concat(abs(transactionlines."Quantity"), ' ', coalesce(unitstypeuom."Unit_name", 'Units')) |
Text | Y | Quote item quantity and unit |
| Status | transaction_item_change_log."Status" |
Text | Y | Quote status |
| Team | employee."Department" |
Text | Y | Employee team |
| Name | Attribute | Data type | Mandatory Y/N | Description |
|---|---|---|---|---|
| Quote_item_ID | transactionlines."Unique_key" |
Text | Y | Unique identifier of the quote item |
| Line_id | transactionlines."Line_id" |
Text | Y | Identifier of the line in the quote transaction |
| Quote_ID | transactionlines."Transaction" |
Text | Y | Unique identifier of the quote |
| Created_at | transactions."Created_date" |
Date | Y | Creation date |
| Creator | employee."Entity_id" |
Text | Y | Employee name |
| Value | abs(transactionlines."Net_amount") |
Double | Y | Value of the quote item |
| Quantity | concat(abs(transactionlines."Quantity"), ' ', coalesce(unitstypeuom."Unit_name", 'Units')) |
Text | Y | Quote item quantity and unit |
| Status | transaction_item_change_log."Status" |
Text | Y | Quote status |
| Team | employee."Department" |
Text | Y | Employee team |
A break down of the activities is listed below, based on each model that contains the activity:
This identifies the creation action of a quote item
transaction_item_change_log."Field" = 'Amount'
This identifies a change to the value of a quote item
transaction_item_change_log."Field" = 'Quantity'
This identifies a change to the quantity of a quote item
transaction_item_change_log."Status" = 'Closed'
This identifies that a quote item has been canceled or voided
This identifies the creation action of a sales order item
transaction_item_change_log."Field" = 'Amount'
This identifies a change to the value of a sales order item
transaction_item_change_log."Field" = 'Quantity'
This identifies a change to the quantity of a sales order item
transaction_item_change_log."Status" = 'Closed'
This identifies that a sales order item has been canceled or voided
This identifies the creation action of a delivery item
systemnote."field" = 'TRANDOC.KSTATUS' and systemnote."newvalue" = 'Picked'
This identifies that the goods for this delivery item have been picked
systemnote."field" = 'TRANDOC.KSTATUS' and systemnote."newvalue" = 'Packed'
This identifies that the goods for this delivery item have been packed
systemnote."field" = 'TRANDOC.KSTATUS' and systemnote."newvalue" = 'Shipped'
This identifies that the goods for this delivery item have been shipped
This identifies the creation action of an invoice item
transaction_item_change_log."Field" = 'Amount'
This identifies a change to the value of an invoice item
transaction_item_change_log."Field" = 'Quantity'
This identifies a change to the quantity of an invoice item
systemnote."Field" = 'TRANDOC.KSTATUS' and systemnote."New_value" = 'Voided'
This identifies the cancellation of an invoice, which is applied to the individual invoice items
This identifies payment creation
This seed file is used to add automation-related properties to each activity, used for the automation potential dashboard. For more information, see Simulating Automation Potential.
| Field | Type | Description |
|---|---|---|
| Activity | Text | Display name for the activity |
| Event_cost | Double | Cost associated with the activity |
| Event_processing_time | Integer | Processing time associated with the activity (in milliseconds) |
This seed file is used to define properties for the due dates. For more information, see Due Dates.
| Field | Type | Description |
|---|---|---|
| Due_date | Text | The name of the due date |
| Due_date_type | Text | The Due date type |
| Fixed_costs | Boolean | An indication whether costs are fixed or time based |
| Cost | Double | Fixed costs: The amount of costs. Variable costs: The amount of costs per Time and Time_type |
| Time | Integer | A number indicating the amount of time in case of time-based costs |
| Time_type | Text | Type of time period for cost calculations. This can be any of the following values: day, hour, minute, second or millisecond |
A variable exists in dbt_project.yml called Automated_users for users to specify the automated users that exist in the Object table. Please add the object.id for these users to this variable.
NetSuite SuiteQL relies on some incredibly large tables for its data, which can be filtered by specifying the record types required. Not filtering on these can cause a lot of performance issues, and will replicate a lot of superfluous data.
If you plan on using CSV files and are going to be using the SQL Query Editor for exporting the SuiteQL tables, the SQL Query Editor tool only allows for up to 5,000 rows to be exported in each query. If more rows are needed, one can filter based on date, and add the results together into a larger file.
Filtering the transactionline table is important, as it can be a rather large table if one does not. However, this requires joining the transactionline and transaction tables in order to filter transactionline to only include the transaction types that are listed in the filtering above. Please use the custom query for the CData job for transactionline in order to filter correctly.
DELETE activities like Delete sales order or Delete invoice will remove the transaction, and subsequent transaction lines, from the transaction, transactionline, systemnote, and transaction_item_change_log tables.
Void activities are built with NetSuite having Void transactions using reversing disabled. In NetSuite, go to Setup -> Accounting -> Accounting Preferences to check.
NetSuite is structurally built around the header level, so tracking item level changes requires utilizing a mixture of SuiteTalk and SuiteQL Schemas to find and pull the requisite data for process mining.
If you encounter errors when running a job that state column not found, go to the Advanced tab of the NetSuite Connection in CData and set the Row Scan Depth: to 0
CData Sync may exhibit some issues in filtering the extraction tables on multiple values, so this is something to keep in mind if you do encounter similar issues.