IJ20620: IT IS NOT POSSIBLE TO PERFORM A RETURN OF A ROTATING ITEM USING MIF.

APAR status

• Closed as program error.

Error description

• PROBLEM
  Attempting to RETURN a Rotating ITEM using MIF results
  in the error below:
  BMXAA0151E - Rotating Asset 2078 is not a
  rotating asset.
  
  STEPS TO REPRODUCE:
  The steps below use
  MAXDEMO as example:
  
  1)Go to Inventory Usage
  application.
  Create a new record as below:
  
  Usage: PF01
  From
  Storeroom: CENTRAL
  Usage Type MIXED.
  
  Click on New
  Row.
  
  ITEM:PUMP100
  Rotating Asset: 2078
  To Site:
  MCLEAN
  Location:6THFLOOR
  GL Debit Account: 6600-800-800
  
  Save.
  Change the Status to Complete
  
  2)Execute the query below in
  Maximo database and take note of the first value. This will be
  the value of ISSUEID.
  
  select matusetransid from matusetrans
  where itemnum = 'PUMP100' and rotassetnum = '2078' and
  issuetype = 'ISSUE' order by matusetransid desc;
  
  3)Import the
  XML below using the Object Structure MXINVISSUE.
  
  Fill in the
  TAG <max:ISSUEID> with the value of the step 2.
  
  <?xml
  version="1.0" encoding="UTF-8"?>
  <soapenv:Envelope
  
  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
  
  xmlns:max="http://www.ibm.com/maximo">
   <soapenv:Header />
  
  <soapenv:Body>
   <max:SyncMXINVUSE>
   <max:MXINVUSESet>
   <!--Zero
  or more repetitions:-->
   <max:INVUSE action="AddChange">
  
  <max:AUTOCREATED>0</max:AUTOCREATED>
  
  <max:AUTOSPLIT>0</max:AUTOSPLIT>
   <max:BINFLAG>0</max:BINFLAG>
  
  <max:DESCRIPTION>Test INVUSSE</max:DESCRIPTION>
  
  <max:FROMSTORELOC>CENTRAL</max:FROMSTORELOC>
  
  <max:ORGID>EAGLENA</max:ORGID>
  
  <max:SITEID>BEDFORD</max:SITEID>
  
  <max:STATUS>COMPLETE</max:STATUS>
  
  <max:USETYPE>MIXED</max:USETYPE>
   <max:INVUSELINE>
  
  <max:FINANCIALPERIOD>201910</max:FINANCIALPERIOD>
  
  <max:FROMBIN>F-4-2</max:FROMBIN>
  
  <max:PHYSCNT>0.0</max:PHYSCNT>
  
  <max:RETURNAGAINSTISSUE>1</max:RETURNAGAINSTISSUE>
  
  <max:RETURNEDQTY>0</max:RETURNEDQTY>
   <max:SPLIT>0</max:SPLIT>
  
  <max:VALIDATED>0</max:VALIDATED>
  
  <max:FROMSTORELOC>CENTRAL</max:FROMSTORELOC>
  
  <max:INVUSELINENUM>1</max:INVUSELINENUM>
  
  <max:ITEMNUM>PUMP100</max:ITEMNUM>
  
  <max:ITEMSETID>SET1</max:ITEMSETID>
  
  <max:LINETYPE>ITEM</max:LINETYPE>
  
  <max:ORGID>EAGLENA</max:ORGID>
   <max:QUANTITY>1</max:QUANTITY>
  
  <max:LOCATION>6THFLOOR</max:LOCATION>
  
  <max:ROTASSETNUM>2078</max:ROTASSETNUM>
  
  
  
  					<max:ISSUEID></max:ISSUEID>
  
  
  <max:TOSITEID>MCLEAN</max:TOSITEID>
  
  <max:USETYPE>RETURN</max:USETYPE>
   <max:GLDEBITACCT>
  
  <max:VALUE>6600-800-800</max:VALUE>
   </max:GLDEBITACCT>
  
  </max:INVUSELINE>
   </max:INVUSE>
   </max:MXINVUSESet>
  
  </max:SyncMXINVUSE>
   </soapenv:Body>
  </soapenv:Envelope>
  
  
  
  RESULTS:
  [10/28/19 15:35:31:010 BRT] 00000130 SystemOut O 28
  Oct 2019 15:35:31:010 [ERROR] [MAXIMO] [] BMXAA6695E - The MBO
  could not be batch validated for object INVUSELINE. The error
  is ROTASSETNUM. Ensure that the object exists in the maxobject
  table. Check the log files in the home directory to determine
  the cause and source of the
  error.
  
  psdi.util.MXApplicationException: BMXAA0151E - Rotating
  Asset 2078 is not a rotating asset.
  
   at
  psdi.mbo.MAXTableDomain.validate(MAXTableDomain.java:167)
  
   at
  psdi.app.asset.FldAssetnum.validate(FldAssetnum.java:192)
  
   at p
  sdi.app.inventory.FldInvUseLineRotAssetnum.validate(FldInvUseLin
  eRotAssetnum.java:64)
  
   at
  psdi.mbo.MboValue.validate(MboValue.java:1713)
  
   at
  psdi.mbo.MboValue.validate(MboValue.java:1616)
  
   at
  psdi.mbo.Mbo.validateAttributes(Mbo.java:5002)
  
   at
  psdi.mbo.Mbo.validate(Mbo.java:4575)
  
   at psdi.iface.mos.MosProc
  essImpl.checkValidateErrors(MosProcessImpl.java:2336)
  
   at psdi.
  iface.app.invusage.MaxInvUseProcess.checkValidateErrors(MaxInvUs
  eProcess.java:144)
  
   at psdi.iface.mos.MosProcessImpl.setAdditio
  nalTableData(MosProcessImpl.java:1710)
  
   at psdi.iface.mos.MosPr
  ocessImpl.createChildrens(MosProcessImpl.java:969)
  
   at psdi.ifa
  ce.mos.MosProcessImpl.fillMaximoTables(MosProcessImpl.java:810)
  
  
   at psdi.iface.mos.MosProcessImpl.processExternalData(MosProces
  sImpl.java:344)
  
   at psdi.iface.mos.MosProcessImpl.processObject
  StructureService(MosProcessImpl.java:239)
  
   at psdi.iface.mic.Mi
  cService.processObjectStructureData(MicService.java:859)
  
   at ps
  di.iface.mic.MicService.processObjectStructureService(MicService
  .java:647)
  
   at psdi.iface.mos.MOSServiceBean.secureProcessMOSIn
  ternal(MOSServiceBean.java:291)
  
   at psdi.iface.mos.MOSServiceBe
  an.maxSecureProcessMOS(MOSServiceBean.java:153)
  
   at psdi.iface.
  mos.MOSServiceBean.wsMaxSecureProcessMOS(MOSServiceBean.java:186
  )
  
   at psdi.iface.mos.EJSLocalStatelessmosservice_43551b5c.wsMax
  SecureProcessMOS(Unknown Source)
  
   at psdi.iface.webservices.OSW
  ebServiceProxy.invokeService(OSWebServiceProxy.java:89)
  
   at psd
  i.iface.webservices.JAXWSWebServiceProvider.invoke(JAXWSWebServi
  ceProvider.java:120)
  
   at
  sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  
  
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
  sorImpl.java:90)
  
   at sun.reflect.DelegatingMethodAccessorImpl.i
  nvoke(DelegatingMethodAccessorImpl.java:55)
  
  EXPECTED RESULTS:
  
  The action should work.
  
  REPORTED IN VERSION:
  Tivoli's
  process automation engine 7.6.1.0-IFIX20190301-1635 Build
  20180718-1141 DB Build V7610-83 HFDB Build HF7610-02
  

Local fix

• NA
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * maximo MIF users                                             *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * It is not possible using MIF MXINVUSE to return a rotating   *
  * asset issued in the Inventory Usage.                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• This is fixed in code.
  The fix for this APAR is contained in the following maintenance
  package:
  	 | release\fix pack | Interim Fix for Release 7.6.1.2 Product
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• maximo
  

Fix information

• Fixed component name

  MAXIMO ASST MGM

• Fixed component ID

  5724R46AM

Applicable component levels