Date Stamp in PERSACTION table

 5 Replies
 0 Subscribed to this topic
 22 Subscribed to this forum
Sort:
Author
Messages
thummel1
Veteran Member
Posts: 121
Veteran Member
    Hi,
    I'm wondering what would be the equaivalent to the Date Stampof PA Actions in the PERSACTION table? There are several date fields in there but none of them seem to reference the date that the transaction was entered. Logically, it seems that there would be one data field that contained the same date (since we run a PA100 on a nightly basis), but all the date field have a variety of dates or no date.

    Does this data field exist?
    Mary Porter
    Veteran Member
    Posts: 337
    Veteran Member
      look at PERSACTHST.DATE_STAMP and PERSACTHST.CREATE_DATE and see if either of those dates line up with PA100
      Dave Curtis
      Veteran Member
      Posts: 136
      Veteran Member
        PERSACTION has no date stamp. (unless I have missed it) but, as Mary said, the PERSACTHST has the dates it was entered
        Shane Jones
        Veteran Member
        Posts: 460
        Veteran Member
          If you need a date while it is still in persaction you could connect a process to it and there would be records on the process being triggered. Many options on the tracking through IPA...
          Shane Jones
          Tools: HR, Payroll, Benefits, PFI, Smart Office, BSI, Portal and Self-Service
          Systems: Lawson, Open Hire, Kronos, Crystal Reporting, SumTotal Learning
          ** Teach others to fish...
          Matt
          Basic Member
          Posts: 13
          Basic Member
            The DATE_STAMP in PERSACTHST is the date that it became history (processed by a PA100), not the date that the pa52 was created.
            Matt
            Basic Member
            Posts: 13
            Basic Member
              Version 10 has the following fields added to the PERSACTION table:

              [CREATE_USER_ID] [char](10) NOT NULL,
              [CREATE_TIME] [decimal](6, 0) NOT NULL,
              [CREATE_DATE] [datetime] NOT NULL,
              [TIME_STAMP] [decimal](6, 0) NOT NULL,
              [DATE_STAMP] [datetime] NOT NULL,

              So the problem will be solved when you upgrade...