How To Fix FDC_POSTING_001224 - No authorization for company code &1

SAP Error Message - Details

• Message type: E = Error

• Message class: FDC_POSTING_001 - FI Postings

• Message number: 224

• Message text: No authorization for company code &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 FDC_POSTING_001224 - No authorization for company code &1 ?

  The SAP error message FDC_POSTING_001224 indicates that a user does not have the necessary authorization to post transactions for a specific company code. This is a common issue in SAP systems where user roles and authorizations are strictly managed to ensure compliance and security.
  Cause:
  The error typically arises due to one or more of the following reasons:
  
  Missing Authorization: The user does not have the required authorization object for the company code in question.
  Role Assignment: The user’s role does not include the necessary permissions to post transactions for that specific company code.
  Company Code Restrictions: The user may be restricted from accessing certain company codes based on their role or organizational structure.
  Profile Issues: The user profile may not be correctly configured to allow postings in the specified company code.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after the error occurs to see which authorization check failed. This will provide insight into what is missing.
  Review the authorization objects related to financial postings, such as F_BKPF_BSA (for document posting) and F_BKPF_BUK (for company code).
  
  
  
  Modify User Roles:
  
  If you have the necessary permissions, you can modify the user’s roles using transaction code PFCG. Ensure that the role assigned to the user includes the necessary authorizations for the company code in question.
  If you do not have the necessary permissions, contact your SAP security administrator to request the required authorizations.
  
  
  
  Review Company Code Settings:
  
  Ensure that the company code is correctly set up in the system and that the user is intended to have access to it.
  
  
  
  Testing:
  
  After making changes to the user roles or authorizations, have the user log out and log back in to ensure that the changes take effect.
  Attempt the transaction again to verify that the issue has been resolved.
  
  
  
  Related Information:
  
  
  Authorization Objects: Familiarize yourself with the relevant authorization objects for financial transactions in SAP. Common objects include:
  
  F_BKPF_BSA: Authorization for posting documents.
  F_BKPF_BUK: Authorization for company code.
  
  
  
  Transaction Codes:
  
  SU53: Display authorization check.
  PFCG: Role maintenance.
  SU01: User maintenance (to check user details).
  
  
  
  Documentation: Refer to SAP documentation or your organization’s internal guidelines for managing user roles and authorizations.
  
  
  If the issue persists after following these steps, it may be necessary to consult with your SAP Basis or security team for further investigation.