AP: Number of Check Runs

Sort:
You are not authorized to post a reply.
Author
Messages
BrianH
Basic Member
Posts: 8
Basic Member
    Is there a way to find out how many check runs, or in Lawson terms how many times AP150, AP155, or AP170 has been run for a given time frame? I can build a report if needed, but I don't know if there is a table that houses that info.
    jrbledsoe001
    Veteran Member
    Posts: 91
    Veteran Member
      Hi,

      The GEN database has a table called queuedjob which stores information on every job which is lauched through job scheduler. Use LID to this command to see who ran AP150:
      rngdbdump -c gen queuedjob -v token="AP150" |lashow. This command will save the output to a file in your home directory:
      rngdbdump -c gen queuejob -v token="AP170">ap170.csv

      I have seen some incredibly talented people query this information using a browser based dme but I can't get the syntax right on my system. Maybe a Guru out there is reading this and will chime in.

      Syntax is something like:

      http://[insert server name]/cgi-lawson/dme.exe?[product line]=gen&file=queuedjob&field=username;token&select=token=AP170

      I don't have process flow integrator (PFI) but maybe Lawson allows us to query the GEN tables with PFI.

      joanna.bledsoe@jhsmh.org

      knystrom
      New Member
      Posts: 2
      New Member
        If you want to use excel and Lawson Query Wizard you can choose APPAYMENT, then choose the Check Date as the selected field. put in your date range on criteria. Once you have the list you can filter it into a unigue list to get your count. We also do payments out of CB so we run a separate query for this to combine the total check runs.
        Sean
        New Member
        Posts: 1
        New Member
          If you are looking for the Number of Payment Runs query CBCHECK and count on SERIAL-NUM for the CHECK-DATE range you want. There is a unique sequential serial number for each payment run performed in AP.
          You are not authorized to post a reply.