Sage 100

 View Only
Expand all | Collapse all

Just ran into this on Sage 100 v2016 Advanced -- i

  • 1.  Just ran into this on Sage 100 v2016 Advanced -- i

    Posted 12-14-2016 08:20
    Just ran into this on Sage 100 v2016 Advanced -- is this a bug or WAD? One component of a Kit does not explode in Sales Order Entry Products Sage 100 Description In Sales Order Entry, a Kit Item is entered. When it explodes the components, one of the components is missing from the Lines tab. Components of an Options Bill do not populate Sales Order Entry when the option is exploded. Cause **The component item is missing a Primary Vendor in Item Maintenance.** Resolution - Open Inventory Management, Main, Item Maintenance. - Select your component Item Code. - On the Main tab, enter a Primary Vendor, then press Accept. - In Sales Order Entry, enter the Kit item and click No ""to explode the lines to order by component"". - After you enter an Ordered quantity, click on the Totals tab and the kit will explode all components.


  • 2.  RE: Just ran into this on Sage 100 v2016 Advanced -- i

    Posted 12-14-2016 08:22
    Link to Sage KB Entry - [here](https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=51290&sliceId=1&dialogID=6723&cmd=displayKC&docType=kc&noCount=true&stateId=6724&isLoadPublishedVer=&docTypeID=DT_Article&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl)


  • 3.  RE: Just ran into this on Sage 100 v2016 Advanced -- i

    Posted 12-14-2016 08:23
    It's a regular inventory item


  • 4.  RE: Just ran into this on Sage 100 v2016 Advanced -- i

    Posted 12-14-2016 08:23
    Is the item not appearing a miscellaneous code? If so, then I think it is a WAD Bug......


  • 5.  RE: Just ran into this on Sage 100 v2016 Advanced -- i

    Posted 12-14-2016 08:28
    Wonder if it's related to that issue of the Primary Vendor missing from...imports? Some other issue is linked to that missing vendor.


  • 6.  RE: Just ran into this on Sage 100 v2016 Advanced -- i

    Posted 12-14-2016 08:36
    This seems to be primarily an issue with kit type BOM where the component (including subassembly) does not have a primary vendor. It's a rather nasty surprise IMO because there's no warning - the kit component just does not appear on the order.


  • 7.  RE: Just ran into this on Sage 100 v2016 Advanced -- i

    Posted 12-14-2016 08:43
    The component will print on any of the BOM reports


  • 8.  RE: Just ran into this on Sage 100 v2016 Advanced -- i

    Posted 12-14-2016 08:49
    I'm going to check with Sage but I think @BethBowers is onto something - possibly the issue is when the division number has a value but the vendor is blank https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=23875&sliceId=1&cmd=displayKC&dialogID=8040&docType=kc&isLoadPublishedVer=&stateId=8041&docTypeID=DT_Article&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl


  • 9.  RE: Just ran into this on Sage 100 v2016 Advanced -- i

    Posted 12-14-2016 09:06
    I called Sage and they say there's no update on this KB. I think the issue arose when I imported a lists of primary vendors to inventory. I assigned 00 and the primary division and the column holding the primary vendor was sometimes blank. I believe the problem arises if you import a value to the primarydivision and the primary vendor is left blank during VI. I tested this with DFDM to CI_Item$ by blanking fields 36 and 37 (primary division / primary vendor) and then placed a kit type bill onto an SO and the components exploded as expected. I still think it's a bug but apparently not high on Sage's fix list. This issue **should not arise under normal circumstances** when you enter an item manually and are not also using VI to import the primary vendor.


  • 10.  RE: Just ran into this on Sage 100 v2016 Advanced -- i

    Posted 12-14-2016 09:15
    Resolution: - Used Crystal to export out list of all CI_Item where PrimaryDivision = ""00"" (which is what I assigned) and PrimaryVendor="""" - Use VI to import to those items and set PrimaryDivsion=


  • 11.  RE: Just ran into this on Sage 100 v2016 Advanced -- i

    Posted 12-14-2016 10:28
    trying to catch up. Does this error / problem, happen; when the component items have ""no primary vendor"" at all? Not all companies record a primary vendor for their items. Or is it related to an ""incomplete"" primary vendor (one missing the ""00"" division?


  • 12.  RE: Just ran into this on Sage 100 v2016 Advanced -- i

    Posted 12-14-2016 13:35
    The problem occurred for me when an item have a primary vendor division # but the primary vendor number was blank. In my case the issue arose because I used VI to import primary vendors and must have imported some where the vendor number was blank (yet I was assigning the division to be 00)