How To Fix FAC_ACC_DET_MESSAGE029 - Account &2 is blocked for planning in chart of accounts &1.

SAP Error Message - Details

• Message type: E = Error

• Message class: FAC_ACC_DET_MESSAGE - Message for account determination

• Message number: 029

• Message text: Account &2 is blocked for planning in chart of accounts &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 FAC_ACC_DET_MESSAGE029 - Account &2 is blocked for planning in chart of accounts &1. ?

  The SAP error message FAC_ACC_DET_MESSAGE029 indicates that a specific account (denoted as &2) is blocked for planning in the specified chart of accounts (denoted as &1). This typically occurs in the context of financial planning or budgeting processes within SAP, particularly in modules like SAP Controlling (CO) or SAP Financial Accounting (FI).
  Cause:
  
  
  Account Blocking: The account in question has been marked as blocked for planning. This could be due to various reasons, such as:
  
  The account is not intended for planning purposes.
  The account is set to be inactive or blocked in the configuration settings.
  The account is part of a closed fiscal year or period.
  
  
  
  Configuration Settings: The chart of accounts may have specific settings that restrict certain accounts from being used in planning scenarios.
  
  
  User Permissions: The user may not have the necessary permissions to access or modify the planning data for that account.
  
  
  Solution:
  
  
  Check Account Status:
  
  Navigate to the account master data in SAP and check if the account is indeed blocked for planning. You can do this by using transaction codes like FS00 (for account master data) or OB52 (for fiscal year variant).
  
  
  
  Modify Account Settings:
  
  If the account should be available for planning, you may need to change its status. This can be done by editing the account master data and ensuring that the planning block is removed.
  
  
  
  Review Chart of Accounts Configuration:
  
  Check the configuration of the chart of accounts to ensure that the account is allowed for planning. This may involve consulting with your SAP configuration team or reviewing the settings in transaction OBY6 (for chart of accounts).
  
  
  
  User Permissions:
  
  Ensure that the user has the necessary authorizations to access and modify planning data. This may involve checking user roles and authorizations in transaction SU01.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or consult with your SAP support team for any specific guidelines related to planning and account management.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  FS00: Display/Change G/L Account Master Data
  OB52: Maintain Fiscal Year Variants
  OBY6: Define Chart of Accounts
  SU01: User Maintenance
  
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  
  By following these steps, you should be able to identify the cause of the error and implement the necessary changes to resolve it.