Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
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.

How to prevent Time Card Row deletions and attribute changes

Summary:

After a time card has been approved, we want to restrict workers from deleting rows within the time card and have from changing a time attribute called Time Charge.

Content (required):

We are using the HCM Extract Changes Only extract to pull time card labor hours and their associated time charge. Each row of data is associated with a distinct time charge attribute. After the time card is approved and extracted users can make additional updates to the time card however we do not want them to delete rows within the time card. If they delete a row, the next time the extract runs, nothing will be pulled to reflect the hours were deleted. Instead they'll need to 0 out each day for the old row and

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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