Location Import Errors Report

Purpose: Use the Location Import Errors Report to review errors related to locations that occurred during the import into Order Broker using the process described under Importing Locations through File Storage API. You can schedule imports or run them on demand through the Schedule Jobs screen.

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

Invalid address? The import process creates a location record even if the address specified in the import file is incomplete or invalid. In this case, the location is not listed on the errors report. If the location is not included as expected in inventory search results or order assignments, you can use the Edit Location to verify or correct the address.

Correcting import errors: See Understanding location import errors for more information.

Database table: The errors listed on this report are from the location_import table. Records in that table with a processed code of 40 are not included in the report, as these updates processed successfully.

For more information: See Importing Locations 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 Location 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 location imports that failed during this range of dates. See Rolling Dates for more information; or,

      • From and To dates: Enter or select the first and last dates to include. The report includes location imports that failed during this range of dates. The From and To dates can be the same, and can be the current date.

      Note:

      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.
      • 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.
  4. Click Run Report.

For more information: See Viewing generated reports.

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:

    Location code: The location to import from the external system.

    Location type: The location type assigned to the location, describing one or more locations within an organization. Each location type indicates the location category (store, warehouse, or vendor), and can also provide additional information, such as “East Coast Stores” or “Outlet Stores.”

    • Name: The name of the location.

    • City: The city for the location’s address.

    • State: The state for the location’s address.

    • Postal: The postal code for the location’s address.

    • Country Code: The country code for the location’s address.

    • Error: See Understanding location 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 Date Format settings defined for the organization control the formatting of the report.

Understanding location import errors

Error Code Error Message Possible Reasons

10

System Record Not Found

The System code specified is invalid. This error does not occur for OCDS Imports, because the import is always scheduled or run on demand for a specific system, and this is the system code that is used.

An invalid system code can also occur if the field exceeded the maximum allowed length. In this case, the description of the error in the error file is System code length.

55

Location Type Code Invalid

The location type code specified is invalid. This error does not occur for OCDS Imports, because the import is always scheduled or run on demand for a specific store or warehouse default location type, as specified at the OCDS Integration tab of the System screen. In this case, the description of the error in the error file is Location_type_code length.

56

Locations Import Failed - Other Error

Can indicate that a field exceeded the maximum allowed length. In this case, the description of the error is included in the error file, for example Address_line one too long.

Also, if a single-position code, such as the Active flag or the Delivery flag, was not set to a valid value, an example of the description of the error in the error file is Q is Invalid for Column Active.

The following errors are not included on the report, but they are included in the import error file.

71

Missing Location Name

The location Name is missing and is a required field. This error occurs if the location name is passed as blank from OCDS.

72

Missing Location Code

The location code is missing and is a required field. This error occurs if the location code is passed as blank from OCDS.

73

Prov,Country,Postal combination invalid

There was a problem with the state or province, country, and postal code or zip code for the location.

75

The Address combination is invalid.

An error was returned through the Oracle Maps Cloud Service; however, the location was still created. This error can occur, for example, when a five-position postal code is passed for a Canadian address.

Note:

No errors are listed on the report if the number of columns in the flat file is invalid. In this case, a general error is listed at the Product Imports History screen. See Importing Locations through File Storage API for background.