) for a system at the Schedule Imports screen.Purpose: Use the System Import Schedule screen to work with the product import schedule for an integrated system, or to run the import process on demand.
Used for the Routing Engine module.
How to display this screen: Click the schedule icon () for a system at the Schedule Imports screen.
Note:
• Available if Use Routing Engine is selected at the Tenant - Admin screen. Only users with Schedule Imports authority can display this screen. See the Role Wizard for more information.
• If the System Import Schedule screen was already open in another tab when you clicked the schedule icon, you advance to this screen with the schedule for the previously-selected system displayed.
In this topic:
• Import Setup and Required Data
• Options at the System Import Schedule screen
Import Setup and Required Data
You can use the System Import Schedule screen to set up a schedule for importing products, system products, locations, product locations, and UPC barcodes. You can also use this screen to run the import on demand.
Process overview: See Importing Items/Products, Inventory, Barcodes, and Locations into the Database for an overview.
Import products from the default system first to prevent import errors: It is important to schedule the product import for the default system before the other systems in the organization. Order Broker requires that the product exist in the default system before you can create the system products or product locations for the other systems.
Important: Oracle recommends that you run this job daily at a time when demands on the system are limited, and when it does not interfere with the database backup.
Additional consideration when scheduling import processes for systems:
• Oracle recommends that you allow about 30 minutes between scheduled import processes to help make sure that each process completes before the next one begins.
• In a multi-server environment, a copy of each import file must be in the Product Import Files folder specified at the Tenant - Admin screen on each server in order for the import to take place. This must be a shared folder. You need to make sure that the files are propagated on all servers, or are in a shared folder that is available to all servers.
• The dates and times are based on the retailer’s time, which may be different from your local time zone.
Note: Each import is optional. For example, you can run the import for products and product locations without also importing locations or UPC barcodes. When the import runs, it includes any import files it finds for the system in the Product Import Files folder specified in the Data Folder Settings area of the Tenant - Admin screen.
For more information: See:
• Location imports: Importing Locations and Location Import Errors Report
• Product and system product imports: Importing Products and System Products and Product Import Errors Report
• Product location imports: Importing Product Locations
• Product UPC barcode imports: Importing UPC Barcodes and Product Barcode Import Errors Report
When the import process is complete, Order Broker sends an email to the email address(es) specified at the Administrative email field at the Event Logging screen if the Email Notifications flag for the Location Product Import option is set to Administrator.
The language used for the email is based on the Language specified for the organization, and the formatting of dates, times, and numbers is also based on the organization-level settings. See the Edit Organization screen for more information.
Sample email contents:
|
****ATTENTION****
Your Product Import Process has Failed. |
|
|
System Code |
store |
|
Import ID |
201 |
|
Date/Time File Finished |
2016-11-26 09:37:53.762 |
|
Uploaded By |
example |
|
# of Product Records |
850 |
|
# of Product Records In Error |
12 |
|
# of Inventory Records |
1,445 |
|
# of Inventory Records In Error |
14 |
|
# of Location Records |
1,300 |
|
# of Location Records In Error |
14 |
|
# of Upc Records |
0 |
|
# of Upc Records in Error |
0 |
|
Please do not respond to this message.
--Order Broker |
|
Information in this email includes:
• Success or failure: The email indicates that the process failed if any product, product location, location, or UPC records failed to update; otherwise, it indicates a success.
• System code: the system scheduled for import, or the selected system when you ran the import on demand.
• Import ID: A unique ID number assigned by Order Broker to identify an import process. This number is displayed at the System Imports History screen and listed on the Location Import Errors Report, Product Import Errors Report, and Product Barcode Import Errors Report.
• Uploaded By: the user ID of the person who scheduled the import process, or ran it on demand.
• # of Product Records: The total number of product records that were successfully created or updated as a result of the import process.
• # of Product Records in Error: The total number of product import records that were in error for this import process.
• # of Product Location Records: The total number of product location records that were successfully created or updated as a result of this import process.
• # of Product Location Records in Error: The total number of product location import records that were in error for this import process.
• # of Location Records: The total number of location records that were successfully created or updated as a result of this import process.
• # of Location Records in Error: The total number of location import records that were in error for this import process.
• # of Upc Records: The total number of product UPC barcodes that were successfully created or updated as a result of this import process.
• # of Upc Records In Error: The total number of UPC barcodes that were in error for this import process.
Always generated? If the Email Notifications flag for the Location Product Import option at the Event Logging screen is set to Administrator, Order Broker generates this email regardless of whether the import process ran because you scheduled it, or you ran it on demand.
Negative number? A negative number of records generally indicates that an error occurred. Check the server log for more information.
If number of records and number of records in error are both 0: The email lists a number of records and a number of records in error as 0 if there was no import file to process. This situation might occur if:
• you did not import a particular type of record; for example, there were no product barcodes to import, or
• the name of an import file did not match the naming convention; for example, a product barcode file was named PRODUCT_BARCODE.TXT (no system specified) or PRODUCT_BARCODE_SYS.txt (the txt extension was lowercase).
• In a multi-server environment, the import file was not propagated to all servers.
In any of these cases, the email indicates that the import was successful.
For more information: See the System Imports History screen and the Location Import Errors Report, Product Import Errors Report, and Product Barcode Import Errors Report for more troubleshooting information related to the product import process.
Note: Some errors that can occur from the data in the flat import file are not written to the related import database table, so in that case the error is noted only in the error file and not on the related report; for example: an invalid number of columns in the flat file or an empty file.
Options at the System Import Schedule screen
Import products from the default system first to prevent import errors: It is important to schedule the product import for the default system before the other systems in the organization. Order Broker requires that the product exist in the default system before you can create the system products, product locations, or locations for the other systems.
Additional considerations when scheduling import processes for systems:
• Do not schedule more than one import at a time.
• Oracle recommends that you allow about 30 minutes between scheduled import processes to help make sure that each process completes before the next one begins.
|
Option |
Procedure |
|---|---|
|
schedule the import for an integrated system |
1. Select the Enabled flag if it is not already selected. 2. Select each day of the week when the process should run, or select Daily to run the process every day. 3. Enter the time, in HH:MM format (military time), when the process should run for all selected days. 4. Optionally, change the Days to Keep Errors to any number from 1 to 99. 5. Click Save. Note: The dates and times are based on the retailer’s time, which may be different from your local time zone. |
|
review or change the import schedule for a system |
Change any of the fields on this screen, as described under Fields at this screen, and click update. |
|
import products and locations on demand |
1. Select the Run now flag. 2. Click Save. 3. Click OK at the confirmation window. Note: You need to have a schedule set up in order to run the import on demand. You can review the import process at the System Imports History screen, and you can review errors through the Product Barcode Import Errors Report, Product Import Errors Report, and Location Import Errors Report. |
|
Field |
Description |
|---|---|
|
Organization |
The code and description of the organization. |
|
System |
The code identifying the system. |
|
Name |
The description of the system. |
|
Schedule |
|
|
Indicates whether Order Broker should automatically run the import process based on the schedule defined at this screen. Note: If this field is unselected, you cannot run the import process, and the remaining fields on this screen are display-only; however, if you change this field from selected to unselected, the screen retains your settings so that you can easily return the system to its previous import schedule. |
|
|
Enter the number of days to retain errors in the product_import, product_location_import, location_import, and product_import_log tables after an import process completes. Each time you run the import process for a system, it deletes these records if the indicated number of days has passed. Once these records are deleted, the import process is no longer listed at the System Imports History screen, and you cannot review errors through the Location Import Errors Report, Product Import Errors Report, and Product Barcode Import Errors Report. Note: The process also creates records in the import tables for records that are not in error. These records are eligible to be cleared from the import tables the next time an import process runs for the system. Enter a number from 1 to 99. Required if the Enabled flag is selected. Default = 7. |
|
|
Day of Week |
Use these fields to select the day(s) of the week and the time of day to have Order Broker run the import process: • Day: Select one or more days of the week (Sunday through Saturday), or select Daily to automatically select all days. At least one day is required if the Enabled flag is selected. • Time: Enter the time to begin the import process for all selected days. Required if any day is selected. Note: The dates and times are based on the retailer’s time, which may be different from your local time zone. |
|
Last run |
|
|
Date |
The last date and time when the import process ran, either because it was scheduled or you ran it on demand. This information is stored in the system table. |
|
Run Now |
Select this flag to run the import process on demand. The process runs after you click OK at the confirmation window, and then click Save to accept your entries at the screen. Note: You need to have a schedule set up in order to run the import on demand. |
|
Last updated |
|
|
Date |
The last date and time when you updated the information at this screen. |
|
By |
The user ID of the person who last updated the information at this screen. |
________________________________
Copyright © 2018, Oracle and/or its affiliates. All rights reserved.
Legal
Notices