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.

Best Practice for Environment Management through implementation

edited Jan 11, 2017 11:33PM in Human Capital Management 1 comment

Summary

Refreshing Prod no longer an option?

Content

We're commencing an implementation of HCM Cloud and have two environments to use. I'm concerned that we're not going to be able to do as we've done previously:

  1. Config done in TST, Data Migration iteration 1 into TST
  2. Completed Config moved to PRD, Data Migration iteration 2 into PRD
  3. UAT/Validation performed in PRD
  4. PRD reset to initial blank state and config migrated again
  5. Migration and Go Live

This document expressly says that this is no longer possible: 2002697.1

I'm sure we've done as above previously, but the last implementation had 3 environments so it wasn't an issue. How does everyone else handle having two environments and the need for a clean environment for Data Migration iterations and UAT?

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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