Versions Compared

Old Version 8

changes.mady.by.user Angelica Domingo

Saved on

compared with

New Version 9

changes.mady.by.user Angelica Domingo

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

This screen will provide details to how XYZs should be imported to configure a proper layout of the facility.

Sequence of Operations

...

– Importing XYZs Start-to-Finish

The process of importing XYZs can be summarized as follows:

...

Refer to Data Import to learn how to configure ProTrack Warehouse in order to import each XYZ component data.

Info
titleInfo
  • Remove the "header" “header” row(s) on each worksheet.
  • Save each worksheet as its own separate CVS format file.
  • Do not comingle floor related data elements within the same file (i.e., locations for Facility 1 and Floor 1 should be in the same file, and should not include locations for Facility 1 and Floor 2).
  • Each data element (Floor, Aisle Path, etc.) needs to have its own Directory to import. Cannot import Floor data in the same Directory in which Aisle Paths are being imported. These must be configured even if specific data elements are not going to be imported.
  • Importing locations requires that ProTrack Warehouse is idle (no background processing) during the import process.

...

  1. If WMS files are also imported into the Test Environment (uncommon), one-hour prior to importing locations set WMS Import process to No
    1. Ensure there are no WMS files ready to process
      1. The main and Scheduled WMS directories should be empty
    2. Via the ProTrack Warehouse UI go to Configuration - System - – Scheduled Tasks
    3. Set Topic WMS Import to No, and Save
  2. Allow background processing to complete
    1. Via the ProTrack Warehouse UI go to Monitor - – Scheduled Request.
    2. Search by ALL Topics. Ensure all Topics are in one of these Statuses (if they are not then do not proceed with location import)
      1. WMS Import in RFP only
      2. All others
        1. IGN
        2. ERR

...

  • Duplicate Location ID
  • Missing a mandatory field
  • Data in the wrong format
  • Invalid Floor ID or Segment ID
  • Coordinates of the Location fall off the Floor
  • A Location shares coordinates with a node
  • Sending Segment ID when Segment ID is not set up in the interface
  • The coordinates of a Location don't don’t match up with the placement of the Segment being sent with the Location