...
This is transaction is to be executed manually if needed. This is for sending of 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:
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 | ||
---|---|---|
| ||
Configuration occurs on two levels.
The configuration can be found under the transaction '/PACG/ECM_DEFADR' or using the standard user menu '/PACG/EC' The addresses from this configuration are read only when user-specific configuration is missing.
The configuration can be found under the transaction '/PACG/ECM_USRADR' or using the standard user menu '/PACG/EC'
Technical documentationThe logic for addresses was implemented in the following classes:
ProcessAfter setting the configuration, when sending people to the FSM cloud system should send 3 Idocs with the appropriate addresses. Below is a sample test. FSM database result: |
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.
...