How To Fix FCC1705 - You are not authorized to process session &1 in the background

SAP Error Message - Details

• Message type: E = Error

• Message class: FCC1 - Messages in Financial Closing Cockpit

• Message number: 705

• Message text: You are not authorized to process session &1 in the background

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 FCC1705 - You are not authorized to process session &1 in the background ?

  The SAP error message FCC1705, which states "You are not authorized to process session &1 in the background," typically occurs when a user attempts to execute a background job or process a session that they do not have the necessary authorizations for. This can happen in various SAP modules, particularly in Financial Accounting (FI) or Controlling (CO) when dealing with background processing.
  Cause:
  
  Authorization Issues: The user does not have the required authorizations to execute the specific session in the background. This could be due to missing roles or authorizations in the user's profile.
  Session Locking: The session may be locked or restricted for background processing due to system settings or configurations.
  Incorrect User Role Assignment: The user may not be assigned to the correct roles that allow background processing for the specific transaction or session.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after the error occurs to check the authorization check failure. This will show you which specific authorizations are missing.
  Review the user's roles and authorizations in transaction PFCG to ensure they have the necessary permissions to execute the session in the background.
  
  
  
  Modify User Roles:
  
  If the user lacks the necessary authorizations, you may need to add the required roles or adjust the existing roles to include the necessary authorizations for background processing.
  
  
  
  Consult with Security Team:
  
  If you are not authorized to make changes to user roles, contact your SAP security team or administrator to request the necessary authorizations.
  
  
  
  Check Session Settings:
  
  Ensure that the session you are trying to process is configured to allow background processing. This may involve checking the session's settings in the relevant transaction or configuration.
  
  
  
  Testing:
  
  After making changes to authorizations or roles, test the process again to ensure that the error is resolved.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SU53: Display Authorization Check
  PFCG: Role Maintenance
  SM37: Monitor Background Jobs
  
  
  
  Documentation: Refer to SAP documentation or your organization's internal documentation for specific role and authorization requirements related to the session you are trying to process.
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on authorization issues.
  
  
  By following these steps, you should be able to identify and resolve the authorization issue causing the FCC1705 error message.