PA90.1 Health & Safety Incident

Sort:
You are not authorized to post a reply.
Author
Messages
Brad
Basic Member
Posts: 6
Basic Member
    We have been playing around PA90.1 and cannot find where changes made using the form are written to any sort of a history or audit table.  We did find the OSHA table fields in the data dictionary table with a topic of 'OS' and assigned field numbers, but no place where they would be stored.  These fields were also not an option on HR10.1 - Data Item Attributes with a topic of 'OS'.  Actually, 'OS' wasn't even an option and appears that the Topic field values on HR10.1 are hard coded in the screen COBOL code.

    Are we missing something or are we going to have to create a custom history table and track ourselves? 

    Thanks in advance!
    Greg Moeller
    Veteran Member
    Posts: 1498
    Veteran Member
      Not knowing anything about PA, or what your exact requirements are, so sorry if this seems off-handed.
      PA90.1

      PA90.1 - Health and Safety Incident

      Use Health and Safety Incident (PA90.1) to track government and non-government reportable information about injuries and illnesses. **More Information You define statuses, categories, and types that suit the specific tracking your organization requires. Information collected on this form can be used on a variety of reports such as the OSHA 300 and OSHA 300A reports or the Canada Workers Compensation Board Form 7.

      Updated Files

      OSHA
      PACOMMENTS
      PAFOLLOWUP
      PAINCICOST



      Referenced Files

      DEPTCODE
      EMPLOYEE
      HRSECLEV
      HRSUPER
      INSTCTRYCD
      JOBCODE
      OSHESTAB
      PACOMMENTS
      PAEMPLOYEE
      PCODES
      PCODESDTL
      PRSYSTEM



      INVOKED Programs

      IFCU
      IFAC
      ACAC
      ACTA
      API4
      IFLU
      IFOB
      IFUP
      IFSG
      SLSE
      SLSU
      Karen Ploof
      Veteran Member
      Posts: 118
      Veteran Member
        I am pretty sure that there is no history logging for PA90 changes. Greg's info seems to confirm that because the list of files updated does not include a history log file. That means there is a possibility that the files have a "last changed date" or something like that, but that's as good as it will get.

        I don't know the details, but when we wanted to log changes to ACH direct deposit and to fields in our custom files, our programmer created the functionality so it was written to the normal history log files rather than creating custom files to store the data. In the case of ACH, she said the "topic" code already existed and she created new topic codes for the custom files. It worked really well because we had all changes logged to the same file. I am sure the overhead associated with this customization was an issue, but I'm not sure whether it was more work than creating a custom file.

        Karen
        Greg Moeller
        Veteran Member
        Posts: 1498
        Veteran Member
          Another option: Wait for Infor10. If you sat in on those Tech and App webinars (now available on myLawson) -- It seems that there is a LOT of auditing now in place --esp for HR/Payroll in the new version.
          Greg Moeller
          Veteran Member
          Posts: 1498
          Veteran Member
            There is a date stamp and a userid column in the OSHA, PAFOLLOWUP and PAINCICOST tables - apparently we don't use this function here, as all 3 of these tables are empty.
            You are not authorized to post a reply.