Sage 100

 View Only
  • 1.  VI Import into A/P Invoice Data Entry - with J/C i

    Posted 07-23-2012 10:01
    VI Import into A/P Invoice Data Entry - with J/C info: Import was/is working fine in 4.30, but now having issue in 4.5. When the Job # changes on the lines for a given invoice, the system appears to be treating it as a Header record (i.e. HS Record) as opposed to a Line record (i.e., L Record). So for a given invoice, the 1st 3 lines are for Job #123, and they appear to import fine. But on that 4th line for that invoice which is for Job #124, it appears the system is treating it as a Header record - and therefore it fails. And then when the Job # changes again for the lines on that invoice, it does the same thing, in that it appears it's being treated as a Header record. Records tab is still set as ""Skip Record if Job # = blank"" - because we do have some blank records in the Excel file that we do in fact want to skip. Thoughts?


  • 2.  RE: VI Import into A/P Invoice Data Entry - with J/C i

    Posted 07-23-2012 14:44
    I'll just check the most obvious (to me anyway): In VI, there are fields for H.JobNo and a L.JobNo. To which field are you assigning the job number in your import?


  • 3.  RE: VI Import into A/P Invoice Data Entry - with J/C i

    Posted 07-23-2012 16:03
    If it is L.JobNo try removing the field and adding back - or possibly rebuilding the job. I've had to rebuild a lot of VI jobs when they hit 4.4. Is anything else a header record that you're reading from the file that might be changing when the job# changes?


  • 4.  RE: VI Import into A/P Invoice Data Entry - with J/C i

    Posted 07-24-2012 10:30
    My 4.30 import job has H.JobNo and L.JobNo, both pulling from the same spot in my source file. And at the end of my import job I also have another L.JobNo, which is set to Assign nothing/blank if {AP_InvoiceDetail.CostCode$} = """" . Can't remember exactly why I had to do this originally, but I'm guessing I was running into an issue with line records that did not apply to a Job. So I tried removing the H.JobNo field from the 4.5 import, and that seemed to help. Prior to doing that I researched that Header JobNo field in the A/P Inv d/e header file, and it in fact is present in both 4.30 and 4.5 - and it appears that field gets populated with the 1st Job # used on the Lines - although I still don't quite understand the purpose of that field when it's very possible that the Lines will reference multiple Jobs.