How To Fix VW698 - Shipment &1 read from the archive

VW698 - Overview

• Message type: E = Error

• Message class: VW - Shipment Processing Output

• Message number: 698

• Message text: Shipment &1 read from the archive

What causes this issue?

Shipment &V1& is no longer available in the database and was retrieved
from the <DS:GLOS.11B6DBF51F59D4119B540060B0671ACC>archive</>.

System Response

The archived document can only be displayed but not changed.

How to fix this error?

Note that the system uses the current
<DS:GLOS.3526AFFEAFAB52B9E10000009B38F974>Customizing</> settings and
current master data to display from the archive. It is therefore
possible that the document is displayed differently to when it was
archived.
Display of the <DS:GLOS.3526C7CEAFAB52B9E10000009B38F974>document flow
</> is not supported for archived documents. To display the connection
between the current shipment and preceding/subsequent documents, use the
relationship browser, which you can call from the Environment menu.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message VW698 - Shipment &1 read from the archive ?

  The SAP error message VW698, which states "Shipment &1 read from the archive," typically occurs when the system attempts to access shipment data that has been archived. This can happen in various scenarios, such as when trying to display or process a shipment that is no longer stored in the active database but has been moved to an archive for storage efficiency.
  
  Cause:
  
  Archived Data: The shipment data you are trying to access has been archived, meaning it is no longer available in the active database.
  Accessing Archived Data: The system is configured to read from the archive, but the necessary permissions or configurations may not be set up correctly.
  Missing Archive Information: The archive file may not be available, or the archive information may not be correctly configured in the system.
  
  
  Solution:
  
  Check Archive Settings: Ensure that the archive settings in your SAP system are correctly configured. You may need to check the archive object