How To Fix AJ355 - Simulated billing documents were invoiced

SAP Error Message - Details

• Message type: E = Error

• Message class: AJ - Billing program

• Message number: 355

• Message text: Simulated billing documents were invoiced

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 AJ355 - Simulated billing documents were invoiced ?

  The SAP error message AJ355, which states "Simulated billing documents were invoiced," typically occurs in the context of billing and invoicing processes within the SAP system. This message indicates that there are billing documents that were created in a simulated mode but have already been processed as actual invoices. Here’s a breakdown of the cause, potential solutions, and related information:
  
  Cause:
  
  Simulated Billing Document: The error arises when a billing document that was created in a simulated state (for testing or review purposes) has been mistakenly processed as an actual invoice.
  Inconsistent Data: There may be inconsistencies in the billing data, where the system is trying to process a document that should not be invoiced.
  User Error: A user may have inadvertently executed a transaction that led to the simulation being treated as a real billing document.
  
  
  Solution:
  
  Check Billing Document Status: Verify the status of the billing documents in question. You can do this by