Forum Discussion

neilbkc's avatar
neilbkc
New Contributor
3 days ago
Solved

Mid-year base entities to new parent

Mid-year we created a new parent entity and added base entity relationships to it because the base entities moved to a different legal entity. We load YTD trial balance and the previous parent should...
Cube View
Reports
  • rhankey's avatar
    rhankey
    3 days ago

    On the Entity dim, I would normally use Relationship PercentConsolidation=0 or 100% in place of the InUse=False or True property.

    If I understand correctly, you have a base entity that is to "appear" under one parent for the first half of the year and "appear" under a second parent for the second half of the year.  If using the same base entity, that base entity's month 6-12 still needs to hold the true YTD values from M1 irrespective of whether it moved parents or not.  You would need to manually post an elimination entry or write elimination or share logic that reverses the YTD M6 data as it rolls up to the new parent so that the old parent sees the YTD M6 data through to the end of the year, and the new parent only sees the effect of what occurs from M7 (subtracting out YTD M6) onward.  At a base entity level, you'll still see all 12 months of YTD data - as it is the same entity rolling up to two different parents.  But the parents only aggregate what belongs to them.

    The other option is to create a new base level entity for when it needs to move to a different parent, and journal move what you want from the old base entity to the new base entity.  If this is a one-of situation, this might be easier to understand and implement.  If this could be a recurring need, the other option is the better choice.

rhankey's avatar
rhankey
Contributor II
3 days ago

On the Entity dim, I would normally use Relationship PercentConsolidation=0 or 100% in place of the InUse=False or True property.

If I understand correctly, you have a base entity that is to "appear" under one parent for the first half of the year and "appear" under a second parent for the second half of the year.  If using the same base entity, that base entity's month 6-12 still needs to hold the true YTD values from M1 irrespective of whether it moved parents or not.  You would need to manually post an elimination entry or write elimination or share logic that reverses the YTD M6 data as it rolls up to the new parent so that the old parent sees the YTD M6 data through to the end of the year, and the new parent only sees the effect of what occurs from M7 (subtracting out YTD M6) onward.  At a base entity level, you'll still see all 12 months of YTD data - as it is the same entity rolling up to two different parents.  But the parents only aggregate what belongs to them.

The other option is to create a new base level entity for when it needs to move to a different parent, and journal move what you want from the old base entity to the new base entity.  If this is a one-of situation, this might be easier to understand and implement.  If this could be a recurring need, the other option is the better choice.