1 Reply Latest reply on May 31, 2019 6:49 AM by JohnGoodwin

    Loading FX rates from HFM to Essbase/Planning Applications

    3358578

      Hello,

      I am new to HFM and FDMEE tools. Is there a way to load FX rates from HFM to Essbase/Planning applications. I have set up the Import format/ Location and Data load rule. When I execute the rule, it errors out with a following error:

      2019-05-30 11:43:39,932 INFO  [AIF]: [HFMService] Info:Filter Slice: S#Actual.Y{[Base]}.P{[Base]}.W#Periodic.E#[None].V#<Entity Currency>.A#Average.I#[ICP None].C1#[None].C2#[None].C3#[None].C4#[None]

      2019-05-30 11:43:39,937 INFO  [AIF]: [HFMService] Info:Error: The POV selected for this function is invalid.

      2019-05-30 11:43:39,943 INFO  [AIF]: [HFMService] Info:[extractData:1399] END (oracle.epm.fm.common.exception.HFMException: EPMHFM-1057: The POV selected for this function is invalid.)

       

      Is the issue due to how source filters in Data load rule is set?  As you can see above- All custom dims and the entity is set to 'None'. I am not sure how to use the member list - [Currencies] in the source filter.

        • 1. Re: Loading FX rates from HFM to Essbase/Planning Applications
          JohnGoodwin

          The error can be down to the combination of the source filters and select POV is incorrect, Looking at the slice created Also I don't see any periods or year defined which could be down to a period mapping issue.

          I think it is best to take a step back and look at the requirements first,. It might be worh discussing with the HFM admin to understand the POV where the exchange rates are be held. Maybe create a grid in the HFM app to make sure you have the POV correct. Then move these into FDMEE, at the same time make sure you have all the period mappings correct.

          You also need to understand how exchange rates are being held in the planning application, is the default currency method that is being used, if so the exchange rates are held in a planning table and then pushed to Essbase. You may need to investigate whether to use the OLU to load the rates.

           

          Cheers

           

          John