IF you are building the dimension from a file that is in a parent/child format, it will automatically make the first instance of a member as stored and subsequent instances (with a different parent) as shared. For level or generation builds, it is more work to actually get shared member rollups.
You can prevent shared members from beig created by going into the dimension build properties and specifying to not allow shared members
The "Never Share" property prevents implicit sharing (aka "Implied Shares"). It doesn't prevent the creation of a regular 'explicit' shared member. However, as Glenn explained, that can be done through the load rule setting.
Thanks for you input. Sorry if I dont understand.
1) Yes. I am using parent/child build method. Can you please clarify where I can make changes to prevent shared member being created? Is it in the rule file "Dimension build settings" tab??
2) Also for the member if the member property codes is set to N which is "Never Share" how its allowing to create another member as "Shared Member".
Thanks for your input. I believe my questions are answered and I need a small clarification on the below.
I understand that a member which as property as "never shared" can be explicitly shared by creating the same member again and editing the member properties to" Shared member" which is done manually. If I don't specify it as " Shared member", then validation fails saying " Duplicate member name".
But in automated process using rule file and an input file, how is member created as "Shared Member" where I don't specify member property code as shared.