How To Fix CRMN_REPORT120 - PARTNER_NO_SECOND/PARTNER_PFT_SECOND not usable due to authorization

CRMN_REPORT120 - Overview

• Message type: E = Error

• Message class: CRMN_REPORT - Reporting: Messages

• Message number: 120

• Message text: PARTNER_NO_SECOND/PARTNER_PFT_SECOND not usable due to authorization

What causes this issue?

Program error: These search criteria cannot be used by the application
in this case.

System Response

These search criteria are reserved for the authorization check in the
Reporting Framework. They can only be used by applications if this will
not lead to collision after FM CRM_REPORT_RF_CHECK_AUTHORITY (the
authorization check does not require the search criteria in this case).

How to fix this error?

If FM CRM_REPORT_RF_CHECK_AUTHORITY does not permit an external
application, the Reporting Framework should be called up twice.
- First call up with first partner
- Second call up with second partner and the GUID list from the first
step
Whether the authorization itself requires the search criteria depends on
the problem and the search criteria. Therefore, it is advisable to use
the if-then-else statement:
CALL CRM_REPORT_RF_CHECK_AUTHORITY.

<call RFW only once with both partners>

<call RFW twice as described above>

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

CRMN_REPORT120 - Details

• The SAP error message "CRMN_REPORT120 PARTNER_NO_SECOND/PARTNER_PFT_SECOND not usable due to authorization" typically indicates that a user is attempting to access or perform an action related to a partner function or partner number for which they do not have the necessary authorizations. This error is common in SAP Customer Relationship Management (CRM) systems when dealing with partner data.
  
  Cause:
  
  Authorization Issues: The user does not have the required authorization to access or modify the specified partner number or partner function.
  Role Configuration: The user's role may not include the necessary permissions for the specific partner functions or partner numbers.
  Data Restrictions: There may be restrictions in place that limit access to certain partner data based on organizational rules or data privacy regulations.
  
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to check the authorization check that failed. This will provide insight into which specific authorization object is missing.
  Review the user's roles and authorizations