Zero Copy Connector for ERP scheduled extraction field descriptions

  • Release version: Yokohama
  • Updated January 30, 2025
  • 2 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 Zero Copy Connector for ERP allows ServiceNow customers to create and manage jobs that extract data from ERP systems at defined intervals. This capability is essential for automating data synchronization between ERP and ServiceNow, ensuring timely and accurate data availability.

    Show full answer Show less

    Key Fields and Their Practical Use

    • Name: Assign a unique identifier to each scheduled extraction job for easy reference and management.
    • ERP system: Select the pre-configured ERP system linked to the extraction table, ensuring the extraction targets the correct data source.
    • Extraction table: Specify the exact ERP extraction table from which data is pulled, enabling precise data retrieval.
    • Frequency: Define how often the extraction runs with flexible scheduling options:
      • Hourly: Runs repeatedly every hour at the specified minutes and seconds.
      • Daily: Runs once daily at the scheduled time.
      • Weekly: Runs weekly on a selected weekday and time.
      • After Completed Job: Chains the extraction to start after another active job finishes, avoiding scheduling loops.
    • Next scheduled start: Set the exact start time in 24-hour format for the next job execution.
    • Active: Toggle to enable or disable the scheduled extraction job.
    • Maximum no of retries on error: Configure up to 10 retry attempts if a job fails, which reruns the entire job from the start, improving robustness but potentially increasing processing time.
    • Extraction will retry after: Specify the wait time before retrying a failed job, allowing control over retry intervals.
    • Encoded query: Input a filter string to limit extracted data, optimizing extraction scope.
    • Generate encoded query script: Provide a script that supersedes the encoded query string, offering advanced filtering capabilities for data extraction.

    Practical Benefits for ServiceNow Customers

    By configuring scheduled extraction jobs with these fields, customers can automate ERP data imports efficiently, control execution timing, handle errors gracefully through retries, and tailor data selection via encoded queries. This setup ensures seamless and reliable integration between ERP systems and ServiceNow, supporting accurate reporting and operational workflows.

    The Scheduled extraction form in Zero Copy Connector for ERP 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.
    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.
    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.
    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 Encoded query strings.
    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).