Suspending an Employee's Access

The HRM application allows the ability to automatically suspend an employee's access to all Advantage applications based on their Personnel Action Code. To do this, you can establish a Personnel Action with the User Access Option value set to Suspend.  When this PACT code is used on an Employee Status Maintenance (ESMT) transaction, an HRDOC is automatically generated and submitted with the Locked Out field checked. The employee’s access to all Advantage application(s) is then locked. When the employee logs out of all of their current sessions and logs back in, they receive the following error message: Your User ID is locked. Please contact your security administrator.

Note: If the user’s access is changed, and the user is currently logged into an Advantage session, their access changes will not occur until the user has logged out of all Advantage application sessions, and logs back into the Advantage application(s).

  1. Create an Employee Status Maintenance (ESMT) transaction.

  2. Complete each of the required sections on the Employee Status Maintenance transaction. Note:  * ” denotes a required field.

  3. In the Personnel Action code, enter a code from Personnel Action that has the User Access Option set to Suspend.

  4. Validate and Submit the Employee Status Maintenance transaction. An HRDOC is automatically generated, with the Locked Out check box selected, and is submitted to the Final phase.

  • If Workflow is implemented, the HRDOC is placed in the Submitted Status /Pending Phase until the transaction has been approved and submitted to the Final Phase /Submitted Status.

  • If the Employee Status Maintenance transaction is for a future date, the auto generated HRDOC is placed in the Rejected Status/Draft Phase until the Trigger Date has been reached. When the trigger date has been reached, a System Maintenance Utility (SMU) job is kicked off; (for example, nightly or some other user defined time) and the transaction is submitted to the Final Phase, when the date constraint would no longer prevent the submission.