How To Fix STRALAN_SPAM173 - Starting import:

SAP Error Message - Details

• Message type: E = Error

• Message class: STRALAN_SPAM - Messages for RSTLAN_IMPORT_OCS

• Message number: 173

• Message text: Starting import:

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 STRALAN_SPAM173 - Starting import: ?

  The SAP error message STRALAN_SPAM173 typically occurs during the import of Support Package or Add-On in the SAP system. This error indicates that there is an issue with the import process, often related to the transport directory or the import queue.
  Cause:
  
  Transport Directory Issues: The transport directory may not be correctly set up or may have missing files.
  Lock Entries: There may be lock entries in the transport management system that prevent the import from proceeding.
  Incorrect Configuration: The system configuration may not be aligned with the requirements for the Support Package or Add-On being imported.
  Version Compatibility: The Support Package or Add-On may not be compatible with the current version of the SAP system.
  Missing Dependencies: There may be missing dependencies or prerequisites that need to be addressed before the import can proceed.
  
  Solution:
  
  Check Transport Directory: Ensure that the transport directory is correctly configured and that all necessary files are present.
  Clear Lock Entries: Use transaction code SM12 to check for and delete any lock entries that may be causing the issue.
  Review Configuration: Verify that the system configuration is correct and meets the requirements for the Support Package or Add-On.
  Check Compatibility: Ensure that the version of the Support Package or Add-On is compatible with your current SAP system version.
  Resolve Dependencies: Check for any missing dependencies and resolve them before attempting the import again.
  Use Transaction SPAM: If you are using the Support Package Manager (SPAM), ensure that you are following the correct steps and that the system is in a stable state before starting the import.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SPAM, SE01, SE09, and SM12 for managing transports and checking for locks.
  SAP Notes: Check SAP Notes related to the specific Support Package or Add-On for any known issues or additional steps that may be required.
  System Logs: Review system logs and the transport logs for more detailed error messages that can provide further insight into the issue.
  SAP Community: Consider reaching out to the SAP Community or forums for additional support and shared experiences from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be beneficial to contact SAP support for further assistance.