ESU Installation Comparison Using SQL

oracle-sql-developer

If your JDE EnterpriseOne installation has been installed for more than oh, 2 weeks your pathcodes have obviously gotten out-of-sync. Ok, maybe its not that bad, but DV and PY can become much different than PD faster than a three-legged fox in a hen house. Is that fast? I dont know, but it doesnt take long. There are many reasons as to why the pathcodes get out-of-sync:

  • Testing an ESU without cleaning up after it didnt resolve the issue
  • Forgetting about an ESU that was installed in DV or PY
  • Developers being slow to do retro-fits

Now, Developers, dont get upset. I love developers. They provide job security for CNC Admins! Now come on Im just hackin on ya.

You can use SQL Developer to connect to the E1Local database.

The SQL I used to compare the ESU installations between pathcodes is below. This example tells us which ESUs are in PY910 but not in PD910. The SDSUDET=’90’ indicates that the ESU has been installed in that pathcode.

select sdpkgname as ESUNAME from f9671
where sdsudfut2='PY910' and sdsudet = '90'
minus
select sdpkgname as ESUNAME from f9671
where sdsudfut2='PD910' and sdsudet = '90'

Any other quick and dirty SQLs that you use to report on ESUs? Please leave them in the comments below.

Leave a Reply