PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 03/01/2020 2:06 PM by  LauraPat
New Payroll GL interface to Lawson Financials
 2 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Bonisick
Program Exec
Private
New Member
(1 points)
New Member
Posts:1


Send Message:

--
02/19/2020 5:41 PM
    Hi all.

    Could use some guidance and reference points on best practices and lessons learned re' integrating a payroll solution to Lawson financials.

    Anyone have advice or sample file specs, etc. they would share?

    Thanks,

    Bill
    Tags: Payroll, Interface, GL
    Ragu Raghavan
    Private
    Private
    Veteran Member
    (1065 points)
    Veteran Member
    Posts:371


    Send Message:

    --
    02/19/2020 9:15 PM
    I have done this many years back. The table GLTRANSREL is the staging/interface table. you need to have this table populated with the transactions from the external payroll app (using importdb, excel add-ins or some mechanism)
    It is probably better to have it summarized, so the employee's pay rate etc. are not visible on a drill-around.
    Once the data is in GLTRANSREL, edit via GL65, and then run GL165 to import into Lawson.
    After that, it is just standard Lawson processing: GL190 etc.

    if the volume of transactions is not too heavy, you could potentially do AGS calls to GL40 and create the JEs.
    LauraPat
    Sr. Application Engineer
    Private
    Advanced Member
    (82 points)
    Advanced Member
    Posts:40


    Send Message:

    --
    03/01/2020 2:06 PM
    We recently installed a WorkDay system for our HR and Payroll. I had to write six individual interfaces for Finance data that goes into GLTRANSREL as well as GMDISTREL.

    My interfaces all use process automation. They are all triggered via the presence of files, out of Workday, using File Channels/Receivers in Rich Client. The flows start by moving the files from our network location to the Lawson work file location on our Linux server. The flows then load the data to GLTRANSEL/GMDISTREL (via execution of a Unix script and captures record counts as well as errors), strips out the run group(s) and updates the appropriate GL165/GM500 job(s) with the run group(s) being processed (so only that specific run group is updated) and finally submits the jobs. An email is generated to the appropriate users which contains the run group being processed. The files are backed up to a backup location with a date/time stamp added to the file name(s) And the files are finally deleted from the original location, as well as the Landmark location, so that the process doesn't get triggered again because of the same file(s). I wrote requirements and support documentation all of the interfaces. We are on V10 on-premise. Feel free to email me if you'd like to discuss further. I'd be happy to share my documentation with you if u think it could help you. Have a good day!

    laura.jarvis@baystatehealth.org
    You are not authorized to post a reply.