Sage 100

 View Only
  • 1.  Hi. Tried the knowledge base on this and while it

    Posted 08-08-2011 20:49
    Hi. Tried the knowledge base on this and while it found a notation, the KB never came up. So am hoping someone here might have a suggestions. In SO Invoice DE (MAS90 4.05 w/JO) Client is getting an 47 SOWDED line 10068. Appreciate any help.


  • 2.  RE: Hi. Tried the knowledge base on this and while it

    Posted 08-09-2011 04:56
    Interesting. My search hangs also. Error 47's are data corruption errors. At what point is the program going south? When you begin, after entering an item? Probably will need to rebuild a key file or relink your line files....


  • 3.  RE: Hi. Tried the knowledge base on this and while it

    Posted 08-09-2011 06:00
    Pathetic, SSO KB still isn't working. Search Results come up but it just hangs upon clicking on them.


  • 4.  RE: Hi. Tried the knowledge base on this and while it

    Posted 08-09-2011 08:15
    Deb, Error 47 is short string. In this case the Shipping Invoice Detail (SO6$) is short. Analysis and Relink Line files S/O Invoice Line Detail File (SO6). Program is trying to check (21,1) Line Type and (81,1) Drop Ship flags. Drop DEBUG and PRINT SO6$ should give you the Invoice Number.


  • 5.  RE: Hi. Tried the knowledge base on this and while it

    Posted 08-09-2011 09:06
    Yep was still hanging for me too. Makes it so terribly useful. Kenneth, not sure I can A&L the line files as JO is installed. Will check...thanks for helping!


  • 6.  RE: Hi. Tried the knowledge base on this and while it

    Posted 08-09-2011 09:36
    Deb, I missed where you said they were using Job Ops. You cannot use Analyze & Relink Line files to fix Sales Order (SO2) Purchase Order (PO2) or S/O Invoice (SO6) detail line files. Instead the SO6 record must be fixed manually (per Job Ops Tech Reference Guide). You could use DFDM to find the pointer to the bad index and reset forward index pointer to 0. You may need to contact Job Ops to verify correct fix. You may also want to run the Job Ops Validation Utility.


  • 7.  RE: Hi. Tried the knowledge base on this and while it

    Posted 08-09-2011 09:41
    Per Job Ops 4.05 Tech Ref Guide: If the Sales Order Invnoice Data Enrtry file is damaged and Work Tickets are being invoiced, Analyze & Relink Line Files should not be used to repair data. Instead manually repair the data in the S/O Invoice Detail Line File (SO6) or manually reinitialize the SO6 file then re-eneter the invoices. Note: If the Sales Order Invoice Data Entry file is damaged and there are no Work Tickets being invoiced, you may use the Analyze & RelinkLine Files utility.


  • 8.  RE: Hi. Tried the knowledge base on this and while it

    Posted 08-09-2011 09:48
    That's what I read too. checking to see how many invoices are in the batch. Easiest answer is to reinitialize SO 5 & 6, but knowing them, there's a herd of invoices in the file.


  • 9.  RE: Hi. Tried the knowledge base on this and while it

    Posted 08-09-2011 12:14
    KB is active finally.......................... But unfortunately, as it has been noted, this fix will not work for Deb. Error 47 SOWDED 10068, in Sales Order Invoice Data Entry for Sage MAS 90 and 200 DETAILS : Error 47 SOWDED 10068, in Sales Order Invoice Data Entry Entry Type: Informational Product: Sage MAS 90 ERP, Sage MAS 200 ERP, Sage MAS 200 ERP - SQL Server Edition Application: Sales Order Version Reported: 3.71 Subject: Error 47 SOWDED 10068, in Sales Order Invoice Data Entry Possible Workaround: Note: Use caution when working with repair utilities. Always make a backup first. If necessary, seek the assistance of a qualified Sage Software business partner o Open Library Master / Repair / Analyze and Relink the SO6 file. Open Library Master / Repair / Rebuild Application Sort Files for the Sales Order module. Answer 'YES' to recalculate.