Purpose of INCLUDE_MEMBERS_NOT_IN_HIERARCHY

[praveen_kumar334]

Hi Team, 

Can someone please help me in getting exact purpose of CONFIG.HIERARCHY.INCLUDE_MEMBERS_NOT_IN_HIERARCHY statement. As per my understanding referring help.sap.com, It is basically used to read the orphans members. But when i see most of the Planning content, they are using  are keywords though the respective members are available in hierarchy. 

Can someone please help in getting the reason for it. Thanks.

Regards,

Praveen. 

[Susanne_Helbig]

Dear @praveen_kumar334,

the following note should explain the purpose of this statement:
3263115 - Data is not completely copied by Data Action script 

We're using this statement in our content to avoid data inconsistencies after performing data actions in case that master data is not properly maintained.

I hope this helps.

Best regards
Susanne

[praveen_kumar334]

Thanks @Susanne_Helbig for your reply and sorry for late response. Here I have one question. What is the case if master data is maintained properly in the hierarchy, then in that case, we do miss the correct in our data action. Let's consider the below scenario : 

Now, I have added one more company code C14 which is already maintained in master data(dimension table) as shown below.

Now in this case, since all the members of the company code dimension is assigned to hierarchy and with the config script CONFIG.HIERARCHY.INCLUDE_NOT_IN_HIERARHCY_MEMBER, what members will it fetch ?

Thanks in advance. 

Regards,

Praveen.

[Susanne_Helbig]

@praveen_kumar334 as I don't know what you want to achieve with your advanced formula, let me give you some more details:
Data Actions are always running on the default hierarchy set in your model, unless you don't specify a different hierarchy in your advanced formula (using CONFIG.HIERARCHY).

Let's assume you want to aggregate the data booked on company code and post it to company code #
then you would get the following results depending on your settings:

Does this answer your question?

Best regards
Susanne

[JefB]

Also check recent note 3428695.The config setting "INCLUDE_MEMBERS_NOT_IN_HIERARCHY" only works on those dimension members that are included under the "not in hierarchy" node in the dimension.

[JefB]

You still face the issue if you chose not to display orphan members in dimension configuration, see recent note 3428695. The config setting "INCLUDE_MEMBERS_NOT_IN_HIERARCHY" only works on those dimension members that are included under the "not in hierarchy" node in the dimension. 😞