Before using transaction PFCG (Role Maintenance) in SAP systems, two prerequisites must be met. First, tables USOBT (Authorization Object Defaults) and USOBX (Check Indicators) must be filled with SAP-delivered authorization default values, which provide the standard authorization objects and check indicators for transactions. These tables, maintained via transaction SU25, ensure that PFCG can propose appropriate authorizations when building roles. Second, the system profile parameter auth/no_check_in_some_cases must be set to Y, enabling the system to bypass authorization checks for certain transactions, which is necessary for PFCG to function correctly during role creation and maintenance. Setting this parameter to N would enforce stricter checks, potentially restricting PFCG functionality. Tables USOBT_C and USOBX_C are customer-specific and not required for initial PFCG setup, as they store customized values rather than SAP defaults. These steps ensure that PFCG operates effectively, supporting secure and efficient role management in SAP environments.