How To Fix /EACC/DMM072 - Transport request not written (&1)

SAP Error Message - Details

• Message type: E = Error

• Message class: /EACC/DMM -

• Message number: 072

• Message text: Transport request not written (&1)

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 /EACC/DMM072 - Transport request not written (&1) ?

  The SAP error message /EACC/DMM072 Transport request not written (&1) typically indicates an issue with the transport request process in the SAP system. This error can occur for various reasons, and understanding the cause is essential for finding a solution.
  Causes:
  
  Authorization Issues: The user may not have the necessary authorizations to create or modify transport requests.
  Transport Directory Issues: There may be problems with the transport directory or the transport management system (TMS) configuration.
  Transport Request Lock: The transport request might be locked by another user or process, preventing it from being written.
  System Configuration: There could be misconfigurations in the transport landscape or issues with the transport routes.
  Database Issues: There may be underlying database issues that prevent the transport request from being saved.
  
  Solutions:
  
  Check Authorizations: Ensure that the user has the necessary authorizations to create and manage transport requests. This can be done by checking the user's roles and authorizations in the SAP system.
  Review Transport Directory: Verify that the transport directory is correctly configured and accessible. Check the transport directory path and ensure that it has the necessary permissions.
  Unlock Transport Request: If the transport request is locked, identify the user or process that has locked it and resolve the lock. You can use transaction SE03 to check for locks.
  Check TMS Configuration: Review the transport management system configuration to ensure that all transport routes and systems are correctly set up. You can use transaction STMS to access TMS settings.
  Database Check: If there are database issues, check the database logs for any errors and resolve them. You may need to involve your database administrator for assistance.
  System Logs: Check the system logs (transaction SM21) for any related error messages that could provide more context about the issue.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE01 (Transport Organizer), SE03 (Transport Organizer Tools), and STMS (Transport Management System).
  SAP Notes: Search for SAP Notes related to transport issues. SAP frequently releases notes that address specific problems and provide solutions.
  Documentation: Review SAP documentation on transport management for best practices and troubleshooting steps.
  
  If the issue persists after trying the above solutions, consider reaching out to SAP support for further assistance.