ESU Retrofits and Transfering Objects
<hint of sarcasm>Although JDE/PeopleSoft/Oracle has done such an awesome job with all of their products</hint of sarcasm>, sometimes you are forced to modify some of the objects.
To prevent the ESU from clobbering our modified objects and getting users really confused and frustrated, the development team (they are also the business analysts) and the CNC team have come up with the following procedures:
- All objects that have been modified are tracked and well documented by the Development Team (DT)
- DT requests CNC to install and apply the ESU to DV and PY
- Users test and approve the ESU affected object without the custom modifications in PY
- DT retrofits the object in DV and promotes it to PY
- Users test and approve the object, now with the custom modifications, in PY
- DT requests CNC to apply the ESU to PD
- CNC applies the ESU to PD and then notifies DT
- DT manager then runs the SQL below to set the Modified Date and the Updated Date in the OL811/F9861 to a date prior to the date that the object was moved to PY (we use 107001 just to make sure)
- DT then promotes the object to PD
- CNC builds and deploys the package
The SQL to set the Date Modified and the Update Date of the object to a prior date (thanks to our Development Team manager for the SQL):
UPDATE OL811/F9861 SET SIUPMJ = 107001, SIDM = 107001 WHERE SIOBNM IN ('P01012','F0101') AND SIPATHCD = 'PD811'
Do you use a different method?
Tags: cnc, EnterpriseOne - Install/Upgrade, EnterpriseOne - SQLs, esu, oracle, peoplesoft, sql
1 Trackback(s)