How To Fix /SCWM/WB_CORE071 - Archive file already open

/SCWM/WB_CORE071 - Overview

• Message type: E = Error

• Message class: /SCWM/WB_CORE -

• Message number: 071

• Message text: Archive file already open

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.

/SCWM/WB_CORE071 - Details

• The SAP error message /SCWM/WB_CORE071 Archive file already open typically occurs in the context of the SAP Extended Warehouse Management (EWM) module when there is an attempt to access or manipulate an archive file that is already in use or open by another process. This can happen during operations such as archiving, data retrieval, or processing of warehouse tasks.
  
  Cause:
  
  Concurrent Access: The archive file is being accessed by another user or process, which prevents your current operation from proceeding.
  Incomplete Previous Operation: A previous operation that involved the archive file may not have completed successfully, leaving the file in a locked state.
  System Configuration: There may be configuration issues or settings that lead to improper handling of archive files.
  
  
  Solution:
  
  
  Check for Active Processes: 
  
  Use transaction codes like SM50 or SM66 to check for active processes that might be using the archive file. If you find any, you may need to wait for them to