How To Fix EDATEX152 - Period from &1 is before generation start date &2

EDATEX152 - Overview

• Message type: E = Error

• Message class: EDATEX - Messages for Data Exchange Processes

• Message number: 152

• Message text: Period from &1 is before generation start date &2

What causes this issue?

If this error message occurs during the generation of data exchange
tasks, you can find the relevant service provider and data exchange
process in the log in the following information message:
"<(>&<)>0 tasks generated for process <(>&<)>1, ServProv(third)
<(>&<)>2, ServProv(own) <(>&<)>3" (EDATEX244)

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 due date control (<DS:TRAN.EEDMIDESERVPROV02>EEDMIDESERVPROV02
- Change</>) for the third party service provider and data exchange
process.
If necessary, set the "Generation From" date to the "Period From" date
mentioned in message EDATEX152. &V1&.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message EDATEX152 - Period from &1 is before generation start date &2 ?

  The SAP error message EDATEX152 indicates that there is an issue with the date range specified for a data extraction or reporting process. Specifically, the error states that the "Period from &1 is before generation start date &2." This means that the starting date you are trying to use for a particular operation is earlier than the date that the system has set as the beginning of the data generation or extraction process.
  
  Cause:
  
  Incorrect Date Input: The user may have entered a start date that is earlier than the allowed generation start date.
  Configuration Settings: The system may have been configured with a specific generation start date that restricts the periods that can be selected for data extraction.
  Data Availability: The data for the specified period may not have been generated or made available in the system yet.
  
  
  Solution:
  
  Check the Dates: Review the date you are trying to use (period from &1) and compare