How To Fix /CFG/FTI_BUSN_ERROR060 - App not in scope

SAP Error Message - Details

• Message type: E = Error

• Message class: /CFG/FTI_BUSN_ERROR -

• Message number: 060

• Message text: App not in scope

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 /CFG/FTI_BUSN_ERROR060 - App not in scope ?

  The SAP error message /CFG/FTI_BUSN_ERROR060 with the description "App not in scope" typically indicates that a specific application or functionality is not included in the current configuration or scope of the system. This error often arises in the context of SAP Fiori applications or when using the SAP Fiori Launchpad.
  Cause:
  
  Application Not Activated: The application you are trying to access may not be activated in the system.
  Authorization Issues: The user may not have the necessary authorizations to access the application.
  Scope Definition: The application may not be included in the defined scope of the Fiori Launchpad or the specific business role assigned to the user.
  Configuration Issues: There may be configuration issues in the backend system that prevent the application from being recognized as part of the scope.
  
  Solution:
  
  
  Check Application Activation:
  
  Go to the SAP Fiori Launchpad and check if the application is activated. You can do this by navigating to the Fiori Apps Library or using transaction codes like SE80 or SE11 to check the application status.
  
  
  
  Review Authorizations:
  
  Ensure that the user has the necessary roles and authorizations to access the application. You can check this in transaction PFCG (Profile Generator) to see if the user has the required role assigned.
  
  
  
  Scope Definition:
  
  Verify the scope definition in the Fiori Launchpad. Ensure that the application is included in the business catalog assigned to the user’s role. You can check this in the Fiori Launchpad Designer.
  
  
  
  Configuration Check:
  
  Review the backend configuration for the application. Ensure that all necessary settings are correctly configured in the SAP system. This may involve checking the OData services, system aliases, and other related configurations.
  
  
  
  Transport Requests:
  
  If the application was recently transported from a development environment, ensure that all necessary transport requests have been successfully imported into the target environment.
  
  
  
  Consult Documentation:
  
  Refer to the official SAP documentation for the specific application to ensure that all prerequisites and configurations are met.
  
  
  
  Related Information:
  
  SAP Fiori Apps Library: This is a useful resource to check the status of Fiori applications, their prerequisites, and configuration details.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address specific issues related to this error message.
  Community Forums: Engage with the SAP Community or forums where other users may have encountered similar issues and can provide insights or solutions.
  
  If the issue persists after following these steps, it may be beneficial to reach out to your SAP Basis or technical team for further investigation.