Sage 100

 View Only

  • 1.  Payroll Data Entry Import 2018 w/2.19.4 from ASCII file

    Posted 09-16-2019 20:21
    The source file is fixed length ASCII.
    Sample Record:

    0007 00000000760 20190908H REG 10000000000 00007150

    Division No is at 20,2 (ex. 60), Employee No is at 13,7 (ex. 0000007).

    Here are the pieces of the import that pertain to the EmployeeKey
    Temp002 is setup similar with appropriate Col/Pos and Length.

    Import Testing result:


    What am I missing here?

    BTW - If I rearrange the record so the Dept and EmployeeNo are like this: "60-0000007" it works fine.


    ------------------------------
    Greg Stiles
    S & W Microsystems
    Torrance CA
    310.787.1010
    ------------------------------


  • 2.  RE: Payroll Data Entry Import 2018 w/2.19.4 from ASCII file

    Posted 09-16-2019 22:27
      |   view attached
    Try this KB 86744.  It doesn't look you have step three.

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

    Attachment(s)

    pdf
    Importing Employee Key KB 86744.pdf   39 KB 1 version


  • 3.  RE: Payroll Data Entry Import 2018 w/2.19.4 from ASCII file

    Posted 09-16-2019 23:45
    Yep, that does look like the issue. Will test it tomorrow. Thanks @Jeff Schwenk​

    ------------------------------
    Greg Stiles
    S & W Microsystems
    Torrance CA
    310.787.1010
    ------------------------------

    Original Message


  • 4.  RE: Payroll Data Entry Import 2018 w/2.19.4 from ASCII file

    Posted 09-17-2019 10:20
    There are also several sample VI jobs in the PR folder which can be helpful to review formatting. Jeff's recommendation is what I think your answer is here ( just working on a similar VI job myself ).

    ------------------------------
    Wayne Schulz - Schulz Consulting - 860-516-8990
    ------------------------------



  • 5.  RE: Payroll Data Entry Import 2018 w/2.19.4 from ASCII file

    Posted 09-17-2019 10:53
    I find having a PR VI invaluable when migrating to the new PR.  The tax rule codes are difficult to determine (as @Doug Higgs ​has noted).  So dumping the last PR from perpetual history into Excel, then using that to import into v2019 PR is a quick and dirty way test whether you have mastered the set up.  Plus it is an easy way to give the client value as a leave behind if they are not importing their time currently.

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

    Original Message


Related Content