Do you have any question about this error?
Message type: E = Error
Message class: RLB - Reuse Library
Message number: 072
Message text: &1 can be transported, &3 cannot
The package of the referencing object and the object being referred to
are not compatible:
&V1& belongs to package &V2& that is connected to the Workbench
Organizer. This object can therefore be transported.
&V3& belongs to package &V4& that cannot be transported (e.g. local
private objects)
If you were to transport this constellation it would mean that the
object being referred to would not exist in the target system.
An error message is issued.
Change the package of the object being referred to or choose a
different object.
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.
RLB072
- &1 can be transported, &3 cannot ?The SAP error message RLB072 typically indicates an issue related to transport requests in the SAP system. This message means that a specific object (denoted by &1) can be transported, but another object (denoted by &3) cannot be transported due to certain restrictions or conditions.
Cause:
- Transport Layer Issues: The object that cannot be transported may belong to a transport layer that is not allowed for the current transport request.
- Object Type Restrictions: Certain object types may have restrictions on transportability based on their configuration or the system landscape.
- Missing Authorizations: The user may not have the necessary authorizations to transport the object.
- Dependencies: The object that cannot be transported may have dependencies on other objects that are not included in the transport request.
- Transport Route Configuration: The transport route may not be correctly configured, preventing certain objects from being transported.
Solution:
- Check Transport Layer: Verify the transport layer settings for the objects involved. Ensure that the object that cannot be transported is assigned to a transport layer that allows it to be included in the transport request.
- Review Object Types: Check the object types and their transportability settings. Some objects may be marked as non-transportable.
- Authorization Check: Ensure that the user has the necessary authorizations to transport both objects. This may involve checking roles and profiles assigned to the user.
- Dependency Analysis: Analyze the dependencies of the object that cannot be transported. Ensure that all required objects are included in the transport request.
- Transport Route Configuration: Review the transport route configuration in the Transport Management System (TMS) to ensure that it is set up correctly for the objects you are trying to transport.
- Consult Documentation: Refer to SAP documentation or notes related to transport issues for further guidance.
Related Information:
If the problem persists after following these steps, it may be beneficial to consult with your SAP Basis team or SAP support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
RLB071
Object &1 &2 &3 is not assigned to a package
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RLB070
No node text exists
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RLB073
&1 is to be delivered to the customer, &3 not
What causes this issue? The packages of the referencing object and the object being referred to are not compatible: &V1& belongs to package &...
RLB074
SAPScript document &1 &2 does not have a TADIR entry
What causes this issue? Either the SAPScript document type &V1& or the document &V1& &V2& does not exist.System Response The...
Click on this link to search all SAP messages.