Avoiding Java classes conflicts using a\_customer.xml file
Consider this scenario (which I came across). You have extended _psdi.app.workorder.WO_ out of the box MBO class with your own _cust.app.workorder.WO_ class to implement you own business logic for work orders. After a while you install the Maximo Scheduler extension and you soon discover that all your custom logic has gone because the WORKORDER object handler in Database Configuration is now _psdi
Consider this scenario (which I came across). You have extended _psdi.app.workorder.WO_ out of the box MBO class with your own _cust.app.workorder.WO_ class to implement you own business logic for work orders. After a while you install the Maximo Scheduler extension and you soon discover that all your custom logic has gone because the WORKORDER object handler in Database Configuration is now _psdi