Crystal Reports Conversion From UNV to UNX

building reports crystal reports
,
1

Has anyone else been working on converting Crystal reports 2020 reports from using UNV universes to UNX universes?

We have started on our conversion work and have found an issue where the relationship to the UNV universe is still retained after the universe is published to Business Objects.

— Steps to Reproduce —

Start with a Crystal Reports 2020 report that uses a UNV universe as a source.

  1. Set the datasource location to point to the equivalent UNX universe.
  2. Save the repointed Crystal Report out to Business Objects Enterprise by overwriting the existing Crystal Report.
  3. Observe that the Crystal Report in Business Objects is still referencing the UNV universe as well as the UNX universe by looking at the report properties and the default universe.

We opened a case with SAP on this on 2025-12-16T06:00:00Z but after three different support people I’m not sure we have anyone that understands what the issue is.

I found 3280081 - Webi report associated with both unv and unx after promotion (:locked_with_key: SAP site login required) and implemented the fix but it does not appear to have any effect on Crystal Reports. As a side note, we have not encountered the issue from this KBA with our Web Intelligence reports as of yet but we are using APOS Web Intelligence Migrator to convert our Web Intelligence reports and that may have some impact.

2

Just curious - if the unv is removed from the CMS (or not visible to the active user), do you get an error or does it switch to the unx? I seem to remember this happening a while back with WebI, and it had to do with the various ways that the report engine tries to find the universe to use (CUID, universe ID, universe short name, etc.).

3

Yes, we have found that if you delete the UNV universe and then run the Refresh Options on the Crystal Report in the CMC, the reference to the UNV universe will be removed. Not ideal but it appears to be workable. The UNV universe can even be restored from the recycle bin and the reference will remain removed.

We’ll see if SAP replies with this as the “Proposed Solution” to my open case now that I have posted this work around in public.

4

Glad you found a workaround, but I agree that’s not ideal and I wouldn’t accept it as a “solution”.