Skip to Content

HR Triggers not defaulting End dates

Hi All,

I've managed to configure the HR triggers to generate Access requests for creation, changes, and deletions.

My issue is that the deletion request does not seem to consider the HR trigger configuration around validity dates.

I have set the proposed valid to / from dates in the HR Trigger configuration but they do not appear on the Access Request.

Also, approvers are not able to override these blank entries despite having configured the workflow stages to allow them to edit change details and add assignments to the request.

The impact of this is that if the HR record meets the criteria for a leaver (even if the effective date of the action is in the future), the access request is triggered immediately. If the approver then approves the request, the deletion is also effective immediately. This means that if the users' access will be removed immediately even though the users are not leaving immediately,

Ultimately, I want the ability to trigger a deletion request which will either automatically consider the EFFECTIVE date of the HR Action or allow the approvers to have the flexibility specify the date when the deletion should be performed. Any ideas on how to achieve this?


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    Jun 01, 2012 at 01:05 PM


    Have you reviewed SAP Note 1705700?  This already release, but will be included in SP09.



    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Sharad Parasher

      What about  if the scenario is opposite?

      We have client who would like to create CUP Termination request for Termination that were process mannually in ECC 6.0 in the PAST 3 Weeks ?

      GRC 5.3 termination request does not take OLD dates ?

      Is there any work around to this ?



  • Sep 09, 2013 at 04:28 PM

    Hi Simon,

    Were you able to achieve this?  I'm trying to do something similar.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 09, 2013 at 07:52 PM

    Create the BRF+ rule to update the BEGDA for the HR action.  You also need to add "delete" action to the request type (in SPRO-->GRC-->User Provisioning-->Define Request Type) that will be using the HR trigger because the request needs to "delete" the value for the field and then update it with the future date.  I implemented this for HR terminations and it was quite tricky.  Don't forget to map the BRF+ function ID to the AC Application Mapping in SPRO as well.

    Add comment
    10|10000 characters needed characters exceeded