How To Fix ICC_CL368 - Could not determine posting period


SAP Error Message - Details

  • Message type: E = Error

  • Message class: ICC_CL - Messages (Chile)

  • Message number: 368

  • Message text: Could not determine posting period

  • Show details Hide details
  • What causes this issue?

    The system could not determine the posting period.

    How to fix this error?

    Contact your system administrator.

    Procedure for System Administrators

    Check the function module DATE_TO_PERIOD_CONVERT.

    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message ICC_CL368 - Could not determine posting period ?

    The SAP error message ICC_CL368, which states "Could not determine posting period," typically occurs in the context of financial postings or transactions where the system is unable to identify the appropriate posting period for a given transaction. This can happen for various reasons, and understanding the cause is essential for resolving the issue.

    Causes:

    1. Missing or Incorrect Periods: The posting period may not be open for the specified company code or fiscal year. This can happen if the period has been closed or if the configuration does not allow postings in that period.

    2. Configuration Issues: The configuration settings for the fiscal year variant or posting periods may not be set up correctly. This includes settings in the financial accounting (FI) module.

    3. Document Type Restrictions: Certain document types may have restrictions on the posting periods they can use, leading to this error if the document type is not allowed in the current period.

    4. User Authorization: The user may not have the necessary authorizations to post in the specified period.

    5. Transaction Type: The type of transaction being processed may not be compatible with the current posting period settings.

    Solutions:

    1. Check Posting Periods: Go to the transaction code OB52 to check the open and closed posting periods for the relevant company code and fiscal year. Ensure that the period you are trying to post to is open.

    2. Review Configuration: Verify the configuration settings for the fiscal year variant in transaction code OB29. Ensure that the periods are defined correctly and that the settings align with your business requirements.

    3. Document Type Settings: Check the settings for the document type being used in transaction code OBA7. Ensure that it allows postings in the desired period.

    4. User Authorizations: Confirm 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 to analyze authorization failures.

    5. Consult with Finance Team: If the issue persists, consult with your finance team or SAP support to ensure that there are no other underlying issues affecting the posting periods.

    Related Information:

    • Transaction Codes:

      • OB52: Change Posting Periods
      • OB29: Define Fiscal Year Variant
      • OBA7: Document Type Configuration
      • SU53: Authorization Check
    • SAP Notes: Check SAP Notes related to ICC_CL368 for any specific patches or updates that may address this issue.

    • Documentation: Review SAP documentation on financial posting periods and fiscal year variants for a deeper understanding of how these elements interact.

    By following these steps, you should be able to identify the cause of the ICC_CL368 error and implement the necessary solutions to resolve it.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant