Physical Count allows duplicate Serial #'s

Hi,

We just became aware that the Physical Count entry allows you create duplicate Serial #'s.    We would like to find a way to not allow this.

Scenario:   We have multiple warehouses set up, and are in a multi-bin environment.   When you for instance make an Adjustment via Transaction Entry, when you try to use a serial # that has already been used for the item, Sage pop's up and tells you it is in use and you cannot use it, or when you try to enter the distribution, it wont let you (it does allow the same Serial # on different item #'s.)

But when you do a Physical Count, it lets you do anything.   In our case when it became clear, we had an item that was transferred from one warehouse to another.  When transferred, it shows in the new warehouse in location  "In Transit".   A few days later at the receiving warehouse they did a physical count and the same item/serial # was added to a different Bin Location.   Now, it shows a Qty of 2 On Hand for that Item/Serial #, when in fact there is one.   

The one in a regular bin location shipped/invoiced and is now gone, but we still show one in "In Transit".

The question is:  Why is this allowed, and what can we do to prevent this?  Users here are good about not allowign this normally, but I would like a way of preventing it from even possibly happening.  Sage controls it in some areas but not here for some reason

Thank you.

Parents
  • 0

    Sounds like a bug.  I didn't see anything in the KB that looked relevant to your issue unless you are importing the items into physical count.

    Which MB solution are you using, DSD or Scanco?  You should open a case with the appropriate one and you might have to open a case with Sage.

    If you can, try to duplicate the issue in a test company by copying your production company to a new company code for testing.  This will help you prepare steps needed to duplicate the issue which will usually expedite the support cases.

Reply
  • 0

    Sounds like a bug.  I didn't see anything in the KB that looked relevant to your issue unless you are importing the items into physical count.

    Which MB solution are you using, DSD or Scanco?  You should open a case with the appropriate one and you might have to open a case with Sage.

    If you can, try to duplicate the issue in a test company by copying your production company to a new company code for testing.  This will help you prepare steps needed to duplicate the issue which will usually expedite the support cases.

Children
No Data