MSCM SOH Information

 3 Replies
 2 Subscribed to this topic
 38 Subscribed to this forum
Sort:
Author
Messages
Jimmie
Basic Member
Posts: 22
Basic Member

    Good morning, 

     

    We are on 10.1.8.25 and currently working through a couple of items.  One is having an issue where our techs are scanning out inventory but when the issue reaches MSCM from the device it goes into a unreleased status due to insufficient SOH.  Once we are aware of this we make the necessary adjustments on inventory but we aren't always finding them.  Has anyone else found a way to stop the handheld from performing an issue when the SOH is not enough according to S3?  Is there a way to get that information to a handheld device?  

     

    Alternately, how do you handle the inventory updates for situations like this to keep this from occurring?  Do you find this is more of an issue when you have auto receiving in place for daily deliveries?

    Kat V
    Veteran Member
    Posts: 1020
    Veteran Member
      No - because you can do the same thing in S3 on IC21. You can add whatever lines, qty and uom you want as long as it's active in the IC12. It's not until you release it that you get the error - which is what happens in MSCM.

      If it helps - it *is* adding them in IC21 - we find it easier to work and release from there.
      Jen U
      New Member
      Posts: 2
      New Member

        We created an IPA flow to identify these issues and send an email to the end-users.  

        JimY
        Veteran Member
        Posts: 510
        Veteran Member
          Hi Jen U,
          Would you be willing to share the flow? I would be interested. Thank you.