Using a Consolidation Group in 2 different hierarchies - pitfalls?

[Former Member]

Hi,

A consolidation group G100 can be assigned to two hierarchies. H1 and H2.

In General

Are there any pitfalls to watch out for?

Specifically

COI / PL30:

What happens when running PL30 tasks for H1 then H2?

Will it overwrite the G100 a PL30 posting from the H1 consolidation run or leave them?

List Of Total Records:

When running a report with logic = none,

we will see only 1 PL30 records for G100

When running a report with logic = standard

Hierarchy = H1

We will see the same PL30 record for G100

When running a report with logic = standard

Hierarchy = H2

We will see the same PL30 record for G100

BI Reporting

Upon load to BI, only 1 record will be loaded

Other

Anything else to consider?

[Former Member · Accepted solution]

Hi Monty, I hope all is well.

Because COI is executed separately for each hierarchy, when the hierarchies are completely independent - no shared cons groups, there is no overwriting of COI postings.

In the example provided because the cons group is the same for both, there is no need for additional COI records. Plus, because hierarchy is not a characteristic. there is no way for a separate record.

I see no concerns or anything else to consider.

[Former Member · Accepted solution]

Thanks Dan,

This is exactly what I thought but I haven't tested the scenario in many years.

I hope all is well with you - i might be back on here a bit more these days, so looking forward to being involved again.

[Former Member · Accepted solution]

Dan agrees with my conceptual thoughts, does anyone else have experience of doing this scenario in their system either as a prototype or for real?