IV39747: ERROR WHEN SENDING WO STATUS CHANGE FROM MOBILE TO CORE MAXIMO

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • We are using Maximo 7.5 and Mobile Work Manager. In Mobile
    Data Manager
    we have used the Work Manager Options to add status INPRG to the
    WORKORDER object, meaning that it should be possible to send
    only the status change for a WO from APPR to INPRG from Mobile
    to core, without sending the whole WO record.
    
    
    
    
    A WO is created in core, required information is populated and
    status changed to ISSUED, which is a synonym of APPR.
    
    
    Through the Mobile Data Manager query, the WO is downloaded to
    the Mobile client.
    
    
    When changing status of the WO in Mobile, to INPRG and clicking
    OK  there is an error message:
    
    
    "Could not send status to Maximo server.  The work order status
    was previously changed in server."
    
    
    But the workorder has not at all been changed, updated or
    modified in core Maximo, so I can't understand where this
    message is coming from.
    
    We can send other information that updated the workorder in
    core, like Actual labor hours or material usage.
    
    
    Steps to reproduce issue:
    
    Error when sending WO status change from Mobile to
    core Maximo
    
    Create a new a status, ISSUED  in the WOSTATS domain, which is
    a synonym of APPR.
    
    
    Add INPRG as a status to WORKORDER in Work manager options in
    Mobile  Data Manager
    
    Create a new Workorder record and change it to status ISSUED.
    
    In Maximo Mobile homepage, pull up this new work order and
    select to change status to INPRG
    
    You will get  the following error:
    
    "Could not send status to Maximo Server:
     The work order status was previously changed in server."
    
    
    The logs show the following:
    
    Here is the error in the log:
    
    
    [12/7/12 9:08:56:302 UTC] 0000002b SystemOut     O 07 Dec 2012
    09:08:56:
    302 [INFO] [MAXTESTUI] [] mobileserviceinterceptor: doPost()
    called
    /maximomobile/mobileservice/MOBILEWO
    [12/7/12 9:08:56:302 UTC] 0000002b SystemOut     O 07 Dec 2012
    09:08:56:
    302 [INFO] [MAXTESTUI] [] mobileserviceinterceptor: content
    Length = 615
    [12/7/12 9:08:56:333 UTC] 0000002b SystemOut     O 07 Dec 2012
    09:08:56:
    333 [ERROR] [MAXTESTUI] [] [BMEX03] Failed to invoke method
    changeWOStatus
    [12/7/12 9:08:56:333 UTC] 0000002b SystemOut     O 07 Dec 2012
    09:08:56:
    333 [ERROR] [MAXTESTUI] [] [BMEX03]      Parameter Count = 6
    [12/7/12 9:08:56:333 UTC] 0000002b SystemOut     O 07 Dec 2012
    09:08:56:
    333 [ERROR] [MAXTESTUI] [] [BMEX03]             App Name =
    MOBILEWO
    [12/7/12 9:08:56:333 UTC] 0000002b SystemOut     O 07 Dec 2012
    09:08:56:
    333 [ERROR] [MAXTESTUI] [] Exception:
    java.lang.reflect.InvocationTargetException
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke
    (NativeMethodAccessorImpl.java:60)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke
    (DelegatingMethodAccessorImpl.java:37)
     at java.lang.reflect.Method.invoke(Method.java:611)
     at com.mro.mobile.webservice.WebServiceInvocationHandler.
    invokeAppServiceBean(WebServiceInvocationHandler.java:314)
     at com.mro.mobile.servlet.ServiceInterceptorServlet.doPost
    (ServiceInterceptorServlet.java:326)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
     at com.ibm.ws.webcontainer.servlet.ServletWrapper.service
    (ServletWrapper.java:1657)
     at com.ibm.ws.webcontainer.servlet.ServletWrapper.service
    (ServletWrapper.java:1597)
     at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter
    (WebAppFilterChain.java:104)
     at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter
    (WebAppFilterChain.java:77)
     at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter
    (WebAppFilterManager.java:908)
     at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest
    (ServletWrapper.java:934)
     at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest
    (ServletWrapper.java:502)
     at
    com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest
    (ServletWrapperImpl.java:179)
     at
    com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleReques
    t
    (CacheServletWrapper.java:91)
     at
    com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.
    java:864)
     at
    com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContai
    ner.
    java:1592)
     at
    com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLin
    k.
    java:186)
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.
    handleDiscrimination(HttpInboundLink.java:452)
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.
    handleNewRequest(HttpInboundLink.java:511)
     at
    com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequ
    est
    (HttpInboundLink.java:305)
     at
    com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complet
    e
    (HttpICLReadCallback.java:83)
     at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.
    futureCompleted(AioReadCompletionListener.java:165)
     at com.ibm.io.async.AbstractAsyncFuture.invokeCallback
    (AbstractAsyncFuture.java:217)
     at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions
    (AsyncChannelFuture.java:161)
     at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
     at
    com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
     at
    com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHand
    ler.
    java:775)
     at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)
    Caused by:
    psdi.util.MXApplicationException: BMXAF2202E - The work order
    status
    was previously changed in server.
     at com.mro.mobile.appservice.mobilewo.MobileWOServiceBean.
    changeWOStatus(MobileWOServiceBean.java:275)
     ... 32 more
    
    
    System information:
    
    App Server IBM WebSphere Application Server 7.0
    
    Version IBM Maximo Asset Management 7.5.0.2 Build 20120219-2030
    DB
    Build V7502-00
    IBM Maximo for Service Provider 7.5.0.0 Build 20110417-2000 DB
    Build
    V7500-16
    Tivoli's process automation engine 7.5.0.2-IFIX20120706-1221
    Build
    20120219-2030 DB Build V7502-25
    Mobile 7.5.0.0 Build 20110421-1725 DB Build V7500-07
    IBM Maximo Asset Management Scheduler 7.5.0.0 Build BUILD_NUM DB
    Build
    V7501-03
    
    Server OS Windows Server 2008 R2 6.1 build 7601 Service Pack 1
    
    Server DB Oracle 11.2 (Oracle Database 11g Enterprise Edition
    Release
    11.2.0.3.0 - 64bit Production With the Partitioning, Real
    Application
    Clusters, Automatic Storage Management, OLAP, Data Mining and
    Real Application Testing options)
    

Local fix

  • Dev to provide fix
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Mobile7.5.0.0                                                *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * ERROR WHEN SENDING WO STATUS CHANGE FROM MOBILE TO CORE      *
    * MAXIMO                                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * No                                                           *
    ****************************************************************
    

Problem conclusion

  • The problem is already fixed on Mobile 7.5.1.0
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV39747

  • Reported component name

    MOBILE WORK MAN

  • Reported component ID

    5724R62WM

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-04-12

  • Closed date

    2013-08-01

  • Last modified date

    2013-08-01

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

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

Fix information

  • Fixed component name

    MOBILE WORK MAN

  • Fixed component ID

    5724R62WM

Applicable component levels

  • R750 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

IBM Maximo Mobile Work Manager
Mobile Work Mgr

Software version:

750

Reference #:

IV39747

Modified date:

2013-08-01

Translate my page

Machine Translation

Content navigation