Do you have any question about this error?
Message type: E = Error
Message class: CM_CBESCOM_INB - Message Class for ESComXML Inbound Processing
Message number: 019
Message text: Import request &1 was already deleted
The import request has already been deleted.
INCLUDE EHSPRC_ESCOM_INB_CANC OBJECT DOKU ID TX
INCLUDE EHSPRC_ESCOM_INB_RELOAD OBJECT DOKU ID TX
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.
CM_CBESCOM_INB019
- Import request &1 was already deleted ?The SAP error message CM_CBESCOM_INB019 indicates that an import request (transport request) you are trying to process has already been deleted from the system. This can occur in various scenarios, such as when you attempt to import a transport request that has been removed or is no longer available in the transport directory.
Cause:
- Manual Deletion: The transport request may have been manually deleted by a user with the appropriate permissions.
- System Cleanup: A system cleanup process may have removed the transport request due to retention policies or other maintenance activities.
- Transport Directory Issues: There may be inconsistencies in the transport directory or database that lead to the system not being able to find the requested transport.
- Incorrect Request Number: The request number you are trying to import may be incorrect or mistyped.
Solution:
Verify Request Status: Check the status of the transport request in the Transport Management System (TMS) to confirm whether it exists or has been deleted.
- Use transaction code
SE01
orSE09
to view transport requests.Check Transport Directory: Ensure that the transport request is still present in the transport directory on the file system. You can check the transport directory path defined in the system settings.
Recreate the Transport Request: If the transport request has been deleted and you still need the changes, you may need to recreate the transport request. This involves re-collecting the objects and creating a new transport request.
Consult with Basis Team: If you are unsure about the deletion or if it was part of a system cleanup, consult with your SAP Basis team. They may have logs or additional information regarding the deletion.
Check for System Errors: Look for any system errors or logs that might indicate why the request was deleted or if there are any underlying issues with the transport system.
Use Transport Logs: Review transport logs for any additional information that might help diagnose the issue.
Related Information:
If the issue persists after following these steps, consider reaching out to SAP support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
CM_CBESCOM_INB018
An import request was found
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CM_CBESCOM_INB017
&1 import requests were found
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CM_CBESCOM_INB020
Check for request &1 started; update the worklist
Prnfung lSuft im Hintergrund; Aktualisieren Sie den ArbeitsvorratWhat causes this issue? The extended ESComXML check was started in the background. ...
CM_CBESCOM_INB021
Import request &2 locked by user &1; action not possible
What causes this issue? The system could not lock the import request '&V2&' because it is being edited by the user &V1&.Sys...
Click on this link to search all SAP messages.