PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 04/04/2017 2:43 PM by  Greg Moeller
Lawson Installation and Database Document
 5 Replies
Sort:
You are not authorized to post a reply.
Author Messages
MrManny
DBA
Private
New Member
(7 points)
New Member
Posts:3


Send Message:

--
04/03/2017 3:53 PM

    If this is not the right forum to post this question, please direct me to where I can post it.

    I just inherited a Lawson system that is only being used for historical purpose. We only have one user using the system. We want to retire the system and would like to extract some relevant data first.

    I know nothing about Lawson and I am only looking at this from the database point of view. The database is Microsoft SQL 2008. The login screen of the application shows "Portal 9.0.0.6.515, Technology 9.0.0.6.634'

    On our system, there are 9 databases. It looks as if the GEN and LOGAN databases are used for authentication.

    Is there an installation manual that will tell me which databases are being used by the application and what is stored in the tables? How do I log in as an administrator into Lawson to see how the system is configured. I am looking for some general information that will help me better understand the database back end as it relates to the application.

    I can see some of the data we are looking for in EMPLOYEE and APPLICANT tables. 

    Any information will be highly appreciated.

     

    Thanks,

    MrManny.

     

    Woozy
    Private
    Private
    Veteran Member
    (3469 points)
    Veteran Member
    Posts:701


    Send Message:

    --
    04/03/2017 4:15 PM
    Hi MrManny,

    Unfortunately, application databases (meaning databases holding actual employee-related data) are named at the whim of the installer. For example, in our (v9.0.1) systems, we have our four application databases on our DEV server (LSFDEV, LSFTEST, LSFTRN, AND LSFPRIST), on our Sandbox server we have one application database (SAND) and on production we have one application database (PROD). GEN is an environment database (i.e. system users, roles, batch jobs, etc) and if I remember correctly, LOGAN is an environment database related to processflows and other stuff.

    However, if you will post a list of all the databases you see, I'm guessing there are folks on here who can make educated guesses about which databases are used for what.

    Good Luck!
    Kelly
    Kelly Meade
    J. R. Simplot Company
    Boise, ID
    MrManny
    DBA
    Private
    New Member
    (7 points)
    New Member
    Posts:3


    Send Message:

    --
    04/04/2017 9:51 AM

    Hi Kelly,

    Thanks for the information. I  know what the databases are for based on the naming convention. My main concern is trying to determine what information the tables contain and their relationship with each other. For example, if I am extracting data from the EMPLOYEE table, I want to make sure that I am extracting all relevant data from HRHISTORY table as well, making sure I am joining on the right column/key. I can do this manually by examining the data in each table and running traces to determine the relationship. It just takes a long time.

    I did a search to find a particular string on all the tables in one of the databases and it showed up in the following tables. I now need to figure out their relationship. Some of the table names are self explanatory.

     

    APPLICANT
    BENEFICRY
    BNCOMMENTS
    CICInput
    EMACHDEPST
    EMDEPEND
    EMPLOYEE
    FidelityHrHistory
    HRHISTORY
    PACOMMENTS
    PAEMPLOYEE
    PARTICIPNT
    PensionFlag
    PREMPGARN
    PWSELECT

    Thanks,

    MrManny

    Woozy
    Private
    Private
    Veteran Member
    (3469 points)
    Veteran Member
    Posts:701


    Send Message:

    --
    04/04/2017 10:01 AM
    Ahhh - that's a different question.

    None of the relationships are built in the database, as I'm sure you've noticed. It's all managed by the application. I'd suggest you check out the ERDs on LawsonGuru.

    https://www.lawsonguru.com/Tech/Dat...ERDs.aspx. then go to the Lawson Applications tab and click the Human Resources link.

    My guess is that "CICInput", "FidelityHRHIstory", and "PensionFlag" are custom tables that will not be in the ERDs.

    I hope this helps. I don't really have time to provide relationship details for all of these.
    Kelly
    Kelly Meade
    J. R. Simplot Company
    Boise, ID
    MrManny
    DBA
    Private
    New Member
    (7 points)
    New Member
    Posts:3


    Send Message:

    --
    04/04/2017 2:13 PM

    Thanks again for the information. I will check out the Entity Relationship Diagrams and see what I can figure out.

    Thanks,

    MrManny.

    Greg Moeller
    Private
    Private
    Veteran Member
    (3873 points)
    Veteran Member
    Posts:1377


    Send Message:

    --
    04/04/2017 2:43 PM
    Send me your email, and I'll share the files that I have....
    You are not authorized to post a reply.