How To Fix /STMC/CR_LOG136 - Deleted '&1' records from '&2'.

SAP Error Message - Details

• Message type: E = Error

• Message class: /STMC/CR_LOG -

• Message number: 136

• Message text: Deleted '&1' records from '&2'.

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 /STMC/CR_LOG136 - Deleted '&1' records from '&2'. ?

  The SAP error message /STMC/CR_LOG136 Deleted '&1' records from '&2'. typically indicates that a certain number of records (denoted by &1) have been deleted from a specific table or dataset (denoted by &2). This message is often related to data management processes, such as data archiving, data cleansing, or data consistency checks.
  Cause:
  
  Data Archiving: The records may have been deleted as part of a data archiving process where old or unnecessary data is removed to optimize database performance.
  Data Consistency Checks: The system may have identified inconsistencies or errors in the data, leading to the deletion of problematic records.
  Manual Deletion: Records could have been manually deleted by a user or through a batch job.
  Data Migration: During data migration processes, certain records may be deemed unnecessary or duplicates and thus deleted.
  
  Solution:
  
  Review Logs: Check the logs or reports generated during the process that led to the deletion. This can provide insights into why the records were deleted.
  Data Recovery: If the deletion was unintentional, you may need to restore the records from a backup if available.
  Adjust Archiving Settings: If the deletion was part of an archiving process, review the archiving settings to ensure they align with your data retention policies.
  Data Validation: Implement data validation checks to prevent the deletion of important records in the future.
  Consult Documentation: Refer to SAP documentation or support for specific guidance related to the module or process that generated the message.
  
  Related Information:
  
  Transaction Codes: Depending on the context, you may want to look into transaction codes related to data archiving (e.g., SARA) or data management.
  SAP Notes: Check SAP Notes for any known issues or updates related to the specific module or process you are working with.
  User Authorizations: Ensure that users have the appropriate authorizations to prevent accidental deletions.
  System Performance: Monitor system performance post-deletion to assess the impact of the removed records.
  
  If you continue to experience issues or if the deletion of records is causing operational problems, it may be beneficial to consult with your SAP Basis team or SAP support for further assistance.