How To Fix AXT_GEN363 - Customizing object &1 &2 has not been transported

AXT_GEN363 - Overview

• Message type: E = Error

• Message class: AXT_GEN - Generation framework

• Message number: 363

• Message text: Customizing object &1 &2 has not been transported

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 AXT_GEN363 - Customizing object &1 &2 has not been transported ?

  The SAP error message AXT_GEN363 indicates that a customizing object has not been transported. This typically occurs when you attempt to transport a customizing object (like a configuration setting or a development object) from one SAP system to another (e.g., from a development system to a quality assurance or production system), but the object is not included in the transport request.
  
  Cause:
  
  Missing Transport Request: The customizing object was not included in a transport request when it was created or modified.
  Transport Request Not Released: The transport request containing the object has not been released, meaning it is still in a "modification" state and cannot be transported.
  Incorrect Transport Layer: The object may belong to a different transport layer that is not configured for the current transport.
  Object Not Assigned: The object may not be assigned to a transport request at all.
  
  
  Solution:
  
  
  Check Transport Request:
  
  Go to the transaction code SE09 or SE10 to check the transport