Enterprise Transformations, It's all About Performance Management

When it comes to Planning Security we have to grant it at two levels: 1. Planning application roles  2. Planning artifacts access   Planning application roles are granted in Shared Services and Planning artifacts access such as Web forms and dimensions/members are maintained and defined from a Planning user interface. Security on these artifacts is defined from within the Planning application. Planning artifacts are stored in the Planning relational repository. So, if you planning to migrate security for an application which is in 11.1.1.x to 11.1.2.2, the best way is to use the typical upgrade approach but in case you cant use that, here is an approach in which we will be using the 11.1.1.3 LCM back to Restore it in 11.1.2.2. Here is an outline how we will be doing that, we will export security from version 11.1.1.3 using LCM, edit the files convert them in 11.1.2.2 supportable format and then will perform LCM import. In this blog post will only be t...

Here is one of the issues I have faced during Planning Application upgrade and how I was able to resolve that. I have restored Replica application which was from version 11.1.1.3 to an 11.1.2.2 environment, now when I tried to upgrade a Planning application from 11.1.1.3 to 11.1.2.2 I got  the following error in the logs(Location of upgrade logs: Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\planning): [FMWGEN][SQLServer JDBC Driver][SQLServer]The object 'DF__HSP_SYSTE__ESS_XXXX' is dependent on column 'ESS_DEF_PSWD' . On investigating further I was able to found that Planning is able to execute all the steps till line 70, line number 71 in the upgrade script is: ALTER TABLE HSP_SYSTEMCFG ALTER COLUMN ESS_DEF_PSWD VARCHAR(30) BTW you can find the upgrade scripts at: Oracle\Middleware\EPMSystem11R1\products\Planning\config\sql When I tried executing above ALTER query directly on database I got following: Msg 5074, Level 16, State 1, Lin...

Issue: Even though a user is provisioned for a Planning application in Shared Services, when you try to log into that application by that user you get following error: Failed to sync with user provisioning. Check Planning log for details The basic reason for this issue is the SID (Security token IDentifier) mismatch between Shared Services and Planning repository for a user. In other words  even though the User/Group name is same in both repositories but the identifier is different. Point to note: Planning uses SIDs, not the User or Group name for syncing and internal communication.  There may be times when you will be able to log into a planning application using few users and few of them will give this sync error. A simple way to check if you are running into SID mismatch issue is to check the SID in Shared Services schema table CSS_USERS/GROUPS and HSP_USERS/GROUPS.  Utilities which we use to sort this issue are ProvisionUsers and UpdateUsers bu...