How To Fix /PMG/GE_COR013 - Correspondence of type &1 and frequency &2 not pending update

/PMG/GE_COR013 - Overview

• Message type: E = Error

• Message class: /PMG/GE_COR -

• Message number: 013

• Message text: Correspondence of type &1 and frequency &2 not pending update

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.

/PMG/GE_COR013 - Details

• The SAP error message /PMG/GE_COR013 indicates that there is an issue with the correspondence type and frequency specified in the system. This error typically arises in the context of the SAP Public Sector Management (PSM) module, particularly when dealing with correspondence management.
  
  Cause:
  The error message /PMG/GE_COR013 usually occurs due to one or more of the following reasons:
  
  Incorrect Correspondence Type or Frequency: The specified correspondence type (&1) or frequency (&2) may not be valid or may not exist in the system.
  No Pending Updates: There may not be any pending updates for the specified correspondence type and frequency combination. This could happen if the correspondence has already been processed or if there are no records that match the criteria.
  
  Configuration Issues: There may be configuration issues in the correspondence management settings that prevent the system from recognizing the correspondence type and frequency.
  Authorization Issues: The user may not have the necessary authorizations to access or