Do you have any question about this error?
Message type: E = Error
Message class: /SMB/TRANSP_INFRA -
Message number: 264
Message text: Repeating import due to previous result in Import History
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.
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.
The SAP error message
/SMB/TRANSP_INFRA264
indicates that there is a repeating import due to a previous result in the import history. This typically occurs in the context of transport management, where a transport request is being imported into a system, but the import process is being interrupted or has already been executed with a certain result.Cause:
- Previous Import Result: The transport request may have been imported previously, and the system is detecting that the same request is being attempted again without any changes or updates.
- Import History: The import history for the transport request indicates that the request has already been processed, which prevents it from being imported again.
- Transport Request Status: The transport request may be in a status that does not allow for re-import, such as being marked as "completed" or "failed" without the possibility of re-importing.
Solution:
- Check Import History: Review the import history for the transport request in question. You can do this using transaction
STMS
(Transport Management System) and navigating to the import history of the relevant transport request.- Delete or Adjust Previous Import: If the previous import was unsuccessful or needs to be re-imported, you may need to delete the previous import result or adjust the transport request accordingly. This can involve:
- Reverting changes made by the previous import if necessary.
- Adjusting the transport request to ensure it is in a state that allows for re-import.
- Re-transport the Request: If the transport request needs to be re-imported, ensure that it is properly released and that there are no locks or issues preventing the import.
- Check for Dependencies: Ensure that there are no dependencies or prerequisites that need to be addressed before re-importing the transport request.
- Consult Logs: Check the transport logs for any additional error messages or warnings that may provide more context on why the import is being blocked.
Related Information:
STMS
for transport management, SE01
for transport organizer, and SE09
for managing transport requests.If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
Feature | Free Access | Free Trial |
---|---|---|
Basic SAP error explanation | ![]() |
![]() |
Step-by-Step Usage Guide | ![]() |
![]() |
Interactive SAP Coach Assistance | ![]() |
![]() |
AI Troubleshooting for T-Code Errors | ![]() |
![]() |
/SMB/TRANSP_INFRA263 ID Clash Resolution failed
Self-Explanatory Message Since SAP believes that this specific error message is ...
/SMB/TRANSP_INFRA262 ID Management preparation failed
Self-Explanatory Message Since SAP believes that this specific error message is ...
/SMB/TRANSP_INFRA265 Error in source solution determination
Self-Explanatory Message Since SAP believes that this specific error message is ...
/SMB/TRANSP_INFRA266 A source solution might have been deleted, which is not allowed
Self-Explanatory Message Since SAP believes that this specific error message is ...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.