How To Fix PLA664 - IT 2013 : Record(s) with non zero accnu already exits in database at &1

SAP Error Message - Details

• Message type: E = Error

• Message class: PLA - Message class for Payroll LAtinamerica

• Message number: 664

• Message text: IT 2013 : Record(s) with non zero accnu already exits in database at &1

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 PLA664 - IT 2013 : Record(s) with non zero accnu already exits in database at &1 ?

  The SAP error message PLA664 IT 2013: "Record(s) with non-zero accnu already exists in database at &1" typically occurs in the context of the SAP system when dealing with accounting documents or records that are being processed in the system. This error indicates that there are existing records in the database that have a non-zero account number (accnu) for the specified entity, which is causing a conflict with the operation you are trying to perform.
  Cause:
  
  Existing Records: The primary cause of this error is that there are already existing records in the database for the specified account number that have not been cleared or processed correctly.
  Data Integrity Issues: There may be issues with data integrity, where the system is trying to create or modify records that conflict with existing data.
  Incorrect Processing: The error may arise if the system is trying to perform an operation (like posting or clearing) that is not allowed due to the presence of existing records.
  
  Solution:
  
  Check Existing Records: Investigate the database for existing records associated with the specified account number. You can use transaction codes like SE16 or SE11 to view the relevant database tables.
  Clear or Adjust Records: If you find records that are causing the conflict, you may need to clear them or adjust them as necessary. This could involve reversing transactions or making corrections to the data.
  Consult Documentation: Review SAP documentation or notes related to this error message for any specific guidance or patches that may address the issue.
  Transaction Codes: Use relevant transaction codes (like FB03 for displaying documents) to analyze the records and understand why they are causing the conflict.
  Contact Support: If you are unable to resolve the issue, consider reaching out to SAP support or your internal SAP team for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes that are relevant to financial postings, such as FB01 (Post Document), FB02 (Change Document), and FB03 (Display Document).
  Database Tables: Understand the relevant database tables that store accounting records, such as BKPF (Accounting Document Header) and BSEG (Accounting Document Segment).
  SAP Notes: Search for SAP Notes related to PLA664 for any specific fixes or recommendations provided by SAP.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.