How To Fix 72118 - Invalid entry for determining period

SAP Error Message - Details

• Message type: E = Error

• Message class: 72 - Message Class for Time Management Reports

• Message number: 118

• Message text: Invalid entry for determining period

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message 72118 - Invalid entry for determining period ?

  The SAP error message 72118, "Invalid entry for determining period," typically occurs in the context of financial or controlling modules when the system is unable to determine the correct period for a transaction or entry. This can happen for various reasons, including configuration issues, incorrect data entry, or missing master data.
  Causes:
  
  Incorrect Period Settings: The fiscal year variant or period settings may not be correctly configured in the system.
  Invalid Date Range: The date entered for the transaction may fall outside the defined fiscal periods.
  Missing Master Data: Required master data (like cost centers, profit centers, etc.) may be missing or incorrectly set up.
  Authorization Issues: The user may not have the necessary authorizations to post in the specified period.
  System Configuration: There may be issues with the configuration of the controlling area or company code.
  
  Solutions:
  
  
  Check Fiscal Year Variant: Ensure that the fiscal year variant is correctly set up and that the periods are open for posting.
  
  Navigate to SPRO ? Financial Accounting ? Financial Accounting Global Settings ? Fiscal Year Change to review the settings.
  
  
  
  Verify Posting Periods: Check the posting periods in the system to ensure that the period you are trying to post to is open.
  
  Use transaction code OB52 to review and adjust the open and closed periods.
  
  
  
  Review Transaction Dates: Ensure that the date of the transaction is within the valid range of the fiscal periods.
  
  Adjust the transaction date if necessary.
  
  
  
  Check Master Data: Verify that all required master data is correctly maintained and active.
  
  Use transaction codes like KS01 (Create Cost Center) or KP06 (Change Cost Center) to check the relevant master data.
  
  
  
  Authorization Check: Ensure that the user has the necessary authorizations to post in the specified period.
  
  Consult with your SAP security team to verify user roles and authorizations.
  
  
  
  Consult SAP Notes: Check for any relevant SAP Notes that may address this specific error message or provide additional guidance.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OB52 (Maintain Posting Periods), SPRO (SAP Reference IMG), and others related to financial postings.
  SAP Documentation: Review SAP Help documentation for detailed information on fiscal year variants and posting periods.
  Support: If the issue persists, consider reaching out to SAP support or your internal SAP support team for further assistance.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.