New report: /PACG/ECM_USERS_MIGRATION has been created in order to allow migration of users previously created and stored in an existing table /PACG/ECM_USER . The records will be are transferred into new tables PACG/ECM_USERS and PACG/ECM_UCOMP.
| Note |
|---|
To run this report use transaction /PACG/ECM_USER_MIG or execute /PACG/ECM_USERS_MIGRATION in SE38 (or SA38) |
The initial screen allows for the selection of:
...
Each of the fields contains search help.
...
The
...
Additionally there is a migration option: Without data consistency check checkbox. Upon setting this to yes, all users in the specified range will be migrated without checking for data existence, duplicates and conflicts.
After entering the selected values/ ranges of values, deciding about the migration option and pressing execute button, the program finds the data within the selected range and guides through migration process. If the Company ID is left blank, then the selected user/users will be migrated to all companies to which the user is already linked in table /PACG/ECM_USER. If the Company ID is entered and user and personnel number ranges are blank then all users/personnel number belonging to the entered company will be migrated.
The migration program has an additional feature which checks data consistency. This feature can be turned on and off by setting the checkbox Without data consistency check. In case when consistency check is turned on and a 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 new tables: /PACG/ECM_USERS and /PACG/ECM_UCOMP for a specific user (in case of users conflict) or for user and company combination (in case of 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 new tables: /PACG/ECM/USERS and /PACG/ECM_UCOMP, then the setting that was previously migrated will be defaulted and no selection screen will be displayed.
| Info |
|---|
Please refer to the below section to see more information and the examples of conflicts:
|
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 . (blank value/ JUK) 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. Only one value per user should be specified.
...
In order to avoid migration of duplicated data, the migration program displays additional selection screen to choose , where proper record to be migrated should be chosen.
...
In order to do that please select the record and click Migrate Users button.
...
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, Perm ID) 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.
...
In order to avoid migration of duplicated data, the migration program displays additional selection screen to choose where the proper user /company configuration should be chosen to be migrated.
...
. In order to do that please select the record and click on Migrate user company assignment button.
...
After valid choice the program continues with migration.
| Info |
|---|
After the initial entry on the selection screen and optional record selection |
...
in case of conflicts |
...
, the program |
...
displays all users and companies in the selected range and |
...
presents the data to be migrated. This screen provides an option to review the data and delete some rows before migration confirmation. Please remember to click on Confirm migration button after reviewing the data. |
...
After confirmation, the log information with numbers of records created in each table and is displayed.
...
Additionally the Final migration status ALV Grid with list of initially selected users and migration status messages are is displayed.:
...
The As a result of migration, the users selected on the initial screen have been migrated to new tables: /PACG/ECM_USERS and /PACG/ECM_UCOMP:
...
...
| Info |
|---|
The migration program checks also user validity and user lock based on USR02 table (fields: GLTGV, GLTGB, UFLAG) |
...
: |
...
The non valid users or users with lock are successfully migrated (as they can be easily unlocked or their validity can be adjusted later on) but the program displays the warning icons in Usr valid, Usr lock fields in Final Migration Status screen for information.
...