How To Fix /SMB/TRANSP_INFRA730 - Start working on reference changes

/SMB/TRANSP_INFRA730 - Overview

• Message type: E = Error

• Message class: /SMB/TRANSP_INFRA -

• Message number: 730

• Message text: Start working on reference changes

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_INFRA730 - Start working on reference changes ?

  The SAP error message /SMB/TRANSP_INFRA730 Start working on reference changes typically occurs in the context of transport management within the SAP system. This error is related to the transport infrastructure and indicates that there are reference changes that need to be processed.
  
  Cause:
  
  Reference Changes: The error usually arises when there are changes in the reference objects (like tables, programs, or other objects) that have not been properly processed or are pending in the transport request.
  Transport Request Issues: There may be issues with the transport request itself, such as it being locked, incomplete, or not properly released.
  System Configuration: Misconfiguration in the transport landscape or issues with the transport directory can also lead to this error.
  
  
  Solution:
  
  
  Check Transport Requests:
  
  Go to the Transport Organizer (transaction code SE09 or SE10) and check for any transport requests that are in a "modification" or "released" state.
  Ensure that all necessary objects are included in the transport request.
  
  
  
  Release Transport Requests:
  
  If