How To Fix 6B072 - No correspondence is printed after saving

SAP Error Message - Details

• Message type: E = Error

• Message class: 6B - Real estate correspondence messages

• Message number: 072

• Message text: No correspondence is printed after saving

What causes this issue?

According to the settings you made in Customizing, a correspondence
print is not triggered when newly created master data types are saved.

System Response

No letter is printed.
This is only for your information.

How to fix this error?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Procedure for System Administrators

Change the corresponding settings in Customizing if correspondence is
to be printed for certain master data types directly after they have
been created.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 6B072 - No correspondence is printed after saving ?

  The SAP error message 6B072 ("No correspondence is printed after saving") typically occurs in the context of document processing, particularly when dealing with correspondence or output documents in SAP. This error indicates that the system did not generate any output (like a printout or email) after saving a document, which can be frustrating for users expecting to see correspondence generated automatically.
  Causes:
  
  
  Output Type Configuration: The output type may not be configured correctly in the system. This includes settings related to the output medium (e.g., print, email) and the conditions under which the output should be generated.
  
  
  No Output Determination: The system may not have determined any output for the document based on the settings in the output determination procedure.
  
  
  User Settings: The user profile or settings may not allow for automatic output generation.
  
  
  Document Status: The document may not be in a status that allows for correspondence to be printed. For example, if the document is incomplete or in a draft state.
  
  
  Missing Master Data: Required master data (like customer or vendor information) may be missing or incomplete, preventing the output from being generated.
  
  
  Authorization Issues: The user may not have the necessary authorizations to generate output.
  
  
  Solutions:
  
  
  Check Output Type Configuration:
  
  Go to the output type configuration in transaction NACE (for application area relevant to your document, e.g., Sales, Purchasing).
  Ensure that the output type is correctly set up, including the conditions for triggering the output.
  
  
  
  Review Output Determination:
  
  Check the output determination procedure to ensure that the correct output type is assigned to the document type you are working with.
  
  
  
  Verify User Settings:
  
  Check the user settings in transaction SU01 to ensure that the user has the correct output settings.
  
  
  
  Document Status:
  
  Ensure that the document is in a status that allows for output generation. If necessary, complete or change the status of the document.
  
  
  
  Check Master Data:
  
  Verify that all required master data is complete and accurate. This includes checking customer/vendor records and ensuring that all necessary fields are filled.
  
  
  
  Authorization Check:
  
  Ensure that the user has the necessary authorizations to generate the output. This can be checked in transaction SU53 after attempting to generate the output.
  
  
  
  Test Output Generation:
  
  Try to manually trigger the output generation to see if it works. This can help identify if the issue is with automatic generation or a broader configuration issue.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as NACE (for output types), SU01 (user maintenance), and SU53 (authorization check).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Documentation: Review SAP documentation related to output management and correspondence processing for more detailed guidance.
  
  If the issue persists after checking these areas, it may be beneficial to consult with your SAP Basis or functional team for further investigation.