How to use /LOGS4H/USER_MANAGER - UI-Logging User Manager

SAP Transaction Code - Details

• Transaction Code: /LOGS4H/USER_MANAGER

  Description: UI-Logging User Manager

  Release: S/4HANA and ECC 6

• • Program: /LOGS4H/USER_MANAGER

    Screen: 1000

    Authorization Object: /LOGS4H/UI

  • Development Package: /LOGS4H/COMMON

    Package Description: Common part of UI Logging solution

    Parent Package: /LOGS4H/SERVICE_LOGGING

  • Module/Component: GRC-UDS-LOG

    Description: SAP UI Data Protection Logging

Smart SAP Assistant

• SAP Tcode: /LOGS4H/USER_MANAGER - UI-Logging User Manager

  
  Overview:
  The SAP transaction code /LOGS4H/USER_MANAGER is a UI-Logging User Manager. It is used to manage user access to the UI-Logging system. This system allows users to log and monitor user interface (UI) activities in the SAP system. 
  
  Functionality:
  The /LOGS4H/USER_MANAGER transaction code allows users to manage user access to the UI-Logging system. This includes creating, editing, and deleting user accounts, assigning roles and permissions, and setting up logging rules. It also allows users to view logs of UI activities in the SAP system. 
  
  Step-by-step How to Use:
  1. Access the /LOGS4H/USER_MANAGER transaction code in the SAP system. 
  2. Create a new user account by entering the required information in the appropriate fields. 
  3. Assign roles and permissions to the new user account. 
  4. Set up logging rules for the new user account. 
  5. View logs of UI activities in the SAP system by selecting the appropriate log type from the dropdown menu. 
  6. Save any changes made to the user account or logging rules. 
  7. Exit the /LOGS4H/USER_MANAGER transaction code when finished. 
  
  Other Recommendations:
  It is recommended that users familiarize themselves with the UI-Logging system before using this transaction code, as it can be difficult to understand without prior knowledge of how it works. Additionally, users should ensure that all changes made to user accounts and logging rules are saved before exiting the transaction code, as any unsaved changes will be lost when exiting.