How To Fix OIUH902 - FI G/L Account & blocked for creation

SAP Error Message - Details

• Message type: E = Error

• Message class: OIUH - Message Class for RAZF Development

• Message number: 902

• Message text: FI G/L Account & blocked for creation

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 OIUH902 - FI G/L Account & blocked for creation ?

  The SAP error message OIUH902 indicates that a Financial General Ledger (G/L) account is blocked for creation. This typically occurs in the context of the SAP system's financial accounting module, particularly when trying to create or modify a G/L account.
  Cause:
  
  
  Blocking Status: The G/L account may be blocked for creation due to various reasons, such as:
  
  The account is marked as blocked in the system settings.
  The account is part of a chart of accounts that has restrictions.
  The user does not have the necessary authorizations to create or modify G/L accounts.
  
  
  
  Configuration Settings: There may be configuration settings in the Financial Accounting (FI) module that prevent the creation of new G/L accounts.
  
  
  User Authorizations: The user attempting to create the G/L account may lack the necessary permissions or roles assigned in the SAP system.
  
  
  Solution:
  
  
  Check Account Status:
  
  Navigate to the G/L account master data and check if the account is marked as blocked. If it is, you may need to unblock it or create a new account with a different number.
  
  
  
  Review Configuration:
  
  Check the configuration settings in the Financial Accounting module to ensure that there are no restrictions on creating new G/L accounts. This can be done through transaction codes like OX15 (for chart of accounts) or OX19 (for account groups).
  
  
  
  User Authorizations:
  
  Verify the user roles and authorizations. Ensure that the user has the necessary permissions to create G/L accounts. This can be checked through transaction SU53 (to analyze authorization issues) or by consulting with your SAP security team.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to the specific error message for any additional insights or updates that may be relevant.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance, especially if this is a recurring issue or if it affects multiple users.
  
  
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  FS00: Create/Change G/L Account Master Data
  OBD4: Define G/L Account Groups
  OX15: Maintain Chart of Accounts
  SU53: Display Authorization Check
  
  
  
  SAP Notes: Search for SAP Notes related to error OIUH902 for any patches or updates that may address the issue.
  
  
  User Training: Ensure that users are trained on the proper procedures for creating G/L accounts and understand the implications of account blocking.
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.