How To Fix /SCMTMS/FAG_MSG795 - Not all carrier RFQs can be marked for archiving; cannot archive


SAP Error Message - Details

  • Message type: E = Error

  • Message class: /SCMTMS/FAG_MSG -

  • Message number: 795

  • Message text: Not all carrier RFQs can be marked for archiving; cannot archive

  • Show details Hide details


  • 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_MSG795 - Not all carrier RFQs can be marked for archiving; cannot archive ?

    The SAP error message /SCMTMS/FAG_MSG795 indicates that not all carrier Request for Quotations (RFQs) can be marked for archiving, which means that there are certain conditions or data inconsistencies preventing the archiving process from completing successfully.

    Cause:

    1. Incomplete Data: Some RFQs may have incomplete or inconsistent data that prevents them from being archived.
    2. Active References: There may be active references or dependencies related to the RFQs that need to be resolved before archiving.
    3. Status Issues: The RFQs may be in a status that does not allow them to be archived (e.g., they are still open or in use).
    4. Authorization Issues: The user may not have the necessary authorizations to mark certain RFQs for archiving.
    5. Custom Logic: There may be custom logic or enhancements in place that affect the archiving process.

    Solution:

    1. Check RFQ Status: Review the status of the RFQs that are not being marked for archiving. Ensure that they are closed or completed.
    2. Data Consistency: Verify that all required fields in the RFQs are filled out correctly and that there are no inconsistencies in the data.
    3. Resolve Dependencies: Identify and resolve any active references or dependencies related to the RFQs. This may involve checking for linked documents or processes that need to be completed.
    4. Authorization Check: Ensure that the user attempting to archive the RFQs has the necessary authorizations to perform the archiving action.
    5. Use Archiving Object: Make sure you are using the correct archiving object and that the configuration for archiving is set up properly in the system.
    6. Consult Logs: Check the application logs for more detailed error messages or warnings that can provide additional context on why the archiving is failing.
    7. SAP Notes: Look for relevant SAP Notes that may address this specific error message or provide guidance on archiving RFQs in your version of SAP.

    Related Information:

    • Archiving Process: Familiarize yourself with the archiving process in SAP, including the necessary steps and prerequisites for archiving RFQs.
    • Transaction Codes: Use transaction codes like SARA (Archive Administration) to manage archiving objects and monitor the archiving process.
    • Documentation: Refer to SAP documentation or help guides related to the Transportation Management System (TMS) and archiving processes for more detailed instructions and best practices.

    If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or functional team for further investigation or to reach out to SAP support for assistance.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo's SAP support assistant is amazing. Saves me countless hours trying to solve complex SAP issues myself. It's a real game changer!
Rate 1
Thomas Michael
SAP Consultant, Author & Speaker