How To Fix FICO1047 - Data overlap: valid to date of previous period was deleted

SAP Error Message - Details

• Message type: E = Error

• Message class: FICO1 -

• Message number: 047

• Message text: Data overlap: valid to date of previous period was deleted

What causes this issue?

The dates entered for the validity period overlap with the validity
dates of another period for this condition.
You entered a <LS>valid-from date</> that is before the <LS>valid-to
date</> of the previous period.

System Response

The system deletes the <LS>valid-to date</> of the previous period. As a
result, the period is implicitly limited by the <LS>valid-from date</>
of the current period, which means that the previous period is valid up
to the <LS>valid-from date</> of the current period minus one calendar
day.

How to fix this error?

If you do not want the system to delete the <LS>valid-to date</> of the
previous period, switch to the previous period and enter a <LS>valid-to
date</> that is before the <LS>valid-from date</> of the current period.

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 FICO1047 - Data overlap: valid to date of previous period was deleted ?

  The SAP error message FICO1047, which states "Data overlap: valid to date of previous period was deleted," typically occurs in the context of financial accounting (FI) and controlling (CO) modules when there is an inconsistency in the date ranges of master data or transaction data. This error indicates that there is a conflict with the validity periods of certain data entries, often related to periods that have already been closed or posted.
  Cause:
  
  
  Data Overlap: The error usually arises when you attempt to change or delete a record that has a validity period that overlaps with another record. For example, if you have a record that is valid until a certain date, and you try to delete or modify it, the system detects that this action would create an inconsistency in the data.
  
  
  Period Closing: If a financial period has been closed and you attempt to make changes to data that affects that period, it can trigger this error. This is common when trying to adjust master data or transaction data that has already been posted.
  
  
  Incorrect Configuration: Sometimes, the configuration settings for the validity periods in the system may not be set correctly, leading to overlaps.
  
  
  Solution:
  
  
  Check Validity Periods: Review the validity periods of the records involved. Ensure that there are no overlaps and that the records are correctly configured. You may need to adjust the validity dates to resolve the conflict.
  
  
  Avoid Changes in Closed Periods: If the error is due to trying to modify data in a closed period, consider whether the change is necessary. If it is, you may need to reopen the period (if your business processes allow for this) or make the necessary adjustments in the next open period.
  
  
  Data Consistency Check: Run a consistency check on the relevant data. This can help identify any discrepancies or issues that need to be resolved.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to this error message for specific guidance and troubleshooting steps.
  
  
  Contact SAP Support: If the issue persists and you cannot find a resolution, consider reaching out to SAP support for assistance. They can provide more detailed insights based on your specific system configuration and data.
  
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like SE11 (Data Dictionary) or SE16 (Data Browser) to check the underlying tables and data related to the error.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide additional troubleshooting steps.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the cause of the FICO1047 error and implement a suitable solution.