How To Fix FQ772 - The indicators "Complete" and "Released" were reset

SAP Error Message - Details

• Message type: E = Error

• Message class: FQ - Payment Requests and Payment Program

• Message number: 772

• Message text: The indicators "Complete" and "Released" were reset

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 FQ772 - The indicators "Complete" and "Released" were reset ?

  The SAP error message FQ772, which states "The indicators 'Complete' and 'Released' were reset," typically occurs in the context of financial accounting and controlling, particularly when dealing with the completion status of certain documents or processes in SAP.
  Cause:
  This error message usually indicates that there is an inconsistency in the status of a financial document or transaction. The "Complete" and "Released" indicators are used to signify that a document has been finalized and is ready for processing. If these indicators are reset, it may be due to:
  
  Manual Intervention: A user may have manually reset the status of the document.
  System Process: A background job or process may have altered the status due to certain conditions not being met.
  Data Integrity Issues: There may be issues with data integrity or consistency in the database, leading to unexpected changes in document status.
  Configuration Issues: Incorrect configuration settings in the system could lead to this error.
  
  Solution:
  To resolve the FQ772 error, you can take the following steps:
  
  Check Document Status: Review the document in question to understand why the indicators were reset. Look for any recent changes or updates made to the document.
  Review User Actions: If the reset was due to manual intervention, check the user logs to identify who made the changes and why.
  Reprocess the Document: If the document needs to be completed or released again, you may need to reprocess it according to the business rules and workflows defined in your organization.
  Consult with Technical Support: If the issue persists, it may be necessary to consult with your SAP technical support team or a functional consultant to investigate further. They can check for any underlying issues in the system or database.
  Check Configuration Settings: Review the configuration settings related to document processing in your SAP system to ensure they are set up correctly.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FB03 (Display Document), FBL1N (Vendor Line Item Display), or FBL3N (G/L Account Line Item Display) to analyze the document status.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common problems.
  User Documentation: Review user manuals or documentation related to financial processes in your organization to ensure compliance with procedures.
  
  By following these steps, you should be able to identify the cause of the FQ772 error and implement a solution to resolve it.