How To Fix /UI2/SPACE013 - Transport: No package allowed in scope &1

SAP Error Message - Details

• Message type: E = Error

• Message class: /UI2/SPACE -

• Message number: 013

• Message text: Transport: No package allowed in scope &1

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 /UI2/SPACE013 - Transport: No package allowed in scope &1 ?

  The SAP error message /UI2/SPACE013 Transport: No package allowed in scope &1 typically occurs during the transport of UI5 applications or Fiori elements when the system detects that a package is not allowed in the specified transport request. This can happen for various reasons, often related to the configuration of the transport landscape or the specific settings of the package.
  Cause:
  
  Package Restrictions: The package associated with the object you are trying to transport may have restrictions that prevent it from being included in the transport request. This can be due to the package being marked as "local" or "not transportable."
  Transport Layer Configuration: The transport layer may not be configured to allow certain packages to be transported.
  Development Class Settings: The development class (package) may not be assigned to a transportable package or may be set to a non-transportable status.
  
  Solution:
  
  
  Check Package Settings:
  
  Go to transaction SE80 or SE21 and check the package associated with the object.
  Ensure that the package is transportable. If it is marked as local or non-transportable, you may need to change its status or create a new transportable package.
  
  
  
  Adjust Transport Layer:
  
  Check the transport layer settings in transaction STMS. Ensure that the transport layer allows the transport of the package in question.
  
  
  
  Reassign Objects:
  
  If the package is not transportable, consider moving the objects to a different package that is transportable. You can do this by using transaction SE80 or SE11 to reassign the objects to a new package.
  
  
  
  Create a New Transport Request:
  
  If you are unable to modify the existing transport request, you may need to create a new transport request and include the objects in a transportable package.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to transport management and package settings for any specific guidelines or updates.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  SE80: Object Navigator
  SE21: Transport Organizer
  STMS: Transport Management System
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
  Transport Management: Familiarize yourself with the transport management process in SAP, including how to manage packages and transport requests effectively.
  
  If the issue persists after trying the above solutions, consider reaching out to your SAP Basis team or consulting SAP support for further assistance.