Prev
Next
Forums Supply Chain Management Infor SCM

MSCM-Item not crossing

 1 Replies
 0 Subscribed to this topic
 17 Subscribed to this forum
Sort:
Author
Messages
Patricia Mane
Basic Member
Posts: 24
Basic Member
8/22/2016 12:37 PM

    We have several inventory locations within our facility..  Our Surgery Center added a couple items and replaced a couple.  When they attempt to do the download to handhelds for counting, we have this one item that will not cross over.  It has been verified and everything is setup correctly.  Outside of bouncing the server, can anyone provide any guidance on what else to look at.  It is our understanding that items should cross within seconds of being added to an inventory location.

    Thanks

    JimY
    Veteran Member
    Posts: 510
    Veteran Member
    8/22/2016 4:51 PM
      Hi Patricia,
      Not sure if this will help. We had a similar issue when a clerk would order an item through the hand held it would create a requisition, but a blank line. We found that even though the item was set up correctly in the par location it was not showing up in MSCM. Below is what Infor Support had us do to correct it. It clears out the tables and then they get rebuilt when you restart Websphere on your MSCM Server. I would talk to them first before you try it.

      To correct these items, use IC12 and set the Allow Issues flags to Y or you can Quickpaint the ITEMLOC table on the Lawson schema; the ALLOW-ISS-FL should either be 'Y' or 'N'; this field should never be blank, as it is a Boolean value (Y/N).

      After correcting the items, please do the following:

      1. Stop MSCM in WebSphere (both Enterprise Application and Application)
      2. Run these statements in MSCM database which will clear your staging tables and then repopulate everything.

      TRUNCATE TABLE MSCM.MSCM.LAWSON_ITEMLOC
      TRUNCATE TABLE MSCM.MSCM.LAWSON_ITEMSRC
      TRUNCATE TABLE MSCM.MSCM.LAWSON_BINGRPDTL
      TRUNCATE TABLE MSCM.MSCM.ICAUDIT_TRACKER

      3. Restart MSCM in WebSphere
      4. Allowed the MSCM system to repopulate these tables-- note this make take some time as all S3 data from the truncated tables will be refreshed

      5. Retest the issue again and let me know the results.