Sage 100

I'd definitely take a look in SQL.  If duplicates of the SQL primary key have happened, that is bad... but what Sage considers to be the key fields, and what SQL considers to be the key fields, may be different.

That's what I was thinking, like maybe the key was considered only the item, warehouse, and bin, and not the Lot Number. It's doing it on all 4 records, so I don't feel like it's file corruption.

I'd definitely take a look in SQL.  If duplicates of the SQL primary key have happened, that is bad... but what Sage considers to be the key fields, and what SQL considers to be the key fields, may be different.

I'd look at the raw data, absolutely, and assume nothing.  My secondary worry would be a corrupted data dictionary, causing a false warning in DFDM.

That's what I was thinking, like maybe the key was considered only the item, warehouse, and bin, and not the Lot Number. It's doing it on all 4 records, so I don't feel like it's file corruption.

I'd definitely take a look in SQL.  If duplicates of the SQL primary key have happened, that is bad... but what Sage considers to be the key fields, and what SQL considers to be the key fields, may be different.

Beth, 

the key value or this file is: Itemcode + WarehouseCode+LotSerialNo+PalletID

I tested what you are trying to do, and it happens on a clean install, so this is not data corruption.

To work around it try this:

• Change the qty on hand
• Add or change the field "palletid"
• Click UPDATE
• Tou will be asked to remove the old key answer YES
• Remove or change the pallet id back to what it was previously.
• Click Update
• You will be asked again to remove the old key – answer YES

you should now have just the one record and the qty on hand will be corrected.

I'd look at the raw data, absolutely, and assume nothing.  My secondary worry would be a corrupted data dictionary, causing a false warning in DFDM.

That's what I was thinking, like maybe the key was considered only the item, warehouse, and bin, and not the Lot Number. It's doing it on all 4 records, so I don't feel like it's file corruption.

I'd definitely take a look in SQL.  If duplicates of the SQL primary key have happened, that is bad... but what Sage considers to be the key fields, and what SQL considers to be the key fields, may be different.

Wow, @David Overholt - never would have thought of the pallet!  THANK YOU SO MUCH!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Beth, 

the key value or this file is: Itemcode + WarehouseCode+LotSerialNo+PalletID

I tested what you are trying to do, and it happens on a clean install, so this is not data corruption.

To work around it try this:

• Change the qty on hand
• Add or change the field "palletid"
• Click UPDATE
• Tou will be asked to remove the old key answer YES
• Remove or change the pallet id back to what it was previously.
• Click Update
• You will be asked again to remove the old key – answer YES

you should now have just the one record and the qty on hand will be corrected.

I'd look at the raw data, absolutely, and assume nothing.  My secondary worry would be a corrupted data dictionary, causing a false warning in DFDM.

That's what I was thinking, like maybe the key was considered only the item, warehouse, and bin, and not the Lot Number. It's doing it on all 4 records, so I don't feel like it's file corruption.

I'd definitely take a look in SQL.  If duplicates of the SQL primary key have happened, that is bad... but what Sage considers to be the key fields, and what SQL considers to be the key fields, may be different.

Anddddddd - today I was able to update the QOH without any issue.

WHY, COMPUTER, WHY?????????????????????????????

Wow, @David Overholt - never would have thought of the pallet!  THANK YOU SO MUCH!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Beth, 

the key value or this file is: Itemcode + WarehouseCode+LotSerialNo+PalletID

I tested what you are trying to do, and it happens on a clean install, so this is not data corruption.

To work around it try this:

• Change the qty on hand
• Add or change the field "palletid"
• Click UPDATE
• Tou will be asked to remove the old key answer YES
• Remove or change the pallet id back to what it was previously.
• Click Update
• You will be asked again to remove the old key – answer YES

you should now have just the one record and the qty on hand will be corrected.

I'd look at the raw data, absolutely, and assume nothing.  My secondary worry would be a corrupted data dictionary, causing a false warning in DFDM.

That's what I was thinking, like maybe the key was considered only the item, warehouse, and bin, and not the Lot Number. It's doing it on all 4 records, so I don't feel like it's file corruption.

I'd definitely take a look in SQL.  If duplicates of the SQL primary key have happened, that is bad... but what Sage considers to be the key fields, and what SQL considers to be the key fields, may be different.

WHAAAAAAA????   SAGE!!!!!!!!!!

Anddddddd - today I was able to update the QOH without any issue.

WHY, COMPUTER, WHY?????????????????????????????

Wow, @David Overholt - never would have thought of the pallet!  THANK YOU SO MUCH!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Beth, 

the key value or this file is: Itemcode + WarehouseCode+LotSerialNo+PalletID

I tested what you are trying to do, and it happens on a clean install, so this is not data corruption.

To work around it try this:

• Change the qty on hand
• Add or change the field "palletid"
• Click UPDATE
• Tou will be asked to remove the old key answer YES
• Remove or change the pallet id back to what it was previously.
• Click Update
• You will be asked again to remove the old key – answer YES

you should now have just the one record and the qty on hand will be corrected.

I'd look at the raw data, absolutely, and assume nothing.  My secondary worry would be a corrupted data dictionary, causing a false warning in DFDM.

That's what I was thinking, like maybe the key was considered only the item, warehouse, and bin, and not the Lot Number. It's doing it on all 4 records, so I don't feel like it's file corruption.

I'd definitely take a look in SQL.  If duplicates of the SQL primary key have happened, that is bad... but what Sage considers to be the key fields, and what SQL considers to be the key fields, may be different.

But it gets better - I had to do one over again and this time I had to change the Pallet.

I GIVE.

WHAAAAAAA????   SAGE!!!!!!!!!!

Anddddddd - today I was able to update the QOH without any issue.

WHY, COMPUTER, WHY?????????????????????????????

Wow, @David Overholt - never would have thought of the pallet!  THANK YOU SO MUCH!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Beth, 

the key value or this file is: Itemcode + WarehouseCode+LotSerialNo+PalletID

I tested what you are trying to do, and it happens on a clean install, so this is not data corruption.

To work around it try this:

• Change the qty on hand
• Add or change the field "palletid"
• Click UPDATE
• Tou will be asked to remove the old key answer YES
• Remove or change the pallet id back to what it was previously.
• Click Update
• You will be asked again to remove the old key – answer YES

you should now have just the one record and the qty on hand will be corrected.

I'd look at the raw data, absolutely, and assume nothing.  My secondary worry would be a corrupted data dictionary, causing a false warning in DFDM.

That's what I was thinking, like maybe the key was considered only the item, warehouse, and bin, and not the Lot Number. It's doing it on all 4 records, so I don't feel like it's file corruption.

I'd definitely take a look in SQL.  If duplicates of the SQL primary key have happened, that is bad... but what Sage considers to be the key fields, and what SQL considers to be the key fields, may be different.