Do you have any question about this error?
Message type: E = Error
Message class: XMS_ADM - XMS - Administration
Message number: 311
Message text: Transport not possible since object is local
Object created as local object (see object directory entry).
Local objects cannot be transported.
If you would like to transport the object, you must change the object
directory entry and assign a valid and transportable package.
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.
XMS_ADM311
- Transport not possible since object is local ?The SAP error message XMS_ADM311 indicates that a transport request cannot be created or processed because the object in question is local to the system and not available for transport. This typically occurs when you try to transport objects that are not meant to be transported, such as local customizations or configurations that exist only in the development system.
Cause:
- Local Objects: The object you are trying to transport is defined as a local object (e.g., it has a local object name starting with
$_
or is not assigned to a transport request).- Missing Transport Request: The object has not been assigned to a transport request, which is necessary for it to be moved to another system (e.g., from Development to Quality Assurance).
- Development Environment: The object was created or modified in a way that it is not recognized as transportable.
Solution:
Check Object Assignment:
- Ensure that the object is assigned to a transport request. You can do this by checking the object in the relevant transaction (e.g., SE80 for development objects).
- If it is a local object, you may need to create a transport request and assign the object to it.
Convert Local Object:
- If the object is a local object, you can convert it to a transportable object. This can usually be done by:
- Opening the object in the relevant transaction.
- Using the option to "Create Transport Request" or "Assign to Transport Request" (this may vary depending on the type of object).
Recreate the Object:
- If the object cannot be converted or assigned to a transport request, you may need to recreate it in a way that it is transportable. This may involve creating a new object and ensuring it is assigned to a transport request from the start.
Check Transport Layer:
- Ensure that the transport layer is correctly configured and that you have the necessary authorizations to create and manage transport requests.
Consult Documentation:
- Refer to SAP documentation or help resources for specific instructions related to the type of object you are working with.
Related Information:
If you continue to experience issues, consider reaching out to your SAP Basis team or consulting SAP support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
XMS_ADM310
Object directory entry does not yet exist; save first
What causes this issue? No object directory entry exists for the current object.System Response Object can only be transported when there is a objec...
XMS_ADM309
Object can only be deleted in original system &
What causes this issue? You want to delete an object whose original entry is in system <(>&<)>.System Response Object may only be de...
XMS_ADM312
No transport request selected
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
XMS_ADM313
Object can only be maintained in language &
What causes this issue? The original language of the object is &.System Response The system issues an error message and will not allow you to co...
Click on this link to search all SAP messages.