How to use /LTB/TR_WHUSED_MAINT - Maintenance of trule where used list

SAP Transaction Code - Details

• Transaction Code: /LTB/TR_WHUSED_MAINT

  Description: Maintenance of trule where used list

  Release: S/4HANA only

• • Program: /LTB/TR_MODEL_WHUSED_MAINTAIN

    Screen: 1000

    Authorization Object:

  • Development Package: /LTB/TR_MODEL

    Package Description: SAP LT Basis: Transformation Rule (Model)

    Parent Package: /LTB/TR

  • Module/Component: CA-LT

    Description: Landscape Transformation

Smart SAP Assistant

• SAP Tcode: /LTB/TR_WHUSED_MAINT - Maintenance of trule where used list

  
  Overview:
  The SAP transaction code /LTB/TR_WHUSED_MAINT is used to maintain the trule where used list. This list contains all the rules that are used in the system and can be used to identify which rules are being used and which are not. 
  
  Functionality: 
  This transaction code allows users to view, create, edit, and delete rules from the trule where used list. It also allows users to view the details of each rule, such as its name, description, and associated objects. Additionally, users can search for specific rules by name or description. 
  
  Step-by-step How to Use: 
  1. Enter the transaction code /LTB/TR_WHUSED_MAINT into the command field. 
  2. The trule where used list will be displayed. 
  3. To view a rule’s details, select it from the list and click on “Display”. 
  4. To create a new rule, click on “Create” and enter the necessary information. 
  5. To edit an existing rule, select it from the list and click on “Change”. 
  6. To delete a rule, select it from the list and click on “Delete”. 
  7. To search for a specific rule, enter its name or description into the search field and click on “Search”. 
  8. When finished, click on “Save” to save any changes made or “Cancel” to discard them. 
  
  Other Recommendations: 
  It is recommended that users familiarize themselves with the trule where used list before using this transaction code as it can be difficult to navigate without prior knowledge of how it works. Additionally, users should always save their changes before exiting the transaction code to ensure that any changes made are not lost.