How To Fix GI170 - Error in period determination (Ld &, CoID & )


SAP Error Message - Details

  • Message type: E = Error

  • Message class: GI - FI-SL update

  • Message number: 170

  • Message text: Error in period determination (Ld &, CoID & )

  • Show details Hide details
  • What causes this issue?

    The system could not define a posting period with this posting date.

    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?

    Check the posting period definition (T009A/T009B).

    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message GI170 - Error in period determination (Ld &, CoID & ) ?

    The SAP error message GI170, which states "Error in period determination (Ld &, CoID &)," typically occurs during the process of determining the posting period for a transaction in SAP. This error can arise in various modules, including Logistics and Controlling, and is often related to configuration issues or missing data.

    Causes of GI170 Error

    1. Incorrect Period Settings: The posting period may not be open for the specified company code or ledger. This can happen if the period is closed in the financial settings.

    2. Missing Configuration: The configuration for the fiscal year variant or the posting periods may not be set up correctly in the system.

    3. Invalid Ledger: The ledger specified in the transaction may not be valid or may not have the correct settings.

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

    5. Data Inconsistencies: There may be inconsistencies in the master data or transaction data that prevent the system from determining the correct period.

    Solutions to GI170 Error

    1. Check Posting Periods:

      • Go to the transaction code OB52 to check the open and closed posting periods for the relevant company code and ledger. Ensure that the period you are trying to post to is open.
    2. Review Fiscal Year Variant:

      • Check the fiscal year variant settings in transaction code OB29. Ensure that the fiscal year variant is correctly assigned to the company code and that the periods are defined properly.
    3. Validate Ledger Settings:

      • Ensure that the ledger specified in the transaction is correctly configured. You can check this in the configuration settings for the ledger.
    4. User Authorizations:

      • Verify that the user has the necessary authorizations to post in the specified period and ledger. This can be checked in transaction code SU53 after the error occurs.
    5. Check Master Data:

      • Review the master data related to the transaction to ensure there are no inconsistencies or missing information that could affect period determination.
    6. Consult SAP Notes:

      • Search for relevant SAP Notes in the SAP Support Portal that may address specific issues related to the GI170 error.

    Related Information

    • Transaction Codes:

      • OB52: Maintain Posting Periods
      • OB29: Maintain Fiscal Year Variant
      • SU53: Display Authorization Check
    • SAP Documentation: Refer to the official SAP documentation for detailed information on period determination and configuration settings.

    • SAP Community: Engage with the SAP Community forums for insights and solutions from other users who may have encountered similar issues.

    By following these steps, you should be able to identify the cause of the GI170 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