Cleaning Up The Effects Of Deleting User Overrides In EnterpriseOne
Share
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
Average Rating
2 thoughts on “Cleaning Up The Effects Of Deleting User Overrides In EnterpriseOne”
Leave a Reply Cancel reply
This site uses Akismet to reduce spam. Learn how your comment data is processed.
More Stories
Quick Tip: Hold All JDE Job Queues
The following SQL statement will put all JDE Job Queues on hold: UPDATE SY920.F986130 SET QCQUSTS='02' This statement is very...
How To Disable Client Package Deployment
If you have a development client that has been neglected and JDE wants you to install 15 update packages but...
Quick Tip: Limit The Number Of Rows Returned From A SQL Query
This is pretty basic, but I had to look up the syntax to use for SQL on IBM DB2 so...
Quick Tip: Where Is An Application On The Menu?
The following SQL will give you a good idea if an application or UBE is on the menu and where...
Quick Tip: Decline All Update Packages Using SQL
A quick way to decline all packages that have been marked for deployment on a development client is use SQL:...
Quick Tip: Change A Scheduled Job’s Time Zone Using SQL
If you work with multiple time zones, especially if one uses Daylight Saving Time and the other does not, it...
R98222B – UBE that clears all objects out of a project specified in the processing option.
Thanks, Ricky.