HI Manish,
Agree with Matt. But in nut shell,
Check if users have MX_LOGONALIAS attribute is filled in with required value
If not, then create a job to assign MX_LOGONALIAS with %MSKEYVALUE%@XYZ.NET values
Also, update the user load from your source to include this attribute for any new user
Then make sure if createABAPuser task has useralias = %MX_LOGONALIAS% attribute.
PS: If attribute MX_LOGONALIAS is a trigger attribute for any repository(ies), then it would trigger Modify task for those repositories when you assign MX_LOGONALIAS to users in mass meaning the users will be updated with alias in abap system.
If not an trigger attribute, then any user created henceforth will get alias.
PPS: The above steps are explained in config guide shared by Matt. Thanks.
Kind regards,
Jai
Message was edited by: Jai Suryan