finding related workflow....

You can use the WorkUnits Pending Action view to narrow your search down, and from there you should be able to filter down to date or some other key WorkUnit criteria field to limit the number of records you have to search through.

Have you tried building a key string (Company+Process Level +Employee+Action+Action Nbr+Effective Date), then as the work unit is being built in the trigger code, write this key string value as a work unit variable. You can use the key string in a number of different tools (sql, COBOL, Design Studio, etc) and query the Work Unit Variable table or Object, depending if you're using PFI or IPA, later on to find the work unit.

Tim, that's a good solution, however it only works if you have control over the workunit trigger code. In the case of Lawson-delivered ones, such as for PA52 and Requisitions, would require doing something similar, but rather than putting it in the trigger code, it could be done as the first step in the flow itself.

Shane, David's solution is the only way I know. You can do a scan of the workunits table, and in the "key string" you will find the variables strung together that will match to a personnel action. In other words, take the PA fields (company, 'E', eff date, action code, employee, etc. etc.) -- you will need to look at the workunits table to get the exact format -- and work backwards.