Cleaning Up The Effects Of Deleting User Overrides In EnterpriseOne

August 4, 2008May 16, 2014

Read Time:36 Sec

Over a year ago, I wrote about how to delete User Overrides in EnterpriseOne.

Well, I had to use that process the other day and felt I should probably publish a fix to an unfortunate effects of using the User Overrides application.

What are these effects? Well, when you delete a User Override, it is first placed in your default project and then deleted. Unfortunately, after it is deleted, the object is not removed from your project.

So, to clean up what could be hundreds of objects from your default project, run the following SQL:

DELETE FROM SY811/F98222 
WHERE POOMWUSER ='***userid***'
AND POOMWOBJID LIKE'%GF%'

Can you think of anything that would make this easier?

Author

Stewart Schatz

Career: Principal CNC Consultant for Syntax Systems Limited specializing Oracle JD Edwards EnterpriseOne and the technology that supports it. Side Hustle: Owner/Operator of E1Tips.com Location: Lancaster, PA USA What I like to do: Invest in Family, Explore Technology, Lead Teams, Share Knowledge/Experience, Hunt, Hike, etc.

stewart@9rains.com

http://stewartschatz.com

Happy

Sad

Excited

Sleepy

Angry

Surprise

Average Rating

5 Star

4 Star

3 Star

2 Star

1 Star

(Add your review)

2 thoughts on “Cleaning Up The Effects Of Deleting User Overrides In EnterpriseOne”

Ricky says:

February 9, 2009 at 5:54 PM

R98222B – UBE that clears all objects out of a project specified in the processing option.

Reply
stewart says:

February 11, 2009 at 2:11 PM

Thanks, Ricky.

Reply