How To Fix FQM109 - Not authorized to delete queue entry for source appl. &1, company code &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FQM - Financial Quantity Management Message Class

• Message number: 109

• Message text: Not authorized to delete queue entry for source appl. &1, company code &2

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 FQM109 - Not authorized to delete queue entry for source appl. &1, company code &2 ?

  The SAP error message FQM109 indicates that a user is not authorized to delete a queue entry for a specific source application and company code. This error typically arises in the context of financial transactions or processes that involve queue management, such as payment processing or document handling.
  Cause:
  The primary cause of this error is a lack of appropriate authorization in the user's role or profile. The user attempting to delete the queue entry does not have the necessary permissions assigned to their user ID for the specified source application and company code.
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after the error occurs to check the authorization check that failed. This will provide insight into which specific authorization object is missing.
  
  
  
  Review Role Assignments:
  
  Go to transaction code PFCG to review the roles assigned to the user. Ensure that the roles include the necessary authorizations for the source application and company code in question.
  
  
  
  Modify Authorizations:
  
  If the required authorizations are missing, you may need to modify the existing roles or create a new role that includes the necessary authorizations. This may involve adding specific authorization objects related to queue management and deletion rights.
  
  
  
  Consult with Security Team:
  
  If you do not have the necessary permissions to change roles or authorizations, consult with your SAP security team or administrator. They can assist in reviewing and updating the user’s authorizations.
  
  
  
  Testing:
  
  After making changes to the user’s authorizations, have the user log out and log back in to ensure that the new authorizations take effect. Then, attempt to delete the queue entry again.
  
  
  
  Related Information:
  
  Authorization Objects: The specific authorization objects that may be relevant include those related to financial transactions, queue management, and document processing. Common objects to check include F_BKPF_BUK (Authorization for Company Code) and F_BKPF_AKT (Authorization for Activity).
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  SMQ1/SMQ2: For monitoring and managing queues.
  SLG1: For viewing application logs, which may provide additional context for the error.
  
  
  Documentation: Refer to SAP documentation or your organization’s internal guidelines for managing user roles and authorizations.
  
  By following these steps, you should be able to identify the cause of the FQM109 error and implement a solution to grant the necessary permissions to the user.