HFM Application Design Basic and important doubts

Question

Hi Can one Make me clear for the following doubts?
1.A and B are 2 entities now i am going to delete B entity for this year, reason is that not having business operations. what could i do for B entity before deleting?. B is having data for
the past few years and i want that data for future purpose to analyze its operations for the past. requesting you please how to start think on this?
2. In Value dimension which one is first between these 2 Proportion or Elimination?
3. what are flagged accounts? how to understand this concept?
5. in HFM we load web objects data, what are they? is it specific to Web client or desktop client or for both? please list out all types of web objects.
6. While creating application profile we can find "Start year and Number of years". how many years Oracle has recommended? only 20 years or there is no such criteria?
7. While creating application profile we can find 6 frequencies knowing to my knowledge max we can use 4 1for Monthly, 2 for QTD, 3 for HYTD,4 for YTD. and now my doubt is that what other 2 we can use for? keeping in view of what other 2 frequency's the application has been designed for?

Answer 1

1) You propose deleting entity B, yet you said you require data for this entity. Do not delete the entity since once it has been deleted all data associated with this entity INCLUDING any intercompany transactions which another entity may have had with it, will be unavailable.
2) I'm not certain but I think [Proportion] comes first when considering execution of Sub Calculate. In general do not write rules which require a sequence between these two nodes, if this is your reason for asking the question.
3) "Flagged accounts" is not a standard expression. Possibly you are referring to the statement of "flagging an account" for a particular attribute. If so, this simply means to enable or set an account's attribute such as IsCalculated, or IsICP. This concept extends beyond the accounts dimension.
5) Not sure what you're looking for here. Oracle provides a great deal of documentation with its products, including an API guide.
6) There is no particular criteria. The most important consideration is selection of the start year since this can never be changed without rebuilding the application with a new profile. It is possible to add years to an application. HFM provides a utility for this with the 11.1.x release.
7) The number of frequencies available is directly related to the period structure you define in the application profile. Most applications use:
Periodic (= Monthly)
Quarterly
Yearly
I occasionally see Half Year though this is uncommon. Weekly applications can have an additional frequency, where Periodic = Week to Date, and then Monthly is above Periodic. I suppose in this case you could have five frequencies:
Periodic
Monthly
Quarterly
HalfYearly
Yearly
Daily is not recommended for HFM.
I recommend not creating more frequencies than you truly need. Although this doesn't seem to have an impact on application performance, it does present the users with more options to click through when choosing a point of view. Consider that every user every day will click on the point of view selector many times, so reducing the number of clicks required can have a large impact on your users.
--Chris