How To Fix FARR_CONTRACT_UI007 - You are not authorized to display account determination settings

FARR_CONTRACT_UI007 - Overview

• Message type: E = Error

• Message class: FARR_CONTRACT_UI - Revenue Accounting - Contract UI

• Message number: 007

• Message text: You are not authorized to display account determination settings

What causes this issue?

You attempted to display the Account Determination configuration for
Revenue Accounting without the necessary display authorization.

System Response

The operation was terminated.

How to fix this error?

The system uses the F_RR_ACCTD authorization object to grant you access
to the Account Determination configuration. However, your user master
record does not contain the F_RR_ACCTD authorization object.

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message FARR_CONTRACT_UI007 - You are not authorized to display account determination settings ?

  The SAP error message FARR_CONTRACT_UI007 indicates that the user does not have the necessary authorization to display account determination settings in the SAP system. This typically occurs in the context of the SAP Contract Accounts Receivable and Payable (FI-CA) module.
  
  Cause:
  The error is caused by insufficient user authorizations. Specifically, the user role assigned to the individual does not include the necessary permissions to access the account determination settings. This can happen due to:
  
  Missing Authorization Objects: The user may not have the required authorization objects assigned to their user profile.
  Role Configuration: The roles assigned to the user may not be configured correctly to include access to the relevant transaction or settings.
  Profile Restrictions: The user profile may have restrictions that prevent access to certain areas of the system.
  
  
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to see which authorization check failed.