How To Fix TR_AUSL635 - Customer namespace not included in delivery request

SAP Error Message - Details

• Message type: E = Error

• Message class: TR_AUSL - Software Delivery Composer Messages

• Message number: 635

• Message text: Customer namespace not included in delivery request

What causes this issue?

A customer namespace has been defined for the table. However, the
corresponding entry is not in the delivery request.

System Response

The system displays the relevant entries in the results overview in the
object list check.

How to fix this error?

Check whether the specified entries are delivery-relevant.
For a delta delivery, an entry may not be required in the request.
If the customer namespace is relevant for delivery, include it in the
delivery request by selecting the entry and choosing <LS>Correct Entries
</>.
If you do not want to deliver the customer namespace, select the message
and choose <LS>Set Entries to 'Completed'</>.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message TR_AUSL635 - Customer namespace not included in delivery request ?

  The SAP error message TR_AUSL635, which states "Customer namespace not included in delivery request," typically occurs during the transport process when you are trying to transport objects that are in a customer namespace (usually defined as objects that start with a specific prefix, such as Z or Y) but the transport request does not include these objects.
  Cause:
  
  Transport Request Configuration: The transport request may not be configured to include objects from the customer namespace. This can happen if the transport request was created without the necessary authorizations or if the objects were not properly added to the request.
  Missing Objects: The objects you are trying to transport may not have been included in the transport request, or they may have been excluded due to a configuration issue.
  Transport Layer Settings: The transport layer settings may not allow for the transport of objects from the customer namespace.
  
  Solution:
  
  Check Transport Request: Verify that the transport request you are using includes the necessary objects from the customer namespace. You can do this by checking the contents of the transport request in the Transport Organizer (transaction SE09 or SE10).
  Add Objects to Transport Request: If the objects are missing, you can manually add them to the transport request. Use transaction SE80 or SE11 to locate the objects and add them to the appropriate transport request.
  Review Transport Layer Settings: Ensure that the transport layer settings allow for the transport of customer namespace objects. You may need to consult with your Basis team to verify these settings.
  Create a New Transport Request: If the current transport request is not suitable, consider creating a new transport request and ensuring that all necessary objects are included from the start.
  Check Authorizations: Ensure that you have the necessary authorizations to transport objects from the customer namespace. If you lack the required permissions, contact your SAP administrator.
  
  Related Information:
  
  Transport Organizer (SE09/SE10): Use these transactions to manage and monitor transport requests.
  Transport Management System (TMS): Familiarize yourself with TMS settings and configurations, as they govern how transports are handled in your SAP landscape.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to transport requests and customer namespaces. You can search for notes in the SAP Support Portal.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.