How To Fix GG352 - Ledger & cannot be posted to

SAP Error Message - Details

• Message type: E = Error

• Message class: GG - Messages for FI-SL customizing

• Message number: 352

• Message text: Ledger & cannot be posted to

What causes this issue?

The configuration settings have been defined so that posting is not
allowed to ledger &V1&.

System Response

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

How to fix this error?

If you want to post data directly to ledger &V1&, you must set the
indicator so that posting is allowed to the ledger.
<DS:TRAN.GCJU>Proceed</>

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message GG352 - Ledger & cannot be posted to ?

  The SAP error message GG352 typically indicates that there is an issue with posting to a specific ledger in the system. This error can arise due to various reasons, and understanding the cause is essential for finding a solution. Here’s a breakdown of potential causes, solutions, and related information:
  Causes of Error GG352
  
  
  Ledger Configuration: The ledger you are trying to post to may not be configured correctly in the system. This could include settings related to the fiscal year, posting periods, or ledger types.
  
  
  Posting Periods: The posting period for the ledger may be closed or not open for the transaction type you are trying to post. Each ledger can have its own posting period settings.
  
  
  Authorization Issues: The user may not have the necessary authorizations to post to the specified ledger.
  
  
  Document Type Restrictions: The document type being used for the posting may not be allowed for the specified ledger.
  
  
  Currency Issues: If the ledger is set up for a specific currency, and the transaction is in a different currency, this could lead to posting issues.
  
  
  Data Consistency: There may be inconsistencies in the data being posted, such as missing mandatory fields or incorrect account assignments.
  
  
  Solutions to Error GG352
  
  
  Check Ledger Configuration: Review the configuration of the ledger in the SAP system. Ensure that it is set up correctly for the intended transactions.
  
  
  Open Posting Periods: Verify that the posting period for the ledger is open. You can do this by navigating to the relevant transaction (e.g., OB52) and checking the posting period settings.
  
  
  Review User Authorizations: Ensure that the user has the necessary authorizations to post to the ledger. This can be checked in the user roles and profiles.
  
  
  Document Type Settings: Check if the document type being used is allowed for the ledger. You may need to adjust the settings in the document type configuration.
  
  
  Currency Compatibility: Ensure that the currency of the transaction matches the currency settings of the ledger. If necessary, convert the transaction to the appropriate currency.
  
  
  Data Validation: Review the data being posted for any inconsistencies or missing information. Ensure that all mandatory fields are filled out correctly.
  
  
  Related Information
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OB52 (for posting periods), OBA7 (for document types), and SU01 (for user authorizations).
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to error GG352. SAP Notes can provide additional insights or solutions.
  
  
  Documentation: Refer to SAP documentation or help files for detailed information on ledger configuration and posting processes.
  
  
  Support: If the issue persists, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  
  By following these steps, you should be able to identify the cause of the GG352 error and implement the appropriate solution.