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

Close

How To Fix /PRA/ACCOUNTING102 - FI G/L account & blocked for posting


SAP Error Message - Details

  • Message type: E = Error

  • Message class: /PRA/ACCOUNTING -

  • Message number: 102

  • Message text: FI G/L account & blocked for posting

  • 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 /PRA/ACCOUNTING102 - FI G/L account & blocked for posting ?

    The SAP error message /PRA/ACCOUNTING102 indicates that a General Ledger (G/L) account is blocked for posting. This can occur for various reasons, and understanding the cause is essential for resolving the issue. Here’s a breakdown of the potential causes, solutions, and related information:

    Causes:

    1. Account Blocked for Posting: The G/L account may have been explicitly blocked for posting in the account settings.
    2. Account Type Restrictions: The account may be set up in such a way that it does not allow postings for certain types of transactions (e.g., only allowing certain document types).
    3. Period Closing: The posting period may be closed, preventing any further postings to that account.
    4. Company Code Settings: The company code settings may restrict postings to certain accounts.
    5. User Authorizations: The user may not have the necessary authorizations to post to that specific G/L account.

    Solutions:

    1. Check Account Settings:

      • Go to the G/L account master data (transaction code FS00).
      • Check the "Control Data" tab to see if the account is marked as blocked for posting. If it is, you can remove the block if appropriate.
    2. Review Posting Periods:

      • Check the posting period settings (transaction code OB52) to ensure that the period is open for posting. If the period is closed, you may need to open it or post in a different period.
    3. Verify Company Code Settings:

      • Ensure that the company code settings allow postings to the G/L account in question. This can be checked in the configuration settings.
    4. Check User Authorizations:

      • Ensure that the user has the necessary authorizations to post to the G/L account. This can be checked with the security team or by reviewing the user roles and authorizations.
    5. Consult with Finance Team:

      • If the account is intentionally blocked for business reasons, consult with the finance team to understand the implications of unblocking the account.

    Related Information:

    • Transaction Codes:

      • FS00: G/L Account Master Data
      • OB52: Open and Close Posting Periods
      • SU01: User Maintenance (to check user authorizations)
    • Documentation: Refer to SAP Help documentation for detailed information on G/L account management and posting periods.

    • Support: If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting SAP Notes for any known issues related to this error message.

    By following these steps, you should be able to identify the cause of the error and implement the appropriate solution.

    • 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