How To Fix WS371 - & documents processed, of which & with errors (see list log)

SAP Error Message - Details

• Message type: E = Error

• Message class: WS - Supplier Billing Document

• Message number: 371

• Message text: & documents processed, of which & with errors (see list log)

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 WS371 - & documents processed, of which & with errors (see list log) ?

  Certainly! Here's a detailed explanation regarding the SAP error message WS371 and the related message about documents processed with errors:
  
  SAP Error Message: WS371
  Message Text:
  
  "Documents processed, of which & with errors (see list log)"
  
  1. Cause
  
  The message WS371 typically appears during batch input sessions, data uploads, or mass processing transactions in SAP.
  It indicates that the system has processed a number of documents (or records), but some of them encountered errors during processing.
  The placeholder "&" in the message is replaced by the actual number of documents processed and the number of documents with errors.
  The errors can be due to various reasons such as:
  
  Incorrect or missing data in the input file or batch input session.
  Validation failures in the SAP system (e.g., mandatory fields missing, incorrect data formats).
  Authorization issues.
  Business logic errors (e.g., posting to a closed period, invalid account assignments).
  Technical issues like communication errors or system inconsistencies.
  
  
  
  
  2. Solution
  
  
  Check the List Log:
  
  The message advises to "see list log." This log contains detailed information about which documents failed and why.
  
  In batch input sessions, you can display the session log via transaction SM35.
  Review the error messages for each failed document to identify the root cause.
  
  
  
  Analyze Error Details:  
  
  Look for specific error messages or codes associated with each failed document.
  Identify if errors are due to data issues, missing master data, or configuration problems.
  
  
  
  Correct the Data or Configuration:  
  
  Fix the input data errors (e.g., correct missing or invalid fields).
  Ensure all required master data exists and is valid.
  Adjust configuration or authorization if needed.
  
  
  
  Reprocess the Failed Documents:  
  
  After corrections, re-run the batch input session or data upload for the failed documents.
  Alternatively, process the documents manually if the volume is small.
  
  
  
  Prevent Future Errors:  
  
  Implement data validation checks before uploading.
  Provide clear instructions or templates for data preparation.
  Automate error handling and reporting.
  
  
  
  
  3. Related Information
  
  
  Transaction Codes:
  
  SM35 – Batch Input: Session Overview and Log Display.
  ST22 – Dump Analysis (if errors cause short dumps).
  SLG1 – Application Log (sometimes used for detailed error logs).
  
  
  
  Common Scenarios:
  
  Mass creation or change of master data (e.g., customers, vendors).
  Posting of financial documents via batch input.
  Data migration or interface processing.
  
  
  
  SAP Notes and Documentation:
  
  Check SAP Notes related to the specific transaction or module you are working with.
  Review SAP Help Portal for batch input processing and error handling.
  
  
  
  
  Summary
  
  
  
  Aspect
  Description
  
  
  
  
  Cause
  Some documents failed during batch input or mass processing due to data or system errors.
  
  
  Solution
  Review the session or processing log, identify errors, correct data/configuration, reprocess.
  
  
  Related Info
  Use SM35 to check logs, ST22 for dumps, SLG1 for application logs; ensure data validity.
  
  
  
  
  If you provide the exact context (transaction, module, or process), I can help you with more specific troubleshooting steps.