Skip to Content
avatar image
Former Member

SAP IDM Attribute Options Similar to Distribution Parameters for Fields ( Tcode SCUM) in CUA

I'm setting up New Connections to ABAP Systems. for few Attributes I would like to maintain it locally , like User Parameters in CRM, and few attributes globally. Like CUA settings in SCUM, Can we Modify them in Jobs and passes. Do we have any equivalent settings like SCUM settings below in IDM.

Global -You can only maintain the data in the central system. The data is then automatically distributed to the child systems. These fields do not accept input in the child systems, but can only be displayed.

Default -You maintain a default value in the central system that is automatically distributed to the child systems when a user is created. After the distribution, the data is only maintained locally, and is not distributed again, if you change it in the central or child system.

RetVal -You can maintain data both centrally and locally. After every local change to the data, the change is redistributed to the central system and distributed from there to the other child systems.

Local -You can only maintain the data in the child system. Changes are not distributed to other systems.

Everywhere -You can maintain data both centrally and locally. However, only changes made in the central system are distributed to other systems, local changes in the child systems are not distributed.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    Feb 13 at 09:51 AM

    Hello Siva,

    I have no experience in CUA, but IDM should normally be the central system for all the information. Meaning the data should be changed in IDM and it provisions into the backend system.

    We have some fields that are maintained in the backend systems and read back into IDM though (through jobs). So it's of course possible, but then you have to decide per attribute, where it lives. I would never recommend to have the possibility to change the data of one field in several systems. That kind of defeats the purpose of having an IDM in the first place. ;)

    So either IDM is the owner of the attribut and you can only change it there or the backend system is the owner of the field and you read the information back into IDM.

    .

    Regards,

    Steffi.

    Add comment
    10|10000 characters needed characters exceeded

  • Feb 14 at 12:38 AM

    Hello Siva,

    If you want to use the IDM as central provisioning system then there is no point in using the CUA too. However, if this is the business need then yes attribute/field updation to each target system can be controlled by modifying the standard Plugins.

    Regards,

    C Kumar

    Add comment
    10|10000 characters needed characters exceeded

  • Feb 12 at 05:06 AM

    Hi Siva,

    I assuming you are speaking about values maintained in the parameters tab under SU01 in ABAP system.

    Create a repository constant specific to a particular repository or repository type constant applicable for all repositories of that type and maintain the parameters which you want to push to ABAP system.

    Or else you can even maintain in the MX_PARAMETER attribute and link it to MX_PERSON entry type and maintain values in the the Help Value table which can be used during the new user creation.

    Regards,

    deva

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hello Deva,

      In SAP CUA we have a tcode called SCUM, which has values that control how attributes are controlled .. like global , local, everywhere. Trying to make a comparision the CUA with IDM

      regards

      siva