How To Fix 65117 - Effective from date of the condition is before the issue start

SAP Error Message - Details

• Message type: E = Error

• Message class: 65 - Securities class data

• Message number: 117

• Message text: Effective from date of the condition is before the issue start

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 65117 - Effective from date of the condition is before the issue start ?

  The SAP error message 65117, which states "Effective from date of the condition is before the issue start," typically occurs in the context of pricing conditions or other time-dependent data in SAP. This error indicates that there is a mismatch between the effective date of a condition record and the date on which the transaction or document is being processed.
  Cause:
  
  Date Mismatch: The effective date of the condition record (e.g., pricing, discounts) is set to a date that is earlier than the date of the transaction or document being processed.
  Incorrect Configuration: The condition records may not be configured correctly, leading to the effective date being set incorrectly.
  Data Entry Errors: Manual entry errors when creating or updating condition records can lead to incorrect effective dates.
  
  Solution:
  
  
  Check Condition Records:
  
  Go to the relevant transaction (e.g., VK13 for pricing conditions) and check the effective dates of the condition records.
  Ensure that the effective date is set to a date that is on or before the date of the transaction.
  
  
  
  Update Condition Records:
  
  If the effective date is incorrect, update the condition record to reflect the correct effective date that aligns with the transaction date.
  
  
  
  Review Transaction Dates:
  
  Verify the date of the transaction or document being processed. Ensure that it is correct and aligns with the intended business process.
  
  
  
  Consult Documentation:
  
  Review any relevant documentation or configuration guides to ensure that the condition records are set up correctly.
  
  
  
  Testing:
  
  After making changes, test the transaction again to ensure that the error is resolved.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VK11 (Create Condition), VK12 (Change Condition), and VK13 (Display Condition) for managing pricing conditions.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  User Roles and Authorizations: Ensure that the user has the necessary authorizations to view and modify condition records.
  Consult with SAP Support: If the issue persists, consider reaching out to SAP support for further assistance.
  
  By following these steps, you should be able to resolve the error message 65117 and ensure that your condition records are correctly aligned with your transaction dates.