---
sourceDocument: Yokohama Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/application-development

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# ERP Canvas scheduled extraction field descriptions

# ERP Canvas scheduled extraction field descriptions {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of ERP Canvas scheduled extraction field descriptions

The Scheduled Extraction form in ERP Canvas allows ServiceNow customers to create and manage jobs that extract data from ERP systems at specified intervals.
This functionality is essential for automating data synchronization between ERP systems and ServiceNow, ensuring timely and consistent data availability for business processes.
Show full answer Show less  

## Key Fields and Their Functions

* **Name:** Assign a unique identifier for each scheduled extraction job for easy management and reference.
* **ERP system:** Select the pre-configured ERP system linked to the extraction job.
* **Extraction table:** Specify the ERP extraction table from which data will be pulled.
* **Frequency:** Define when the extraction runs---options include hourly, daily, weekly, or triggered after completion of another job. For example:
  * **Hourly:** Specify exact start time to repeat every hour.
  * **Daily:** Specify a daily start time.
  * **Weekly:** Choose a weekday and time for weekly execution.
  * **After Completed Job:** Start extraction after a specified active job finishes, preventing loops.
* **Next scheduled start:** Set the exact time (24-hour format) for the next extraction run.
* **Active:** Toggle to enable or disable the scheduled extraction.
* **Maximum no of retries on error:** Configure up to 10 retries if the job fails, with the entire job rerun on each attempt. This is important for ensuring data consistency despite transient errors.
* **Extraction will retry after:** Define the wait time before retrying, if retries are enabled, in days, hours, minutes, and seconds.
* **Encoded query:** Paste an encoded query string to filter the extraction data for more targeted data pulls.
* **Generate encoded query script:** Use a script to generate or override the encoded query, providing advanced filtering capabilities. The script takes precedence over the static encoded query string.

## Practical Application for ServiceNow Customers

By leveraging these fields, ServiceNow customers can precisely schedule and control data extraction jobs from ERP systems, adapting frequency and filtering to their operational needs. The retry mechanism ensures robustness against failures, and filtering options enable extraction of only relevant data, optimizing integration performance and data accuracy. This setup facilitates seamless data flow into ServiceNow, supporting automated workflows and reporting.  
The Scheduled extraction form in ERP Canvas enables you to create and edit jobs to extract data at regular intervals.
For process details, see [Create a scheduled extraction in ERP Canvas](https://servicenow-prod.fluidtopics.net/0wHInDak5uLNIuT0HtHL0Q "Schedule extraction of information for an ERP (Enterprise Resource Planning) extraction table to capture large amounts of data from the system of record at a regular interval.").
{#erp-data-hub-scheduled-extraction-field-descriptions__table_rgs_xr5_bdc__entry__2}

| Field | Description |
|-|-|
| Name | A unique name that identifies this scheduled extraction. |
| ERP system | ERP system that the extraction table is linked to. The system must already be configured. |
| Extraction table | Name of the ERP extraction table from which to pull data. |
| Frequency | When to run the extraction. * Hourly: Specify the next scheduled start in hours, minutes, and seconds to repeat hourly. For example, adding 20:30:00 starts the scheduled extraction the next time the clock reaches 20:30:00 (9:30 pm) and then hourly after that (21:30:00, 22:30:00, 23:30:00, and so on). * Daily: Specify the next scheduled start in hours, minutes, and seconds to repeat daily. For example, adding 20:30:00 starts the scheduled extraction the next time the clock reaches 20:30:00 (9:30 pm) and then every subsequent day at 20:30:00. * Weekly: In Weekday, select the day of the week to run the scheduled extraction. Specify the next scheduled start in hours, minutes, and seconds to repeat weekly. For example, selecting Sunday and specifying 03:00:00 starts the scheduled extraction the next Sunday at 3:00 am and then every subsequent week on Sunday at 3:00 am. * After Completed Job: In After job, select an existing job that, when it completes, the new job you're creating should start. The job you specify must be active. Note: If you don't see the job that you want to use listed in After job, check if the job is already scheduled before or after another job. Only jobs that won't create a loop are permitted. {#erp-data-hub-scheduled-extraction-field-descriptions__ul_twd_dpv_bdc} |
| Next scheduled start | Time, in 24-hour format, for when the scheduled extraction should run. |
| Active | Option that indicates the scheduled extraction is active and should be executed at the specified frequency and time. |
| Maximum no of retries on error | If the job fails, set the maximum number of retries (from 0 through 10) the scheduled job should attempt before stopping. Note: Each retry uses the same query and retries the entire job. For example, if the total job contains 5000 records and the job fails after 2000 records are successfully processed, the entire job is rerun again on the next retry. For more information, see [Import sets key concepts](https://www.servicenow.com/docs/access?context=c_ImportSetsKeyConcepts&version=yokohama&pubname=yokohama-integrate-applications&ft:locale=en-US). |
| Extraction will retry after | If the Maximum no of retries on error field is set to a number between 1-10, specify the amount of time (in days, hours, minutes, and seconds) the system should wait before attempting the extraction again. |
| Encoded query | Create an encoded query string using a filter on the extraction table list and paste the string into this field. For example: For more information, see [Encoded query strings](https://www.servicenow.com/docs/access?context=c_EncodedQueryStrings&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US). |
| Generate encoded query script | Generate an encoded query script to use on the extraction table to fetch the data. For example: The script entered in Generate encoded query script takes precedence over information entered into the Encoded query field. You can append the encoded query to the script (as in the example). |
[Table 1. ERP scheduled extraction table fields]

{#erp-data-hub-scheduled-extraction-field-descriptions__table_rgs_xr5_bdc}