How to use CRM_IC_FW_PROF - Define CMS Role Profiles

SAP Transaction Code - Details

• Transaction Code: CRM_IC_FW_PROF

  Description: Define CMS Role Profiles

  Release: S/4HANA only

• • Program:

    Screen: 0

    Authorization Object:

  • Development Package: CRM_IC_CUSTOMIZING3

    Package Description: IC WebClient Customizing

    Parent Package: CRM_IC_FRAMEW

  • Module/Component: CRM-IC

    Description: Interaction Center WebClient

Smart SAP Assistant

• SAP Tcode: CRM_IC_FW_PROF - Define CMS Role Profiles

  
  Overview: 
  CRM_IC_FW_PROF is a SAP transaction code used to define CMS role profiles in the SAP CRM system. It is used to create and maintain roles and profiles for users in the system. 
  
  Functionality: 
  CRM_IC_FW_PROF allows users to create and maintain roles and profiles for users in the system. It also allows users to assign roles and profiles to users, as well as assign authorization objects to roles. This transaction code is used to define the access rights of users in the system. 
  
  Step-by-step How to Use: 
  1. Enter the transaction code CRM_IC_FW_PROF into the command field. 
  2. Select “Create” from the menu bar. 
  3. Enter a name for the role profile and select “Save”. 
  4. Select “Assign Authorization Objects” from the menu bar. 
  5. Select the authorization objects that you want to assign to the role profile and select “Save”. 
  6. Select “Assign Roles” from the menu bar. 
  7. Select the roles that you want to assign to the role profile and select “Save”. 
  8. Select “Assign Profiles” from the menu bar. 
  9. Select the profiles that you want to assign to the role profile and select “Save”. 
  10. Select “Activate” from the menu bar to activate the role profile. 
  
  Other Recommendations: 
  It is recommended that users test their role profiles before activating them in order to ensure that they are working properly and that all of the authorization objects are assigned correctly. Additionally, it is recommended that users regularly review their role profiles in order to ensure that they are up-to-date with any changes in authorization objects or roles that may have occurred since they were last reviewed.