How To Fix COM_DML_CUST173 - Archiving object & could not be included in the transport request

SAP Error Message - Details

• Message type: E = Error

• Message class: COM_DML_CUST - MDF Messages

• Message number: 173

• Message text: Archiving object & could not be included in the transport request

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message COM_DML_CUST173 - Archiving object & could not be included in the transport request ?

  The SAP error message COM_DML_CUST173 typically indicates that there is an issue with archiving objects that cannot be included in a transport request. This error can occur in various scenarios, particularly when dealing with data archiving and transport management in SAP systems.
  Cause:
  
  Transport Request Issues: The archiving object you are trying to transport may not be properly configured or may not be included in the transport request due to restrictions or settings in the transport management system.
  Authorization Issues: The user may not have the necessary authorizations to include certain objects in the transport request.
  Configuration Errors: There may be configuration errors in the archiving object settings or in the transport layer.
  Missing Dependencies: The archiving object may have dependencies that are not included in the transport request, leading to this error.
  
  Solution:
  
  Check Transport Request: Ensure that the transport request is correctly configured and that the archiving object is included. You may need to manually add the object to the transport request.
  Review Authorizations: Verify that the user has the necessary authorizations to include the archiving object in the transport request. You may need to consult with your SAP security team.
  Check Configuration: Review the configuration of the archiving object in transaction SARA (Archive Administration) to ensure that it is set up correctly.
  Dependencies: Make sure that all dependencies of the archiving object are included in the transport request. This may involve checking related customizing settings or other objects that need to be transported alongside the archiving object.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message. There may be patches or updates that resolve known issues.
  Testing in Development: If possible, test the transport in a development environment to identify any issues before moving to production.
  
  Related Information:
  
  Transaction Codes: 
  
  SARA: Archive Administration
  SE09/SE10: Transport Organizer
  
  
  SAP Notes: Search for specific SAP Notes related to the error message or archiving objects in the SAP Support Portal.
  Documentation: Review SAP documentation on data archiving and transport management for best practices and troubleshooting steps.
  
  If the issue persists after trying the above solutions, it may be beneficial to engage with SAP support for further assistance.