How To Fix SEPA028 - You are not authorized to display mandates for company code '&1'

SAP Error Message - Details

• Message type: E = Error

• Message class: SEPA - SEPA Mandate: Messages

• Message number: 028

• Message text: You are not authorized to display mandates for company code '&1'

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message SEPA028 - You are not authorized to display mandates for company code '&1' ?

  The SAP error message SEPA028 indicates that a user is not authorized to display mandates for a specific company code. This error typically arises in the context of handling SEPA (Single Euro Payments Area) mandates, which are used for direct debit transactions in the Eurozone.
  Cause:
  The error is caused by insufficient authorization for the user trying to access the mandates associated with the specified company code. This can happen due to:
  
  Missing Authorization Roles: The user does not have the necessary roles assigned that allow access to the mandate data for the specified company code.
  Authorization Object Restrictions: The authorization objects related to SEPA mandates (such as F_BKPF_BES for accounting documents) may not be configured correctly for the user.
  Company Code Configuration: The company code may not be properly set up in the user's profile or the user may not be assigned to that company code.
  
  Solution:
  To resolve the SEPA028 error, you can take the following steps:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after the error occurs to see which authorization check failed. This will provide insight into what specific authorization is missing.
  Review the user's roles and authorizations in transaction SU01 or PFCG.
  
  
  
  Assign Necessary Roles:
  
  If the user lacks the necessary roles, work with your SAP security team to assign the appropriate roles that include access to SEPA mandates for the relevant company code.
  
  
  
  Review Authorization Objects:
  
  Ensure that the relevant authorization objects are correctly configured. For SEPA mandates, check objects like F_BKPF_BES and ensure that the user has the necessary authorizations for the company code in question.
  
  
  
  Company Code Assignment:
  
  Verify that the user is assigned to the correct company code in their user profile. This can be checked in the user master record.
  
  
  
  Testing:
  
  After making changes, have the user log out and log back in, then attempt to access the mandates again to see if the issue is resolved.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  SU01 - User Maintenance
  PFCG - Role Maintenance
  SU53 - Display Authorization Check
  
  
  Authorization Objects: 
  
  F_BKPF_BES - Authorization for Accounting Document
  F_SEPA_MANDATE - Specific to SEPA mandates (if applicable)
  
  
  Documentation: Refer to SAP Help documentation for detailed information on SEPA mandates and authorization management.
  
  If the issue persists after following these steps, it may be necessary to consult with your SAP Basis or Security team for further investigation.