How To Fix C$679 - Document &1 &2 was not generated correctly (exception '&3')

SAP Error Message - Details

• Message type: E = Error

• Message class: C$ -

• Message number: 679

• Message text: Document &1 &2 was not generated correctly (exception '&3')

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 C$679 - Document &1 &2 was not generated correctly (exception '&3') ?

  The SAP error message C$679 indicates that a document (identified by &1 and &2) was not generated correctly due to an exception specified by &3. This error typically occurs in the context of document processing, such as invoice generation, delivery documents, or other transactional documents in SAP.
  Causes:
  
  Data Inconsistencies: There may be missing or inconsistent data in the document that is being processed.
  Configuration Issues: Incorrect configuration settings in the document type or related processes can lead to generation failures.
  Authorization Issues: The user may not have the necessary authorizations to generate the document.
  System Errors: Technical issues, such as system performance problems or bugs in the SAP system, can also cause this error.
  Custom Code: If there are custom enhancements or modifications in the document processing logic, they may introduce errors.
  
  Solutions:
  
  Check Document Data: Review the data associated with the document (e.g., customer/vendor details, item details) to ensure that all required fields are filled out correctly and that there are no inconsistencies.
  Review Configuration: Verify the configuration settings for the document type in question. Ensure that all necessary settings are correctly defined in the relevant customizing transactions (e.g., SPRO).
  Authorization Check: Ensure that the user has the necessary authorizations to create or process the document. This can be checked in transaction SU53 or by consulting with your security team.
  Analyze Exception Code: The exception code (&3) can provide more specific information about the nature of the error. Look up the exception code in SAP documentation or consult with your SAP support team for further insights.
  Check System Logs: Review system logs (transaction SLG1) for any related error messages or warnings that could provide additional context for the failure.
  Debugging: If you have access to debugging tools, you can analyze the program logic to identify where the error occurs. This may require assistance from a developer or SAP support.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide patches or updates.
  
  Related Information:
  
  Transaction Codes: Depending on the context of the document, you may need to use specific transaction codes to investigate further (e.g., VF03 for billing documents, ME23N for purchase orders).
  SAP Community: Engaging with the SAP Community forums can provide insights from other users who may have encountered similar issues.
  SAP Support: If the issue persists and cannot be resolved internally, consider reaching out to SAP Support for assistance.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.