Documentation for ProTrack Warehouse 7.6.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

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:

  1. Assuming all facilities are set up already, import floors.
  2. Import Aisle Paths.
  3. Import Travel Paths.
  4. Generate Nodes via the Facility Layout Java applet screen.
  5. Import Segments.
  6. Import Locations (Levels are imported with Locations simultaneously).
  7. Build a pre-cache of node-to-node travel.
  8. OPTIONAL: Build a pre-cache of location-to-location travel.

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

Info

  • Remove the “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.


Preparing ProTrack Warehouse for XYZ Import

Locations should be imported into a Test Environment, and then use the Location Move Process to move the locations from Test to Production Environments. The process of moving data from Test Environment to Production should be completed by a database admin (DBA), and is described in the ProTrack Warehouse Technical Guide.

The location data elements can only be imported when ProTrack Warehouse is idle and there is no background processing. Again, this importing should be done into a Test Environment, and then moved into the Production Environment. The following process describes preliminary procedures to prepare the Test Environment for import:

  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

Once these processing queues have been emptied, proceed with importing of XYZ data elements.

After all location data elements have been imported and changes have been validated, restart the ProTrack Warehouse background processing.

  1. Re-start the WMS Import process.
    1. Go to Configuration > System > Scheduled Tasks.
    2. Set Topic WMS Import to Yes, and click .
  2. Go to Monitor > Scheduled Request.
    1. Search by ALL Topics.
    2. Ensure that the Topic WMS Import is moving from RFP to INP.


Common Import Errors

When importing a floor, the most important thing to consider is the size. All other components that are part of the layout will error out if they do not fall inside the coordinates of the floor. It is recommended that you know the coordinates of most of your components before deciding the size of the floor. That is not to say the size cannot be changed at any point, but doing your research beforehand can save a great deal of time and effort down the road.

Floors

  • Duplicate Floor ID
  • Missing a mandatory field
  • Data in the wrong format
  • Sending a non-existent Facility ID
  • Same start and end coordinates

Aisle Paths

  • Duplicate Aisle Path ID
  • Missing a mandatory field
  • Data in the wrong format
  • Same start and end point
  • Invalid Floor ID
  • One point of the Aisle Path falls off the floor
  • Two Aisle Paths are identical
  • An Aisle Path with the same coordinates as a Travel Path

Travel Paths

  • Duplicate Travel ID
  • Missing a mandatory field
  • Data in the wrong format
  • Start or End points do not reside on existing nodes.
  • Invalid floor

Segments

  • Duplicate Segment ID
  • Missing a mandatory field
  • Data in the wrong format
  • Invalid Aisle ID
  • A Segment that crosses a Node
  • A Segment goes past the end point of its associated Aisle Path, either due to the length or inset of the Segment
  • A Segment goes off the floor

Locations

  • 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 match up with the placement of the Segment being sent with the Location
  • No labels

null

Copyright © 2015 - present. TZA Confidential. All rights reserved.