Anyone know if it is possible to pull data from a Parent Entity into one of its children.
I could use case or a list but would rather try and create something that based upon a condition , data flag or review level pulls data from the entity's immediate parent.
Any insight appreciated
Technically it is possible, but you need to be sure that the data you intend pull from the parent is up-to-date in respect to consolidation at the moment you are pulling it. The other situation you need to possibly be aware of are the different currencies. You need to write the rules in a way that it works even if the parent is in a different currency than the child.
So technically it is possible, but I would stay away from it due to practical reasons...
I'm not happy about it but it's a legacy of the original design which means supplemental information is needed which are driven from Entity consolidated values.
The other option was to look at HS.Input to a consolidation point, again something that does not appeal.
So to try and explain a simple view of the scene…,
An Entity contains some revenue 100k, and there are 5 other Entities these all sum to a single consolidated view.
Say this means Revenue is 3,000,000 all fine.
However there is a need to identify the Revenue across different items, for example revenue stream.
This information is not based upon and logic etc it is held within a different source but can only effectively be determined upon knowing the consolidated view.
To assist the User experience they would benefit from seeing the 3,000,000 and then being able to assign appropriate revenue streams. (Possibly through HS.Input)
The other option was to pull the 3,000,000 into one of the child entities and input the revenue stream.
The actual business problem is a little more detailed, I'm created a simplified example or at least tried to!
The requirement seems very odd. If they want to separate out revenue streams, why does their GL account structure not support this breakout? Would the use of a custom dimension by product line etc. support them?
As Thanos points out, it sounds like they are asking for some type of allocation, if revenue is 3 millions at a consolidated level, we want to assign a proportionate share to entity X? You say above that the information is not based on any kind of logic, which I think you are saying that their current data creation process is ineffective at facilitating their reporting needs. In which case, I would try and pull them away from the cliff of writing rules to fix bad process and instead drive them towards journals until they can modify the account structure accordingly.