How To Fix USMD1039 - Transport request will be deleted: model name is in customer namespace

SAP Error Message - Details

• Message type: E = Error

• Message class: USMD1 - Datenmodel

• Message number: 039

• Message text: Transport request will be deleted: model name is in customer namespace

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 USMD1039 - Transport request will be deleted: model name is in customer namespace ?

  The SAP error message USMD1039 indicates that a transport request is being deleted because the model name is in the customer namespace. This typically occurs in the context of SAP Master Data Governance (MDG) when working with data models that are defined in the customer namespace (e.g., Z or Y).
  Cause:
  
  Customer Namespace: The model you are trying to transport is defined in a customer namespace. SAP restricts the transport of certain objects in customer namespaces to prevent issues with custom developments and to ensure that they are managed properly.
  Transport Request Issues: The transport request may not be properly configured or may not have the necessary authorizations to transport objects in the customer namespace.
  Model Deletion: The system may automatically delete the transport request if it detects that the model is in a customer namespace and is not eligible for transport.
  
  Solution:
  
  Check Model Configuration: Ensure that the model you are trying to transport is correctly configured and that it is intended to be transported. If it is a custom model, consider whether it needs to be transported or if it can remain in the development environment.
  Use the Correct Transport Request: Make sure you are using a transport request that is appropriate for customer namespace objects. You may need to create a new transport request specifically for the custom model.
  Authorization Check: Verify that you have the necessary authorizations to transport objects in the customer namespace. You may need to consult with your SAP Basis or security team to ensure you have the right permissions.
  Manual Transport: If automatic transport is not possible, consider manually recreating the model in the target system or using other methods to move the model (e.g., through a custom script or manual entry).
  Consult Documentation: Refer to SAP documentation or notes related to Master Data Governance and transport requests for any specific guidelines or restrictions regarding customer namespace objects.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on handling transport requests in customer namespaces.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  Transport Management System (TMS): Familiarize yourself with the Transport Management System in SAP, as it governs how transport requests are created, managed, and moved between systems.
  
  If the issue persists after following these steps, consider reaching out to SAP support for further assistance.