How To Fix /SCMTMS/FAG_MSG748 - RFQ &1 version &3 is in status &2; cannot archive

/SCMTMS/FAG_MSG748 - Overview

• Message type: E = Error

• Message class: /SCMTMS/FAG_MSG -

• Message number: 748

• Message text: RFQ &1 version &3 is in status &2; cannot archive

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_MSG748 - RFQ &1 version &3 is in status &2; cannot archive ?

  The SAP error message /SCMTMS/FAG_MSG748 indicates that a Request for Quotation (RFQ) in the Transportation Management System (TMS) is in a status that prevents it from being archived. The message typically includes placeholders for the RFQ number (&1), version number (&3), and the current status (&2).
  
  Cause:
  The error occurs because the RFQ is not in a status that allows for archiving. Common statuses that may prevent archiving include:
  
  Open
  In Process
  Completed
  Canceled
  Any other status that is not marked as "archivable"
  
  
  Solution:
  To resolve this issue, you need to change the status of the RFQ to one that allows for archiving. Here are the steps you can take:
  
  
  Check the Status: Identify the current status of the RFQ by using the transaction code related to RFQs in TMS (e.g., /SCMTMS/RFQ).
  
  
  Change the Status: If the RFQ is in a status that can be changed, update it to a status that allows archiving. This may involve:
  
  Completing any outstanding processes related