How To Fix /SMB/TRANSP_INFRA100 - Correction solution already existed on the DB, archiving and deleting...

SAP Error Message - Details

• Message type: E = Error

• Message class: /SMB/TRANSP_INFRA -

• Message number: 100

• Message text: Correction solution already existed on the DB, archiving and deleting...

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 /SMB/TRANSP_INFRA100 - Correction solution already existed on the DB, archiving and deleting... ?

  The SAP error message /SMB/TRANSP_INFRA100 typically indicates that there is an issue related to the transport infrastructure, specifically concerning corrections or transport requests that already exist in the database. This can occur during the transport of changes or when trying to archive or delete transport requests.
  
  Cause:
  
  Duplicate Correction Requests: The error often arises when there is an attempt to create or transport a correction request that already exists in the database.
  Transport Directory Issues: There may be inconsistencies or issues in the transport directory or transport logs.
  Archiving Issues: If you are trying to archive or delete transport requests that are still referenced or have dependencies, this can lead to conflicts.
  Database Constraints: There may be database constraints or locks that prevent the operation from completing successfully.
  
  
  Solution:
  
  
  Check for Existing Requests: 
  
  Use transaction SE01 (Transport Organizer) to check if the correction request already exists. If it does, you may need to adjust your transport strategy.
  
  
  
  Delete