Product Imports History
Purpose: Use the Product Imports History screen to review summary information on the product, product location, location, and UPC imports that have taken place for a system. See Importing Items/Products, Inventory, Barcodes, Images, and Locations into the Database for an overview of the import process.
Used for the Routing Engine module.
How to display this screen: Click the history icon () next to a Product Import entry for a system at the View Active Schedules screen.
Note:
- Available if Use Routing Engine is selected at the Tenant screen. Only users with View Active Schedules authority can display this screen. See the Role Wizard for more information.
- Available only if the Product Import is currently enabled, or if there are any product import records that have not been purged.
- If the Product Imports History screen was already open in another tab when you clicked the history icon, you advance to this screen with the product imports history of the previously-selected organization and system displayed.
- History is retained for the number of days specified in the Job History retention setting at the Tenant-Admin screen.
Reviewing import errors:
- Reports: Use the Location Import Errors Report, Product Import Errors Report, and Product Barcode Import Errors Report to review any errors that occurred related to location, product, or barcode imports.
- Error files: Errors related to product location imports are tracked in an import error flat file that is available through the file storage API. See Product Location Import Error Files for more information.
Note:
Some errors that can occur from the data in the import file are not written to the related import database table, so in that case the error is noted only in the error file or record, and not on the related report, for example: an invalid number of columns in the import file, a numeric field that contains alphabetical data, or a date that is not formatted correctly.Options at this screen
Option | Procedure |
---|---|
Search for an import process |
Use the Job Number, Start Date, or Status fields to restrict the displayed imports to those that match your entries and click Search:
Note: You cannot select a status of Paused; however, a job stays in this status only briefly when it switches to another server to complete running. |
Understand general errors |
If an error occurred for an import process itself, it is displayed in the Error field. |
Fields at this screen
Field | Description |
---|---|
Summary fields: | |
Organization |
The code identifying the organization associated with the system that generated the import process. The organization description is to the right of the organization code, separated by a hyphen. |
System |
The code identifying the system that generated the import process, either because you ran it on demand from the Schedule Jobs screen, or it was scheduled at that screen. This is the system you selected at the Schedule Jobs screen. The system description is to the right of the system code, separated by a hyphen. |
Search fields: | |
Job Number |
A unique ID number assigned by Order Broker to identify an import process. Optionally, enter a number and click Search to display this import process only. |
Start Date |
Optionally, enter a date to display imports that started on that date. |
Status |
Optionally, select a status of:
|
Results fields: | |
Job Number |
A unique ID number assigned by Order Broker to identify an import process. Note: An import is associated with a single job number, regardless of whether Order Broker breaks it out into multiple batches for processing. |
Start Date |
The date and time when the import process started. |
End Date |
The date and time when the import process ended. |
Duration |
The amount of time, in minutes and seconds, that the import process ran. HH:MM:SS format, but displayed in MM:SS format if the import took less than an hour. |
Submitted By |
Indicates how to import was submitted. This could be the ID of the user who submitted or scheduled the process, or the client ID used to authenticate the run job API request message. SYSTEM is displayed here if the job ran successfully through a schedule; however, if a scheduled job was rejected, the ID of the user who scheduled the job is displayed. |
Status |
Indicates whether any product or product location errors occurred for the import process:
|
Error |
Indicates the general error, if any, that prevented the product import from taking place. If this field indicates Error importing file. See error file for details, this could indicate that at least one of the import files included invalid data, such as:
In this case, the process moves the file to the error container in the FILE_STORAGE table. This field indicates Error importing from OCDS. See error log for details if errors occurred during OCDS Imports. See that help topic for more information. Note: General errors are not included in the Product Import Errors Report, and Product Barcode Import Errors Report, in the case of the Location Import Errors Report, some general errors are included on the report with the description Location Import Failed - Other Error. |
Type |
Indicates that the top row for the following columns lists the number of records Processed, while the bottom row for the following columns lists the number of records Errored. |
Product Records |
Top row: The total number of product records included in the import process, including any records that were in error. Bottom row: The total number of product import records that were in error. If there were any errors, you can use the Product Import Errors Report to review them. |
Inventory Records |
Top row: The total number of product location records that included in the import process, including any records that were in error. Bottom row: The total number of product location import records that were in error. See Product Location Import Error Files for more information. |
Location Records |
Top row: The total number of location records included in the import process, including any records that were in error. Bottom row: The total number of location import records that were in error. If there were any errors, you can use the Location Import Errors Report to review them. |
UPC Records |
Top row: The total number of product UPC barcode records included in the import process, including any records that were in error. Bottom row: The total number of product UPC barcode import records that were in error. If there were any errors, you can use the Product Barcode Import Errors Report to review them. |
Image Records |
Top row: The total number of product image records included in the import process, including any records that were in error. Product images are displayed in Store Connect. Bottom row: The total number of product image import records that were in error. A product import image record could be in error because the URL for the image was not formatted correctly. See Importing Items/Products, Inventory, Barcodes, Images, and Locations into the Database for an overview. |