Message type: E = Error
Message class:  TR_AUSL - Software Delivery Composer Messages 
Message number: 591
Message text: Object from another namespace (&1 instead of &2):
The delivery request &V3& contains objects from the namespace <ZH>&V1&
</> but the delivery is assigned to the namespace <ZH>&V2&</>.
The system displays these objects in the results overview of the object
list check.
If you are not the owner of the namespace <ZH>&V2&</>, you are not
allowed to deliver these objects, or only with the agreement of the
owner.
Check whether the objects are delivery-relevant and remove those that
are non-relevant.
Error message extract from SAP system. Copyright SAP SE.
The SAP error message TR_AUSL591 indicates that there is an issue with the transport of an object that belongs to a different namespace than expected. This typically occurs when you are trying to transport an object (like a program, function module, or class) that is defined in a different namespace than the one you are currently working in.
Cause: Namespace Mismatch: The object you are trying to transport is in a different namespace than the one specified in the transport request. For example, if you are working in a custom namespace (like Z or Y) and the object belongs to a standard namespace (like SAP's own namespaces), this error can occur. Transport Request Configuration: The transport request may not be configured correctly to include objects from different namespaces. Development Class Issues: The object might be assigned to a development class that is not allowed to transport objects from other namespaces.
Solution: Check Object Namespace: Verify the
 Get instant SAP help. Sign up for our Free Essentials Plan.
Get instant SAP help. Sign up for our Free Essentials Plan. 
TR_AUSL590 Table contents belong to a table that cannot be transported directly
What causes this issue?  The current delivery request &V1& contains entries from tables that cannot be transported directly. This could be bec...
TR_AUSL589 Status of checks already performed for &1 invalidated (&2, &3, &4)
What causes this issue?  The system has set the status of the completed object list checks for the delivery request &V1& to invalidated. This ...
TR_AUSL592 Object from SAP or partner name range (&1 instead of namespace &2):
What causes this issue?  The current delivery request &V3& contains objects from the name range <ZH>&V1&</>, however the n...
TR_AUSL593 &1 (type &2) cannot be checked: flagged requests exist
What causes this issue?  The object list check for delivery request &V1& of type &V2& (for delivery component &V3&) cannot be ...
Click on this link to search all SAP messages.