With Essbase implied sharing, some members are shared even if you do not explicitly set them as shared. These members are implied shared members. When an implied share relationship is created, each implied member assumes the other member’s value. Essbase assumes (or implies) a shared member relationship in these situations:
A parent has only one child
A parent has only one child that consolidates to the parent
The data type of the parent is Label Only (in this case, the parent inherits the value of the first child, regardless of the aggregation settings used for the child)
In a Planning data form that contains members with an implied sharing relationship, when a value is added for the parent, the child assumes the same value after the data form is saved. Likewise, if a value is added for the child, the parent usually assumes the same value after a data form is saved.
For example, when a calculation script or load rule populates an implied share member, the other implied share member assumes the value of the member populated by the calculation script or load rule. The last value calculated or imported takes precedence. The result is the same whether you refer to the parent or the child as a variable in a calculation script.
When necessary, you can avoid implied sharing on Planning data forms. See Implied Sharing Issues.