How To Fix /SMB/TRANSP_INFRA355 - Starting Import of Customer Solution Structure

SAP Error Message - Details

• Message type: E = Error

• Message class: /SMB/TRANSP_INFRA -

• Message number: 355

• Message text: Starting Import of Customer Solution Structure

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_INFRA355 - Starting Import of Customer Solution Structure ?

  The SAP error message /SMB/TRANSP_INFRA355 Starting Import of Customer Solution Structure typically occurs during the transport process in SAP, particularly when dealing with the import of a transport request that includes a customer solution structure. This message is not necessarily an error but rather an informational message indicating that the import process is starting.
  Possible Causes:
  
  Transport Request Issues: The transport request may not be properly configured or may have missing components.
  Authorization Issues: The user performing the import may not have the necessary authorizations to execute the transport.
  System Configuration: There may be inconsistencies in the system configuration or the target system may not be properly set up to receive the transport.
  Dependencies: The transport may depend on other transports that have not yet been imported.
  
  Solutions:
  
  Check Transport Request: Ensure that the transport request is complete and correctly configured. Verify that all necessary objects are included.
  Review Authorizations: Confirm that the user has the appropriate authorizations to perform the import. This can be checked in transaction SU53 or by consulting with your security team.
  System Configuration: Ensure that the target system is properly configured and that all necessary components are in place. Check for any system notes or updates that may need to be applied.
  Check Dependencies: Review any dependencies that the transport may have. If there are other transports that need to be imported first, ensure they are completed.
  Logs and Traces: Check the transport logs for any additional error messages or warnings that may provide more context about the issue. You can do this in transaction STMS (Transport Management System) or by checking the logs in transaction SLG1.
  
  Related Information:
  
  Transaction Codes: 
  
  STMS: Transport Management System
  SE01: Transport Organizer
  SE09: Workbench Organizer
  SE10: Customizing Organizer
  
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address specific issues related to transport imports.
  Documentation: Review SAP documentation related to transport management for best practices and troubleshooting steps.
  
  If the issue persists after checking these areas, it may be beneficial to consult with SAP support or your internal SAP Basis team for further assistance.