Maintenance of User Type as Default entry:
I was having a bit of hard time in maintaining and getting user type synchronized across configurations done in EUP (SPRO) and Access request.
In EUP (SPRO --> GRC --> Access Control --> User Provisioning --> Maintain End-User Personalization), we have a field to maintain the “User Type” with default entry (if required), so as per my customer requirements, We had to go with “Dialog” so I got it maintained with default value as DIALOG in EUP in GRC-development and captured in TR (workbench) and transported across the follow-on systems. But there we started encountering an issue with this String “Dialog”. Access request for create or change account were not getting provisioned and when I looked for the Audit log, I saw the request is getting triggered to the escape route as GRC was not able to recognize the entry for User type as Dialog. It said: “Invalid user type D”. Even in the access request form also, user type was displaying just “D” but I thought GRC might have shorten the word to just a letter but it was kind of ignorance
Then I realized that GRC can’t recognize this user defined key-words but R3 defined key-words and then thought of utilizing R3 skills. In R3 we have user types as below:
A: Dialog
B: System
C: Communication
S: Service and
R: Reference
And then I entered just the key word, like “A” for dialog type and Yahoo!!, it worked 
So, with the maintenance in EUP as below:
I can see user type coming up correctly in Access request forms as below:
Thought to share across to help others to overcome such issues.
Cheers,
Ameet