Maximo Anywhere

Expand all | Collapse all

IJ07847 - Resolved in Anywhere FIX001

  • 1.  IJ07847 - Resolved in Anywhere FIX001

    Posted 10 days ago
    Just curious if anyone who has Anywhere 7.6.4 ifix001 can confirm if this is resolved or not. I was just playing around in our Dev and it appears I managed to do a count on an obsolete item even after having ifix001 installed already from the Physical count default query

    (physcntdate <= (getDate() - ccf)) and stagingbin=0 and rotating=0


    Thanks

    IJ07847: MAXIMO ANYWHERE PHYSICAL COUNTS APPLICATION ALLOWS RECOUNTS TO HAPPEN ON OBSOLETE ITEMS.


    ------------------------------
    Ryan Medernach
    Application Support
    MEG Energy
    Calgary AB
    ------------------------------


  • 2.  RE: IJ07847 - Resolved in Anywhere FIX001

    Posted 9 days ago
    Edited by Bradley Downing 9 days ago
    After applying the fix and rebuilding the app, I trust you deleted the onboard data from your device, or in the case of using iOS you deleted the app and re-downloaded it?  Or did this occur in the emulator after you flushed cache from there?

    ------------------------------
    Bradley K. Downing , MBA
    IBM Certified Adv. Deployment Prof. Maximo v7.6.1
    IBM
    Bakersfield CA
    ------------------------------



  • 3.  RE: IJ07847 - Resolved in Anywhere FIX001

    Posted 9 days ago
    This is Android and a fresh rebuild and deploy to a tablet. I'm more curious if anyone else is seeing this issue. I'm thinking maybe I missed a configuration when having to merge all the files as the ifix is a straight overwrite (unzip overtop of your existing configs/app/etc.). It could be just a deployment error on my side.

    The README.txt with the list of fix's doesn't state what file(s) may have been changed to resolve this issue. It would be nice if the standard used for Maximo IFIX's was followed with a ListOfAPARs&ChangedFiles.xlsx


    Thanks

    ------------------------------
    Ryan Medernach
    Application Support
    MEG Energy
    Calgary AB
    ------------------------------



  • 4.  RE: IJ07847 - Resolved in Anywhere FIX001

    Posted 9 days ago
    I have not seen this. If you are thinking that perhaps there is a merge issue then I would also suggest the following: review your build folders and ensure that if you are using Eclipse that you ensure your workspace gets the update as well as your install folder.  I cannot tell you how many times I have made a change, gone through a build process, sand say "WTF! Where is my change!?" only to realize that I did not manage my change correctly.  Not saying you are as silly as me... just a warning that you may have overlooked your workspace?

    And yes having the ability to see which files have been modified is nice.  Although if you have followed best practice you should hnot have to worry about this since all your customizations ar win your now custom extensions and any overwrites will not affect those directly.  The only exception to this is the application's app.xml.  But that also should not be an issue if you have a) properly commented out the old code and inserted/ updated you own code with comments. The updates will then not interfere with your customization in most cases.

    ------------------------------
    Bradley K. Downing , MBA
    IBM Certified Adv. Deployment Prof. Maximo v7.6.1
    IBM
    Bakersfield CA
    ------------------------------



  • 5.  RE: IJ07847 - Resolved in Anywhere FIX001

    Posted 8 days ago
    I'm not sure what version you're on of core Maximo, but I hit a different issue entirely where physical counts don't work at all. With the new inventory work centers they added in 7.6.1.1 they added a nextphyscntdate attribute to invbalances to track when the next physical count will be due. Anywhere enters the physical count against a view they created instead of directly against INVBALANCES. Well this view doesn't have this attribute and causes the error "BMXAA4176E - Attribute NEXTPHYCNTDATE does not exist. Gather the logs from the <HOME> directory and determine the process or app referencing the invalid attribute."

    I'm going to open this case with IBM. Sorry I couldn't be more help but I appreciate the forum post as it allowed me to test the physical count app for the first time in a long time and find a brutal blocker for some of our customers.

    ------------------------------
    Steven Shull
    Director of Development
    Projetech Inc
    Cincinnati OH
    ------------------------------



  • 6.  RE: IJ07847 - Resolved in Anywhere FIX001

    Posted 7 days ago
    Hi Steven,

    Have faced same issue and IBM have documented resolution steps in below URL.
    FYRP, if you have missed it.

    https://www.ibm.com/support/pages/attribute-nextphycntdate-does-not-exist-when-performing-physical-count

    ------------------------------
    Kalaiselvan Matheswaran
    ------------------------------



  • 7.  RE: IJ07847 - Resolved in Anywhere FIX001

    Posted 7 days ago
    I appreciate you sending this. IBM had sent me this in the case but I had not seen it before then. I'm still trying to get them to attempt to fix in the update scripts as it's not something users should have to do manually IMO. I'm sure it has to do with Anywhere supporting more than just 7.6.1.1/7.6.1.2 so they couldn't blindly create it, but DBC files support evaluating results of a query first so it should be easy for them to tell if the customer has the attribute or not to then modify the view to avoid the issue for most customers.

    ------------------------------
    Steven Shull
    Director of Development
    Projetech Inc
    ------------------------------



  • 8.  RE: IJ07847 - Resolved in Anywhere FIX001

    Posted 7 days ago
    Hi Steven,

    This behaviour has been previously reported. Unfortunately there was not a way to automatically detect the exact fix pack version of Maximo in order to provide a fix in an interim fix or fix pack. The method to fix this for Maximo 7.6.1.1 and above is available here: https://www.ibm.com/support/pages/attribute-nextphycntdate-does-not-exist-when-performing-physical-count


    ------------------------------
    Jason Caerels
    QA Lead
    IBM
    ------------------------------