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.

Scheduled Processes Time Zone for Global Implementation

Summary: Unable to set different time zones for scheduling scheduled processes Legislation Wise


Content (required): We are in a Global Implementation with countries from East to West (Same Instance/environment used by all geos). Scheduled Processes are recommended by Oracle to run during NON working hours. However there is no possible time zone in which all Geos are not working due to the global stretch of the project.

Requesting for best practice on how to schedule these. (Scheduled processes list attached)


Version (include the version you are using, if applicable): 23A (11.13.23.01.0)


Code Snippet (add any code snippets that support your topic, if applicable):

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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