...
The migration program has an additional feature which checks data consistency. In case when duplicated records exist in /PACG/ECM_USER, the program will trigger the extra selection screen to enable the choice of desired setting to be migrated to /PACG/ECM_USERS and /PACG/ECM_UCOMP for a specific user (users conflict) or for user and company combination (users company assignment conflict). When multiple records of generic user settings for different companies exist in /PACG/ECM_USER but one record (one user or company user combination) already exists (was previously migrated) in /PACG/ECM/USERS and /PACG/ECM_UCOMP then the setting that was previously migrated will be defaulted, and no selection screen will be displayed.
Users conflict is a situation when a user or personnel number has varying generic records (different values for fields: FSM Usr Id, Perm ID, FSM Usr ac.) for different companies. In the example below, the user JUK has different FSM User ID record linked with different companies. This is incorrect, as the FSM User ID is a general user setting and should be set up per user only not per user/company combination.
...
After valid choice the program continues with migration.
User company assignment conflict is a situation when a user has duplicated company assignment with different settings. It is possible to have some values assigned per user and company (such as: Subcontr., Plannable, Not active, User CT) but multiple records for the same user and the same company should not be allowed. The data in the below example is incorrect. The user JUK is incorrectly assigned to company 8 with two different settings: plannable -yes, not active - no, and plannable - no, not active -no.
...