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
Get Started: AI Resources for Oracle Cloud HCM – Go Here

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

Restricting transactions submission

edited May 3, 2021 8:27AM in Human Capital Management 8 comments

Content

We are encountering a large volume of transaction issues and failures due to what we have so far sourced as more than one transaction being submitted on the employee for the same effective date or when a future dated change is in place. Is there any way to prevent a transaction from being submitted on an employee with another already effective change for the same date or future dated change on the assignment?

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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