Skip to main content

Error cannot change item number because location is inventory

This is a case where you were not able to change item number of this asset from change item number.

This error comes when we use select action "change Item Number" on asset application and assets location is inventory.

To resolve this error you need to transfer this item to non inventory location using inventory usage application only.

Also you need to select asset number or given full quantity if you want to move all asset attached with same item number and complete this record then asset location will be changed to your mentioned location inventory usage line.

Then you will be able to change item no. on asset application.

Comments

Popular posts from this blog

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...

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...

BMXAA4211E - Database error number 1 has occurred when operating mbo...

 BMXAA4211E - Database error number 1 has occurred when operating on WFINSTANCE This solution you can use for any table generic solution in oracle db only  this is duplicate id issue.. (if you cannot remove duplicate just increase nextval like i did since in my case too i can't find duplicate and max value is greater than nextval. select max(WFID) from maximo.wfinstance *select maximo.WFINSTANCESEQ.NEXTVAL from dual; increase you value with some 1000's from o/p of query 1... example *alter sequence maximo.WFINSTANCESEQ restart start with 17572034; Similary if it comes for wfcallstack   BMXAA4211E – Database error number 1 has occurred when operating on WFCALLSTACK:   Report the error to the owner of the deployment.     check maxvalue    select max(wfcallstackid) from maximo.WFCALLSTACK     check next value    select maximo.WFCALLSTACKSEQ.NEXTVAL from dual; increase value by some 10000 etc...... alter sequence max...