Skip to main content

Unable to change Tool status to Obsolute, Workorder exists on this item

Hi If you are getting this  error you need to close,complete or cancel these workorders otherwise you will not be able to make this tool Obsolute.

Below are other things you can check to make tools exists so as to not get error's like that:-

1. Check Workorders exists on it or not which are not in cancelled or complete or closed status

Query

1. Workorder

select * from maximo.wpitem where itemnum='YOURTOOLNUM' and wonum in
(select wonum from maximo.wonum where status not in (SELECT MAXVALUE FROM SYNONYM domain where domainid ='WOSTATUS' AND maxvalue not in ('COMP','CLOSE','CAN'))


2. Check for invbalances

Select * from maximo.invbalances where curbal>0 and itemnum='YOURITEMNUM'

3. Check if there is any asset exist on this item

Select * from maximo.asset where  itemnum='YOURITEMNUM'

4. check for joptool

Select * from maximo.jobitem where  itemnum='YOURITEMNUM'


5. Check for MR which are not close or cancel

Select * from maximo.mrline where itemnum='YOURITEMNUM' and mrnum in
(select mrnum from maximo.mr where status not in status not in (SELECT MAXVALUE FROM MAXIMO.SYNONYM domain where domainid ='MRSTATUS' AND maxvalue not in (,'CLOSE','CAN'))

6. Check for PR

select * form maximo.prline where itemnum='YOURITEMNUM' and itemsetid='YOURITEMSITEMSETiD' and prnum in (select prnum from pr where siteid=prline.siteid and status in ( select value from MAXIMO.synonymdomain where domainid='PRSTATUS' and  maxvalue not in ('COMP', 'CAN')));

7. Check for open PO exists

select * form maximo.poline where itemnum='YOURITEMNUM' and itemsetid='YOURITEMSITEMSETID' and ponum in (select ponum from maximo.po where siteid=poline.siteid and status in ( select value from MAXIMO.synonymdomain where domainid='POSTATUS' and  maxvalue not in ('COMP', 'CAN','REVISE')));

8. Check for open Contracts

select * form maximo.ContractLine where itemnum='YOURITEMNUM' and itemsetid='YOURITEMSITEMSETID' and contractnum in (select contractnum from maximo.contract where siteid=ContractLine.siteid and status in ( select value from MAXIMO.synonymdomain where domainid='CONTRACTSTATUS' and  maxvalue not in ('COMP', 'CAN','REVISE')));

9. Check for CI exists






























Comments

Popular posts from this blog

Maximo Bean Class Methods

Methods of Bean Classes of Maximo Reset Method   This method is called when a new filter is applied for the dialog's MboSet.  @see psdi.webclient.system.beans.DataBean#reset()     @Override     public void reset() throws MXException     {             try         {                 saveCurrentSelection();         }         catch (RemoteException e)         {             handleRemoteException(e);         }         super.reset();     } Initialize It is used to initialize values on a d...

Maximo Interview Questions - Maximo Technical and Functional Questions

Technical Questions How do you rate your self in :- 1. PL/SQL 2. Java 3. Automation Script 4. Mbo Customization 5. Admininstration Jobs 6. Funtional Concepts 7. Maximo Configuration Do not rate anything less than 7 unless you don't want interview to skip the topic Deployment / Administration  1. Explain LDAP integration? 2. Explain SSO and LTPA token? 3. What is global security? 4. How session is managed in Websphere or Maximo? 16. How to insert attributes from Backend? 5. How request is passed in Maximo? 6. How to do horizontal and vertical clustering? 7. Explain how you confire websphere for maximo manually? 8. What are Websphere MQ? 9. What is JMS, Connection Factory and Queues? 10. What is difference between vmm and ldap sync integration ? 11. What is Standalone and federated repository? 12. How to install a new language in Maximo? 13. What are the steps to apply a Fix pack in Maximo, Websphere or DB2? 14. Have you worked on any performance checking tools? 15...

BMXAA1581E No object with the name {0} is set up in the JNDI tree. Check the JMS/JNDI setup in the server administration console

 BMXAA1581E No object with the name {0} is set up in the JNDI tree. Check the JMS/JNDI setup in the server administration console This error might come after you setup queue after you create destination then queue in websphere and add same in external system Add/Modify queue and same thing in main table of external system..... When u click on publish maximo can give this error......... reason is JNDI name you specifiy in maximo when adding queue from select action does not match with jndi name you specify in websphere...... Go to Websphere ->resources->JMS->queues ->and open your queue and check jndi name now check same name in maximo add/modify queue select your queue and check the jndi name........ Check the connection facility class in add/modify queues compare it with other queue whether it is requried / cusotmized or something delete data of your new queue(if it is not required else take backup or ask integration team to resend in case you have backup).. and now tr...