This article explains an EPLS problem where the the EPLS software is not updating the Local Database tables with new data entered into the Central Database tables.
- EPLS connects to Central Database correctly
- ‘Sync Successful’ message appears either at EPLS startup or after selecting ‘Update Files’ in the Config section
- Records entered into critical tables in the Central Database (e.g. Items, Material_Group_Codes, Plant_Lines, Plants, Production_Lines, Users, User_Roles, etc.) are not added to the tables of the same names in the Local Database after the successful sync
Table Update / Synchronization Process
When EPLS opens on an IPC, it connects to the Central Database and downloads the key tables to update the Local Database on the IPC. During this process, EPLS compares the Last_Sync_Date in the Local Database Configurations table to the Modification_Date for each record in each of the critical tables in the Central Database (e.g. Items, Material_Group_Codes, Plant_Lines, Plants, Production_Lines, Users, User_Roles, etc.). If the Modification_Date field value is greater (i.e. record is newer) than the Last_Sync_Date, EPLS will copy the new record from the Central Database table to the corresponding table on the Local Database.
Configuration Table with Last_Sync_Date Circled (from Local Database):
Item Table with Modification_Date Circled (from Central Database):
Blank Records with Modification_Date Fields
If someone manually enters new records but does not enter a current date in the date field, the system may assume the data is old (i.e. the Modification_date field value will be less than the Last_Sync_date) and not update it.
Further, if the record not updated has a field used as a foreign key in another table (e.g. Item # field in Item table used in the Item_Lots table), this can cause further failures in the synchronization process.
To prevent this from happening, make sure the current date is used in the date field when updating tables in the SQL database for EPLS. To enforce this policy in EPLS, the attached database script can prevent users from leaving the Modification_date field value empty (from Ed Heinrich).
Enter additional comments here