How To Fix EEDMSET223 - Generation ignores times that are different 00:00:00 and 23:59:59

SAP Error Message - Details

• Message type: E = Error

• Message class: EEDMSET - Messages for Settlement

• Message number: 223

• Message text: Generation ignores times that are different 00:00:00 and 23:59:59

What causes this issue?

You want to create a settlement unit with a validity period that does
not have a from-time or to-time of 00:00:00 or 23:59:59 respectively.
This is not necessary as the allocation of points of delivery to the
settlment unit can only take place to-the-day. Therefore, times of the
day are ignored during generation of the settlement units (transaction
EEDM_SETTLUNIT_GEN).

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

However, settlement still handles a day offset (such as a gas day)
correctly. For example, if the allocation of a point of delivery to a
settlement unit is only valid until June 30, 2010, settlement would
still take place correctly until July 1, 2010 at 05:59:59.

System Response

This message is for information only.

How to fix this error?

No further action is necessary.

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 EEDMSET223 - Generation ignores times that are different 00:00:00 and 23:59:59 ?

  The SAP error message EEDMSET223, which states "Generation ignores times that are different 00:00:00 and 23:59:59," typically occurs in the context of data extraction or report generation where time intervals are being processed. This error indicates that the system is ignoring certain time values because they are considered to be equivalent in the context of the operation being performed.
  Cause:
  
  Time Interval Handling: The error arises when the system encounters a time range that includes both the start of the day (00:00:00) and the end of the day (23:59:59). In many systems, these two times are treated as equivalent for the purpose of data extraction or reporting, leading to the message that the generation process is ignoring these times.
  Configuration Settings: There may be specific settings in the configuration of the data extraction or reporting tool that dictate how time intervals are handled, which could lead to this error if not set correctly.
  Data Overlap: If the data being processed has overlapping time intervals that include both of these times, the system may not know how to handle them properly.
  
  Solution:
  
  Adjust Time Intervals: Modify the time intervals in your query or report to avoid using both 00:00:00 and 23:59:59. Instead, consider using a more precise time range that does not include both extremes.
  Check Configuration: Review the configuration settings for the data extraction or reporting tool to ensure that they are set up to handle time intervals correctly. This may involve consulting with your SAP administrator or reviewing documentation.
  Use Alternative Time Values: If possible, use alternative time values that do not trigger this error. For example, you might use 00:00:01 for the start of the day and 23:59:58 for the end of the day.
  Consult SAP Notes: Check the SAP Support Portal for any relevant notes or updates regarding this error message. There may be patches or updates that address this issue.
  
  Related Information:
  
  SAP Documentation: Refer to the official SAP documentation for the specific module you are working with, as it may provide insights into how time intervals are handled.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered this error and what solutions they have found.
  Testing: If you are in a development or testing environment, try replicating the issue with different time intervals to better understand the conditions that lead to the error.
  
  By addressing the time interval handling and ensuring that your configurations are correct, you should be able to resolve the EEDMSET223 error.