How To Fix 3G358 - Posting period could not be determined

3G358 - Overview

• Message type: E = Error

• Message class: 3G - Payroll: International

• Message number: 358

• Message text: Posting period could not be determined

What causes this issue?

The posting period could not be determined for one of the following
reasons:
No destination could be found in the ALE distribution model for the
CompanyCode.GetPeriod method.
A system or communication error occurred when executing the function
'BAPI_COMPANYCODE_GET_PERIOD' in the target system.

Error message extract from SAP system. Copyright SAP SE.

3G358 - Details

• The SAP error message 3G358: Posting period could not be determined typically occurs when the system is unable to identify the appropriate posting period for a transaction. This can happen for various reasons, and understanding the cause is essential for resolving the issue.
  Causes:
  
  
  Closed Posting Periods: The posting period for the transaction date may be closed in the system. If the period is closed, the system will not allow postings to that period.
  
  
  Missing Configuration: The configuration for the fiscal year variant or posting periods may not be set up correctly. This includes settings in the controlling area or company code.
  
  
  Incorrect Document Date: The document date may fall outside the defined posting periods.
  
  
  Authorization Issues: The user may not have the necessary authorizations to post in the specified period.
  
  
  Period Locking: The posting period may be locked for certain users or groups, preventing them from posting in that period.
  
  
  Solutions:
  
  
  Check Posting Periods:
  
  Go to the transaction