How To Fix SCPR799 - No activation logs found for BC Set &1

SAP Error Message - Details

• Message type: E = Error

• Message class: SCPR - BC Sets

• Message number: 799

• Message text: No activation logs found for BC Set &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 SCPR799 - No activation logs found for BC Set &1 ?

  The SAP error message SCPR799 "No activation logs found for BC Set &1" typically occurs when you are trying to activate a Business Configuration (BC) Set in SAP, but the system cannot find any activation logs associated with the specified BC Set. This can happen for several reasons, and here are some potential causes, solutions, and related information:
  Causes:
  
  BC Set Not Activated: The BC Set you are trying to activate may not have been activated previously, or the activation process may have failed.
  Missing Logs: The activation logs for the BC Set may have been deleted or not generated due to an error during the activation process.
  Authorization Issues: The user may not have the necessary authorizations to view the activation logs.
  System Issues: There may be underlying system issues or inconsistencies in the configuration that prevent the logs from being found.
  
  Solutions:
  
  
  Check Activation Status:
  
  Verify if the BC Set has been activated by checking the activation status in the relevant transaction (e.g., transaction SCPR20).
  If it has not been activated, try activating it again.
  
  
  
  Review Activation Process:
  
  If the activation process failed, check for any error messages or logs that might indicate what went wrong during the activation.
  You can use transaction SLG1 (Application Log) to check for any relevant logs that might provide more context.
  
  
  
  Re-activate the BC Set:
  
  If the BC Set was not activated successfully, attempt to activate it again. Ensure that you follow the correct steps and that there are no interruptions during the process.
  
  
  
  Check Authorizations:
  
  Ensure that the user attempting to view the activation logs has the necessary authorizations. You may need to consult with your SAP security team to verify this.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that might address this specific error message. There may be known issues or patches available.
  
  
  
  System Consistency Check:
  
  If the problem persists, consider running a consistency check on the system to identify any underlying issues that may be affecting the activation logs.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SCPR20: Used for managing Business Configuration Sets.
  SLG1: Used for viewing application logs.
  
  
  
  SAP Documentation: Refer to the official SAP Help Portal for detailed documentation on Business Configuration Sets and their activation processes.
  
  
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  
  
  If the issue persists after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.