HFM

Improve HFM user experience with dynamic POV memberlists!

Improve HFM user experience with dynamic POV memberlists!

What is the difference between a good HFM application and a great HFM application?
User experience!
Improve user experience with dynamic POV memberlists!

Introduction

A dynamic POV memberlist is based on members set in the POV. This feature can make your HFM application very user friendly.

 

Why using dynamic POV memberlist?

The first benefit of using dynamic list is to improve the user experience in the data input. A dynamic webform will show only what is needed. For example, in some complex organizations, from one Business Unit to another, you do not have access to the same product family or the same market, etc. In this situation, if there is only one input form for all the BUs, each user will only have a few cells to input in a very huge input form. It will take time to find the right cells and there is a risk to input data in the wrong cell category. With a dynamic memberlist, the webform will only display the products related to the selected BU. No time lost, no risk to make a mistake for the user. This is really appreciated by users.

The second benefit is to simplify the development of webforms. In the previous example, in most f  inancial applications the answer will be to create a specific input form dedicated to each BU. Using a dynamic list allows you to create only one webform which will answer to all the needs. And this webform will automatically be up to date if there is a change in the structure.

Dynamic POV list also ease development of Financial Reports. There are “advanced options” in the suppression tool in HFR, but this feature can be very confusing and  difficult to handle in some complex cases. For example, if you need to set three columns for Actual / Forecast / Budget. Note that depending on the month, you need to display a specific forecast scenario. You can do it with the advanced options, but it will take you an hour. It will take you five minutes to set a dynamic list…

 

How does it work?

The principle

Dynamic list can be based on POV members of the following dimensions:

  • Scenario
  • Year
  • Period
  • Entity

You can create a list of any HFM dimensions based on these four dimensions.

It might be a great update by Oracle to allow the creation of dynamic POV memberlist based on any dimension. You can already do very interesting things with the current possibilities.

 

Dynamic list can be used in:

  • Webforms
  • Grids
  • Reports

 

Create the dynamic POV list

 

To set a list as a dynamic list, you have to use the @POV keyword in the name of the list.

EntityLists(3) = “<ListName>(@POV)”

 

In the list script you can get the POV elements using the following syntax:

ScenPOV=HS.MemberListScenario
YearPOV=HS.MemberListYear
PerPOV=HS.MemberListPeriod
EntPOV=HS.MemberListEntity

 

Example

This example shows a dynamic POV memberlist which displays BUs depending on the selected legal entity in POV.

We want to set up a webform  which allows users to split P&L figures by BU.

 

Creation of dynamic POV list

First, name the list with the @POV suffix.

 

aEntityLists(5)  = “ENTITY_BU_NOTSHARED(@POV)”

 

Then, write the script

'ENTITY_BU_NOTSHARED

Case 5

    EntityCur = HS.MemberListEntity

    EntityList=HS.Entity.List(EntityCur,"[Children]")

    For i=LBound(EntityList) to UBound(EntityList)

        If Right(EntityList(i),6) <> "SHARED" Then

            HS.AddEntityToList "", EntityList(i)

        End If

    Next 

 

 

Use the dynamic POV list in the webform

Through Data Form Designer:

 

 

Through Data Form Script:

 

The dynamic webform

As a result we now have one dynamic webform which displays the right BUs.

 

We can change the legal entity and see that the webform will be updated automatically.

 

In this example we could have created one webform for each legal entity as it is usually done. Thanks to dynamic POV memberlists, we can create only one webform.

Here are the advantages of having only one webform :

  • It simplifies the navigation and the user experience
  • It also simplifies final users training. As we do not create a specific webform for each legal entity, they will not have to read a specific user guide for each legal entity
  • It eases the developments. There is only one webform to develop and to update in case of evolution in the organization.

 

Conclusion

 

Dynamic lists are helpful both to increase the user experience and ease developments of the application.

We know from our experience that, well managed and implemented, dynamic lists can create the “wow effect”. It could be the difference between a good HFM application and a great HFM application.

 

Next article Improve HFM user experience with sorted memberlists!
Previous article Strange behavior using Smart View in Excel

4 Comments

  1. « Vous savez, moi je ne crois pas qu’il y ait de bonnes ou de mauvaises applications. Moi, si je devais résumer ma vie aujourd’hui avec vous, je dirais que c’est d’abord des rencontres. Des gens qui m’ont tendu la main, peut-être à un moment où je ne pouvais pas, où j’étais seul chez moi. Et c’est assez curieux de se dire que les hasards, les rencontres forgent une destinée… Parce que quand on a le goût de la chose, quand on a le goût de la chose bien faite, le beau geste, parfois on ne trouve pas l’interlocuteur en face je dirais, le miroir qui vous aide à avancer. Alors ça n’est pas mon cas, comme je disais là, puisque moi au contraire, j’ai pu : et je dis merci à la vie, je lui dis merci, je chante la vie, je danse la vie… je ne suis qu’amour ! Et finalement, quand beaucoup de gens aujourd’hui me disent « Mais comment fais-tu pour avoir cette humanité ? », et bien je leur réponds très simplement, je leur dis que c’est ce goût de l’amour ce goût donc qui m’a poussé aujourd’hui à entreprendre une construction mécanique, mais demain qui sait ? Peut-être simplement à me mettre au service de la communauté, à faire le don, le don de soi… »

    Bon en fait, il y a quand même des applis qui en jettent plus que d’autres, et l’utilisation de ces dynamicPOV révèle l’intérêt porté à l‘expérience utilisateur.
    D’ailleurs, c’est pour quand l’article sur les Sommaires dans HFM ??

    Reply
    • Merci pour ce commentaire Nicolas. 🙂
      En effet, certaines applications en jettent plus que d’autres. La différence se situe très souvent à l’intérêt porté à l’expérience utilisateur (plutôt qu’à la technique).
      Un article sur les sommaires serait une excellente suite. On pourrait parler notamment des sommaires qui utilisent les listes dynamiques. “Effet wow” assuré ! J’en ai encore fait l’expérience il y a peu de temps.

      Reply
  2. Hi, would it be possible to create dynamic member lists for custom dimension? I want to show specific member of custom dimension dynamically base on selected entity in POV.

    Please kindly advise.

    Reply
    • Hi Puwadol,

      Yes it is definitively possible, since you can create dynamic member list for any dimension using dynamic entities/ scenario / year / period from the POV.

      Below is an example from a dynamic memberlist used to display a custom dimension from the entity in the POV

      EntPOV=HS.MemberListEntity
      For Each SITE in Hs.Custom1.List(“USINE”, “[Base]”)
      If InStr(Hs.Custom1.UD1(SITE), Left(EntPOV,5))>0 Then HS.AddMembertoList SITE
      Next

      In the example below we use the UD1 attribute of the Custom dimension to define if this custom dimension should be accessible to the entity in the POV. But there are multiple other ways to do the same thing.

      Nicolas MATHE

      Reply

Leave a Comment

Your data will be safe! Your e-mail address will not be published. Also other data will not be shared with third person. Required fields marked as *

4 × one =