How To Fix /PF1/MSG_PO_GENERAL099 - Correspondence for PO (&1/&2/&3) has been written previously

SAP Error Message - Details

• Message type: E = Error

• Message class: /PF1/MSG_PO_GENERAL -

• Message number: 099

• Message text: Correspondence for PO (&1/&2/&3) has been written previously

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 /PF1/MSG_PO_GENERAL099 - Correspondence for PO (&1/&2/&3) has been written previously ?

  The SAP error message /PF1/MSG_PO_GENERAL099 indicates that correspondence for a Purchase Order (PO) has already been generated and written previously. This message typically arises in the context of the Purchase Order processing, particularly when trying to generate correspondence (like printouts, emails, etc.) for a PO that has already been processed.
  Cause:
  
  Duplicate Correspondence Generation: The most common cause is that the system is attempting to generate correspondence for a PO that has already had correspondence created for it.
  System Configuration: There may be settings in the system that prevent multiple correspondences from being generated for the same PO.
  User Action: A user may have inadvertently tried to generate correspondence multiple times for the same PO.
  
  Solution:
  
  Check Existing Correspondence: Verify if correspondence has already been generated for the specified PO. You can do this by checking the PO history or correspondence logs.
  Review PO Status: Ensure that the PO is in a status that allows for correspondence generation. If the PO is closed or completed, it may not allow further correspondence.
  Use Different Output Type: If you need to send a different type of correspondence, consider using a different output type or modifying the existing one.
  Consult Documentation: Review the documentation or configuration settings related to the output management for POs to understand the rules governing correspondence generation.
  Contact Support: If the issue persists and you believe it should allow for additional correspondence, consider reaching out to your SAP support team or consulting with an SAP expert to investigate further.
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like ME23N (Display Purchase Order) to view the PO details and history.
  Output Determination: Check the output determination settings in the system (transaction NACE) to see how correspondence is configured for POs.
  SAP Notes: Look for any relevant SAP Notes that might address this specific error or provide additional guidance on handling correspondence for POs.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.