How To Fix WS271 - &1 &2 saved (account determination contained errors)

WS271 - Overview

• Message type: E = Error

• Message class: WS - Supplier Billing Document

• Message number: 271

• Message text: &1 &2 saved (account determination contained errors)

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.

WS271 - Details

• SAP Error Message:
  WS271 &1 &2 saved (account determination contained errors)
  
  Meaning / 
  Cause:
  This error occurs during the posting or saving of a document (e.g., a goods movement, invoice, or other financial document) when the system tries to determine the correct G/L account for the transaction but encounters problems. The message indicates that the document was saved, but the account determination process found errors.
  Common causes include:
  
  Missing or incorrect account determination configuration in customizing.
  The system cannot find a valid G/L account for the transaction based on the account determination rules.
  Incorrect or incomplete master data (e.g., material master, vendor master, customer master) that is used in account determination.
  Missing or incorrect valuation class or transaction key in the configuration.
  Issues with the condition records or substitution rules affecting account determination.
  In case of movement types (e.g., inventory postings), the movement type might not be properly linked to an account category reference or valuation class.
  
  
  Where it occurs:
  
  Inventory postings