How to use OIUGR_ASUE - Gen Roy 2.0 - Auto Suspend Exception

SAP Transaction Code - Details

• Transaction Code: OIUGR_ASUE

  Description: Gen Roy 2.0 - Auto Suspend Exception

  Release: S/4HANA only

• • Program:

    Screen: 0

    Authorization Object:

  • Development Package:

    Package Description:

    Parent Package:

  • Module/Component:

    Description:

Smart SAP Assistant

• SAP Tcode: OIUGR_ASUE - Gen Roy 2.0 - Auto Suspend Exception

  
  Overview:
  OIUGR_ASUE is a SAP transaction code used to manage the exceptions for the Gen Roy 2.0 Auto Suspend process. This process is used to automatically suspend users who have not logged into the system for a certain period of time. 
  
  Functionality: 
  The OIUGR_ASUE transaction code allows users to manage exceptions to the Gen Roy 2.0 Auto Suspend process. This includes creating, editing, and deleting exceptions for specific users or groups of users. It also allows users to view a list of all exceptions and their details. 
  
  Step-by-step How to Use: 
  1. Log into the SAP system and enter the OIUGR_ASUE transaction code in the command field. 
  2. Select the “Create Exception” option from the menu. 
  3. Enter the user or group of users that you want to create an exception for in the “User/Group” field. 
  4. Enter a description of the exception in the “Description” field. 
  5. Select a start date and end date for the exception in the “Start Date” and “End Date” fields respectively. 
  6. Click “Save” to save your changes and create the exception. 
  7. To view, edit, or delete an existing exception, select the “Display Exceptions” option from the menu and select an exception from the list that appears. 
  8. To edit an existing exception, click on it and make your changes in the fields provided. 
  9. To delete an existing exception, click on it and then click on “Delete” at the bottom of the screen. 
  
  Other Recommendations: 
  It is recommended that users only create exceptions when absolutely necessary as they can have a negative impact on system performance if used excessively or incorrectly. Additionally, it is important to ensure that all exceptions are deleted when no longer needed as they can cause confusion if left active after their intended use has expired.