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 with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

Retain action/reason of employees for whom leave of absence transaction is seeded

Summary:

When we do some kind of mass updates ( e.g. change in department/location) followed by running the Synchronize Person Assignment from Position scheduled process to synchronize position attributes with employment record(s), a new row is inserted with action as Synchronization From Position. 

Content (required):

When an LOA action/reason record exists with assignment status as Leave of Absence - No Pay, a new record is also inserted with action as Synchronization From Position and assignment status maintained as Leave of Absence - No Pay. 

When this row is inserted, the original action/reason used while seeding LOA transaction becomes history and the same is not reflected in the OTBI analysis

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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