How To Fix FH516 - Upon saving, the G/L account is locked for posting in the prod. system

SAP Error Message - Details

• Message type: E = Error

• Message class: FH - General ledger module messages

• Message number: 516

• Message text: Upon saving, the G/L account is locked for posting in the prod. system

What causes this issue?

INCLUDE GL_ACCOUNT_MASTER_CSVC OBJECT DOKU ID TX LANGUAGE EN

System Response

When you save this change, the G/L account will be locked for posting in
the production system.
This lock is reset automatically when the business change project is
imported to the production system.

How to fix this error?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FH516 - Upon saving, the G/L account is locked for posting in the prod. system ?

  The SAP error message FH516 indicates that a General Ledger (G/L) account is locked for posting in the production system. This typically occurs when the G/L account has been set to a status that prevents further postings, which can be due to various reasons such as year-end closing, account settings, or manual locks.
  Causes of FH516 Error
  
  
  Year-End Closing: The G/L account may be locked due to the year-end closing process. This is common when the fiscal year has been closed, and no further postings are allowed in that year.
  
  
  Account Settings: The G/L account may have been configured with specific settings that restrict postings. This can include settings in the account master data that prevent postings in certain periods.
  
  
  Manual Lock: A user or administrator may have manually locked the G/L account for various reasons, such as preventing accidental postings during a reconciliation process.
  
  
  Posting Periods: The posting period may be closed for the G/L account, preventing any new entries from being made.
  
  
  Solutions to FH516 Error
  
  
  Check Account Status: Review the G/L account settings in the account master data (transaction code FS00). Ensure that the account is not set to "Blocked" for postings.
  
  
  Review Posting Periods: Check the posting period settings (transaction code OB52) to ensure that the period you are trying to post to is open. If it is closed, you may need to open it or post to a different period.
  
  
  Year-End Closing: If the fiscal year has been closed, you may need to perform a reopening of the year (if applicable) or post to the next fiscal year.
  
  
  Consult with Finance Team: If you are unsure why the account is locked, consult with your finance or accounting team. They may have insights into whether the account should be locked and the appropriate steps to take.
  
  
  Transaction Codes: Use transaction codes like FS00 (G/L Account Master Record), OB52 (Open and Close Posting Periods), and others relevant to your SAP configuration to investigate and resolve the issue.
  
  
  Related Information
  
  
  SAP Notes: Check SAP Notes for any specific guidance or patches related to the FH516 error. SAP frequently updates its documentation and may have specific notes addressing this issue.
  
  
  User Authorizations: Ensure that you have the necessary authorizations to view and modify G/L account settings. Lack of permissions can also lead to confusion regarding account status.
  
  
  Documentation: Review your organization's internal documentation regarding G/L account management and posting procedures to ensure compliance with established protocols.
  
  
  By following these steps, you should be able to identify the cause of the FH516 error and take appropriate action to resolve it.