How to use FW60 - Customizing sec.class relation.types

SAP Transaction Code - Details

• Transaction Code: FW60

  Description: Customizing sec.class relation.types

  Release: S/4HANA and ECC 6

• • Program:

    Screen: 0

    Authorization Object:

  • Development Package: FVVW

    Package Description: Treasury Management: Securities

    Parent Package: FS_TRM

  • Module/Component: FIN-FSCM-TRM-TM

    Description: Transaction Manager

Smart SAP Assistant

• SAP Tcode: FW60 - Customizing sec.class relation.types

  
  Overview:
  The SAP transaction code FW60 is used to customize the security class relation types in the SAP system. This code allows users to define the relationship between security classes and authorization objects. It also enables users to assign authorization objects to security classes. 
  
  Functionality: 
  The FW60 transaction code is used to customize the security class relation types in the SAP system. This code allows users to define the relationship between security classes and authorization objects. It also enables users to assign authorization objects to security classes. This helps ensure that only authorized users can access certain areas of the system. 
  
  Step-by-step How to Use: 
  1. Enter transaction code FW60 in the command field of the SAP system. 
  2. Select the “Customizing sec.class relation types” option from the menu that appears. 
  3. Select the “Create” option from the menu that appears. 
  4. Enter a name for the new security class relation type and select “Save”. 
  5. Select the “Assign Authorization Objects” option from the menu that appears. 
  6. Select an authorization object from the list and select “Save”. 
  7. Repeat steps 5 and 6 for each authorization object you want to assign to this security class relation type. 
  8. Select “Activate” from the menu that appears to activate your changes. 
  
  Other Recommendations: 
  It is important to note that when using this transaction code, it is important to ensure that only authorized users have access to certain areas of the system by assigning authorization objects to security classes accordingly. Additionally, it is recommended that users test their changes before activating them in order to ensure they are working as expected.