You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Skip to content
  • Register
    • Learn about the new Oracle AI Agent Studio for Fusion Applications: Watch Now

    Progress with Redwood: Redwood Resources for Oracle Cloud HCM -  Go Here

    How to restrict based on previous Backout status

    in Reporting and Analytics for HCM 5 comments

    Summary:

    Hello All,

    I'm currently working on restricting the custom BIP notification based on below scenario.

    If an employee benefits is backed out and reprocessed again, the notification should not trigger to benefits team - which means the data should not be availble in the data set. But the issue is once the reprocessed is done the status is changing to STARTED again, so how to restrict based on previous VOIDD or BACKOUT status. In other words, if an employee has VOIDD or BACKOUT status in any of their history transaction, then the employee data should not be fetching even if their status changed to STARTED again.

    Tagged:

    Howdy, Stranger!

    Log In

    To view full details, sign in.

    Register

    Don't have an account? Click here to get started!