PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 09/05/2013 12:41 PM by  Terry Wier
LTM- Employee employeement cycle maintence in the system
 2 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Greshan
Private
New Member
(2 points)
New Member
Posts:2


Send Message:

--
09/02/2013 1:25 AM
    Hi,

    I want to know weather it is possible to maintain an employees employment cycle within the organization in LTM? the requirement is the system must maintain an employee Transfer details, past supervisor details, past position details with the organization, promotion details. if the LTM system can maintain such details where is it saved? how can i view it?

    Thank you
    Woozy
    Private
    Private
    Veteran Member
    (3490 points)
    Veteran Member
    Posts:708


    Send Message:

    --
    09/03/2013 12:53 PM
    Hi Greshan - If I understand correctly, you're really asking about if and how LTM stores employee history?

    The answer is that Landmark/TM does store this information, but it isn't stored in a "history" table the way most systems do but rather as an "audit log" by business class/table.

    The historical data is stored as xml in CLOB fields on the database, with each change being marked with an effective date and showing the values that changed on that particular effective date so the history "builds" from oldest to newest. There isn't any "point-in-time" history table. Each business class (table) stores it's own history, so core Employee history (Name, Status, Veteran Code, service dates, etc) is stored in the Employee.AuditLog field. Work Assignment information (job, position, location, supervisor, etc) are stored in the WorkAssignment.AuditLog field. Phone/Email information is stored in EmployeeContact.AuditLog (by record). Address history is stored in EmployeeAddress.AuditLog.

    To see this data in the Rich Client, you open the appropriate business class, then right-click on a record and select "View Audit Log" (if you have security rights to see this).

    Reporting is a whole separate issue. It is very difficult (actually almost impossible) to report off this history information. We actually had to have one of our DBAs extract the AuditLog information, parse it out, and build a true set of "HR History" tables for us to query against. It is extremely painful.

    I hope this is helpful. Sorry there isn't a better answer.

    Kelly
    Kelly Meade
    J. R. Simplot Company
    Boise, ID
    Terry Wier
    Private
    Private
    Basic Member
    (39 points)
    Basic Member
    Posts:13


    Send Message:

    --
    09/05/2013 12:41 PM
    Hello, this is Terry Wier from Dashboard Gear.

    Dashboard Gear has incorporated all LTM data into our off-the-shelf Lawson HCM reporting data mart. We initially did this for the one of the larger states using Lawson HCM. If you are curious how easy reporting on historical information can be to include LTM data please click on the link below.

    HR Recorded Demo 

    http://www.screencast.com/t/8sV96iXUVUPa 

    Terry Wier
    Dashboard Gear
    763-208-9937

    You are not authorized to post a reply.