How To Fix PRC_MESSAGES_EXT715 - Check currently not possible

SAP Error Message - Details

• Message type: E = Error

• Message class: PRC_MESSAGES_EXT -

• Message number: 715

• Message text: Check currently not possible

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 PRC_MESSAGES_EXT715 - Check currently not possible ?

  The SAP error message "PRC_MESSAGES_EXT715 Check currently not possible" typically occurs in the context of the SAP Project System (PS) or the SAP Controlling (CO) module, particularly when dealing with project-related checks or validations. This error can arise due to various reasons, and understanding the cause is essential for finding a solution.
  Possible Causes:
  
  Missing Configuration: The error may occur if there are missing configurations in the project settings or if the project is not properly set up.
  Authorization Issues: The user may not have the necessary authorizations to perform the check or access certain data.
  Data Inconsistencies: There may be inconsistencies in the data related to the project, such as missing master data or incorrect settings.
  System Issues: Temporary system issues or inconsistencies in the database can also lead to this error.
  Lock Entries: If another user or process is currently accessing the project or related data, it may lead to a lock that prevents the check from being performed.
  
  Solutions:
  
  Check Configuration: Review the project configuration settings to ensure that all necessary parameters are correctly set up. This includes checking the project definition, work breakdown structure (WBS), and any related settings.
  Verify Authorizations: Ensure that the user has the appropriate authorizations to perform the check. This can be done by checking the user roles and permissions in the SAP system.
  Data Consistency Check: Perform a data consistency check to identify any missing or incorrect data. This may involve checking master data, transaction data, and any related settings.
  System Restart: If the issue is due to a temporary system problem, restarting the SAP system or the relevant application server may resolve the issue.
  Check for Locks: Use transaction codes like SM12 to check for any lock entries that may be preventing access to the project data. If locks are found, they may need to be released.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes or patches that may address this specific error message. SAP frequently releases updates that can resolve known issues.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CJ20N (Project Builder), CJ01 (Create Work Breakdown Structure), and CJ02 (Change Work Breakdown Structure) to navigate project-related tasks.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  Documentation: Review SAP documentation related to the Project System and Controlling modules for best practices and troubleshooting steps.
  
  If the issue persists after trying the above solutions, it may be necessary to involve your SAP Basis or technical support team for further investigation.