Data replication overview

This document provides the information on data movement from the ERP database to the Factory Track database both for initial setup and on-going operation. There are two types of data that is required to be synchronized:

• One type of data set are downloaded for a single time and are not required to be synchronized again (For example, shifts or time-off groups)
• The other type of data sets are synchronized on a continuing basis.

The data files supported for 6.01 release:

• Departments
• Tasks
• Shifts
• Time-Off Groups
• Employees
• Holidays

The operator can run queries to download the required data type.

The process can be divided into three stages:

• Download of data from Native ERP system to staging table in Factory Track
• Apply Defaults to Staging table
• Posting data to Factory Track Master Files

The general methodology employed must consist of these steps:

• Synchronization is considered as a "Batch" activity which can be scheduled using the background task feature of Mongoose, or can be started by the user.
• For each data set processed, control data is created that contains information from the download. This is created when the download starts and the master files are updated after the process is finished.
• As the data is received from the ERP, the file is placed on the staging tables/staged data that are created for later processing.
• After all the data is downloaded and the control record updated, the temporary data is updated with values before being processed. If the data exists in the database, each field is checked for the value and set, as required. If the record does not exist, the data is created and populated with the values from the temporary data. In some instances, creation of a record can cause the creation of additional record(s).
• After the data is updated/created, the temporary data is updated and processed.
• After all temporary records are updated, the control record is updated.