Sage 100

Is there a setting in Sage100 that will completely prevent the receiving of the same serial number in Sage?

It seems that Sage will allow you to have the same serial serial number for the same item as long as they are in different warehouses. As you imagine, this is creating lots of challenges now.

Does anyone know of a way to prevent this?

Thank you

Michael

------------------------------
Michael Davis
Warren Averett Technology Group
------------------------------

It is absolutely ridiculous that the programming does not recognize a conflict to have the same item, same serial number in different warehouses as a problem. I've just added an IDEA to our IDEAtion90 listing under Distribution; so we can put this in front of Sage Development with the next round of "ideas".  Give it a review, add comments and vote.  

------------------------------
Madeline Stefanou
RKL eSolutions, LLC
------------------------------

This has been a design characteristic since the Evolution 2 (character based) days, and likely even before that.  It has to do with the key structure used starting with the IM_ItemCost table.  The general key structure is ItemCode + WhsCode+TierType+GroupSort.  GroupSort is a combination of things that vary based on the TierType. LIFO/FIFO based on receipt data and LOT/SERIAL based on their unique numbers.  The way it is designed, Lot and Serial work identically with the exception that Serial type items are restricted to a quantity of no more than one.  And clearly, it is acceptable to carry the same item/lot in two warehouses as far as the key structure is concerned.  I feel your pain, but I expect Sage to come back with WAD on this one... saying the manufacturer assigns the serial number and therefore, there should not be more than one of anything...

As you can see, this all works fine for all other tier types except serial.  And serial works fine as long as the manufacturer creates truly unique serial numbers for you to use.  if this is not the case for some reason, you must only use one warehouse, or only use one warehouse to sell out of and only use other warehouses to move damaged or expired inventory into prior to whatever procedures are needed to deal with them.  

------------------------------
Randy Marion
------------------------------

There was a thread on this topic a while back.  A post in the thread below indicated that DSD wrote custom code to minimize the pain point.  Another post indicated that Sage was taking the WAD defense.

Serialized Item - Qty greater than one allowed if different warehouse. Is this right?? | Sage 100

While it never hurts to create an Ideation suggestion, don't expected any action from Sage unless there is a business case for increasing Sage's revenue stream with the rewrite....

------------------------------
Jeff Schwenk
Owner
Bottomline Software, Inc.
Waynesboro VA
(540) 221-4444

Improving bottom lines for over 25 years!
------------------------------

Original Message:
Sent: 02-04-2025 13:05
From: Randy Marion
Subject: Duplicate Serial Numbers in Sage (Different Warehouses)

This has been a design characteristic since the Evolution 2 (character based) days, and likely even before that.  It has to do with the key structure used starting with the IM_ItemCost table.  The general key structure is ItemCode + WhsCode+TierType+GroupSort.  GroupSort is a combination of things that vary based on the TierType. LIFO/FIFO based on receipt data and LOT/SERIAL based on their unique numbers.  The way it is designed, Lot and Serial work identically with the exception that Serial type items are restricted to a quantity of no more than one.  And clearly, it is acceptable to carry the same item/lot in two warehouses as far as the key structure is concerned.  I feel your pain, but I expect Sage to come back with WAD on this one... saying the manufacturer assigns the serial number and therefore, there should not be more than one of anything...

As you can see, this all works fine for all other tier types except serial.  And serial works fine as long as the manufacturer creates truly unique serial numbers for you to use.  if this is not the case for some reason, you must only use one warehouse, or only use one warehouse to sell out of and only use other warehouses to move damaged or expired inventory into prior to whatever procedures are needed to deal with them.  

------------------------------
Randy Marion
------------------------------

I've seen this in the situation where my customer is using Bill of Materials to create serialized items. I can't recall what got them to the duplicate serial items. It was either that someone create the same serial number to separate warehouses or it came in on an RMA somehow. It doesn't happen very often but when it does it seems to be a DFDM project.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
CT
------------------------------

Thank you every for the suggestions. My search skills were definitely off yesterday. The DSD options look interesting.

I also found an KB on Sage for WO talking about the similar, so I am sure in Sage's mindset it is WAD. Thanks for adding as a 90 mind suggestion, may be Sage will rethink this.

------------------------------
Michael Davis
Warren Averett Technology Group
------------------------------

Original Message:
Sent: 02-05-2025 08:32
From: Wayne Schulz
Subject: Duplicate Serial Numbers in Sage (Different Warehouses)

I've seen this in the situation where my customer is using Bill of Materials to create serialized items. I can't recall what got them to the duplicate serial items. It was either that someone create the same serial number to separate warehouses or it came in on an RMA somehow. It doesn't happen very often but when it does it seems to be a DFDM project.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
CT
------------------------------