Input data at Parent Entity

Hi,
We are thinking of creating a "Input" rule for parent entities for a scenario for an account and have couple of questions
1. My assumption is, when we write the rule, it by default enables input for all parent entities and no need to put any condition for POV. Correct?
2. Account should NOT be tagged as "IsCalculated" and should be "ISConsolidated". Correct?
Thanks in advance.

Hi,
First question: I don't think it uses parent entities by default, or any POV by default for that matter. We specify each POV we want to run the INPUT sub on, whether it be entities, accounts, custom dimensions, periods, year, etc. Just be aware that once you run an INPUT rule on a parent entity, it never uses the numbers loaded or entered in the base entities. It's a case where the sum of [Contribution Total] of the children Do NOT EQUAL the <Entity Currency> of the parent.
Second question: If the account is tagged IsConsolidated, it should work only starting with the parent entity since it ignores all date in children entities. Also, we do have accounts that have INPUT rules on them but that aren't tagged as IsCalculated, and it works fine.
Dany

Similar Messages

Input data on parent

I'd like to input data on parent account and then allocate the amount on child account with allocation keys. Can I do that with hyperion planning? I'd like to do the same thing with parent and child entities.
Best regards,
Ludovic

Yes - this is possible. In order to do this in Hyperion Planning, your version must be setup as a "Target" version, and not a "Bottom-up" Version.
If you don't want to use a "target" version, designers will sometimes create "proxy" members that represent an upper-level member in a hierarchy (but are actually level 0). These can be used to hold amounts to be allocated. The benefit of this approach is that the amount to be allocated doesn't actually get overwritten with the results of the allocation. This can make testing and validations easier. With that said, these proxy members can be difficult to manage, especially if you need to allocate from many upper-level points in a hierarchy.
Hope this helps,
- Jake

Is it a best practice to Input Data directly to Parent Currency ?

Dear Gurus,
I understand this question is very simple, but I am wondering is it a best practice to Input data directly into <Parent Currency>?
I am having a scenario where users do translation in Oracle and they wish to see the same number in HFM. As the process that they follow is unique in nature by Entity->Account [OR] for all Entities->Account, creating Override accounts is not helping us and rapidly increasing the Override hierarchy month-on-month.
Thanks...
Satya

By overriding the accounts, I assume you are referring to accounts that are translated historically as opposed to the default translation performed by HFM?
If so, I have seen two general approaches to achieve this:
a) Allowing the user to directly override the translation at IsTransCurr (i.e. <parent currency> if parent is in a currency other then entity)
b) Entering in a special currency rate in a rate account and then adjusting the translate routine to translate your account by that rate.
I personally, am a bigger fan of the first option.

How to implement parent entity for core data

Hi there.
I am starting a document-based Core Data application (Cocoa) and developed the following data model;
The 'invoice' entity is a parent entity of 'items', because ideally I would want there to be many items for each invoice. I guess my first point here is - is what I am trying to do going to be achieved using this method?
If so, I have been trying several ways in Interface Builder to sort out how to implement this structure with cocoa bindings. I have made a Core Data app before, just with one entity. So this time, I have two separate instances of NSArrayController's connected to tables with relevant columns. I can add new 'invoice' entities fine, but I can't get corresponding 'items' to add.
I tried setting the Managed Object Context of the 'item' NSArrayController to this;
I thought this would resolve the issue, but I still have found no resolution to the problem.
If anyone done something similar to this, I'd appreciate any help
Thanks in advance,
Ricky.

Second, when you create a Core Data Document Based application, XCode generates the MyDocument class, derivating from NSPersistentDocument. This class is dedicated to maintain the Managed Object Model and the Managed Object Context of each document of your application.
There is only one Context and generally one Model for each Document.
In Interface Builder, the Managed Object Context must be bound to the managedObjectContext of the MyDocument instance: it's the File's owner of the myDocument.xib Nib file.
It's not the case in your Nib File where the Managed Object Context is bound to the invoiceID of the Invoice Controller.
It's difficult to help you without an overall knowledge of your application, perhaps could you create an InvoiceItem Controller and bind its Content Set to the relationship of your invoice.

Data at base level not consolidating to the parent entity

HI All
I have an issue with data which exisits at the base level but do not consolidate to its parent entity.
For example,
2000
2001
2002
2003
Here only 2002 has data, but that is not appearing at 2000. I have checked the accounts and there we have set the IsConsolidated property.
The consolidation happens for other entities like 1000 & 3000. The problem is only with 2000.
Has anyone come accross this before and what is the best way to fix this?
Thanks,
Appu

Is it possible that you have not activated consolidation of the entities for the period you want to consolidate? Check out the Ownership Management screens for the entity 2000. Are all child entities set to Active? Is the proper Method set? Is the PCON = 100?
Also have you tried to select one of the child entities (e.g. 2001) and run the Force Calculate Contribution? What does this entity return at the +[Contribution]+ level?

Reporting: Parent entity level not able to view(Legal consol)

Hi friends,
Working on intercompany elimination using AUtomatic adjustments. Eliminations are happening correclty.
can it be possible to see data at consolidate entity/Parent level.
Rows: c_ACCT dim - BS items(Amount due from IC, Amount due to IC, IC elimination of ARAP)
Column1: Enity - 1000,1020,E_CG1000
column2: Group - G_CG1000
With above expansion, able to see elimination perfectly.
But when i try to include parent enity(CG1000) in column1 memberset, values are disappearing in EVDRE datarange.
i.e.Column1: Enity - CG1000,1000,1020,E_CG1000
How can see data in above fashion?
Properly defined hierarchy using dynamic hierarchy editor.
Groups dim.
ID | EVDESCRIPTION               | CuRRENCY_TYPE | ENTITY | GROUP_CURRENCY | PARENT_GROUp |     STORE_ENTITY     STORE_GROUP_CURR     CONSO_TYPE     DATASRC_LEVEL
G_CG1000 |SPA Group Consolidated | G |     E_CG1000          |USD             |     G_H1|     Y |     Y
G_CG1040 |SPA Ausi Consolidated      | G |     E_CG1040       |AUD             |G_CG1000 |     Y |     Y
G_H1 |Investments                | G |     E_H1               | USD                |     Y     Y |     Y     2010.DEC     Y
NON_GROUP |NOT A Consolidation Group Member (Used for Input data)|     N
Entity DIM
ID     |EVDESCRIPTION|           PARENTH1 |     CURRENCY|     ELIM |     INTCO     |ENABLEJRN     ELIMFILTER
E_H1     Investments               USD
H1     Investments               USD
CG1000     SPA Limited Group     H1     USD             Y
E_CG1000 SPA Limited Group Con CG1000     USD             Y
1000     SPA Limited            CG1000     USD                  IC1000     Y     Y
1010     SPA USA Inc            CG1000     USD                  IC1010     Y
1020     SPA Europe BV            CG1000     EUR                  IC1020     Y     Y
Regards,
Naresh

replaced old librfc32.dll file with new file..
issure resolved.

Advice on inserting data at parent level

Hi experts,
I would need some advice on how can I enter data at parent level. As we cannot enter data at parent level I am figuring out different strategies to do so. The one I seem to like the most is to create members representing the parents where we can input the data. For example:
- 2008.Total (Parent)
    + 2008.Generic (Leaf)
    + 2008.Jan (Leaf)
    + 2008.Feb (Leaf)
    + etc....
I would need to do this in different dimensions in my application. So here are the questions:
1) Is there anything wrong about doing this?
2) Is there a better option? (what is the Best Practice in this case?)
3) In the case of doing this for the TIME dimension, there are some properties which value is not easy to set for those members (TIMEID, YEAR and LEVEL). I don't really know where and how those properties are used and the help doesn't help me much (what is the "time format required for Analysis Services"?). So what values have you used in these properties for such members?
Thank you very much,
Rafael

Hi Rafael,
What purpose is your application designed for? In a legal consol application, would never mess with the standard time dimension setup, in particular the time dimension. The setup of the Time.Level and Time.Year properties are very sensitive in the operation of some of the business rules, particularly the opening balances & account transformation rules (where there's a time-period offset functionality). I always try to retain the standard time dimension setup there.
This means, for example, using a seperate datasrc member (or members) if the customer insists on having "13th period" for year-end adjustments. If they don't go into December along with the standard December values, then the carry-forward opening balances for the following year can be very tricky to calculate.
If your application is purely analytics, or for planning, then you should still understand what business rules features you want to use before deciding the time dimension design. When I've had year-total input data, I either
1.) use a standard 12-month time dimension, and by practice always put total-year data in December. Set up input schedules appropriately, and train people appropriately. Use Dec not Jan, or else the year-total and periodic/YTD computations in the cube won't work correctly. And consider your Account.Acctype carefully.
2.) If the data is for annual values that aren't directly part of the P&L or B/S, and are things like allocation drivers, tax rates, inflation rates, stuff like that -- which doesn't get added up along with the monthly values to come to a total-year "full picture" -- then I follow the structure from the old Outlooksoft demo. Create each of your years with the standard 12 months. Then create
Input.Year
xxxx Input.Quarter
xxxxxxxx 2008.Input
xxxxxxxx 2009.Input
xxxxxxxx 2010.Input
etc.
Then set your YEAR = 2008,LEVEL=MONTH for 2008.Input, etc.
This approach works well in logic *LOOKUPs and also keeps the dimension structure clean & intuitive for end users. If you put your 2008.Input under 2008.Q1 or 2008.Q4, then every time someone lays out or drills down in a report, they will curse the designer, since they now need to remove that extra column of the 2008.Input member.
With the datasrc approach for the "13th month" you can control whether the year-end adjustments are there or not, for those few reports where you'll want to see them. And 99% of the time, your time dimension "looks" normal.
I'm sure there are other approaches beyond what I've discussed, but I've never gotten into trouble using one or both of these two.
Regards,
Tim

Rules - Parent entity not rolling up from base calcs

What's the problem: Parent Entity member is calculating with a number for a certain account, even though I've specifically excluded this from happening in my rule. I don't want the parent entity to calculate
What should happen: Parent Entity member should just add up the result of its children for that account
Hi guys,
I have a calculation that is designed to specifically run at base entity level only. So I'm expecting that the parent result for a certain account should just be the addition of the results in its child entity members for that account
You can see from the code snippet below that I'm running the statements only when they're enclosed by the vIsBaseEntity conditional statement.
I want to get the required number, a simple A-B calc which looks at the change from prior year (but flips the sign if it's an equity account) into the SBS_MOVE custom 1 member.
If vIsBaseEntity then
     For Each vBSMoveAcct in HS.Account.List("","CalcBSMovementAccounts")
          If HS.Account.UD2(vBSMoveAcct) = "Equity" Then
     HS.Exp "A#" & vBSMoveAcct & ".C1#SBS_MOVE." & All_NONES_XC1C2C4 & " = A#" & vBSMoveAcct & "." & ALL_TOPS_XC2C4 & " - A#" & vBSMoveAcct & ".Y#Prior.P#Last." & ALL_TOPS_XC2C4
          Else
          'Standard Calculation
          'C1#SBS_MOVE = Prior Year End Amount - Current Period Balance Sheet Amount
          HS.Exp "A#" & vBSMoveAcct & ".C1#SBS_MOVE." & All_NONES_XC1C2C4 & " = A#" & vBSMoveAcct & ".Y#Prior.P#Last." & ALL_TOPS_XC2C4 & " - A#" & vBSMoveAcct &"." & ALL_TOPS_XC2C4
          End If
     Next
end if
However what actually happens is that whilst the base entities do calc, as specified in the rule, the parent entity does as well for a few accounts, even though that's not specified anywhere in my rule (or in my rules file anywhere else)
The parent entity for a certain account (Pl reserves), instead of giving me the result of (Current Year YTD minus Prior Year YTD), just gives me the result of Current Yr YTD, or just the A part of the A-B.
The above code is the only place where SBS_MOVE calculates.
I've tried to use a HS.Clear to clear that parent intersection first but to no avail.
So the intersection doesn't have any erroneous data left in it, it actively calculates a result for that parent member when I've specifically told it not to! Why???
Please help!
Thanks,
Sal

To expand a little on this for newbies who may look for this problem:
The aggregation operator never aggregate means that nowhere in your application will any intersection containing this member aggregate so if this is your problem the symptoms will be:
1. Dynamic Calc doesn't work.
2. Any aggregation scripts that are aggregating on intersections with that member will not work
eg. for example you have a member "no project" and you set it to never aggregate, then any parents in any dimension where they intersect with "no project" will fail to show data, whether they be dynamic calc or you are running a script.
If you have months or quarters the easiest way to see this is that suddenly the automated sums on the forms where you are using your "no project" member stop working so that your period data doesn't roll up into quarter or year.
Agnete
Edited by: Agnete on Oct 8, 2012 7:58 PM

Unable to view ECA and PCA value dimension for Parent Entity

Hi,
Situation: There is a parent Enity in (INR) with about 5 children Entity ( also in INR). Application default currency is USD .
Parent has ' allowadjfromchildren' selected and Children have 'allowAdjs' selected .
When I pull up a data grid with Parent and children for a particular POV , I can see data in < Entity currency > , < Entitty curr Adj> , <parent curr> , <Parent Currency Adj> for all children , However I dont see the <Entity curr Adj > or < parent curr Adj> at the Parent Level .
I can only see <entity currency> <entity curr total> and <parent curr>, <parent curr total> for the Parent .
qs. 1 . is this standard functionality ? Since Adjustment was not made at parent level , those intersection of ECA and PCA for parent will remain empty ?
qs 2 : Is there a way to roll up the sum of all children values in ECA into ECA at parent level ? rule change may be ?
eg . If child 1 has 10 , child 2 has 20 and child 3 has 30 in ECA , then their Parent to have 60 in ECA.
Currenty in our Appsettings we DO NOT have the Consolidationrules parameter selected .
Not sure if i was clear , Will appreciate some thoughts and direction on this .
Vik.

Hi,
Seeing that the currency is the same for the parent and children in your example, you will not see a difference between the children's <Entity Curr Adjs> and <Parent Curr Adjs>. In other words, if you post $10 to Child1 <Entity Curr Adjs>, you will also see that same amount in the <Parent Curr Adjs> - that is normal behavior and the child will only contribute the $10 to the parent. Because you have selected AllowAdjFromChildren HFM will allow you to post to [Parent Adjs] and [Contribution Adjs].
Q1: Yes, the adjustments are made to the child and will form part of the <Entity Currency> amounts in the parent. The parent's adjustment value members will store journals to the parent.
Q2: The sum of all the [Contribution Total] value members of the children will make up the <Entity currency> of the parent.
Q3: No, you will see the 60 in <Entity Currency> of the parent -- the way it works in more detail below:
EC + ECA = ECT;
Trans to Parent currency and seperate journals to PCA;
Security defines access to the [] nodes and if the parent has AllowAdjsFromChildren then [Parent Adjs] will be available;
Rules apply to [Proportion] and [Elimination] giving [Contribution];
Final adjustments allowed to [Contribution Adjs] to get to [Contribution Total]
Parent <Entity Currency> is the sum of children [Contribution Total];
Process starts again for the parent.
Regards,

Help Please - Parent Entity not clearing

We had a parent entity with 2 base children. We removed those 2 children and made the parent childless. How do we clear that parent entity ?

First of all, avoid making a parent into a child, and alson don't turn parents into children -- in any dimension.
On the entity you have turned into a base: if you are seeing data in the parent which you cannot determine its source, then load a blank rules file temporarily. It should be a rules file containing only:
Sub Calculate()
End Sub
Load this and reconsolidate. You should no longer see numbers in the parent entity (confirm this). Then re-load the original rules file. If you then see data after the original rules file has been loaded, it is most likely from the rules and not from having been a parent previously.
One way you can clear data from a parent is to load a single record data file, where instead of a numeric data value you can load "NoData" for al 12 periods and then load this in replace mode. This approach will clear the data values from the entity.
--Chris

Parent entity not calculating.

Hi,
Earlier today, we posted a few JEs to the children of an entity 'ABC'. When we run the overall consolidation, the process aborts at this entity. When we choose to calculate just this parent entity 'ABC', it calculates all its children but it fails at this parent entity 'ABC'. This parent entity was calculating fine before.

An aborted consolidation is a rules error, not a data error. If you look in the system messages you should see the actual error. Paste the error messages here and maybe we can help. Be sure to look through the details of each red error message.
--Chris

Not able to input data in query analyzer

Hi buddies,
I am working on IP.I have created a input ready query.For few values of company code there is no transaction data available,but it should show us blank so that I can atleast punch data.I am able to punch data for company codes for which transaction data is avilable .For remaining company codes for which transaction data is not availbale it is showing yellow coloured rows not allowing to input data.
Solutions would be really appreciated.This is high priority issue.
With regards,
Lalitha

Hi,
1) if you have no transaction data, it will not show you the company codes, unless you select in your query definition "master data' instead of posted values in the query properties (for company code)
2) yellow lines are subtotals.... To enable it input ready
- set query to input ready in query properties
- set row to plannable in query properties
- very important: make sure each characteristic of your aggregation level has a unique value either in the filter definition or in the definition of your rows or columns. If not, your query will not be plannable
D

How to retrieve input data from a HTML form in the UTF-8 cha

I encountered the following problem with a JWeb Application:
I tried to write a JWeb-Application for OAS 4.0, that retrieves
input data from a HTML form and writes it into an Oracle
database.
All processing should be done in the UTF-8 character set.
The problem is, that the form data retrieved by getURLParameter
are always encoded in a non-unicode character set and I found no
way to change this.
Can anybody tell me what I should do to get the form data in the
UTF-8 character set?
null

Hi
Try set in the JWEB application's Java environment such
SYSTEM_PROPERTY: file.encoding=UTF8.
Andrew
Thomas Gertkemper (guest) wrote:
: I encountered the following problem with a JWeb Application:
: I tried to write a JWeb-Application for OAS 4.0, that
retrieves
: input data from a HTML form and writes it into an Oracle
: database.
: All processing should be done in the UTF-8 character set.
: The problem is, that the form data retrieved by getURLParameter
: are always encoded in a non-unicode character set and I found
no
: way to change this.
: Can anybody tell me what I should do to get the form data in
the
: UTF-8 character set?
null

Last day of each month in a year based on a Input date?

Hi all,
I have a request from a customer who wants to have a yearly report created in BEx Query Designer which starts in January up to December and they want to have a Month To Date (MDT) and Year to Date (YTD) calculation of a key figure. This report will only show one year at the time based on the date the user give as input at the Variable Screen.
This key figure should be calculated by using the last date of each month for input when performing the MTD and YTD calculation and summarizations.
Example:
January: 31.01.2008  Key Figure = 1000. MTD = 1000 and YTD = 1000
February: 29.02.2008  Key Figure = 2500. MTD = (2500-1000) 1500 and YTD = 2500
March: 31.03.2008  Key Figure = 6000. MTD =(6000-2500)=3500 and YTD = 6000
Etcu2026.
This means that I have to have a lot of hidden Key figures which gets restricted on the different month end dates and formulas to calculate the different MTD and YTD results for the months as the year progresses.
The way I have solved it now is that I have a Customer Exit which gives me the Last day of last year (Exp: 31.12.2007) based on input date and use a Offset on the last day of last year date to get the different last dates of each month.
Since we have a leap year (one extra day in February) this year, the offset to calculate the end month dates will be different for 2007 and next year (2009). This solution is not very flexible, and it will not give the correct MTD and YTD if the customer wants to go back to 2007 and off course next year (2009).
One solution is to create 12 Customer Exits that gives me the different month end dates (January-December), and also takes in account leap year for February for the different years. These Exits will be based on the Input date the Customers put in at the variable screen.
I would rather want to avoid making 12 new customer exits and want your advice and expertise to find out if this is possible in any other way (maybe with only 1 customer exit) to get the last date of each month based on an input date.
Thanks for all your advices on beforehand.
Regards
Oddmar Lid

Hi,
Thanks for you replay and documentation, but it doesn't give me excatly the functionality I'm after. The only MTD calculation code the document provides is the calculation of the following functionality:
"Month to Date (MTD) u2013 From the 1st of month to u201CKey Dateu201D - for current year." This doesn't give the the functionality I want, which is to retrieve a given vaule for a Key Figure for the last dates of the months in a year to calculate MTD and YTD.
This way I have created the query is to have multiple hidden Key Figures that calculates the MTD and YTD.
In Columns in Query Designer it will look something like this:
Selection: MTD January--> Date = 31.01.2008, Key Figure (Always Show)
Selection: YTD January --> Date= 31.01.2008, Key Figure (Always Show)
Selection: MTD February --> Date= 29.02.2008, Key Figure (Always Hide)
Formula: MTD February --> MTD February - MTD January (Always Show)
Selection YTD February --> Date = 29.02.2008, Key Figure (Always Show)
And so on....
This is off course a simplified version, but it shows the core of the solution. What I want to achive here is that the dates used to get the Key Figures (last date of a month) is calculated as flexible as possible, so that the users can go back and forth in time without worrying about the leap year problem and so on. I have now used an offset from the last date of last year and this is good for all the normal years, but when it is a leap year the query will use wrong dates to get the key figure vaule for the last date of each month.
Any ideas on how to achieve this without creating 12 different Customer Exit variables (one for each end date of each month)?
Thanks
Regards
Oddmar Lid

How to input data into a table with columns?

I am trying to input data into a table. My table have 5 columns and an unlimited amount of rows. I created a program in LabView that enters the data into the table but it enters all of the data in one row. I would like to enter the first set of information into the first column, the second set of info into the second column and so on. I am including a copy of the program that I am working with. I would like the number of runs to be put into the first column (it should count down like number 5 in first row, number 4 in second row, number 3 in third row, and so on). I would like the applied voltage to be placed in the second column, and so on. Any help or information will be greatly appreciated. I am working with LabView Version 6.1 and 8.0. I am submitting the vi from 6.1.
Attachments:
FJ-PROGRAM.vi ‏68 KB

Pondered,
I looked at your code and I think you might be making things too complicated. I've included a very simple example that demonstrates how to write a 2D array of integers to a table. Hope you find this helpful. It is in LV 7.1.
Chris C
Chris Cilino
National Instruments
LabVIEW Product Marketing Manager
Certified LabVIEW Architect
Attachments:
rows - columns.vi ‏17 KB

Input data at Parent Entity

Similar Messages

Maybe you are looking for