Zero Copy Connector for ERP scheduled extraction field descriptions

  • Release version: Australia
  • Updated March 12, 2026
  • 3 minutes to read
    • Summarize
    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 Zero Copy Connector for ERP scheduled extraction field descriptions

    The Scheduled Extraction form in ServiceNow's Zero Copy Connector for ERP allows you to define and manage data extraction jobs that run at regular intervals from ERP systems. This functionality is essential for automating data synchronization between ERP systems and ServiceNow, ensuring timely and reliable data availability.

    Show full answer Show less

    Key Fields and Their Practical Use

    • Name: Uniquely identifies each scheduled extraction job for clear management.
    • Active: Enables or disables the scheduled job, controlling whether it runs as configured.
    • Extraction table: Specifies the ERP table from which data is extracted, linking the job to the relevant data source.
    • ERP system: Identifies the connected ERP system; must be pre-configured to ensure correct data integration.
    • Application: Automatically set to Zero Copy Connector for ERP, confirming the context of the extraction job.
    • Maximum no of retries on error: Defines how many times the job should retry if a failure occurs, allowing for resilience in data extraction processes.
    • Extraction will retry after: Sets the wait time before retrying a failed extraction, helping to space out attempts and avoid immediate repeated failures.
    • Encoded query and Generate encoded query script: Allows filtering of extracted data using query strings or scripts, with scripts taking precedence for advanced data selection.
    • After extraction: Enables chaining of jobs by specifying a preceding job that must complete before this job runs, preventing scheduling loops.
    • Run as: Specifies the user context under which the extraction runs, important for permissions and auditing.
    • Run: Offers flexible scheduling options including Daily, Weekly, Monthly, Periodically, Once, On Demand, and Business Calendar-based timings, allowing alignment with business needs and calendar events.
    • Time and Time zone: Defines the exact time and applicable time zone for running the extraction, ensuring synchronization across different geographical locations.

    Practical Benefits for ServiceNow Customers

    By using the scheduled extraction configuration, customers can automate the retrieval of ERP data into ServiceNow on a reliable schedule tailored to their operational requirements. The retry options provide robustness against transient errors, while encoded queries and scripts enable precise data targeting, reducing unnecessary processing. Scheduling flexibility, including business calendar integration, aligns extraction jobs with business cycles and events, increasing relevance and efficiency. Overall, these fields empower customers to maintain up-to-date ERP data within ServiceNow, supporting better decision-making and streamlined workflows.

    The Scheduled extraction form in Zero Copy Connector for ERP (Enterprise Resource Planning) enables you to create and edit jobs to extract data at regular intervals.

    For process details, see Create a scheduled extraction in Zero Copy Connector for ERP.

    Table 1. ERP scheduled extraction table fields
    Field Description
    Name A unique name that identifies this scheduled extraction.
    Active Option that indicates the scheduled extraction is active and should be executed at the specified frequency and time.
    Extraction table Name of the ERP extraction table from which to pull data.
    ERP system ERP system that the extraction table is linked to. The system must already be configured.
    Application This field is read only and is filled in automatically with Zero Copy Connector for ERP.
    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 runs again on the next retry. For more information, see Import sets key concepts.
    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:

    Sample encoded query.

    For more information, see .
    Generate encoded query script Generate an encoded query script to use on the extraction table to fetch the data. For example:

    Sample generated encoded query script.

    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).
    After extraction 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, check if the job is already scheduled before or after another job. Only jobs that won't create a loop are permitted.
    Run as Specify the user name to associate with the scheduled extraction.
    Run When to run the extraction.
    • 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 in the time zone specified.
    • Weekly: In Day, 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 in the time zone specified.
    • Monthly: In Day, select the day of the month to run the scheduled extraction. Specify the next scheduled start in hours, minutes, and seconds to repeat monthly. For example, selecting 5 and specifying 03:00:00 starts the scheduled extraction the fifth day of the next month at 3:00 am and then every subsequent fifth of the month at 3:00 am in the time zone specified.
    • Periodically: In Repeat Interval, select the days, hours, minutes, and seconds to repeat periodically. For example, start the scheduled extraction every 3 days, 4 hours, 30 minutes, and 30 seconds.
    • Once: In Starting, click inside the field, select a day and type in a time for the extraction to run once.
    • On Demand: Select the Run now button (next to the Save button) to run the extraction immediately.
    • Business Calendar:Entry Start: Runs on the starting entry dates for the business calendar that you select in the Business Calendar field. A scheduled job runs for the starting date of each of the business entries that you defined for the business calendar. For example, if the business calendar represents a fiscal year, and the starting date of each entry is a fiscal month, the scheduled job runs on the first day of each month.
    • Business Calendar:Entry End: Runs for the ending date for the business calendar that you select in the Business Calendar field. This selection runs in the same manner as Business Calendar:Entry Start, but for the end dates of the associated business calendar entries.
      Note:
      To learn more about creating and using business calendars and defining business calendar entries, see Creating business calendars.
    Time Time, in 24-hour format, for when the scheduled extraction should run.
    Time zone Specify the time zone for the scheduled extraction.