How To Fix HR3PRNA221 - You are not authorized to display accounting documents; see log

HR3PRNA221 - Overview

• Message type: E = Error

• Message class: HR3PRNA - Message class for third party remittance

• Message number: 221

• Message text: You are not authorized to display accounting documents; see log

What causes this issue?

You cannot display the relevant accounting documents because you have no
authorization to access documents returned by the <NP>
FI_DOC_TPR_ITEMS_FIND</> function module. This function module is called
during the acknowledgement of third-party remittance (3PR) postings
using the <NP>RP_REMITTANCE_ACKNOWLEDGEMENT</> function module.

System Response

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

How to fix this error?

Contact your system administrator.

Procedure for System Administrators

You can activate or deactivate the authorization check for the
<NP>FI_DOC_TPR_ITEMS_FIND</> function module by activating or
deactivating the <NP>FI_DOC_READ</> scenario in the <LS>Switchable
Authorization Check Framework</> (transaction <NP>SACF</>).

Error message extract from SAP system. Copyright SAP SE.

HR3PRNA221 - Details

• The SAP error message HR3PRNA221 indicates that a user does not have the necessary authorization to display accounting documents. This error typically arises in the context of HR (Human Resources) and payroll processing, where access to certain financial data is restricted based on user roles and permissions.
  
  Cause:
  
  Authorization Issues: The user lacks the required authorization object to view accounting documents. This could be due to missing roles or permissions in their user profile.
  Role Configuration: The roles assigned to the user may not include the necessary authorizations for accessing accounting documents.
  System Configuration: There may be specific configurations in the SAP system that restrict access to certain documents based on user roles.
  
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to check which authorization objects are missing.
  Review the authorization log to identify the specific authorization object that is causing the issue.
  
  
  
  Modify User Roles:
  
  If you have the necessary permissions, you can modify