Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now

Close

How To Fix GI150 - Error in period determination (Ld &, CoCd & )


SAP Error Message - Details

  • Message type: E = Error

  • Message class: GI - FI-SL update

  • Message number: 150

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

  • Show details Hide details
  • What causes this issue?

    The system could not determine a period for ledger &V1& and company
    code &V2&.

    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?

    Please check the period definition for this combination.

    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

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

    The SAP error message GI150, which states "Error in period determination (Ld &, CoCd &)," typically occurs during the posting of goods movements or inventory transactions. This error indicates that the system is unable to determine the appropriate posting period for the transaction in question. Here are the common causes, solutions, and related information for this error:

    Causes:

    1. Closed Posting Periods: The most common cause is that the posting period for the company code (CoCd) is closed. If the period is closed, the system will not allow postings to that period.

    2. Incorrect Configuration: There may be issues with the configuration of the fiscal year variant or the posting periods in the controlling (CO) or logistics (MM) modules.

    3. Missing Periods: The required posting periods may not be defined in the system for the fiscal year in question.

    4. Authorization Issues: Sometimes, the user may not have the necessary authorizations to post in the specified period.

    5. Document Type Restrictions: Certain document types may have restrictions on posting periods.

    Solutions:

    1. 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 you are trying to post to is open.
    2. Adjust Periods:

      • If the period is closed and you need to post to it, you can temporarily open the period in OB52. However, be cautious with this approach, as it may affect financial reporting.
    3. Review Configuration:

      • Check the configuration settings for the fiscal year variant in OB29 and ensure that the periods are correctly defined.
    4. User Authorizations:

      • Verify that the user has the necessary authorizations to post in the specified period. This can be checked in transaction SU53 after the error occurs.
    5. Document Type Settings:

      • Review the settings for the document type being used to ensure there are no restrictions on posting periods.
    6. Consult with Finance Team:

      • If you are unsure about making changes to posting periods or configurations, consult with your finance or controlling team to ensure compliance with accounting policies.

    Related Information:

    • Transaction Codes:

      • OB52: Change Posting Periods
      • OB29: Define Fiscal Year Variant
      • SU53: Display Authorization Check
    • SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message.

    • Documentation: Review SAP documentation related to period control and fiscal year settings for more detailed guidance.

    By following these steps, you should be able to identify the cause of the GI150 error and implement the appropriate solution.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Sign up for our Free Essentials Plan.


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