BOM Bug

SOLVED

Hi Sage 200 Support

I have been asking for this since we migrated from Sage 50 to Sage 200. 

Is this ever going to be fixed? If I am not mistaken this has been like this for years. The last answer was given to my BP:

"This is in the list of higher priority bugs that I have asked R&D to review for potentially fixing as part of the development work in the future release of Sage 200"

This is something critical to my company!

Looking forward to hearing something from Sage. 

  • 0
    SUGGESTED

    Hi Samuel,

    I have checked the details of the bug you mentioned and note you have not been added as a contact by your Business Partner. Please review this article which will help you pull together a quantified Business Impact which you can provide to your BP to pass to us. The business impact will help us in prioritising which issues to resolve in future versions of the software.

    Kind regards,

    David Stubbings, Technical Support Consultant.

  • 0 in reply to David Stubbings

    Hi David

    Many thanks for your reply. 

    My BP will pull together 'quantified Business Impact'.

    Although I must be honest, if it is true that this problem has been going on for years (this was first reported in v2015) Sage should have fixed it with or without pulling together 'quantified Business Impact'. 

    I can accept that might be other priorities, but waiting 6 years??!! 

    Kind Regards 




  • 0 in reply to David Stubbings

    Morning David

    We have the same problem. Has any progress been made?

    Regards

  • +1
    verified answer

    Hi all

    After a lot of insistence, Sage has finally sorted this out for me. 

    I will share the solution with the comunity.

    1 - MSEStockItem - Remove Duplicates

     

    Delete from MseStockItem Where MseStockItemID in
    (
                    select MseStockItemID from
                    (
                                    select B.MseStockItemID, ROW_NUMBER() OVER (PARTITION BY B.StockCode ORDER BY B.DateTimeCreated) AS RowID from MseStockItem B
                    ) A
                    where A.RowID > 1
    )
    

    2 - MSEWarehouseItem - Remove Duplicates

    Delete from MseWarehouseItem Where MseWarehouseItemID in
    (
                    select MseWarehouseItemID from
                    (
                                    select B.MseWarehouseItemID, ROW_NUMBER() OVER (PARTITION BY B.WarehouseItemID ORDER BY B.DateTimeCreated) AS RowID from MseWarehouseItem B
                    ) A
                    where A.RowID > 1
    

    3- Set Missing Default Warehouse

    DECLARE @Counter bigint
    SET @Counter = (SELECT TOP 1 NextValue FROM Counter)
    UPDATE Counter SET NextValue = NextValue + 1
    
    INSERT INTO MseWarehouseItem(MseWarehouseItemID, WarehouseItemID, IsDefaultWorksOrderWarehouse)
                    SELECT @Counter + RANK() OVER (ORDER BY WarehouseItemID), WarehouseItemID, 0 
                    FROM WarehouseItem 
                    WHERE (WarehouseItemID NOT IN (SELECT WarehouseItemID FROM MseWarehouseItem))
    
    IF (SELECT MAX(MseWarehouseItemID) FROM MseWarehouseItem) > @Counter
                    UPDATE Counter SET NextValue = (SELECT MAX(MseWarehouseItemID) + 1 FROM MseWarehouseItem)
    
    DECLARE itemCursor CURSOR FOR SELECT DISTINCT ItemID FROM WarehouseItem
    DECLARE @ItemID bigint
    OPEN itemCursor
    
    FETCH Next FROM itemCursor INTO @ItemID
    WHILE @@FETCH_STATUS = 0
    BEGIN
                    IF NOT EXISTS(SELECT TOP 1 * FROM MseWarehouseItem, WarehouseItem WHERE MseWarehouseItem.WarehouseItemID = WarehouseItem.WarehouseItemID AND WarehouseItem.ItemID = @ItemID AND MseWarehouseItem.IsDefaultWorksOrderWarehouse = 1)
                    BEGIN
                                    UPDATE MseWarehouseItem SET IsDefaultWorksOrderWarehouse = 1
                                    WHERE WarehouseItemID = (SELECT TOP 1 WarehouseItemID FROM WarehouseItem WHERE ItemID = @ItemID)
                    END
    
                    FETCH Next FROM itemCursor INTO @ItemID
    END