"SAP_SAPUserInSAPRole_Assign" is generated twice when removing a direct assignment (4262316)

When assigning / removing a direct membership in SAPUserInSAPRole that already exists as inherited, the process "SAP_SAPUserInSAPRole_Assign" is generated.

If an assignment is created that already exists as inherited, only the XOrigin changes from 2 to 3 in the existing membership.

Since this is irrelevant for the target system, no provisioning is required in this case.  When assigning, however, the "SAP_SAPUserInSAPRole_Assign" process is generated twice.

When the direct assignment is removed, the process is generated once.

Since the process "SAP_SAPUserInSAPRole_Assign" also depends on the event "Update", the GenCondition has to be extended to exclude this case.