Enterprise Transformations, It's all About Performance Management

Unable to Open Form in Smart View: Error: oraclesv: While using chrome if you try to open data form in Smart view , this will take you to a next tab and that tab that will be blank and will have a url oraclesv: Its a known internal bug, currently worked as an enhancement request: Bug 24686182  - PBCS:OPEN IN SMARTVIEW NOT WORKING IN SIMPLIFIED INTERFACE FROM CHROME Workaround is to use either Firefox or IE for this. If you are using Firefox you have to enable smart view extension: 1. Go to setting and click on Manage Add ons 2.  Enable Smart View Extension ( you may want to enable FR extension as well) and restart browser 3. This should allow you to open data form in smart view. We still have to wait to do this in Chrome. Cheers..!! Rahul S.

When you perform a regular export of dimensions you won’t get a lot of member properties, by default, you will get Member, Parent and Data Storage listing. This is a known behavior listed here . CHANGE OF BEHAVIOR: METADATA EXPORT Metadata exported from Enterprise Planning and Budgeting Cloud will no longer contain any property information for factory metadata. Properties such as member formula and data type are suppressed; only the parent and data storage columns are exported. Customizations made to factory members are tracked and exported separately to the customization file of the applicable module. If you migrate an application that contains customizations in multiple stages, for example, migrate one dimension at a time, you must export and import the following: Metadata of the dimension Customizations from the customization file   If you want to export these custom properties you have to use LCM. LCM will generate a Module Customizatio

We have an option to use OnPrem FDMEE to connect with Cloud instance. If you planning to go that route there are some prerequisites which you need to perform on on-prem FDMEE instance to ensure its connectivity with cloud instance.  Prerequisite: ·          FDMEE should be patched: 11.1.2.4.200 ·         Configure SSL certificate in Web Logic Server (WLS) : o    Importing EPBCS SSL Certificate to WLS o    Update the hostname verification setting to configuring WLS to support wild cards in host name o    Enabling WLS with JSSE SSL, this is to support Java version of SSL o    Oracle documentation:  http://docs.oracle.com/cd/E57185_01/AGFDE/configure_ssl_certificate__102xf468157d.htm ·         Checking Cloud Connectivity: o    Retrieving application detail in FDMEE o    Oracle documentation:   http://docs.oracle.com/cd/E57185_01/AGFDE/erpi_reg_target_app.htm#AGFDE-epmi_target_app_2 If you don’t import certificate you will run into: We followed above

We have an option to use OnPrem FDMEE to connect with Cloud instance. If you planning to go that route there are some prerequisites which you need to perform on on-prem FDMEE instance to ensure its connectivity with cloud instance.  Prerequisite: ·          FDMEE should be patched: 11.1.2.4.200 ·         Configure SSL certificate in Web Logic Server (WLS) : o    Importing EPBCS SSL Certificate to WLS o    Update the hostname verification setting to configuring WLS to support wild cards in host name o    Enabling WLS with JSSE SSL, this is to support Java version of SSL o    Oracle documentation:  http://docs.oracle.com/cd/E57185_01/AGFDE/configure_ssl_certificate__102xf468157d.htm ·         Checking Cloud Connectivity: o    Retrieving application detail in FDMEE o    Oracle documentation:   http://docs.oracle.com/cd/E57185_01/AGFDE/erpi_reg_target_app.htm#AGFDE-epmi_target_app_2 If you don’t import certificate you will run into: We followed above s

I ran in to this issue a couple of times, every time the reason was different and the solution was different. We get this error when we try to take LCM export of the application from Hyperion Shared Services. When shared services try to connect to Hyperion Planning, it internally calls the following servlet: http://<Server>:<Port>/HyperionPlanning/servlet/HspLCMServlet You may get this error when this call fails, it can be because of: 1. Time out the request, 2. Something is blocking this url, 3. Wrong server or port information in the EpmSystem Registry, 4. Because of an internal bug, 5. Something else! :) Here I will be talking about point 3. Situation: My OHS was configured to direct all the traffic using 19000 base port,  its the default port for OHS for EPM system. Because of some reasons I have to reconfigure OHS to 19001 and I have reverted it to 19000. Every thing else was working fine, I can access HSS, Planning Application, Essbase application, r

There can be a situation which will take you by surprise at first: When you can open a data from without issues from the Planning Web but when you try to open the same form from Smart view you will end up in Invalid form Error. The solution is not very complicated, you will be able to figure out the solution quite easily by looking at the error message. When smartview parses the xml to get: GetFormSlice as: <res_GetFormSlice><properties massAllocate="0" gridSpreader="0" cellsURLs="0"/><name id=<FrmId> displayName=<FrmName>/><grid> Here: FrmId is the Object_id of the from           FrmName is Object_Name associated with that id Lets look at the data form form Planning web: Its opening fine. When I open the same form, using the same user from Smart View: If you enable logs of smart view: [SVC] [NOTIFICATION:4] [SVC7257] [SVC] [ecid: 00iS34R^PbnFw0zxzP0AJz21HkE0j6YyS0002^g000000,0] Log

Yes, who uses the report scripts now, but sometimes, that is the best option; here I am not going in the debate that which is better Report Scripts, Calc Exports or MDX. This post will only concentrate on what is the best you can do with the report scripts. I myself faced a challenge in which report script was taking a couple hours to export the data, we have to bring it down to the least, here are few observations which I would like to share with all and hope this will save our fellows' time. Following them I was able to cut down the time up to 1/100X: Here are few stages where we can optimize reports: 1. Pre Report Creation Optimization, 2. Formatting Optimization, 3. Member Selection and Grouping Optimization, 4. Report Specific Optimization, Before from the time report is extracted by report extractor and displayed by report viewer, we can do be some updates to the application, this is pre report creations optimization and this will be common for all the