Professional Documents
Culture Documents
RELEASES YEAR
11.1.2.1 2011
11.1.2.2 2012
11.1.2.3 2013
11.1.2.4 2015
CREATE PROFILE -->> CONTAINS CALENDAR INTELLIGENCE PERIOD, YEAR AND VIEW
CREATE NEW APPLICATION
LANGUAGES --> UPTO 10 CAN BE ADDED
CALENDAR --> TIME PERIODS (INCLUDE HALF YEAR/QTR/month) AND YE
FREQUENCIES -->> PTD, QTD, HTD, YTD VIEW
period hierarchy gets created based on above
CUSTOM DIMENSION ( ATLEAST 2 IS MUST -->>> FROM CURRENCY AND
HFM METADATA
DIMENSION
DIMENSION MEMBER
EXCCHANGE RATE
USER GROUP
SECURITY
DIMENSION PROPERTIES
CURENCY DIMENSION
ENTITY DIEMSNION IS THE CONSOLIDATION DIMENSION OF HFM
DEFCAURRENCY
ALLOWADJS
ISICP INTEROMPANY TRANSACTION HAPPENS AT CHILD LEVEL
ALLOWADJFROMCHILDREN
USERDEFINED1
SECURITY CLASS
HOLDING
SEURITYASPARTNER FOR ICP PARTNER SECURTY CLASS
DEFAULT PARENT
ICP DIMENSION
CREATED IT DURING PROFILE CREATION WE CAN CLICK IMPORT AND LOAF THE PROFILE TO CREATE CUSTOM DIM
TO TRAcK THE CHANGES made to the actual data related to this account dimension member
RULE ON THIS ACCOUNT
PHASED SUBMISSION
HAPPENS AT CHILD LEVEL NOT AT PARENT LEVEL
CURTY CLASS
GENERALLY MTD
D LEVEL YTD BALANCE ARE CALCULATED AND AT PARENT LEVEL PTD BALANCE ARE CALCULATED
D LEVEL PTD BALANCE AND AT PARENT LEVEL CONSOLIDATED VALUE
APPROVAL PROCESS
VIEW FOR THE APPROVAL PROCESS
tain data that does not accumulate from one period to another, and do not translate. Headcount is typically a balance, as is Square Footage
se which are not currency-related, such as headcount, units sold, number of customers, days sales outstanding, number fo new customers,
balance, as is Square Footage, for reporting real estate information, for example.
ng, number fo new customers, etc. The entry of this data can be any way other data is loaded - either directly via load file into HFM, through
via load file into HFM, through forms, grids, journals, smart view, or FDM, among others I'm sure.
sub Calculate ()
HS.Account.Accounttype("AccountName") HS.Account.IsCalculated("")
HS.Account.IsICP("")
HS.Entity.isICP("")
HS.Entity.Member(""
HS.Scenario.Member("")
HS.Account.Member("")
HS.Custom1.Member("")
HS.Value.Member("") "<Entity Currency>" "<Entity Adj Currency>"
HS.Clear "A#ALL"
HS.Clear "A#"3010004.C1#Delhi
HS.Con
HS.OpenDataUnit Returns the data unit item to proces during consilodation, Translation
HS.Pcon
HS.Pown
HS.GetCell
HS.Exp
HS.Trans
.I#[ICP TOP].W#YTD.C1#All Cost Center.C2#TB
HS.Account.isConsoidated("") HS.Account.PlugAccount("")
HS.Period.isFirst("")
HS.Period.isLast("")
HS.Year.isFirst("")
HS.Year.isLast("")
ation, Translation
HFM Rule Basics - 1
Share
Rules gives the wings to HFM application and are incredibly powerful & flexible way to add calculations t
What is a Rule?
Ans: Rules are Combination of Objects & Functions/Methods
Hs is the namespace, Entity is the object, DefCurrency is the function, and E#SpecificEntity is the argume
We have 9 main Subroutines in Rules & under each Sub routine there are member of Functions to simpli
# We load all rules in single file as there is only replace option available and No merge option.
# Rules start with "SUB" and ends with "ENDSUB"
9 Rules are:
1. Calculation -------------------HS.Exp
2. Translation -------------------HS.Trans
3. Consolidation -------------------Call HS.Con
4. Allocation -------------------Call HS.Alloc
5. Input -------------------HS.Input
6. NoInput -------------------HS.NoInput
7. DynamicCalculation -------------------HS.Dynamic
8. TransactionsICP -------------------HS.SupportTran
9. EquityPickup ------------------- HS.PEPU
What is HS. ?
HS. = Hyperion Solution
HFM Rules
There are 2 main Functions
1. Load to the Database ---- HS.Exp
2. Retrieve from the Database-------HS.GetCell
Most Common Less Common Infrequent
Calculate Allocate ICP
Translate Input EPU
Consolidate
NoInput
Dynamic
Data is written only to the base level elements for the following dimensions:
- Account
- ICP
- Custom1
- Custom2
- Custom3
- Custom4 So only base members on the left hand side right hand side top level
Formatting the rules also means using the underscore (_) and colon (:) symbols. When using the undersc
StrAccount = HS.GetCell ("A#7999.C1#Sales") + _
HS.GetCell ("A#7999.C1#Marketing")
pecificEntity is the argument, to define the dimension in the argument, HFM requires the dimension label and a number sign (#).
s. When using the underscore, you are telling the script that the line ending with an underscore is continuing on the next line. For example
d a number sign (#).
on the next line. For example: