Invalid Intersections When Using an Alternate UD1 Structure
Hi all, We have a question about invalid intersections in reports and whether it is just a presentation issue or if we need to be worried about calculations or transformation rules as well.
We have...
Ah, so the key is just the conditional rules making it inaccessible. That shouldn't be a problem.
If you don't like the pink background, you can use formatting on the column. Check the section "Cube View Formatting" in the Design and Reference Guide.
Here's a few questions to try and understand your problem a bit more...
A few screenshots showing how the structures look, how CubeViews are defined, and what the result is, might help visualize the problem.
when you say "we have now created an alternate UD1 structure", what do you mean? Did you add a new branch to the existing UD1 dimension? Did you create a different dimension and assigned it to a different scenario type/cube?
if you're in doubt about which intersections are actually stored (i.e. where calculations happen), you can use the Data Records tool in System -> Tools -> Database, or in rules you can peek into a databuffer object (use the "Log Data Buffer" snippet)
Thank you very much for the reply. Very sorry for my late response. I was away on vacation.
I have attached two images below.
The first image shows our primary UD1 structure and our alternate regional UD1 structure. We use the UD1 structure for departmental and cost center reporting. The intent of the alternate regional UD1 structure is to remove global corporate controlled expenses from the regional unit financials. We kept the numbers the same, but just added _Reg as a suffix to the original UD1s.
As an example, expenses related to global IT departmental costs are not included, so that UD1 is removed from the regional UD1 structure. So, the regional UD1 structure is identical to the primary UD1 structure with the exception of removing specific UD1s of that type.
The second image shows a Quick View of our P&L accounts in the rows and our primary UD1 and alternate UD1 in the columns. Here you can see that some items under the alternate regional UD1 structure are pink for invalid. The reason for this is that we have conditional rules that require certain accounts to have certain UD1s.
For instance, Account 62000 Gross Sales has a constraint of 65000_F Sales. However, in the alternate regional structure the UD1s have _Reg as a suffix, so the account is shown as invalid because in the alternate structure account 62000 doesn’t have that UD1.
Since the alternate UD1 structure is only used for reporting, we don’t think it should cause an issue since the data is loaded using the primary UD1 structure. However, we just want to get some reassurance of this as we roll out this new alternate reporting structure.
Ah, so the key is just the conditional rules making it inaccessible. That shouldn't be a problem.
If you don't like the pink background, you can use formatting on the column. Check the section "Cube View Formatting" in the Design and Reference Guide.
