Migrating Supporting Details/Comments

We recently created a new Hyperion environment by copying our production environment. After that, we created a new dimension for our use going forward. We realized that all supporting details and comments were missing. It makes sense because the details and comments are pointing at specific intersections of data in the SQL database. I've written the SQL to add a default member from the new dim to all the supp details/comments and that fixes the majority of the problem by linking the details to the correct intersections. When I go back into a Planning form and drill down, i can now see the supporting details and comments. However, the form's cells are not turning blue, which is the visual cue that there are underlying details. Does anybody know how these cells get the blue shading that represents underlying details?
Here's my SQL that adds the default new dim member to my underlying details:
UPDATE HSP_COLUMN_DETAIL
SET DIM9 = '233295' --DIM9 is the new Dim and 233295 is the object code of the new dim's default member
WHERE DIM9 = ''
Thanks-
Cameron

Planning uses a caching system so if you make changes directly to the tables (which is not supported) then planning will not always be aware of the changes, if the tables updates are valid then usually a restart of the planning web app will pick up the changes.
Cheers
John
http://john-goodwin.blogspot.com/

Similar Messages

Hyperion Planning Comments and Supporting Detail

I understand that Comments and Supporting Detail are kept in SQL. The question is which DB (if not HYP_PLANNING) and what is the table? thanks...

Cameron,
You should be able to export a file from LCM in an automated fashion.
My theoretical process involves four XML files (you could name these anything - these are just my names):
1) Export_Migration_Definition.xml (This XML file tells the Utility.bat what to export into files 3 & 4 below - Comments and Supporting Detail.)
2) Import_Migration_Definition.xml (This XML file tells the Utility.bat what to import into your Planning app - again Comments and Supporting Detail.)
3) Cell Texts.xml (This is the file that LCM creates with cell text. We'll need to change the version name in this file.)
4) Supporting Detail.xml (This is the file that LCM creates with supporting detail. We'll need to change the version name in this file.)
So where did I get files 1 & 2? If you go into LCM, and setup a manual migration, at the end, you'll see a button to "Save Migration Definition". Planning will create these two files for you. You'll need to go through the motions as if you were going to execute an export, and an import. Except you won't go all the way. At the end of the process, instead of pressing "Execute Migration", you'll press "Save Migration Definition" instead.
Once you've got the Export_Migration_Definition.xml and Import_Migration_Definition.xml, you can automate the export and import. At this point you'll be exporting and importing the same comments and supporting detail, just to make sure it works. Then you need to insert a step in your batch process that does a find/replace on the Version name. You'll be doing the find and replace on files 3 & 4 above. I used Google to find several examples of Find/Replace as part of a batch process.
Please let me know if you see any holes in this. I really don't think you need to interact directly with the repository for either the export or the import. In reality, you don't want to import directly into the SQL repository anyway, because you would typically need to recycle Planning for your changes to take effect.
Hope this helps,
- Jake

Cell Comment and Supporting Detail with User ID

Hi,
I have created couple of SQL to generate the report on Cell Comments and Supporting detail from Planning repository tables 11.1.2.1.
This is working as expected Now I have additional requirement to provide the User information who added the cell comments or Supporting detail
Please let me know if anyone has this before - I wanted to know where the user information stored in these tables when someone entered cell comments
--Cell Text
SELECT
HSP_UNIQUE_NAMES.OBJECT_NAME AS Scenario,
HSP_UNIQUE_NAMES4.OBJECT_NAME AS Version,
HSP_UNIQUE_NAMES2.OBJECT_NAME AS Department,
HSP_UNIQUE_NAMES5.OBJECT_NAME AS YEAR,
HSP_UNIQUE_NAMES3.OBJECT_NAME AS Period,
HSP_UNIQUE_NAMES1.OBJECT_NAME AS Account,
HSP_CELL_NOTE.NOTE_ID,
HSP_CELL_NOTE_ITEM.CONTENTS
FROM HSP_CELL_NOTE
INNER JOIN HSP_CELL_NOTE_ITEM
ON HSP_CELL_NOTE.NOTE_ID = HSP_CELL_NOTE_ITEM.NOTE_ID
LEFT JOIN HSP_UNIQUE_NAMES
ON HSP_CELL_NOTE.DIM1 = HSP_UNIQUE_NAMES.OBJECT_ID
LEFT JOIN HSP_UNIQUE_NAMES HSP_UNIQUE_NAMES1
ON HSP_CELL_NOTE.DIM2 = HSP_UNIQUE_NAMES1.OBJECT_ID
LEFT JOIN HSP_UNIQUE_NAMES HSP_UNIQUE_NAMES2
ON HSP_CELL_NOTE.DIM3 = HSP_UNIQUE_NAMES2.OBJECT_ID
LEFT JOIN HSP_UNIQUE_NAMES HSP_UNIQUE_NAMES3
ON HSP_CELL_NOTE.DIM4 = HSP_UNIQUE_NAMES3.OBJECT_ID
LEFT JOIN HSP_UNIQUE_NAMES HSP_UNIQUE_NAMES4
ON HSP_CELL_NOTE.DIM5 = HSP_UNIQUE_NAMES4.OBJECT_ID
INNER JOIN HSP_UNIQUE_NAMES HSP_UNIQUE_NAMES5
ON HSP_CELL_NOTE.DIM6 = HSP_UNIQUE_NAMES5.OBJECT_ID
--Supporting Detail
SELECT
HSP_UNIQUE_NAMES.OBJECT_NAME AS Scenario,
HSP_UNIQUE_NAMES4.OBJECT_NAME AS Version,
HSP_UNIQUE_NAMES2.OBJECT_NAME AS Department,
HSP_UNIQUE_NAMES5.OBJECT_NAME AS YEAR,
HSP_UNIQUE_NAMES3.OBJECT_NAME AS Period,
HSP_UNIQUE_NAMES1.OBJECT_NAME AS Account,
HSP_COLUMN_DETAIL_ITEM.LABEL,
HSP_COLUMN_DETAIL_ITEM.POSITION,
HSP_COLUMN_DETAIL_ITEM.OPERATOR,
HSP_COLUMN_DETAIL_ITEM.VALUE,
HSP_COLUMN_DETAIL.DETAIL_ID,
HSP_COLUMN_DETAIL_ITEM.GENERATION
FROM HSP_COLUMN_DETAIL
INNER JOIN HSP_COLUMN_DETAIL_ITEM
ON HSP_COLUMN_DETAIL.DETAIL_ID = HSP_COLUMN_DETAIL_ITEM.DETAIL_ID
LEFT JOIN HSP_UNIQUE_NAMES
ON HSP_COLUMN_DETAIL.DIM1 = HSP_UNIQUE_NAMES.OBJECT_ID
LEFT JOIN HSP_UNIQUE_NAMES HSP_UNIQUE_NAMES1
ON HSP_COLUMN_DETAIL.DIM2 = HSP_UNIQUE_NAMES1.OBJECT_ID
LEFT JOIN HSP_UNIQUE_NAMES HSP_UNIQUE_NAMES2
ON HSP_COLUMN_DETAIL.DIM3 = HSP_UNIQUE_NAMES2.OBJECT_ID
LEFT JOIN HSP_UNIQUE_NAMES HSP_UNIQUE_NAMES3
ON HSP_COLUMN_DETAIL.DIM4 = HSP_UNIQUE_NAMES3.OBJECT_ID
LEFT JOIN HSP_UNIQUE_NAMES HSP_UNIQUE_NAMES4
ON HSP_COLUMN_DETAIL.DIM5 = HSP_UNIQUE_NAMES4.OBJECT_ID
INNER JOIN HSP_UNIQUE_NAMES HSP_UNIQUE_NAMES5
ON HSP_COLUMN_DETAIL.DIM6 = HSP_UNIQUE_NAMES5.OBJECT_ID
Regards,
KP

I like to think of the cell comments like post-it notes. If you use them sparingly, they're very useful. If you use them all the time (or use comments in every cell) it's unlikely that they will be as effective.
With regards attaching a document, I think the same can be said.
With regards supporting detail, it always strikes me that if you need more detail within a given cell, that the system should be accommodating this through component child members, rather than a mix of some cells containing supporting detail and others not. I understand that it's quite nice functionality to have though, and looks good when demo'ing.
I think the main take away from this is that every time you show the comments etc to people the first question you get is "Can you report all the comments for a given time period?" and the answer is of course unfortunately "Not easily using a supported method".
Just my thoughts...

Cell comment, Documentation, annotation and supporting detail.

Hi All,
I am actually new to 'Hyperion Planning'. I know what comment, documentation, annotation and supporting detail means. But, can anyone tell me 'WHEN' to use each of these.
Thanks

I like to think of the cell comments like post-it notes. If you use them sparingly, they're very useful. If you use them all the time (or use comments in every cell) it's unlikely that they will be as effective.
With regards attaching a document, I think the same can be said.
With regards supporting detail, it always strikes me that if you need more detail within a given cell, that the system should be accommodating this through component child members, rather than a mix of some cells containing supporting detail and others not. I understand that it's quite nice functionality to have though, and looks good when demo'ing.
I think the main take away from this is that every time you show the comments etc to people the first question you get is "Can you report all the comments for a given time period?" and the answer is of course unfortunately "Not easily using a supported method".
Just my thoughts...

Supporting Detail migration

Hi
I'm doing a supporting detail migration in 11.1.1.1 via SQL because of a difference in dimensionality between source and target.
The good news is that I have successfully inserted the data and when double click a cell in Planning the supporting detail is there. However, the cell colour has not changed.
What can I do so that the cell indicates there is supporting detail?
Cheers

I'm able to insert new supporting detail and the cell colour works fine. It's just the cells containing migrated detail that are not highlighted.
I could probably go in to the detail, click save and the cell colour would update, but that is not feasible for the volumes I'm working with.
Cheers

How to move supporting details from one intersection to other?

Hi,
I want to move data from one intersection to other along with supporting details and comments. Now i want to delete everything (data, supporting detail and comments) from previous intersection. I know how to clear data but do not know how to delete comments and supporting details form that intersection.
Can you help me with this?
Thanks!

I have found it.
Thank
Its Adminstration -> Clear Cell details..

Is there any way to disable supporting detail functionality in Planning?

Hi all
Just had a user request to be able to disable the supporting detail functionality in Planning forms. We are on 11.1.1.3. All we want is to disable the double click functionality that brings up the supporting detail box.
Thanks

Ok I have found a way to disable supporting detail and I thought I would share it in case anyone else needed to do this. Similar to what John has suggested, it involves javascript but a much simpler way.
In the parent directory of where the ValidateData.js file is {[Hyperion_Home]\deployments\Tomcat5\HyperionPlanning\webapps\HyperionPlanning} there are a large number of javascript files. I had a look through these and found the EnterData.js file. Make a backup of this file, and edit the original.
If you edit this, and search for doSupportingDetail, you can simply comment out all of the code in this function except for the return line. Its not a good idea to comment the whole function out or else I would expect other functions may call on this and then fail. At least if its just calling the doSupportingDetail and immediately returning back to the calling function, this would have no issues.
Restart your session and it should all work.
Obviously you can improve this blanket change by specifying which apps / forms supporting detail should apply for by using the equalsIgnoreCase function in the validatedatasample.js example.

Annotations Supporting details

Hi All,
Can I know the difference between Annotations and supporting details??? Is annotations applicable on;y to accounts?? And is there any way that we can export annotations and supporting details to excel ? Please advice
Thanks in Advance

Hi,
Annotation , in very simple terms as Johngoodwin said are comments to accounts and they can be as simple plain text or URL.
Comign to the supporting details (these are the cells in the dataform which are green in colour, if you see any in your form). They have a built in calculator and altogether a different functionality
You can find all information about supporting details , in chapter 6 "working with supporting details" in hp_user document. Explanation with example has been provided.
Hope this info helps
Sandeep Reddy Enti
*HCC*
http://analytiks.blogspot.com

Lack of Migration support for 6.0 & 10g users

Hi,
One of the 1st things we wanted to do with the beta as an existing customer is to validate migrating a project from our existing Production version (6.0) to 11g.
While the import appears to work, opening any imported diagram throws an XML parsing exception.
After raising an SR, it turns out that migrating from previous versions is unsupported until 11gR2.
This puts me in a tricky spot as one of the main business drivers to adopt 11g is product upgrade.
I am very surprised to see existing customers nt being catered for in the new version, as running multiple versions in Prod is not a realistic option for most.
Backwards compatability is therefore very important to the existing user base!
So, questions for Oracle:
1. Can you please reconsider the lack of migration support for R1?
2. if this feature cannot be working for R1, what is the expected release date (even if its just a quarter) for R2?
3. To save my time, is there a list of what other features are not for going to be available in the Beta / R1 release?
As a Beta tester my time is precious, and I need to know what I can expect to work, rather than report issues only to then find out that its not supported...
Thanks,
Ian
.

Hi Ian,
You are right in the sense that upgrade will be supported in BPM 11gR2. More specifically, the upgrade will support OBPM 10gR3 to BPM 11gR2. Customers in older versions of OBPM and ALBPM will need to upgrade to OBPM 10gR3 before attempting the upgrade to BPM 11gR2. To upgrade to OBPM 10gR3, there are a series of pointers in our documentation on how to do this. I can explicitly provide links if you are interested in this mandatory upgrade before moving to BPM 11g.
As per the reason for not being able to support upgrade in this first version of BPM 11g, it simply boils down to time to create the new unified BPM platform which in itself is a major undertake from an Engineering perspective. Once the foundation is complete (this is the objective for BPM 11gR1), we will start working on completing the delta to upgrade OBPM 10gR3 projects to BPM 11gR2 as best as possible. There is a document we have been sharing with customers with Best Practices for implementing OBPM 10gR3 projects with idea of an upgrade to BPM 11g. We do have significant knowledge on some pieces that we will be able to automate from a migration perspective and some others that will be hard to upgrade. If you are interested in this document, we can provide this to you.
If you have any other questions, please let me know. I would be more than happy to assist with migration questions with the most up to date knowledge I have on this front.
Regards,
eduardoc.

Planning Application - Supporting Details

Hi,
We deleted around 4000 members from our planning application and later realised that the few members have budget values tagged to them and also supporting details are included for few of the members. Now we would like to bring back those members to our application. Could you please suggest the best method to bring back those members and the associated supporting details. We donot want to restore the entire the entire application. Is there a way to restore only that particular dimension and its members and the supporting details associated with them. If yes, could anyone of you let me know the process. Our relational DB is SQL 2005.
Request your help for the closure
Thanks,

Assuming you have a backup of your SQL database somewhere (this would be the Planning repository), the following code will extract Supporting Detail:
Supporting Detail
SELECT
     "Plan Type" = P.TYPE_NAME,
     "Scenario" = O1.OBJECT_NAME,
     "Account" = O2.OBJECT_NAME,
     "Entity" = O3.OBJECT_NAME,
     "Month" = O4.OBJECT_NAME,
     "Version" = O5.OBJECT_NAME,
     "Year" = O6.OBJECT_NAME,
     "Activities" = O7.OBJECT_NAME,
     "Employee" = O8.OBJECT_NAME,
     "Value" = I.VALUE,
     "Position" = I.POSITION,
     "Generation" = I.GENERATION,
     "Operator" = I.OPERATOR,
     "SD" = I.LABEL
FROM HSP_COLUMN_DETAIL D
     INNER JOIN HSP_PLAN_TYPE P
          ON D.PLAN_TYPE = P.PLAN_TYPE
     INNER JOIN HSP_COLUMN_DETAIL_ITEM I
          ON D.DETAIL_ID = I.DETAIL_ID
     INNER JOIN HSP_OBJECT O1
          ON D.DIM1 = O1.OBJECT_ID
     INNER JOIN HSP_OBJECT O2
          ON D.DIM2 = O2.OBJECT_ID
     INNER JOIN HSP_OBJECT O3
          ON D.DIM3 = O3.OBJECT_ID
     INNER JOIN HSP_OBJECT O4
          ON D.DIM4 = O4.OBJECT_ID
     INNER JOIN HSP_OBJECT O5
          ON D.DIM5 = O5.OBJECT_ID
     INNER JOIN HSP_OBJECT O6
          ON D.DIM6 = O6.OBJECT_ID
     LEFT OUTER JOIN HSP_OBJECT O7
          ON D.DIM7 = O7.OBJECT_ID
     LEFT OUTER JOIN HSP_OBJECT O8
          ON D.DIM8 = O8.OBJECT_IDYou'll want to modify it a bit to get it to work with your dimensions -- this is from an old project of mine.
I have never tried to write Supporting Detail back in -- I know it has been done, just not by me. I would tread very carefully and only do it on a test database and be really, really, really sure you've got everything working just so. You could easily blow up your data.
Another approach might be to restore that Planning app backup (making sure you made a backup of the current app), and then use LCM to export out Supporting detail, and then suck it back into the app that no longer has it.
^^^I like that idea a lot more even if it is a bit more tedious.
With either approach, you are going to have to sync the Essbase data to the SD data -- hopefully you have a good Essbase backup as well.
Regards,
Cameron Lackpour

Report on Supporting Details

Hi,
Our client has purchased a tool to load supporting details directly into Planning. This is to have the granularity of the cost details. Is there any way that we can generate a report of the supporting details. Will that be restricted to that particular combination or we can have a report of complete P&L where the accounts which have supporting details have also the list displayed below.
Can this view be possible? Please let me know.
Thanks,

hi,
For a data form ,which might be any report ( from business sense) can have supporting details ,which can be easily spotted in green colour.
For example , if its expense of some kind, and it has got supporting details , you can dig into its depth by looking into it to find it constituents ex: travel expense , hotel expense...etc.
Its like a in built calculator, and it does display list. Revert if you need any further info
Sandeep Reddy Enti
HCC
http://hyperionconsultancy.com/

Forcing use of Supporting Detail in Hyperion Planning data form

Hi everyone.
We're using Hyperion Planning 11.1.1.2 and for one particular data form, I'd like force users to HAVE TO use Supporting Detail on specific cells. I think there might be a way to do this using custom JavaScript functions and modifying the form code but I am wondering if there is a way to do this without code on the form. Any suggestions?
Thanks!

A quick simple example
function customCellEnterPre(row, col, cell) {
     if(row == 3 && col ==1)
          doSupportingDetail();
     return true;
Cheers
John
http://john-goodwin.blogspot.com/

ValidateData.js - Need to Force Supporting Detail

I am working on some custom JavaScript for a Hyperion Planning web input form where I need to force users to enter supporting detail. I understand how it's done in the SampleValidateData.js file, however that method will still allow a user to save non-supporting-detail values in a cell.
I would like to cycle through all editable cells and check a property on the cell to see if it contains supporting detail. (ex. by checking the tooltip value)
Does anyone know a specific property I can check on the cell (along with its corresponding value for supporting detail)?
Thanks,
- Jake

Found it. currentDataGrid.isSupporting[r][c]

Supporting detail disappeared and the could not edit

We have a planning app (v 11.1.2.2) and one user told me he entered some data into supporting detail for one cell. After he save it and the cell data became 0. And he could not edit that cell anymore. Tried to editing supporting edit for that cell brought back a blank page. I tried that cell and although the data is 0 and I could not update supporting detail either. It just brings a blank page for supporting detail. User can still enter and edit supporting details for other cells. I can think of a couple things to do:
1. Check the relational db and delete the supporting detail for that cell.
2. Restart Planning services to see if that fixes it.
But before I do that, I want to know if anyone of you encounter the same thing or not. And is there any other way to fix that.
Thanks

Thanks! That icon color is barely visible. I never noticed it was there! I need to change it to more contrast color.

How to copy Supporting details using business rule

Is it possible to copy supporting details and attachment, cell text using business rules. We have Copy version option but i want to make it run using a script, is it possible, please suggest

The supporting detail is held in the planning relational tables and business rules are run against essbase, using a business rule you would probably have to create a custom CDF.
Cheers
John
http://john-goodwin.blogspot.com/

Migrating Supporting Details/Comments

Similar Messages

Maybe you are looking for