• State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 7 replies
  • Subscribers 94 subscribers
  • Views 4513 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to react on UNSAccountInUNSGroup (events don't work)

prueegg
over 6 years ago

I would like to react on each insert and delete in the proxy view UNSAccountInUnsGroup.

The reason is that I don't won't to care if the assigment is done for an SAP, UNSB ord AD Entitlement.

But I've found out that triggers on the view do not work.

So it seems, that I need to do it for each target system type.

But than I'll have the next problem with SAPUserInSAPRole. Since this Table is consolidated in HelperSAPUserInSAPRole I wan't to base on that Helper table.

Es well there, it was not possible to react on events.

Do you have any suggestion how to deal with that?

Parents
  • 0 over 6 years ago

    btw. Im working with 7.1.1

  • +2 over 6 years ago in reply to prueegg

    Just set the flag "Assign by event" in the Designer for HelperSAPUserInSAPRole should do the trick.

  • 0 over 6 years ago in reply to Markus Weiss-Ehlers

    Hi Markus

    Thanks for that advice. It works now, but only in case of a delete event.

    If I look at the Job Queue I see always a "Created by QBMDBQueueProcess: handle object delete for object type SAPUserInSAPRole" followed by corresponding two DB Queue Processes about Membership SAP User in SAP Role. After that there is the "Created by QBMDBQueueProcess: handle object delete for object type HelperSAPUserInSAPRole" which triggers my job.

    But If I add a new Membership I'll only get the process "Created by QBMDBQueueProcess: fire event Assign for object type SAPUserInSAPRole" followed by nothing.

    At the moment, I've now ideal why it behaves that way.

    Do you have any idea?

Reply
  • 0 over 6 years ago in reply to Markus Weiss-Ehlers

    Hi Markus

    Thanks for that advice. It works now, but only in case of a delete event.

    If I look at the Job Queue I see always a "Created by QBMDBQueueProcess: handle object delete for object type SAPUserInSAPRole" followed by corresponding two DB Queue Processes about Membership SAP User in SAP Role. After that there is the "Created by QBMDBQueueProcess: handle object delete for object type HelperSAPUserInSAPRole" which triggers my job.

    But If I add a new Membership I'll only get the process "Created by QBMDBQueueProcess: fire event Assign for object type SAPUserInSAPRole" followed by nothing.

    At the moment, I've now ideal why it behaves that way.

    Do you have any idea?

Children