Since our installations of EnterpriseOne were installed and the data upgraded we have applied and installed thousands of ESUs. On 4 of the 7, we neglected to apply the ESUs to the Pristine pathcode (PS900/PS910). This made researching code changes a bit of a challenge.
So, the other day, I decided to rectify that and apply the many, many ESUs to Pristine. Because there were some very old ESUs and not all of them were registered with Change Assistant, it was a very time consuming. After I had finished, I noticed that there were several ESUs that had only been applied to PS & PD and others that had only been applied to PS, DV & PY. Rather than look through every ESU and risk missing some, I connected to E1LOCAL and wrote a SQL statement to get every ESU that had been applied to the system that was not in every pathcode.
Please see “Use Oracle SQL Developer To Modify The JDE LOCAL Database” for connection instructions.
SELECT * FROM ( SELECT A.SDPKGNAME AS ESUNAME, A.SDSUDFUT2 AS SYS, PS.SDSUDFUT2 AS PS910, DV.SDSUDFUT2 AS DV910, PY.SDSUDFUT2 AS PY910, PD.SDSUDFUT2 AS PD910 FROM F9671 A LEFT JOIN F9671 PS ON A.SDPKGNAME = PS.SDPKGNAME AND PS.SDSUDFUT2='PS910' AND PS.SDSUDET = '90' LEFT JOIN F9671 DV ON A.SDPKGNAME = DV.SDPKGNAME AND DV.SDSUDFUT2='DV910' AND DV.SDSUDET = '90' LEFT JOIN F9671 PY ON A.SDPKGNAME = PY.SDPKGNAME AND PY.SDSUDFUT2='PY910' AND PY.SDSUDET = '90' LEFT JOIN F9671 PD ON A.SDPKGNAME = PD.SDPKGNAME AND PD.SDSUDFUT2='PD910' AND PD.SDSUDET = '90' WHERE A.SDSUDFUT2='ALL' AND A.SDSUDET ='10' ORDER BY A.SDPKGNAME DESC ) WHERE PS910 IS NULL OR DV910 IS NULL OR PY910 IS NULL OR PD910 IS NULL