How To Fix FCLM_MEMO_RECORD029 - You are not authorized to create memo records in company code &1.

SAP Error Message - Details

• Message type: E = Error

• Message class: FCLM_MEMO_RECORD -

• Message number: 029

• Message text: You are not authorized to create memo records in 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 FCLM_MEMO_RECORD029 - You are not authorized to create memo records in company code &1. ?

  The SAP error message FCLM_MEMO_RECORD029 indicates that a user is attempting to create memo records in a specific company code but does not have the necessary authorization to do so. This error typically arises in the context of SAP Financial Closing cockpit or similar financial applications where memo records are used for various financial processes.
  Cause:
  The primary cause of this error is a lack of appropriate authorization for the user in the specified company code. This can happen due to:
  
  Missing Authorization Roles: The user may not have been assigned the correct roles that include the necessary permissions to create memo records.
  Company Code Restrictions: The user may have access to other company codes but not to the one specified in the error message.
  Authorization Object Issues: The relevant authorization objects (e.g., F_LFA1_AKT for vendor master data) may not be properly configured for the user.
  
  Solution:
  To resolve this issue, 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 specific authorization is missing.
  Alternatively, you can use transaction SU01 to review the user's roles and authorizations.
  
  
  
  Assign Necessary Roles:
  
  If the user lacks the necessary roles, work with your SAP security team to assign the appropriate roles that include permissions for creating memo records in the specified company code.
  
  
  
  Review Authorization Objects:
  
  Ensure that the relevant authorization objects are correctly configured. For memo records, you may need to check objects related to financial transactions and memo record creation.
  
  
  
  Test the Changes:
  
  After making changes to the user’s roles or authorizations, have the user log out and log back in to test if the issue is resolved.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or your organization’s internal guidelines for specific authorization requirements related to memo records.
  
  
  
  Related Information:
  
  
  Transaction Codes: 
  
  SU53: Display Authorization Check
  SU01: User Maintenance
  PFCG: Role Maintenance (to manage roles and authorizations)
  
  
  
  Authorization Objects: 
  
  Familiarize yourself with the relevant authorization objects that control access to financial transactions and memo records.
  
  
  
  SAP Notes: 
  
  Check for any SAP Notes related to this error message for additional guidance or known issues.
  
  
  
  If the problem persists after following these steps, it may be necessary to engage with your SAP Basis or security team for further investigation.