Saturday, 12 November 2016

...loading APP files in HFM

I have not posted any thoughts recently because I am working on an amazing migration to the Cloud project and I spend most of my time there. However, recently I got in a situation which reminded me of a discussion that I had a few months ago in OTN. The discussion was related with issues that users had with loading APP files in their upgraded applications.

In my case, we were working on upgrading the applications from to We followed the process suggested by Oracle and we upgraded to and then moved the applications to When I started testing the upgraded applications I found that in one out of the three applications it was not possible to extract and reload the extracted metadata without corrupting the application.

Thursday, 30 June 2016

... where Hyperion comes from?

I hope you do not expect that this is a serious post because it is not... however, it is a post that I am really proud of...

So, where Hyperion comes from?

Wednesday, 15 June 2016

...Calculation status: OK SC

     A few weeks ago, I was working on an application update. I started the update on Friday afternoon and thankfully everything went well. I loaded the new metadata and new rules without any problem, completed the "Clear Invalid data" task in 20minutes and then I started the overnight consolidation in order to reconsolidate the whole application and get the status OK in all scenarios/years/periods. I was home before 7pm

Wednesday, 13 April 2016

...Org by Period

Recently, in the OTN forum, we were discussing the functionality of Org by Period.

Org by Period specifies whether the application allows new consolidation structures to co-exist with previous consolidation structures in the same application.  If it will be set to ‘Y’, it will enable the functionality to activate or deactivate legal entities by reporting period.

As an example, let's consider entity AB which should be consolidate to parent A for period P1 to P3 and then consolidated to parent B for periods P4 to P12. In order to achieve this, in the Ownership management module the entity would be flagged as Active under parent A for periods P1 to P3 and then it will be flagged as Inactive. For periods P4 to P12, the entity will be flagged as Inactive for parent entity A and Active for parent entity B.

Based on this, the parent entity A would retain the values on a YTD basis for only the data that came from P1 to P3.  Data from periods P4 to P12 would be only consolidate to Parent B.

Finally, the metadata would show the entity underneath both Parent A and Parent B, though the various metadata selector dialogs have a "show active only" button when you want to show only the current period's active structure.



Sunday, 3 April 2016

...the consolidation functionality

It is two days before the end of the year-end reporting period and at 4:50 pm the helpdesk receives a new ticket with title “Consolidation of subsidiaries and NCI query”.

Silence in front of my screen… the subject of the ticket is quite worrying for such a week and as I read further down the situation becomes even worst.  The request of the user was to explain how the system calculates the NCI for specific subsidiaries, why the closing balance was 150.000$ and what the movement consolidation movement represents. A lot of questions….


Until today, I have seen four approaches in consolidating the values of an entity to the parent entity.
  • The first approach is to create manual journals at "Entity Curr Adjs". This journal will be posted both at the subsidiary and at the consolidation entity of the group.
  • The second approach is to use the Sub Calculate and the function HS.Exp in order to populate specific members or consolidation accounts at the value dimension members "Entity Currency" / "Entity Curr Adjs".
  • The third approach is to use the Sub Calculate and the function HS.Exp in order to populate specific members or consolidation accounts at the value dimension members [Proportion] / [Elimination].

Friday, 25 March 2016

when to blog....

Hi all,

It’s been quite a while since my last post and I should feel guilty. 

However, the first months of 2016 passed really quickly with a lot of exciting things. Last week, thanks to some friends that I had not seen for 6 months, I remembered that I should post more often in order to keep my thoughts alive.

Topics that I have in mind are:
  • Using Loop structures in the HFM rules - Performance at stake
  • Consolidation journals audit functionality - Transforming HFM to a virtual accountant
  • Cloud and Hyperion - The Titan is finally in the air, or not?
  • SharePoint and Hyperion - Location? Our location is the world
  • Top Gun 2016 - One more year of exciting news
  • FDMEE - The change is here, back to the classroom
  • Hyperion version - Insight, so excited!
Let's see...

...Records & Subcubes in HFM

A few years ago, I decided to spend time to understand how HFM calculation engine works with aim to improve the performance of the r...