How To Fix FMFG_RECON_E066 - Cannot transport until changes are saved

SAP Error Message - Details

• Message type: E = Error

• Message class: FMFG_RECON_E - Reconciliation Tool message class

• Message number: 066

• Message text: Cannot transport until changes are saved

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 FMFG_RECON_E066 - Cannot transport until changes are saved ?

  The SAP error message FMFG_RECON_E066 ("Cannot transport until changes are saved") typically occurs in the context of the SAP system when you are trying to transport changes that have not been saved or activated in the system. This error is often related to the Financial Management (FM) module, particularly when dealing with configuration or settings that need to be transported to another system.
  Cause:
  
  Unsaved Changes: The most common cause of this error is that there are changes in the configuration that have not been saved. This can happen if you have made adjustments in the configuration but have not yet saved them.
  Incomplete Transport Request: The transport request you are trying to use may not be complete or may not include all necessary objects.
  Locking Issues: Sometimes, the objects you are trying to transport may be locked by another user or process, preventing you from completing the transport.
  
  Solution:
  
  Save Changes: Ensure that all changes you have made in the configuration are saved. Go back to the configuration transaction where you made the changes and save them.
  Check Transport Request: Verify that the transport request you are using is complete and includes all necessary objects. You can do this by checking the transport request in the Transport Organizer (transaction SE09 or SE10).
  Release Transport Request: If the transport request is complete, make sure it is released. You can release it in the Transport Organizer.
  Check for Locks: Use transaction SM12 to check for any locks on the objects you are trying to transport. If you find any locks that are preventing the transport, you may need to unlock them or wait for the locking process to complete.
  Review Logs: Check the transport logs for any additional error messages or warnings that might provide more context about the issue.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE09 (Transport Organizer), SE10 (Transport Organizer - Modifiable Requests), and SM12 (Display and Delete Locks).
  Transport Management System (TMS): Understanding how the TMS works can help you manage transports more effectively.
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  
  If the issue persists after following these steps, consider reaching out to your SAP Basis team or consulting SAP support for further assistance.