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 or ME2K to check if there are any open purchase orders linked to the RFQ.
  If there are open purchase orders, you may need to close or delete them before archiving the RFQ.
  
  
  
  Review Active Contracts:
  
  Check if there are any active contracts associated with the RFQ. You can use transaction codes like ME33K to view contract details.
  If contracts are still active, consider closing them if they are no longer needed.
  
  
  
  Analyze Related Documents:
  
  Investigate if there are any other documents (like delivery documents, invoices, etc.) that are still referencing the RFQ.
  Ensure that all related processes are completed.
  
  
  
  Use Archiving Object:
  
  If you have confirmed that there are no dependencies, you can use the archiving object for RFQs to mark them for archiving.
  Ensure that you follow the correct archiving procedures as defined in your organization.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or your organization's guidelines for archiving RFQs to ensure compliance with internal processes.
  
  
  
  Seek Help from SAP Support:
  
  If you are unable to resolve the issue, consider reaching out to SAP support or your internal SAP team for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME2N (Purchase Orders by Vendor), ME33K (Display Contract), and others that can help you analyze the RFQ's status.
  Archiving Process: Understand the archiving process in SAP, including the configuration and prerequisites for archiving RFQs.
  SAP Notes: Check for any SAP Notes related to this error message for additional insights or patches that may address the issue.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate actions to resolve it, allowing you to archive the RFQ successfully.