Transaction review

Transaction Generation
The LYNQ Platform Windows Service on the Web Server is responsible for consolidating your activity into actual transactions.  The workbench will still operate with this service not running but you will not see new transactions in the Transaction Review screen until the service is started. 

Record Security
It’s possible to configure LYNQ so supervisors and line managers can only see their own team member’s transaction records.  Refer to the Advanced User Guide for further information.

All activities performed within the workbench are converted into summary transactions so they can be reported on easily in LYNQ and posted to Enterprise Resource Planning.  Depending on your configuration, transactions may appear immediately after performing the activity or at different stages in your day.  (i.e. when you go to break, lunch or end day).   

The table below provides an overview of which different transaction types are created based on the type of activity performed. 
 

By default, indirect transactions such as break, lunch etc, machine time transactions and production issue transactions are excluded from posting to Enterprise Resource Planning. Transaction rules determine the default status of transactions.  Depending on your configuration, you may have different transaction rules configured to change the default approval status. 

To open Transaction Review:

1. Select Transaction View from Execution Management