Sage 100

 View Only

  • 1.  Transaction Journal VI import

    Posted 08-17-2020 15:30
      |   view attached
    Sage 100 2017 VI job for GL_Transaction Journal for bank transfers - job works in Test Company and test in the live company says it works but when actually importing into live ti gives and error that "Bank code is required" on each header line, even though the bank code is supplied (and shows in the log) and is valid.

    Any ideas?

    ------------------------------
    Phil McIntosh
    President
    Friendly Systems, Inc.
    Asheville NC
    678.273.4010 ext 5
    ------------------------------


  • 2.  RE: Transaction Journal VI import

    Posted 08-17-2020 15:38
    If the VI job has worked before, see if anything in the source-data-format may have changed.

    --

    Friendly Systems, Inc.

    Sage 100 (Mas90/200), Sage 300 (Accpac), SageCRM, xTupleERP
    Visit us on the web at www.friendlysystems.com
    Office:?? 678.273.4010 ext 4
    Mobile: 404.202.9065
    Fax:?????????? ??678.273.4012
    See our blog at www.friendlysystems.com/blog






  • 3.  RE: Transaction Journal VI import

    Posted 08-17-2020 15:44
    I always check the "has anything changed" factor in the system.

    ------------------------------
    Lee Graham
    Friendly Systems, Inc.
    ------------------------------

    Original Message


  • 4.  RE: Transaction Journal VI import

    Posted 08-17-2020 15:59
    I always set primary key columns first before anything else... SourceJournal + EntryNo.

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------



  • 5.  RE: Transaction Journal VI import

    Posted 08-17-2020 16:23
    Sometimes there is too much information supplied in the import.  Try deleting the last detail line - Bank code from the import.  You are already supplying it in the header record.

    ------------------------------
    Jeff Schwenk
    FORMER 90M Board Member
    Bottomline Software, Inc.
    Waynesboro VA
    540-221-4444
    ------------------------------

    Original Message


  • 6.  RE: Transaction Journal VI import

    Posted 08-17-2020 16:26
    Wait... you set up the source journal "Format" in the live company code, with the correct transaction type?

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


  • 7.  RE: Transaction Journal VI import

    Posted 08-17-2020 16:48
    It should be - the test company was created just a couple of days ago just to test the VI job.  I will confirm.

    ------------------------------
    Phil McIntosh
    President
    Friendly Systems, Inc.
    Asheville NC
    678.273.4010 ext 5
    ------------------------------

    Original Message


  • 8.  RE: Transaction Journal VI import

    Posted 08-17-2020 17:07
    @Kevin Moyes - Thanks!  You got us on the right track  it took putting all the fields in the exact order they were in on the left hand side.  Bizarre that it wasn't necessary in the test company with the exact same file...

    ------------------------------
    Phil McIntosh
    President
    Friendly Systems, Inc.
    Asheville NC
    678.273.4010 ext 5
    ------------------------------

    Original Message


  • 9.  RE: Transaction Journal VI import

    Posted 08-19-2020 12:44
    I had a similar message with a client.  We discovered that if the GL account being imported was invalid, it gave that message.  Apparently it was reported to Sage in the year 2015 but they couldn't duplicate (!) so was dropped.  I reported again in 2019 and it was fixed in Feb 2020.  My client is on v2017 and didn't want to sign the legal waiver to get the fix early, so I was never able to get a fix.  I assume it's been included in recent updates for other versions.

    ------------------------------
    Robert White
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


Related Content