How To Fix /PF1/PE_PP_BASIS320 - &1 logs deleted, &2 could not be deleted

SAP Error Message - Details

• Message type: E = Error

• Message class: /PF1/PE_PP_BASIS -

• Message number: 320

• Message text: &1 logs deleted, &2 could not be deleted

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 /PF1/PE_PP_BASIS320 - &1 logs deleted, &2 could not be deleted ?

  The SAP error message /PF1/PE_PP_BASIS320 typically indicates an issue related to the deletion of logs in the SAP system. The message format suggests that it is trying to delete certain logs, but some of them could not be deleted for various reasons.
  Cause:
  
  Authorization Issues: The user executing the deletion may not have the necessary authorizations to delete certain logs.
  Log Locking: The logs might be locked by another process or user, preventing their deletion.
  Database Constraints: There may be database constraints or issues that prevent the deletion of logs.
  Configuration Issues: There could be configuration settings in the system that restrict log deletion.
  Technical Errors: There might be underlying technical issues, such as database corruption or connectivity problems.
  
  Solution:
  
  Check Authorizations: Ensure that the user has the necessary authorizations to delete logs. This can be done by reviewing the user's roles and permissions.
  Check for Locks: Use transaction codes like SM12 to check for any locks on the logs that are preventing deletion. If locks are found, they may need to be released.
  Review Configuration: Check the configuration settings related to log management in the SAP system. Ensure that there are no restrictions on log deletion.
  Database Check: Perform a database check to ensure there are no issues that could be causing the deletion to fail. This may involve checking for database integrity or running database repair tools.
  Consult SAP Notes: Look for relevant SAP Notes that may address this specific error message. SAP frequently releases notes that provide solutions or workarounds for known issues.
  System Logs: Review system logs (transaction SLG1) for any additional error messages or information that could provide more context about the failure.
  Contact SAP Support: If the issue persists and cannot be resolved through the above steps, consider reaching out to SAP Support for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM37 (Job Monitoring), SLG1 (Application Log), and SM12 (Lock Entries).
  SAP Notes: Regularly check the SAP Support Portal for notes related to log management and specific error messages.
  Documentation: Review SAP documentation on log management and deletion processes to understand best practices and system behavior.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.