How To Fix 42273 - &2 physical objects of &1 physical objects were deleted

SAP Error Message - Details

• Message type: E = Error

• Message class: 42 - Information Workbench

• Message number: 273

• Message text: &2 physical objects of &1 physical objects were 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 42273 - &2 physical objects of &1 physical objects were deleted ?

  The SAP error message "42273 &2 physical objects of &1 physical objects were deleted" typically occurs during the execution of a database-related operation, such as a transport or a deletion of objects in the SAP system. This message indicates that a certain number of physical objects (like tables, indexes, etc.) were deleted from the database, and it provides a count of how many were successfully deleted versus how many were attempted.
  Cause:
  
  Transport Request: This error can occur when a transport request is being processed, and some objects are marked for deletion.
  Object Deletion: It may also arise when you are trying to delete certain objects from the system, and the system is reporting how many were successfully deleted.
  Inconsistent State: The system might be in an inconsistent state due to previous operations that did not complete successfully.
  
  Solution:
  
  Check Transport Logs: Review the transport logs to understand which objects were deleted and why. This can provide insight into whether the deletion was expected or if it indicates a problem.
  Consistency Check: Run consistency checks on the database to ensure that there are no inconsistencies due to the deletion of objects. You can use transaction codes like SE14 (Database Utility) to check and repair inconsistencies.
  Re-import Transport: If the deletion was not intended, you may need to re-import the transport request or restore the objects from a backup if they are critical.
  Review Deletion Criteria: If you are performing a deletion, ensure that the criteria for deletion are correct and that you are aware of the implications of deleting those objects.
  Consult Documentation: Refer to SAP documentation or notes related to this error message for specific guidance or patches that may address the issue.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions to common problems.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE80 (Object Navigator), SE11 (Data Dictionary), and SE14 (Database Utility) for managing and troubleshooting database objects.
  Backup and Recovery: Always ensure that you have a backup of your database before performing deletions or major changes to avoid data loss.
  
  If the issue persists or if you are unsure about the implications of the deletion, it may be advisable to consult with your SAP Basis team or SAP support for further assistance.