Product Import Errors Report

Purpose: Use the Product Import Errors Report to review errors related to products or system products 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 products and system products not listed: Only product import records that resulted in error are listed on the report. For example, if the import process included 500 products or system products, and 495 products or system products were created or updated without error, the report lists the 5 errors.

Correcting import errors: The best way to correct import errors is to correct the product record in the integrated system. The next time you process imports for the system, the product will be created or updated correctly. Otherwise, if you attempt to create or update the product using the Order Broker screens, the record cannot be updated correctly with each future scheduled import. You can use the Schedule Jobs to schedule the next import process, or to run it on demand.

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

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, a numeric field that contains alphabetical data, or a date that is not formatted correctly.

For more information: See the Importing Products, System Products, and Item Image URLs through File Storage API or OCDS Imports.

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:

Click the plus sign next to the Operations folder in the left-hand navigation pane.
Highlight the Product Import Errors Report. The center of the screen displays the related Report Options.
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 orders that became fully unfulfillable or partially unfulfillable during this range of dates. See Rolling Dates at the Reports screen for more information; or,
  - From and To dates: Enter or select the first and last dates to include. The report includes orders that became fully unfulfillable or partially unfulfillable during this range of dates. The From and To dates can be the same, and can be the current date.
  Note:
  Product import activity is retained only for the Days to Keep Errorsspecified at the Schedule Jobs screen. For example, if the Days to Keep Errors is set to 7, you cannot generate the report for any dates earlier than the last 7 days.
- 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.
- Email List: Optionally, enter one or more valid email addresses, separated by semicolons (;), to receive the report.
  
  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.
Click Run Report.

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

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

Truncated data? If the data in any column exceeds the allotted width, it is truncated. For example, if the department description exceeds the allotted width of that column, any additional characters beyond that width are omitted. The specific number of characters that fit in each column varies because different characters have different widths: for example, a W is wider than an I.

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:
- Product code: Identifies the item in the default system.
- System product code: The system product code identifying the product in the external system. The system product code might differ from the product code if the external system is not the default system for the organization.
- Master Style: Optional field. Order Broker updates this field for the product only if it passed from the default system.
  
  Note:
  Normally, you would never change the master style for a product in Order Broker.
- product Name: Order Broker updates this field for the product only if it is passed from the default system. Product names can be 1 to 40 positions in length.
- Department: The description of the product's department. Order Broker updates this field for the product only if it is passed from the default system. The department description can be 1 to 40 positions in length, and is informational only. Optional field.
  
  Note:
  If your default system is an Order Management System company, this field is the description of the item/SKU’s Long SKU Department. Long SKU departments are used to identify items within a retail hierarchy.
- Class: The description of the product's class. Order Broker updates this field for the product only if it is passed from the default system. The class description can be 1 to 40 positions in length, and is informational only. Optional field.
  
  Note:
  If your default system is an Order Management System company, this field is the description of the item/SKU’s Long SKU Class. Taken from the base item rather than the SKU if this is a SKU’d item. Long SKU classes can be used together with long SKU departments to identify items within a retail hierarchy.
- Category: The description of the product’s category. Order Broker updates this field for the product only if it is passed from the default system. The category description can be 1 to 40 positions in length, and is informational only. Optional field.
  
  Note:
  If your default system is an Order Management System company, this field is the description of the item/SKU’s Long SKU Division. Long SKU divisions can be used together with long SKU departments and classes to identify items within a retail hierarchy.
- Error: See Understanding product import errors.

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 import errors

Error Code	Error Message	Possible Reasons
10	`System Record Not Found`	The System code provided is not a valid system in Order Broker. This error does not occur for OCDS Imports, because the import is always scheduled or run on demand for a specific system.
11	`Product description required`	The product Name provided was a blank space and did not include any additional information. The product description is required regardless of whether the external system is the default system; however, the information is used only to create or update the product record itself.
12	`Duplicate System Product Code`	There was more than one entry for the same system product. In this case, the product is not created or updated. This error does not occur for OCDS Imports.
13	`Empty Product Code`	No product_cd was specified. This error does not occur for OCDS Imports, because the product code is always passed.
14	`Empty System Product Code`	No system_product_cd was specified for the product. This error does not occur for OCDS Imports, because the same code is used for the product code and the system product code.
15	`System Product / Product Code mismatch`	The system product code and product_cd code provided were not the same, and the external system is the default system. This error does not occur for OCDS Imports, because the same code is used for the product code and the system product code. If Order Management System is the default system, the OROB Product Code ID (K66) system control value should be set to IT.
20	`Primary system product not defined`	The external system is not the default system, and there is no existing product matching the Product code provided. When this error occurs and there are also any product locations included in the import, each of the product location import records will be in error with an error reason of `Product not defined for system`. Large number of primary system product errors? One reason why you might see a large number of records with this error is if the product import for this system ran before the product import for the default system for the organization. By scheduling the import for the default system before the other systems, you reduce the possibility that Order Broker will not be able to create the system product because the product does not exist.
76	`Invalid URL Format`	The URL passed for an item image was not formatted correctly. The URL should be formatted as `https://www.example.com/folder/image.png`, where: `http` or `https` is the protocol `www.example.com` is the domain or server name `folder` is a folder or subfolder where the image is found `image.png` or `image.jpg` is the name of the image The import does not validate that an image is found at the specified URL.
77	`Invalid URL length`	The URL passed for an item image exceeded 255 positions.