on 05-19-2010 6:01 AM
Anyone have some ideas on how to handle SU01 Parameters across multiple ABAP systems ?
Our difficulty is that the parameters required in the ERP system do not exist in the SOLMAN system so I cant create a 'global parameter' list for a user in the MX_PARAMETER and let IDM send it out everywhere.
Parameter examples are ;
/RWD/LANG=EN
MOL= 13
thanks
We looked at creating a PARAM<system number> type field and then changing all the required provisioning tasks, but after a closer look, we decided that parameters on the main ERP/HCM system will be done with an ABAP program. So immediately after HRUSER process has created the SU01 record, the abap program inserts inserts the required 30 or so PIDs according to the HR area. Other reason for doing it this way is that once the PID's are assigned to the user, the user can then change some of them via their transaction screens. So we didn't want IDM changing or even tracking the PIDS after the initial creation.
All other systems had minimal use of parameters and these will be done manually.
Would be a great addition to the IDM application if it did politely handle differing PIDs in multiple ABAP systems !
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the answer...
Phil, did you test the solution proposed?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you don't want to script, do it like the ACCOUNT<REPNAME>.
Create an attribute PARAMETER<REPNAME> and fill it so it fits you.
So you can then set the parameters per system.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.