How To Fix /SCMTMS/FAG_MSG772 - RFQ still in use; cannot be marked for archiving

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/FAG_MSG -

• Message number: 772

• Message text: RFQ still in use; cannot be marked for archiving

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 /SCMTMS/FAG_MSG772 - RFQ still in use; cannot be marked for archiving ?

  The SAP error message /SCMTMS/FAG_MSG772 indicates that a Request for Quotation (RFQ) is still in use and cannot be marked for archiving. This typically occurs in the context of SAP Transportation Management (TM) or related modules where RFQs are part of the procurement process.
  
  Cause:
  The error arises when you attempt to archive an RFQ that is still linked to active documents or processes. Common reasons include:
  
  Open Purchase Orders: There may be purchase orders that reference the RFQ.
  Active Contracts: Contracts or agreements that are still valid and linked to the RFQ.
  Incomplete Processes: The RFQ might be part of an ongoing procurement process that has not been completed.
  Dependencies: Other documents or transactions that depend on the RFQ are still active.
  
  
  Solution:
  To resolve this issue, you need to identify and address the dependencies that are preventing the RFQ from being archived. Here are steps you can take:
  
  
  Check for Open Purchase Orders:
  
  Use transaction codes like ME2N