How To Fix /SMB/TRANSP_INFRA347 - Customer Scope is unchanged: DB update not necessary

/SMB/TRANSP_INFRA347 - Overview

• Message type: E = Error

• Message class: /SMB/TRANSP_INFRA -

• Message number: 347

• Message text: Customer Scope is unchanged: DB update not necessary

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_INFRA347 - Customer Scope is unchanged: DB update not necessary ?

  The SAP error message /SMB/TRANSP_INFRA347 Customer Scope is unchanged: DB update not necessary typically occurs during the transport process in SAP, particularly when dealing with the SAP Business ByDesign or SAP S/4HANA systems. This message indicates that the system has detected that the customer scope (the specific configurations or customizations made for a customer) has not changed, and therefore, there is no need to perform a database update.
  
  Cause:
  
  
  No Changes Detected: The primary cause of this message is that the transport request being processed does not contain any changes that require a database update. This can happen if:
  
  The objects included in the transport request have not been modified.
  The changes have already been applied in the target system.
  The transport request is being reprocessed without any new changes.
  
  
  
  Transport Request Configuration: Sometimes, the transport request may not be configured correctly, leading to the system determining that no updates are necessary.
  
  
  
  Solution:
  
  
  Verify Changes: Check the transport