cancel
Showing results for 
Search instead for 
Did you mean: 

Universe migration issue from UNV to UNX in BO 4.1

Former Member
0 Kudos

Dear all,

We have converted 1 universe from UNV to UNX.After converting we are facing the context error.we have 5 context in universe but out of 5,two context is getting error.But the same is fine in UDT.

Error:

The Context"Context name" in data foundation "Universe name" contains an excluded join that generates a cartisian product error.

Please help to resolve the issue.

Thanks in advance

Regards,,

Manjunath.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Every one,

One join is missed in each context ,we have identified that join and included in context.

Issue has been resolved

Thanks,

M.Manjuanth

Answers (1)

Answers (1)

denis_konovalov
Active Contributor
0 Kudos

This is not migration, this is conversion issue.
You have couple options :
1. Fix context in question manually in UNX universe (or fix the joint in original)

2. Continue using original UNV universe and create new UNX universe for new developments, then slowly phase out original UNV and reports based on it.

There is really no good business case for converting UNV's into UNX's as UNV's are fully supported for considerable future.
And if you do convert - you still have to manually switch all the reports or the original will still be in use by them.

Former Member
0 Kudos

Thank you Denis.

We have verified all the joins which are included in the context as in .UNV file. Even in .UNX file the joins in the Context remains same as in .UNV file. But we are getting this error only in .UNX but not in .UNV. Please advice.

Customer requires the .UNX file only, keeping in mind that SAP might retire .UNV in future.