I have replied in your other blog as well but it seems that its not fixed.
This issue generally happen When the OU of a user is changed in the external provider, perform the following steps to sync the external provider changes to Essbase security:
1. Export the Essbase security from Essbase Administration Services (EAS) Console, which can be found \Oracle\Middleware\user_projects\epmsystem1\EssbaseServer\essbaseserver1\bin
2. In the exported security file, locate each OU user that is having Smartview login issues
3. Perform the following steps to remove impacted users from Essbase security and then refresh from Planning:
· Login to MaxL as an admin user
· Execute command: display user <username>;
Can find each user name in the security dump file
Display user command will give the full user name with provider <username@provider> needed for the next command to drop
· Execute command: drop user <username@provider> from security_file;
· Run another security dump to be sure users were removed from Essbase
· Run a Planning security refresh to sync the user back to Essbase
This should correct the Planning application connection from Smartview login issue for each user.