Zero Copy Connector for ERP scheduled extraction field descriptions
Summarize
Summary of Zero Copy Connector for ERP scheduled extraction field descriptions
The Scheduled Extraction form in the 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 integrating ERP data into ServiceNow efficiently and reliably, enabling automated and recurring data synchronization.
Show less
Key Features
- Name and Activation: Assign a unique identifier to each scheduled extraction and activate it to run at specified times.
- Extraction Table and ERP System: Select the ERP extraction table and associated, pre-configured ERP system from which to pull data.
- Retry Mechanism: Configure up to 10 retries on job failure, with customizable wait times between retries. Retries reprocess the entire job to ensure data consistency.
- Query Filtering: Use either an encoded query string or an encoded query script to filter the data extracted. The script takes precedence if both are provided, allowing advanced data selection.
- Job Sequencing: Define dependencies by specifying another job that must complete before the current extraction starts, preventing execution loops.
- User Context: Specify the user identity under which the extraction job runs, supporting appropriate permissions and auditing.
- Scheduling Options: Flexible scheduling includes daily, weekly, monthly, periodic intervals, one-time runs, immediate on-demand execution, or alignment with business calendar entries (start or end dates).
- Time and Time Zone: Set the exact time and corresponding time zone to ensure the extraction runs accurately according to your business requirements.
Practical Use for ServiceNow Customers
This scheduled extraction setup empowers customers to automate ERP data imports into ServiceNow, maintaining up-to-date information without manual intervention. By configuring retries and filters, customers can ensure robustness and precision in data extraction. Scheduling flexibility, including integration with business calendars, helps align data updates with organizational processes and timelines.
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.
| 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: 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: 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.
|
| Time | Time, in 24-hour format, for when the scheduled extraction should run. |
| Time zone | Specify the time zone for the scheduled extraction. |