Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  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