Prev
Next
Forums Lawson S3 Supply Chain

IC81 changes not updating in MSCM MPC

Sort:
You are not authorized to post a reply.
Author
Messages
F Rongione
New Member
Posts: 2
New Member
4/16/2013 7:28 PM

    We recently upgraded our Lawson environment to 9.0.1.11 from 9.0.1.5.  We are on MSCM MPC 9.0.1.2.4.  After we did the environment upgrade, changes made to pars in IC81 stopped flowing over to the MSCM MPC pars.  Has anyone else had this problem?  Lawson told us to purge ICAUDIT records to make this work.  We have purged a lot of records from ICAUDIT and the changes in IC81 are still not updating in the hand held.  Any ideas?

    Greg Moeller
    Veteran Member
    Posts: 1498
    Veteran Member
    4/16/2013 7:38 PM
      We have this happen ALL the time.... so often, in fact, that I've scheduled a script to be run at least once a day to fix this.
      Lawson will tell you that PT so-and-so fixes this, so you upgrade to that version that includes it, but sooner or later, it'll break again.
      Here's the script that I wrote and scheduled: 
       
##  Execute sqlplus to determine which emps qualify for term
    /usr/local/bin/sqlplus -s mscm/password@sid < /dev/null 2>&1
     DELETE
     FROM MSCM.ICAUDIT_TRACKER
;
commit
;
exit
ENDSQL
      Greg Moeller
      Veteran Member
      Posts: 1498
      Veteran Member
      4/16/2013 7:40 PM
        This deletes the last update time from the MSCM database, and upon the next round of queries (we have ours scheduled every 15 minutes), it will see that it hasn't done an update yet, and will force one.
        JonA
        Veteran Member
        Posts: 1162
        Veteran Member
        4/16/2013 7:46 PM
          We have to do this from time to time as well and it does the trick.
          Jon Athey - Sr. Supply Chain Analyst - Materials Management - MyMichigan Health
          F Rongione
          New Member
          Posts: 2
          New Member
          4/17/2013 1:11 PM
            Thanks for the information.  We are hosted by Velocity so I will work with me on your suggested script.  
            Leslie
            Veteran Member
            Posts: 45
            Veteran Member
            5/9/2013 7:56 PM
              We have this problem as well; we "solved" it by turning off the auditing function for the item location (IC192) in the IC01 setup, but that brings its own set of issues.
              The Alchemist
              Advanced Member
              Posts: 34
              Advanced Member
              5/9/2013 8:25 PM
                I know you said changes in IC81 but thought it might be worth mentioning that if end users are crossing over into IC82 we have seen that most changes do not carry over to MSCM. I believe it is because it does not create an audit record but dont quote me on that.
                You are not authorized to post a reply.