ERP Data Hub scheduled extraction field descriptions

  • Release version: Xanadu
  • Updated October 17, 2024
  • 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 ERP Data Hub scheduled extraction field descriptions

    The Scheduled Extraction form in ERP Data Hub allows ServiceNow customers to create and manage jobs that extract ERP data at regular intervals. This feature enables automated and configurable data pulls from ERP extraction tables, supporting efficient data integration and synchronization.

    Show full answer Show less

    Key Features

    • Name: Assign a unique identifier to each scheduled extraction job for easy management.
    • ERP System: Select the preconfigured ERP system linked to the extraction.
    • Extraction Table: Choose the specific ERP extraction table from which data will be retrieved.
    • Frequency: Define how often the extraction runs:
      • Hourly: Runs at a specified time every hour.
      • Daily: Runs once daily at a specified time.
      • Weekly: Runs weekly on a selected weekday and time.
      • After Completed Job: Starts after the completion of another active job, preventing loops.
    • Next Scheduled Start: Sets the exact time for the next extraction execution (24-hour format).
    • Active: Indicates if the scheduled extraction is enabled and should run as configured.
    • Maximum Number of Retries on Error: Defines how many retry attempts (0-10) to make if a job fails, with each retry rerunning the entire job.
    • Extraction Will Retry After: Specifies the wait time before retrying extraction after an error, applicable if retries are enabled.
    • Generate Encoded Query Script: Allows entering a script that takes precedence for fetching data, enabling advanced query customization.
    • Encoded Query: Allows pasting a filter string to limit data extraction based on specific criteria.

    Key Outcomes

    By configuring scheduled extraction jobs with these fields, ServiceNow customers can automate ERP data retrieval reliably, control retry behavior on errors, and customize data filtering through encoded queries. This setup enhances data accuracy and timeliness in integrations between ERP systems and ServiceNow platforms.

    The Scheduled extraction form in ERP Data Hub enables you to create and edit jobs to extract data at regular intervals.

    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.
    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).
    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.