Versions Compared

Old Version 6

changes.mady.by.user proaxia

Saved on

compared with

New Version Current

changes.mady.by.user proaxia

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note

From SP11 hard deletion option is removed from /PACG/ECM_USERMASTER. The additional transaction /PACG/ECM_TRIG_UDEL - Deletion report for FSM users is dedicated for FSM user deletion.

...

This transaction is for sending user master data (system user) from SAP to FSM. It also allows for user deletion.

Warning

Please be aware that sending users to FSM with the deletion flag set will:

  • remove the user from FSM

  • remove the license assignment

  • remove the permission assignment

  • remove all document ownership of this user (by deleting his unique cloud ID permanently)

This action is not be reversible by re-uploading the user. In such a case the user will be assigned with a new ID.

When triggering programs /PACG/ECM_USERMASTER – User https://proaxia-prod-doc.atlassian.net/wiki/pages/resumedraft.action?draftId=37138765, the determination of addresses with the 'PERN' type is called. As long as there is an entry of "HOME/WORK/OTHER" in transaction /PACG/ECM_DEFADR or /PACG/ECM_USRADR, then the addresses from PA30 infotype 0005 will be sent.

...

.

Expand
titleClick to learn more about Employee Adress determination

Configuration occurs on two levels.

  • The general level concerns the settings of the given E4C Company. In this configuration, we determine the general principle of sending addresses. Please note that only one type of address should be marked as 'default'.

The configuration can be found under the transaction '/PACG/ECM_DEFADR' or using the standard user menu '/PACG/EC'

Image Added

The addresses from this configuration are read only when user-specific configuration is missing.

  •  User-specific level. Within this configuration, you can define specific addresses for a specific person. When defining this configuration, it is also important to remember exactly one 'default' address. Once we define the most specific settings for specific users, it is a good practice to set all three types of addresses (Home / Work / Other). This will avoid inconsistencies between the general configuration and the specific one for the user. (i.e. two addresses will be marked as 'default').

The configuration can be found under the transaction '/PACG/ECM_USRADR' or using the standard user menu '/PACG/EC'

Image Added

 

Technical documentation

The logic for addresses was implemented in the following classes:

  • /PACG/ECM_CL_S_SEL_EMPLOYEE Employee selection class

  • /PACG/ECM_CL_S_SEL_USER User selection class

 

Process

After setting the configuration, when sending people to the FSM cloud system should send 3 Idocs with the appropriate addresses.

Below is a sample test.

Image AddedImage Added

FSM database result:

Image Added

In the event that the entries for PA30 under infotype 105 subtype 0001 is missing for the system user, you will get this error '5A359 User xxx does not exist in this period' when sending the user to FSM. However, the records in FSM under PERSON and UNIFIEDPERSON is still being created regardless in the case personnel records with infotype 105 and subtype 0001 was not found in PA30.

...

If the "Not active" is set in /PACG/ECM_USRADR, this will set the transaction type in the outbound idoc to "D" when sending (See further below).

...

Sending of user to FSM with /PACG/ECM_USERMASTER.Image Removed

...

The outbound idoc shows "D" in transaction type indicating deletion to FSM even though checkbox for delete flag is not set above.Image Removed

...

If deletion of user is required, do NOT delete the user first before deleting the associated personnel (employee) as this will cause some inconsistency in FSM (at time of press) if the same user is recreated. Employee must be deleted first before user.

...