1) Does this environment also include custom objects and versions? Or is it a copy of pristine that just gets ESU's installed?
Answer: Yes it does include custom objects and version. It is a copy of production.
2) If ESU's are installed directly to this environment, it must have it's own path code. How about it's own data set? Or does it share data with PY (CRP)? Not using an existing data set can only complicate the testing of an ESU, as data sometimes has an effect on processing.
Answer: Yes it has it's own pathcode and data set.
3) Standard JDE | PSFT methodology states that ESU's should simply be tested in DV. If they don't work the way you anticipated, you roll back (assuming you installed with the B/U option). Is there a reason you didn't use this basic approach?
Answer: we decided to go with another pathcode for testing ESUs, as last fall we ran into a horable corruption problem where bits and pieces of ESUs got into Prod.. These ESUs, some had been removed, and others were just left in DV (big no no). After discussing with Developers, we felt that having a seperate environment for testing ESUs would help to avoid this issue. The ESU will be tested in ES7333.. when approved will be applied to DV and tested for a week (no development during this time)... then applied to PY and tested again in PY.. then to Prod. Once the ESU has been applied to Prod the ESU environment will be refreshed to the same status as prod.. ready for the next ESU.