How To Fix FICA_CD058 - Posting already assigned to G/L account


SAP Error Message - Details

  • Message type: E = Error

  • Message class: FICA_CD - FI-CA: Cash Desk/Cash Journal

  • Message number: 058

  • Message text: Posting already assigned to G/L account

  • 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 FICA_CD058 - Posting already assigned to G/L account ?

    The SAP error message FICA_CD058 ("Posting already assigned to G/L account") typically occurs in the context of the Financial Contract Accounting (FICA) module when there is an attempt to post a transaction that has already been assigned to a General Ledger (G/L) account. This can happen in various scenarios, such as during the posting of payments, adjustments, or other financial transactions.

    Cause:

    1. Duplicate Posting: The most common cause is that the transaction you are trying to post has already been processed and assigned to a G/L account.
    2. Incorrect Configuration: There may be issues with the configuration of the posting rules or account determination settings in the FICA module.
    3. Data Integrity Issues: There could be inconsistencies in the database or issues with the transaction data that prevent the posting from being completed.
    4. Manual Intervention: If manual adjustments or corrections were made to the postings, it could lead to conflicts with existing entries.

    Solution:

    1. Check Existing Postings: Review the transaction history to see if the posting has already been made. You can use transaction codes like FBL1N (Vendor Line Item Display) or FBL3N (G/L Account Line Item Display) to check for existing entries.
    2. Correct the Transaction: If you find that the transaction has already been posted, you may need to reverse or adjust the original posting instead of trying to post it again.
    3. Review Configuration: Check the configuration settings in the FICA module to ensure that the account determination and posting rules are set up correctly. This may involve consulting with your SAP FI/CO configuration team.
    4. Data Consistency Check: Run data consistency checks to identify and resolve any discrepancies in the database that may be causing the issue.
    5. Consult Documentation: Refer to SAP documentation or notes related to the FICA module for any specific guidance on handling this error message.
    6. Contact SAP Support: If the issue persists and you cannot identify the cause, consider reaching out to SAP support for assistance.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as FBL1N, FBL3N, and FICA-specific transactions for managing postings.
    • SAP Notes: Search for SAP Notes related to FICA and error message FICA_CD058 for any patches or updates that may address the issue.
    • User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.

    By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


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's SAP support assistant is amazing. Saves me countless hours trying to solve complex SAP issues myself. It's a real game changer!
Rate 1
Thomas Michael
SAP Consultant, Author & Speaker