Product Barcode Import Errors Report

Purpose: Use the Product Barcode Import Errors Report to review errors related to product UPC barcodes that occurred during the import into Order Broker using the process described under Importing Items/Products, Inventory, Barcodes, Images, and Locations into the Database, or through OCDS Imports. You can schedule imports or run them on demand through the Schedule Jobs screen.

Successfully imported product barcodes not listed: Only product UPC barcode import records that resulted in error are listed on the report. For example, if the import process included 500 product UPC barcodes, and 495 product UPC barcodes were created or updated without error, the report lists the 5 errors.

Correcting import errors: See Understanding product UPC barcode import errors for more information.

Database table: The errors listed on this report are from the PRODUCT_BARCODE_IMPORT table.

For more information: See Importing UPC Barcodes through File Storage API.

Used for the Routing Engine module.

How to generate this report: Available if Use Routing Engine is selected at the Tenant screen. At the Run Reports screen:

  1. Click the plus sign next to the Operations folder in the left-hand navigation pane.
  2. Highlight the Product Barcode Import Errors Report. The center of the screen displays the related Report Options.
  3. Select:
    • Organization: The organization to include on the report. Defaults from the organization associated with the Default Shipping System from your user profile, but you can override this default. The Data Formats defined for the organization are used on the report.
    • Date range: Select either:
      • Rolling Dates: One of the date ranges available from this field to include errors that occurred during the range of dates. See Rolling Dates at the Run Reports screen for more information; or,
      • From and To dates: Enter or select the first and last dates to include. The report includes errors that occurred during this range of dates. The From and To dates can be the same, and can be the current date.

        Note:

        If the error occurred earlier than the Days to Keep Errors specified for the Product Import at the Schedule Jobs screen, it is not retained in the table or eligible to print on the report.
    • Export to PDF: Select this option to generate a PDF version of the report that you can review in a PDF viewer.
    • Export to Excel: Select this option to generate the report in .XLSX format, which you can open in a spreadsheet application.

      Note:

      You must select either Export to PDF or Export to Excel, or both.

      Note:

      If you select both Export to PDF and Export to Excel, each email recipient receives two separate emails, each with a version of the report attached.
    • Email List: Optionally, enter one or more valid email addresses, separated by semicolons (;), to receive the report.
  4. Click Run Report.

For more information: See Viewing generated reports at the Run Reports screen.

Language and formats: The language, date, time, and number formats on the report are from the Data Formats defined for the organization.

Contents:

  • Organization Name and report title
  • Report Criteria heading:
    • Locations: All.
    • Date Range: The range of dates entered at the Run Reports screen, or calculated based on the Rolling Dates selection at the Run Reports screen or the Schedule Report window.
  • Import ID. Each import ID starts on a new page.
  • System code
  • For each error with the same Import ID:

The footer on each page of the report lists:

  • the date and time when the report was generated
  • the current page number and total number of pages (for example, Page 1 of 6)

The Data Formats defined for the organization control the formatting of the report.

Understanding product UPC barcode import errors

Error Code Error Message Possible Reasons

10

System Record Not Found

The System code specified is invalid.

15

System Product/Product Code mismatch

The system product code does not exist for the System code specified in the import file. This product barcode import error can be the result of a product import error; for example, it can occur if:

  • you created a new product in your integrated systems, and did not run the import process for the default system before the other systems in the organization
  • the import process included product barcodes but not the corresponding products or system products
  • there was other invalid data in the product import that prevented the import process from creating the product or system product

58

Invalid Barcode Type

A barcode type of UPC-A or EAN-13 was not specified.