How To Fix /SMB/MD_AS_CUST028 - Start of log: After Import meth for Transport of Non Customizing Objects

SAP Error Message - Details

• Message type: E = Error

• Message class: /SMB/MD_AS_CUST -

• Message number: 028

• Message text: Start of log: After Import meth for Transport of Non Customizing Objects

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/MD_AS_CUST028 - Start of log: After Import meth for Transport of Non Customizing Objects ?

  The SAP error message /SMB/MD_AS_CUST028 typically occurs during the import of non-customizing objects, particularly when there are issues related to the transport of metadata or configuration settings. This error can arise in various scenarios, such as when there are inconsistencies in the transport request, missing dependencies, or issues with the target system's configuration.
  Cause:
  
  Missing Dependencies: The transport request may depend on other objects or configurations that are not present in the target system.
  Inconsistent Data: There may be inconsistencies in the data being transported, such as mismatched versions or configurations.
  Authorization Issues: The user performing the import may not have the necessary authorizations to complete the operation.
  Transport Directory Issues: Problems with the transport directory or transport management system can also lead to this error.
  System Configuration: The target system may not be properly configured to accept the transported objects.
  
  Solution:
  
  Check Dependencies: Ensure that all dependent objects are included in the transport request. You may need to transport additional requests that contain the required dependencies.
  Review Transport Logs: Analyze the transport logs for more detailed error messages that can provide insights into what went wrong during the import process.
  Authorization Check: Verify that the user performing the import has the necessary authorizations to execute the transport.
  Correct Configuration: Ensure that the target system is correctly configured to accept the transported objects. This may involve checking settings related to the specific objects being imported.
  Re-import: If the issue persists, consider re-importing the transport request after addressing any identified issues.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  
  Related Information:
  
  SAP Transport Management System (TMS): Familiarize yourself with the TMS, as it plays a crucial role in managing transports between systems.
  SAP Notes: Regularly check for SAP Notes related to transport issues, as they often contain fixes or workarounds for known problems.
  System Logs: Use transaction codes like SLG1 (Application Log) or ST22 (Dump Analysis) to gather more information about the error.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.