How To Fix NEW_FEBA117 - You are not authorized to set the selected posting rule

SAP Error Message - Details

• Message type: E = Error

• Message class: NEW_FEBA - Messages for the new bank statement postprocessing

• Message number: 117

• Message text: You are not authorized to set the selected posting rule

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 NEW_FEBA117 - You are not authorized to set the selected posting rule ?

  The SAP error message NEW_FEBA117 indicates that a user is not authorized to set the selected posting rule in the Financial Accounting (FI) module, specifically in the context of bank accounting or payment processing. This error typically arises when a user attempts to perform an action that requires specific authorizations that they do not possess.
  Cause:
  
  Authorization Issues: The user lacks the necessary authorization object to set or change the posting rule. This could be due to missing roles or authorizations in their user profile.
  Configuration Settings: The posting rules may be configured in such a way that only certain users or roles can modify them.
  Transaction Restrictions: The transaction being executed may have restrictions based on user roles or organizational units.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to check which authorization check failed. This will provide insight into what specific authorization is missing.
  Review the user’s roles and authorizations in transaction code SU01 or PFCG to ensure they have the necessary permissions to set the posting rule.
  
  
  
  Modify User Roles:
  
  If the user lacks the required authorization, a security administrator or SAP Basis team member should update the user’s roles to include the necessary authorizations related to the posting rules.
  Ensure that the relevant authorization objects (e.g., F_BKPF_BSA, F_BKPF_BST) are included in the user’s roles.
  
  
  
  Consult with SAP Security Team:
  
  If you are not able to resolve the issue, consult with your SAP security team to review the authorization settings and make necessary adjustments.
  
  
  
  Review Configuration:
  
  Check the configuration of the posting rules in the system to ensure that they are set up correctly and that the intended users have the appropriate access.
  
  
  
  Documentation and Training:
  
  Ensure that users are trained on the correct procedures for setting posting rules and understand the authorization requirements.
  
  
  
  Related Information:
  
  Authorization Objects: Familiarize yourself with the relevant authorization objects that control access to posting rules in SAP FI.
  Transaction Codes: Common transaction codes related to bank accounting and posting rules include:
  
  FBZP: Payment Program Configuration
  FBL1N: Vendor Line Item Display
  FBL3N: G/L Account Line Item Display
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues or provide additional guidance related to this error message.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.