Do you have any question about this error?
Message type: E = Error
Message class: ICLCUST - Checking Customizing Tables
Message number: 067
Message text: Validity range of version &1 overlaps with version &2
The validity range (valid-from date/valid-from time, and valid-to date/
valid-to time) of version &V1& overlaps with version &V2&. This is not
permitted with active versions, but both versions are currently active.
When you create a <DS:GLOS.40552E756CE2C94F9C25358499225F19>claim</>,
the system is unable to uniquely identify the
valid version.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Make changes to the claim date stating the validity period, so that
there is no longer an overlap when activation takes place.
Error message extract from SAP system. Copyright SAP SE.
ICLCUST067
- Validity range of version &1 overlaps with version &2 ?The SAP error message ICLCUST067 indicates that there is an overlap in the validity ranges of two versions of a particular configuration or master data record. This typically occurs in the context of customizing or configuration settings, such as pricing, conditions, or other data that has a defined validity period.
Cause:
The error arises when you attempt to create or modify a version of a record (e.g., a pricing condition) that has a validity range that overlaps with an existing version. For example, if you have:
In this case, Version 2 overlaps with Version 1, which triggers the error message.
To resolve this error, you need to ensure that the validity ranges of the versions do not overlap. Here are the steps you can take:
Check Existing Versions: Review the existing versions of the record in question. Identify the validity ranges of all versions.
Adjust Validity Ranges: Modify the validity range of the new version you are trying to create or adjust the existing versions to eliminate the overlap. Ensure that the validity periods are distinct and do not intersect.
Delete or Archive Old Versions: If certain versions are no longer needed, consider deleting or archiving them to avoid conflicts.
Consult Documentation: If you are unsure about the validity ranges or how to adjust them, refer to the SAP documentation or consult with your SAP administrator or functional consultant.
Testing: After making adjustments, test the changes to ensure that the error no longer occurs and that the system behaves as expected.
VK11
(Create Condition), VK12
(Change Condition), or others related to the specific module (e.g., SD, MM).By following these steps, you should be able to resolve the ICLCUST067 error and ensure that your validity ranges are correctly configured.
Get instant SAP help. Start your 7-day free trial now.
ICLCUST066
Subclaim type &1: Res.type &2 f.subro/salvage must be expectation reserve
What causes this issue? Reserve type &V2& is not flagged as being an expectation reserve.System Response The system issues an error message ...
ICLCUST065
Subclaim type &1: Subro/salvage reserve type &2 not a permitted res.type
What causes this issue? In subclaim type &V1& it is stated that reserve type &V2& is for subrogation or salvage. However, reserve typ...
ICLCUST068
Benefit type &1: Object type &2 has not been defined
What causes this issue? You want to assign object type &v2& to benefit type &v1&, but object type &v2& has not been defined.S...
ICLCUST069
Benefit type &1: No name exists for object type &2
What causes this issue? You want to assign object type &V2& to benefit type &V1& but there is no name for object type &v2& in...
Click on this link to search all SAP messages.