How To Fix FMGL103 - You do not have authorization &1 to post in period &2/&3

SAP Error Message - Details

• Message type: E = Error

• Message class: FMGL - New General Ledger for Public Sector

• Message number: 103

• Message text: You do not have authorization &1 to post in period &2/&3

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 FMGL103 - You do not have authorization &1 to post in period &2/&3 ?

  The SAP error message FMGL103 indicates that a user does not have the necessary authorization to post in a specific financial period. This error typically arises in the context of financial transactions, such as posting journal entries or other financial documents.
  Cause:
  
  Authorization Issues: The user lacks the required authorization object to post in the specified period. This could be due to missing roles or authorizations assigned to the user profile.
  Period Locking: The financial period may be closed or locked for posting, which is a common practice to prevent changes to finalized periods.
  Company Code Settings: The settings for the company code may restrict postings to certain periods based on the fiscal year variant or other configurations.
  
  Solution:
  
  
  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.
  Review the user’s roles and authorizations in transaction PFCG. Ensure that the user has the necessary authorizations for the relevant authorization objects (e.g., F_BKPF_BES for posting in financial accounting).
  
  
  
  Review Period Status:
  
  Check if the period is open for posting. You can do this in transaction OB52 (Maintain Posting Periods). Ensure that the period you are trying to post to is open for the relevant company code and fiscal year.
  If the period is closed, you may need to open it temporarily (if allowed) or consult with your finance team to determine if the posting can be made in a different period.
  
  
  
  Consult with Finance Team:
  
  If the posting period is intentionally closed, discuss with the finance team to understand the policy regarding period closures and whether an exception can be made.
  
  
  
  Adjust Company Code Settings:
  
  If necessary, review the company code settings in transaction OBY6 to ensure that the fiscal year variant and posting period settings align with your posting requirements.
  
  
  
  Related Information:
  
  
  Authorization Objects: Familiarize yourself with the relevant authorization objects for financial postings, such as:
  
  F_BKPF_BES: Authorization for posting in financial accounting.
  F_BKPF_AKT: Authorization for document types.
  
  
  
  Transaction Codes:
  
  SU53: Display authorization check.
  PFCG: Role maintenance.
  OB52: Maintain posting periods.
  OBY6: Company code settings.
  
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to authorization or posting periods.
  
  
  By following these steps, you should be able to identify the cause of the FMGL103 error and take appropriate action to resolve it.