How To Fix RD420 - Document &1/&2 already exists (line items not posted)

SAP Error Message - Details

• Message type: E = Error

• Message class: RD - CO-PA Connection to SAP BW

• Message number: 420

• Message text: Document &1/&2 already exists (line items not posted)

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 RD420 - Document &1/&2 already exists (line items not posted) ?

  The SAP error message RD420 indicates that a document with the same reference already exists in the system, which prevents the posting of line items. This error typically occurs in the context of financial transactions, such as when trying to post invoices, payments, or other accounting documents.
  Cause:
  
  
  Duplicate Document: The most common cause is that a document with the same document number and year already exists in the system. This can happen if:
  
  The document was already posted.
  There was an attempt to post the same document again.
  A user is trying to post a document that has been created but not yet posted.
  
  
  
  Incorrect Document Numbering: If the document number is manually entered or if there is a custom numbering range that overlaps with existing documents, this can lead to conflicts.
  
  
  System Configuration: In some cases, the configuration settings for document types or number ranges may not be set up correctly, leading to issues with document uniqueness.
  
  
  Solution:
  
  
  Check Existing Documents: 
  
  Use transaction codes like FB03 (Display Document) to check if the document already exists in the system. 
  Verify the document number and fiscal year to ensure you are looking at the correct entry.
  
  
  
  Use a Different Document Number: If you are manually entering document numbers, try using a different number that does not conflict with existing documents.
  
  
  Review Document Type Configuration: 
  
  Check the configuration for the document type in transaction OBA7 (Document Types) to ensure that the number range is correctly defined and does not overlap with other document types.
  
  
  
  Consult with Your SAP Administrator: If you are unsure about the document or if the issue persists, consult with your SAP administrator or support team. They can help investigate the issue further and provide guidance on how to resolve it.
  
  
  Check for Open Items: If the document is in a status that prevents posting (e.g., it is in a holding status), ensure that any necessary actions are taken to clear or finalize those items.
  
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  FB03: Display Document
  FB02: Change Document
  FB01: Post Document
  OBA7: Document Types Configuration
  
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for specific notes in the SAP Support Portal.
  
  
  Documentation: Review SAP documentation or help files related to document posting and error handling for additional insights.
  
  
  By following these steps, you should be able to identify the cause of the RD420 error and take appropriate action to resolve it.