Transferring XYZs

The following migration process is to be completed by a database admin (DBA).

The Move_LocationData_sp makes it easy to move XYZ data from one database to another while maintaining the integrity of the data. This functionality allows the user to configure the XYZs for new facilities or make changes to the configuration of existing facilities on a test environment separate from the production environment. This practice provides the security that any unintentional changes will not have a negative effect on the production standard calculations. Additionally, the XYZ data transfer ensures that ProTrack Warehouse does not process incorrectly any of the production data resulting from importing XYZ data while simultaneously importing WMS data.

XYZ Data Transfer - Overview

There are two separate stored procedures that may be run to transfer data from a Test Environment to a Production system. The first (Move_LocationData_sp) is used to move the actual XYZ component data. The second only moves the two caches. Depending on the maintenance scenario, it may only be necessary to move the cache.

The Move_LocationData_sp copies all XYZ component data from one database to another. The stored procedure moves data from the following tables:

1. facility
2. floor
3. aisle_path
4. segment
5. travel_path
6. location
7. level
8. node
9. aisle_path_node
10. travel_path_node

The Move_Cache_sp is used to move just the cache tables from one database to another:

1. NodeCache
2. TravelPathHistory
3. TravelPathHistoryDetails
   

   Info

   • The only XYZ-related data that is NOT moved is that which defines which nodes are interconnected. Since ConnectedNodes is NOT moved, the PopulateConnectedNodes_sp must be run after transferring XYZ data.

All modifications are done in one direction reading from a database that is designated as "Source" and updating the database designated "Destination". Any errors while executing this request will result in a full rollback of the data.

XYZ Data Transfer - Instructions

1. Disable the scheduled task operations in both the Source and Destination environments.
   1. Log in to ProTrack Warehouse.
   2. Click on the System tab under the Configuration menu.
   3. Click on the Scheduled Task sub-tab.
      
      

      
      ^{Fig.198 System Configuration}

      
      
   4. Select "N" for ALL of the drop down boxes.
   5. Select all of the check boxes.
      
      

      
      ^{Fig.198 System Configuration - Disable System}

      
      
   6. Click to save the changes.
2. Ensure that all processing in both environments is complete.
   1. Scheduled Request Records.
      1. Click on the Monitor tab.
      2. Click on the Scheduled Request tab.
      3. Click .
      4. Search for all records where the status is INP.
      5. If there are any records in INP wait for these records to leave INP status. All WMS processing is complete when there are no records in the Scheduled Request that are in INP status.
   2. Batch Process Records.
      1. XYZ data is imported based on a batch process that runs based on a configurable time interval.
      2. Check that there are no files in the import directories on the application server for the following import types:
         1. Facility
         2. Floor
         3. Aisles Path
         4. Segment
         5. Location
         6. Travel Path