HFM 9.2 (Org by Period)

Is this an option in 9.2 or did this start with 9.3

Thank you. I am there now but what is the nest step after i choose this option. I was told this option would allow us to manage our Entity structure and allow us to have different entity structures for each period. So when i add a new entity, is there something i need to check off if it applies to that period? I am not sure what i do now to make this work. There is not much information on this in the Admin guide.
Can someone please explain how this option works and what it does

Similar Messages

  • DRM and HFM integration when Org by period is ON

    Our HFM application has Organization by period turned ON. Thus, when there are entity hierarchy changes, we actually dont move entities but just change their active parents. We are using DRM for master data management where hierarchies are defined. however, when structure changes are to be made in DRM, we have to actually move the nodes from one parent to another. Now loading this revised structure in HFM would change the consolidation structure for all periods and not just subsequent periods. How do we handle this?

    Maybe load the entity changes in merge mode, which will leave them in both the original location and the new location. Replace mode on the other hand will remove the child from the original parent.
    --Chris                                                                                                                                                                                                                                                                                                                                                                                                                               

  • Consolidate YTD in Actual and its relation Org by period in Application set

    Hi Peers,
    Make me clear for the following
    Actual data: the data which is past for 12 month periods of data apply the same with Scenario dimension member"Consolidate YTD. and next Org by period is Future related now please explain me these concepts how,why,where

    Hi,
    Please go through the below link for your answer.
    HFM Scenario
    Regards
    Dev

  • HFM 11 -Org by Period- is it possible to show active entities only in EPMA?

    Hello all,
    when i change entities in pov in the data grid there is a checkbox to filter / show the active entities only.
    So i searched a same function in EPMA to work with the entity dimension more comfortable but i didn´´t found any.
    Is it even possible to filter / show only active entities in the EPMA dimension library like in the data grids?
    best wishes
    Martin

    The active flag for an entity exists in the data realm of HFM, not the metadata. It may change from period to period, while the metadata attributes of entities are not changing with period, they are set at design-time. EPMA handles the metadata (design-time) aspects of entities, therefore it has nothing to do with the Active flag.

  • IC Eliminations and Org by Period

    My metadata includes a company Co.A which in common with Co.B is a child of Co.X in 2006.
    In 2007 Co.A is inactive under Co.X but active in a new branch under a parent Co.Y.
    When I consolidate in 2007 I find an intercompany elimination entry in Co.B.
    i.e It appears that although Co.A is inactive under Co.X HFM sees the entity there, takes A and B to have a common parent and incorrectly performs an elimination.
    How can I overcome this?

    Hi,
    We havent posted any journals and although the entity is shared, it is inactive under the second parent. Does this mean that the inactive tag does not work for shared members?
    Thanks again.
    Seb

  • Extracting data with zero values for periods without data

    Hello Together,
    i extracted data from our hfm application from period 1 to 3.
    Now i found that some rows begin with period 2 or 3 because there are no data in period 1 or 2.
    So my question is, how i can get zero values for periods with no data.
    Hope someone can help me.
    Many thanks in advance.
    Martin
    P.S.: Our actual hfm version is 11.1.1.3
    edit

    For the periods with no data, HFM does not have a "0" to offer for the data extraction. Since the default data extract from HFM has each period on it's own row in the *.dat file, I don't understand your comment about rows starting with period 2 or 3. In the *.dat file the row for period 1 simply won't exist. Are you using a custom approach/tool for data extraction?
    The only time HFM will offer a "0" where there is indeed no data, is if you extract derived data. You must include calculated data, and even then I believe HFM will only extract a "0" for the first period after a period where there was data, and only for flow accounts (Revenue/Expense). so if you have "100" in period 1, and no data in period 2, such that the derived value YTD for period 2 is "0", then you must include calculated values in the extract and you should see "0" for period 2. However, I don't believe HFM will extract "0" for period 3 - instead it will be blank/missing.
    In general it could be very dangerous to force HFM to give zeros where there is no data.
    --Chris                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • Unable to extract HFM Cell text values i.e. Descriptions using ODI

    Hi,
    We are trying to extract the HFM 'Cell Text' values, which is defined as "Description" in the "HFMData" store in ODI into an Oracle RDBMS table using ODI. We are using the KM - "LKM Hyperion Financial management Data to SQL" for this purpose.
    We have followed every detail as defined in John goodwin's post at the below link:
    (Seems like his interface worked with "Descrption" column mapped to the target source file (pls refer the 5th screenshot in the below blog).
    http://john-goodwin.blogspot.com/2010/04/odi-series-extracting-data-from-hfm.html
    However, while we extract we get the below error message everytime we try to extract the Description field. (Without mapping the Description field we are able to extract the HFM data succesfully):
    org.apache.bsf.BSFException: exception from Jython:
    Traceback (innermost last):
    File "<string>", line 1, in ?
    com.hyperion.odi.common.ODIHAppException: Error loading resource string for code '117'. Error code: 1813 (x715)
         at com.hyperion.odi.hfm.ODIHFMDataExtracter.execute(ODIHFMDataExtracter.java:161)
         at com.hyperion.odi.hfm.ODIHFMAppStatement.executeExtract(ODIHFMAppStatement.java:119)
         at com.hyperion.odi.hfm.ODIHFMAppReader.extract(ODIHFMAppReader.java:128)
         at sun.reflect.GeneratedMethodAccessor98.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java)
         at org.python.core.PyMethod.__call__(PyMethod.java)
         at org.python.core.PyObject.__call__(PyObject.java)
         at org.python.core.PyInstance.invoke(PyInstance.java)
         at org.python.pycode._pyx76357.f$0(<string>:1)
         at org.python.pycode._pyx76357.call_function(<string>)
         at org.python.core.PyTableCode.call(PyTableCode.java)
         at org.python.core.PyCode.call(PyCode.java)
         at org.python.core.Py.runCode(Py.java)
         at org.python.core.Py.exec(Py.java)
         at org.python.util.PythonInterpreter.exec(PythonInterpreter.java)
         at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:144)
         at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.execInBSFEngine(SnpScriptingInterpretor.java:345)
         at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.exec(SnpScriptingInterpretor.java:169)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java:2374)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java:1615)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java:1580)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java:2755)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2515)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:534)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:449)
         at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1954)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$2.doAction(StartSessRequestProcessor.java:322)
         at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:224)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.doProcessStartSessTask(StartSessRequestProcessor.java:246)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.access$0(StartSessRequestProcessor.java:237)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$StartSessTask.doExecute(StartSessRequestProcessor.java:794)
         at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:114)
         at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:82)
         at java.lang.Thread.run(Thread.java:619)
    Caused by: com.hyperion.odi.hfm.wrapper.HFMException: Error loading resource string for code '117'. Error code: 1813 (x715)
         at com.hyperion.odi.hfm.wrapper.HFMDriverJNI.executeDataExtract(Native Method)
         at com.hyperion.odi.hfm.wrapper.HFMDataExtracter.executeDataExtract(HFMDataExtracter.java:39)
         at com.hyperion.odi.hfm.wrapper.HFMStatement.executeDataExtract(HFMStatement.java:55)
         at com.hyperion.odi.hfm.ODIHFMDataExtracter.execute(ODIHFMDataExtracter.java:104)
         ... 35 more
    com.hyperion.odi.common.ODIHAppException: com.hyperion.odi.common.ODIHAppException: Error loading resource string for code '117'. Error code: 1813 (x715)
         at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:146)
         at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.execInBSFEngine(SnpScriptingInterpretor.java:345)
         at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.exec(SnpScriptingInterpretor.java:169)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java:2374)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java:1615)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java:1580)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java:2755)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2515)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:534)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:449)
         at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1954)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$2.doAction(StartSessRequestProcessor.java:322)
         at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:224)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.doProcessStartSessTask(StartSessRequestProcessor.java:246)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.access$0(StartSessRequestProcessor.java:237)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$StartSessTask.doExecute(StartSessRequestProcessor.java:794)
         at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:114)
         at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:82)
         at java.lang.Thread.run(Thread.java:619)
    Can anyone please suggest a solution
    Regards,
    Sailendra T

    I have the same error. And I found that the error appeared only with one specific HFM application (I my case). I can import any amount of data from other HFM Applications, but importing from the needed aplication causes the error, and also it crashes the HFM:
    Faulting application HsvDataSource.exe, version 11.1.2.3505, faulting module HsvData.dll, version 11.1.2.3505, fault address 0x000000000013d6f4.HFM server even has no time to write message to a log.
    It's strange behaviour: client can broke server.
    Edited by: 921369 on Jun 25, 2012 3:16 AM

  • Multiple Reporting Periods for local legal reporting

    Dear HFM Gurus,
    How to satisfy Period dimension for Group reporting as well as local legal reporting with different period Example: Holding parent's period - Jan to Dec and Child entity's period Jul to Jun.
    We all know Group's period is supposed to be the local entity's period by default application creation, but we have a special consideration to satisfy the local reporting needs as well.
    Thanks in advance.

    Hi Thanos,
    Group is not managing the data of the local entity, but they would receive them in order to use them correct? Agreed, we also expect and work towards the same.
    Yes, you are right in understanding that Group P01 = Mexico P06 = Jan. Other way to state it is "Lets assume we are maintaining a standard Hierarchy labels (Jan to Dec) instead of P01 to P12". Now the requirement is how best we can satisfy the local reporting (Means do we need to plan for using a Custom dimension or having a separate entity Hierarchy or any other ways to achieve it to satisfy group as well as Mexico?
    Thanks for your help.
    Cheers,
    KS

  • List of routed entities in workflow template

    I am using Weblogic integration server7.0. Try to get all routed entity before workflow starts. Any other way to get the users lists for preview the workflow path? other than parsing template definition xml data.

    This sounds like you have an app with Org by Period enabled.
    Dumping out the dimensions (incl Entities) into a list is something that you can do with the Consultants Utilities delivered with HFM, but unsupported by Hyperion|Oracle.
    Alternately, have a look at the EPM Maestro. This has an Extract to Excel function with an active member filter for ObP apps.

  • Joint Venture Associate Consolidation Translation Question

    Hi All,
    I have two problems with our Joint Venture/Associate Entities and the way they translate/consolidate in HFM which I would appreciate some input on if anyone can help:
    1. Our implementation of HFM is YTD and each period that period's ownership percentage is applied to the whole YTD balance of the P&L which doesn't account for period on period ownership changes. I believe I can overcome this by forcing HFM to think periodically with closing/opening balances and the consolidation rules but does anyone have a neat/best practice way of doing this?
    2. We have movement tables on our Balance Sheet accounts so the consolidation of the JV/Associate's P&L to the Balance Sheet for the parent works on a YTD movement basis, forming the year's closing balance which rolls forward to the opening balance in the next year. This all happens at the Node at [Proportion] and [Contribution]. I need to find a way to make sure that the consolidated amounts are at the current period's closing rate by adjusting the opening balance. I can't see a way of doing this as I don’t think there is a concept of the <Entity Currency> balance at this level.  Any thoughts on this?  I can think of some really messy roundabout ways of doing this but am again wondering if anyone has already worked this through and come up with a neat/best practice way.
    Thanks in advance for any input!

    Hi there,
    Do you use the default consolidation rules or you have written your own custom rules?
    If it is custom rules then both questions can be easily fixed.
    Kind regards,
    Thanos

  • Issue with changing ZeroViewForNonAdj and ZeroViewForAdj

    Hi,
    We have an issue with ZeroViewForNonAdj and ZeroViewForAdj settings.
    Our goal is to load every third month from Planning to the forecast scenario. We started with April and had the ZeroViewForNonAdj and ZeroViewForAdj settings as YTD. When we loaded July we realized that the settings were wrong so we changed them to Periodic. This however didn't change the way the zeros are presented in HFM.
    Do you have any solution to this on how we can get the periodic zeros to be visible?
    - Nicklas

    Hi Nicklas,
    If you change the scenario settings you really need to clear out the scenario and re-load all the data in the scenario to allow HFM to re-derive the periodic values.
    --Chris                                                                                                                                                                                                                                                                                                                                                                                           

  • BSI: Year-To-Date Method ?

    Dear all:
        Im trying to understand bulletin 57 and the change of formula for tax type 003 to "year to date method"... I saw the doc. of bsi about that and it is not very clear, any one could provide an example of what would be the impact? what would change?
    Thank you,

    Hi
    The difference in the methods is the way one translates flow accounts (typicall revenue and expense lines)
    using TRANS function will translate the YTD values and the difference between current period YTD and previous period YTD in translated currency will be written to periodic view
    using TRANSPERIODIC function, HFM will first calculate the periodic value in the entity currency and multiple this by the exchange rate for the period.
    typically if in the application setting you have clicked ON on the "USE PVA for flow accounts", that means you need to use transperiodic method.
    hope this helps

  • Loading HX YTD Data for Actuals

    Should my scenario be set to anything specific if I am loading HX YTD values for my income statement, balance sheet and stats and why? We have had some issues with the data loading accurately and have found that the if we load the data month by month it seems to work. However if we load multiple months the numbers seem to carry and mess up months either before or after that month.
    We have set
    Name- Actual
    Def Parent #root
    Def Freq MTD
    Def View YTD
    Zero View for NA Periodic
    Zero View for Adj Periodic
    Consolidate YTD is checked

    This is an unusuall configuration, and one I would not recommend. If you load data YTD, I recommend making both ZeroView settings also YTD. The setting tells HFM that in the absence of a number loaded to an intersection, HFM should interpret the missing number as a YTD zero. In order to do that, HFM will derive a negative Periodic number equal to the prior period's YTD value.
    The only time we see ZeroView set to Periodic is for forecasting/budgeting, where users will enter periodic amounts and they want HFM to assume the lack of a number implies zero on a Periodic basis. In this case, you are asking HFM to bring forward the prior period's YTD amount. This is also predicated on the idea that Actual data should be loaded YTD, to ensure that changes to data in prior periods gets captured - you do not want to reload prior periods.
    It is very important to note that we do not want to load zeros to HFM which is why it is so important to get this setting right.
    One more point: this setting only impacts flow accounts - it has no bearing on balance accounts.
    --Chris                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • YTD data for PnL Accounts

    Hi All,
    Need some advise on these.
    Our period dimension is Jan-Dec, however, the subsidiaries submit the data only in March, June, September and December.
    We set the DefaultFrequency to MTD, DefaultView to YTD, MissingData0ViewForNonAdj is YTD and MissingData0ViewForAdj is Periodic.
    The data that we load for BS and PnL accounts are all in YTD and we consolidate in YTD (ConsolidateYTD is Yes).
    Now we have situation where one of our entity is sold on December 2010.
    Since the setting zeroview for actual scenario is set to YTD, we are expecting that when we check the december period, the PnL accounts for this entity is in the system with the same amount of september data.
    However, the PnL account show 0 data, even if we select the View to YTD.
    And when we run the consolidation, the PnL data for this entity is not aggregated to the total consol due to the unavailability of the YTD data.
    Is it normal behavior of HFM? Is there any explanation about this?
    Many thanks.
    Regards,
    Indra

    What you see is based on the application design -- specifically the scenario settings. You need to understand the MissingDataAsZero settings. What you describe is the norm for a scenario where these settings are "YTD". That is, you've told HFM to interpret missing data as a YTD zero. In this case, HFM will derive a negative Periodic value in order to arrive at a zero YTD value.
    This is only one of your worries in my opinion. If you have foreign currency entities which only load quarterly rather than monthly, you have a translation problem if you use PVA for flow accounts (app setting) which is the most common configuration. In this case, the P&L accounts loaded only to the last periods of each quarter will use only that period's average rate for all of the activity, rather than the period in which the activity really took place.
    --Chris                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Consolidation in multiple currencies

    Hi there,
    I would like to translate consolidated results in two different currencies. Let's say, for example, USD and EUR.
    Do I need to create two alternative entity hierarchies whose parents def currencies are USD and EUR? Is there any other possible solutions?
    Any customized solution would do the job... even if  highlight me main technical choices, avoiding to disclosing details of your implementations.
    It's very useful to us because we wish to would like to maintain the opportunity to post Contribution Adjs.
    PLEASE HELP!!!

    I will better explain my request:
    PREMISE:
    No Org by Period app; YTD consolidation
    Sub translation manages the convertion applying average YTD rate, opening or closing rate. Some accounts are translated at historical rate. Translation also manages the calculation of the currency translation reserve in equity.
    Consolidation manages the split of equity reserves between minority and group shares. This split involves also the currency translation reserve, by debiting the "Currency Translation Reserve" account and crediting the "Currency Translation Reserve - Minority Share" account.
    Users need to analyze contribution of each single legal entity (including the split effect) both in USD and EUR. In order to properly translate and consolidate figures the quickest and most reasonable solution would be that of creating two alternative hierarchies (one in USD and in EUR). However this turns into headakes when you have to post Contribution Adjs as these must be posted twice, one time in EUR and the other time in USD.
    My question is:
    is there a customized approach that allows me to avoid redundancy in posting Contribution Adjs and also reduce the number of alternative hierarchies? Have you ever faced similar issues? How did u solve them?
    Many thanks again

Maybe you are looking for