Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now

Close

How To Fix 60397 - Account & was entered several times (Delete one entry)


SAP Error Message - Details

  • Message type: E = Error

  • Message class: 60 - Real Estate

  • Message number: 397

  • Message text: Account & was entered several times (Delete one entry)

  • Show details Hide details


  • 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 60397 - Account & was entered several times (Delete one entry) ?

    The SAP error message 60397, which states "Account & was entered several times (Delete one entry)," typically occurs when you are trying to post a transaction that involves a specific account, and that account has been entered multiple times in the same transaction. This is often seen in financial postings, such as journal entries or invoice postings.

    Cause:

    1. Duplicate Account Entries: The most common cause of this error is that the same account has been entered more than once in the line items of a transaction. For example, if you are trying to post a journal entry and you have listed the same GL account in multiple line items, SAP will trigger this error.
    2. Incorrect Data Entry: Sometimes, this can happen due to a simple data entry mistake where the user inadvertently adds the same account multiple times.
    3. Configuration Issues: In some cases, this could be related to specific configurations in the system that restrict multiple entries for the same account in a single transaction.

    Solution:

    1. Review Line Items: Go back to the transaction where the error occurred and review the line items. Look for any duplicate entries of the same account.
    2. Delete Duplicate Entries: Remove one of the duplicate entries for the account in question. Ensure that each account is only listed once in the transaction.
    3. Check for Configuration Settings: If you believe that the error is not due to duplicate entries, check with your SAP administrator or consultant to see if there are any specific configuration settings that might be causing this restriction.
    4. Test the Transaction: After making the necessary adjustments, try to post the transaction again to see if the error persists.

    Related Information:

    • Transaction Codes: This error can occur in various transaction codes related to financial postings, such as FB50 (G/L Account Document Entry), FB60 (Enter Incoming Invoices), or FB70 (Enter Outgoing Invoices).
    • SAP Notes: You can search for SAP Notes related to this error message in the SAP Support Portal for any specific patches or updates that might address this issue.
    • User Training: Ensure that users are trained on proper data entry practices to minimize the occurrence of such errors in the future.

    If the problem persists after following these steps, it may be beneficial to consult with your SAP support team or a technical consultant for further investigation.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Sign up for our Free Essentials Plan.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant