SAP Knowledge Base Article - Public

3688963 - Error “Validity date conflict… release not possible” When Creating a New Version Of a Service Catalog

Symptom

When attempting to create and release a new version of a Service Catalog, the following error appears:

“Validity date conflict with catalog <ID> (Version 1) – release not possible.”

Environment

SAP Cloud for Customer for core applications

Reproducing the Issue

  1. Go to the Service Entitlements work center.
  2. Navigate to the Service Categories view.
  3. Select Catalog ABC.
  4. Create a new version, click Change Status, and choose Release.
  5. System displays error:
    "Validity date conflict with catalog XYZ (Version 1) – release not possible."

Note: ABC represents the Catalog ID being edited, and XYZ represents the other Catalog ID involved in the validity conflict.

Cause

The issue occurs due to overlapping validity periods between two different catalogs (ABC and XYZ) assigned to the same object.
SAP guidelines generally discourage modifying or deleting released versions of service catalogs, as they may already be referenced by other objects, potentially causing inconsistencies.

Resolution

To resolve the issue without deleting or altering an existing released version:

  1. Adjust the validity period of catalog ABC or the conflicting catalog XYZ to remove the overlap.
  2. For example, updating the “Valid To” date of Catalog ABC to an earlier date resolves the conflict.
  3. After correcting the validity period, the new version of Catalog ABC can be released successfully without errors.

Note :- This update needs to be performed from backend. Users may validate the results in their system and proceed with releasing the catalog version as needed.

Keywords

Service Catalog, Validity Date Conflict, Validity Period Overlap, Release not Possible, Service Entitlements, Service Categories , KBA , LOD-LE-CSM-SIC , Service Issue Category , Problem

Product

SAP Cloud for Customer core applications all versions