How To Fix VY458 - Shipment cost document &1 is being writeen to a new archive

SAP Error Message - Details

• Message type: E = Error

• Message class: VY - Messages for freight processing

• Message number: 458

• Message text: Shipment cost document &1 is being writeen to a new 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 VY458 - Shipment cost document &1 is being writeen to a new archive ?

  The SAP error message VY458 indicates that a shipment cost document is being written to a new archive. This message typically arises in the context of the archiving process within SAP, particularly when dealing with shipment costs in the logistics module.
  Cause:
  
  Archiving Process: The error usually occurs when the system attempts to archive a shipment cost document that is still in use or has not been fully processed. This can happen if there are open transactions or if the document is locked by another process.
  Configuration Issues: There may be issues with the configuration of the archiving object related to shipment costs, which could prevent the document from being archived properly.
  Data Consistency: If there are inconsistencies in the data or if the document is linked to other documents that are still active, the archiving process may be interrupted.
  
  Solution:
  
  Check Document Status: Ensure that the shipment cost document is fully processed and not in use by any other transactions. You can check the status of the document in the relevant transaction codes (e.g., VL02N for delivery, or other related transactions).
  Release Locks: If the document is locked, you may need to release the lock. This can be done by identifying the user or process that has locked the document and resolving the issue.
  Review Archiving Configuration: Check the configuration settings for the archiving object related to shipment costs. Ensure that all necessary settings are correctly configured in transaction SARA.
  Run Archiving Program: If the document is ready for archiving, you can manually run the archiving program for shipment costs to see if it processes correctly.
  Consult Logs: Review the application logs (transaction SLG1) for more detailed error messages that can provide insights into why the archiving process is failing.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide patches or updates that could resolve the issue.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SARA (Archiving Administration), SARI (Archiving Information), and SLG1 (Application Log).
  Archiving Objects: Understand the archiving objects related to shipment costs, which can be found in the SAP documentation or through transaction SARA.
  SAP Support: If the issue persists, consider reaching out to SAP support for assistance, especially if it involves complex configurations or potential bugs.
  
  By following these steps, you should be able to diagnose and resolve the issue related to the VY458 error message in SAP.