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

SAP Error Message - Details

• 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.

Smart SAP Assistant

• What is the cause and solution for SAP error message 3G358 - Posting period could not be determined ?

  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 code OB52 to check the posting periods for the relevant company code and fiscal year. Ensure that the period for the transaction date is open.
  
  
  
  Adjust Document Date:
  
  Verify the document date and ensure it falls within an open posting period. If necessary, change the document date to a valid period.
  
  
  
  Review Configuration:
  
  Check the configuration settings for the fiscal year variant and posting periods. Ensure that they are correctly set up in the system.
  
  
  
  User Authorizations:
  
  Ensure that the user has the necessary authorizations to post in the specified period. This can be checked with the security team or through transaction code SU53.
  
  
  
  Consult with Finance Team:
  
  If the issue persists, consult with the finance or controlling team to ensure that there are no specific restrictions or policies in place regarding posting periods.
  
  
  
  Transaction Codes:
  
  Use transaction codes like OB29 to check the fiscal year variant settings and OB37 to review the posting period settings.
  
  
  
  Related Information:
  
  Fiscal Year Variant: This defines how the fiscal year is structured, including the number of periods and special periods.
  Document Types: Different document types may have different posting period rules.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to posting periods.
  
  By following these steps, you should be able to identify the cause of the error and implement the appropriate solution. If the problem continues, it may be necessary to involve your SAP support team for further investigation.