The OneStream Community is temporarily frozen until June 29th due to the ongoing maintenance. Please read the blog post here to learn more.
Forum Discussion
Solved
Custom Grouping/Aggregation of only certain IC
Hello All,
Our customer, who is migrating from BOFC, would like for organizational and technical reasons to keep using his intercompany dimension to capture sales to third parties but would also ne...
You can work with custom member lists as well for this, but realistically, the more future proof solution is - in my view - to use a UD. Easier to maintain and adjust. Using the IC dim is very restricted and not meant to be used for third parties, which means using it in any other way is less easy and less user friendly. Also, how many third party entities (=customers) are there?
I would really push the customer hard on this one. A pro and cons list might help convincing them.
Henning
OneStream Employee
OneStream EmployeeHi Matthieu,
I do not think I understand the full set of requirements here. Maybe an Excel example would help.
Just to clarify, by "third party", do you mean companies that do not belong to the group (i.e. they are not consolidated)?
On a high-level I would say, they should just move those members to a UD called "customer". As you know, the IC dimension cannot be "grouped" using hierarchies as it fully relies on the IsIC setting in the entity dimension. For the customer, the IC dimension is just a name, but they need to understand the technical implications of their request and that there are (likely) more feasible and cheaper alternatives.
Thank you Henning for your feedback. You have perfectly understood the issue. These companies do not belong to the group and as such need to be considered as third party. The wish of the client is indeed to aggregate sub families of IC partners, both to reconcile to a sub family and not a base level. And in the case of a "Third Party" IC to be able to aggregate all sales to a sub-family of IC members.
Do you see this feasible if we keep only IC dimension (could be to use text attribute on entity dimension and manipulate them in a BR to derive this information from entity dimension but interpret it to group for corresponding IC members ?)
- Henning
You can work with custom member lists as well for this, but realistically, the more future proof solution is - in my view - to use a UD. Easier to maintain and adjust. Using the IC dim is very restricted and not meant to be used for third parties, which means using it in any other way is less easy and less user friendly. Also, how many third party entities (=customers) are there?
I would really push the customer hard on this one. A pro and cons list might help convincing them.
Thanks for your answer. We will try convincing the customer to follow OS standards as you say. It will be simpler.
