Sage 100

 View Only
  • 1.  MAS200 v4.40.6 - I'm trying to import into AR Invo

    Posted 02-24-2012 11:46
    MAS200 v4.40.6 - I'm trying to import into AR Invoice History Header a set of UDF values that didn't get posted correctly the first time around. My import job has the typical key fields along with the UDFs. The import is failing only on any invoices that had credit card payments/deposits associated with them with the Error 65 AR_CREDITCARDCOMMONENTRY.PVC 1790. I know Error 65s are typically a Custom Office thing, but that particular screen has not been customized at all, and I've already rebuilt all UDFs and screens multiple times to resolve any issues with the UDFs. Is there any other way to debug the error or anyone think of something else I can look at?


  • 2.  RE: MAS200 v4.40.6 - I'm trying to import into AR Invo

    Posted 02-24-2012 11:49
    Does it fail on the test and the live, or just the live?


  • 3.  RE: MAS200 v4.40.6 - I'm trying to import into AR Invo

    Posted 02-24-2012 11:51
    Both. I extracted all non-credit card invoices and imported first so it wouldn't keep stopping every few records, and now am dealing with the 2000 that do, and each one fails.


  • 4.  RE: MAS200 v4.40.6 - I'm trying to import into AR Invo

    Posted 02-24-2012 11:54
    Is your import job pulling cc# back in or just the changed / added fields?


  • 5.  RE: MAS200 v4.40.6 - I'm trying to import into AR Invo

    Posted 02-24-2012 11:56
    Just Inv No, Header Seq, Type and UDFs.


  • 6.  RE: MAS200 v4.40.6 - I'm trying to import into AR Invo

    Posted 02-24-2012 11:56
    There's no way I would try re-importing over the CC /authorization fields...thats' way too dangerous.


  • 7.  RE: MAS200 v4.40.6 - I'm trying to import into AR Invo

    Posted 02-24-2012 11:58
    Got to be some field that VI thinks is required but, in real life, manages to get by without being filled in or something like that. A lot of work, but you could export ALL of the record info for those 2000 records and import it ALL back in and you'd probably find out which field was causing the problem. Or since it bombs in a test, start throwing fields that look CC-ish on the import and see if you can figure it out that way.


  • 8.  RE: MAS200 v4.40.6 - I'm trying to import into AR Invo

    Posted 02-24-2012 12:02
    Maybe try removing validation on all but key fields?


  • 9.  RE: MAS200 v4.40.6 - I'm trying to import into AR Invo

    Posted 02-24-2012 12:03
    You could try having it read the problem fields from the existing records.