Sage 100

 View Only
  • 1.  Created a VI import to pull in work orders (WO.MAS

    Posted 11-13-2013 13:54
    Created a VI import to pull in work orders (WO.MASTER) and everything appears ok in work order entry, but the component items on the materials tab do not update to the Req work order field in Item Maintenance/Inquiry (even though I've tried importing to the Qty committed field). Has anyone had success importing into Work Order Master? Any tricks I'm missing or is it a lost cause...


  • 2.  RE: Created a VI import to pull in work orders (WO.MAS

    Posted 11-13-2013 14:00
    I would guess it's missing the perform logic. It might be out there but didn't automatically get setup in the VI job, or it might be like importing into TimeCard where you have to manually rebuild the sort files after every import. I don't see any in the list except for WO memos...


  • 3.  RE: Created a VI import to pull in work orders (WO.MAS

    Posted 11-13-2013 14:03
    rebuild of WO definitely added the quantities - I'll check the perform logic but maybe rebuild is the answer - thanks Beth!


  • 4.  RE: Created a VI import to pull in work orders (WO.MAS

    Posted 11-13-2013 14:15
    Poor Work Order. Wish Sage would sell it to ACS.


  • 5.  RE: Created a VI import to pull in work orders (WO.MAS

    Posted 11-14-2013 10:40
    @BethBowers - couldn't agree more!


  • 6.  RE: Created a VI import to pull in work orders (WO.MAS

    Posted 11-15-2013 06:53
    We attempted this a few months back and contacted Sage for help. The one remaining person at Sage who knows what a work order is couldn't give us much. Frustrating because they have the attitude that WO is a legacy module so if something doesn't work don't expect us to fix it- even though the client continues to pay maintenance. We ended up using Sage Intelligence to add the materials to the import source spreadsheet and running an additional vi job to get them in. Thankfully they aren't using the routings yet so we could run one more vi job to assign a step to each WO. As a final step we had to run an export of all open WO material records and import the total to the Required for WO field in the Item Warehouse file because vi doesn't update that either. Needless to say the project was over budget and behind schedule. We didn't try what Beth suggested, sounds like it would have saved us some time.