EPLS Synchronization Process – EPLS Reference Article


This Reference Article defines and explains how the EPLS software synchronizes data from the Central Database to the Local Database.


There are two triggers for the synchronization process:

  1. When the EPLS is started
  2. When the user enters the Configuration screen and selects the “Update Tables” button

Force Synchronization with the Update Tables Button in the System Configuration screen:

When the process is triggered, EPLS checks the Last_Sync_Date field in the Configurations table and compares that value to the Modification_Date field in each record of each table critical to EPLS operation (e.g. Items, Material_Group_Codes, Plant_Lines, Plants, Production_Lines, Users, User_Roles, etc.).  Any record in the Central Database in one of those key tables with a Modification_Date field greater (i.e. newer) than the Last_Sync_Date will cause EPLS to copy that record and update the same record of the same name in the same table in the Local Database.

The tables are synchronized in the following order:

  1. Users
  2. Roles
  3. User_Roles
  4. Transaction_Types
  5. Special_Pack_Codes
  6. Material_Group
  7. Plants
  8. Plant_Lines
  9. Production_Line
  10. Production_Line_Material_Code
  11. Items

After the tables are synchronized, EPLS then looks in the Local Database Item_Lots table for any records with a Needs_Sync field that contains a value of “1”.  Each of these are then copied form the IPC Local Database to the Server Central Database.  Once copied, the Needs_Sync value is set to “0”.

Note: If EPLS has the wrong password for the Central Database, it will yield a false positive for synchronization (it will indicate ‘Synchronization Success’ when, in fact, it failed).


Was this article helpful?

Related Articles