EPM FM-Student Manual Guide 11.1.2
Short Description
Hyperion Financial management Guide 11.1.2.4...
Description
Hyperion Financial Management
Hyperion Financial Management Developed in Partnership with and based on work by Eric Erikson, 123OLAP
HYPERION FINANCIAL MANAGEMENT 11.1. IMPLEMENTATION !OOT CAMP
Copyright Notice Copyright 2009 Oracle Corporation All rights reserved. Based upon the copyrighted works of: 12O!A" ".O. Bo# $%9 "ly&outh CA 9%''9
(o portion of this docu&ent &ay )e reproduced or trans&itted in any for& or )y any &eans* electronic or &echanical* including photocopying* recording* or infor&ation storage and retrieval syste&s* for any purpose other than the purchaser+s personal use* without the e#press written per&ission of Oracle Corporation.
Trademarks
,indows-,indows 2000-,indows "* and /icrosoft Office are trade&arks of /icrosoft Corporation. #cel* ,indows-,indows 2000-,indows "* and /icrosoft Office are products of /icrosoft Corporation. ss)ase is a registered trade&ark of Oracle. Other product na&es &entioned in this docu&ent &ay )e trade&arks or registered trade&arks of their respective co&panies and are here)y acknowledged.
Disclaimer he infor&ation in this docu&ent is su)ect to change without notice. (either Oracle Corporation nor 12 O!A" shall )e lia)le for errors contained herein or conse3uential da&ages in connection with the furnishing* perfor&ance* or use of this &aterial.
TA!LE OF CONTENT"
Intro#$ction A)out the Author..................................................................................................................................................................1
C%apter 1 & O'e r'ie( o) Oracle Hyperion Financial Management 4inancial 5eporting.................................................................................................................... 1-2 64/ 7tructure and 8esign.......................................................................................................... 1-2 What is a Dimension?.......................................................................................................... 1-2 Members.............................................................................................................................. 1-4 Hierarchies - The Family Tree..............................................................................................1-5 Point o !ie"........................................................................................................................ 1-5 Drillin# $% an& Do"n a Dimension.......................................................................................1-'
Oracle "/.............................................................................................................................. 1-' 64/ 7erver Architecture............................................................................................................ 1-' ()mmary.............................................................................................................................. 1-*
C%apter a * Creating Application+ * Pro)ile an# Meta#ata & Cla++ic Application "rofile .................................................................................................................. 2a-1 Creating the Application............................................................................................................ 2a-4 /anaging /etadata...................................................................................................................2a-5 !oading and #tracting /etadata ................................................................................................2a-+ Accounts............................................................................................................................... 2a-1, Application 7ettings................................................................................................................ 2a-12 Consolidation /ethods........................................................................................................... 2a-14 Currencies............................................................................................................................. 2a-15 Custo& 1$.......................................................................................................................... 2a-15 ntity................................................................................................................................... 2a-1*
7cenario................................................................................................................................ 2a-1 Organiation )y "eriod........................................................................................................... 2a-1+ "utting verything ogether...................................................................................................2a-2, ()mmary.......................................................................................................................... 2a-21
C%apter , * EPM Arc%itect "/A vs Classic ...................................................................................................................... 2b-2 PM/ 0om%onents.......................................................................................................... 2b-2
8i&ension /aintenance........................................................................................................... 2b- /ccessin# PM/............................................................................................................. 2b- Application /aintenance......................................................................................................... 2b-1,
Application 8eploy&ent..........................................................................................................2b-1 8ata 7ynchroniation.............................................................................................................. 2b-1 Application ;pgrade............................................................................................................... 2b-1* ask Auto&ation................................................................................................................... 2b-1 ()mmary.......................................................................................................................... 2b-1+
C%apter - * ata Loa#ing he (ative 4or&at..................................................................................................................... -1 8ata !oading Alternatives........................................................................................................... -' 8ata #tracting Alternatives ...................................................................................................... -11 Copying and Clearing 8ata ....................................................................................................... -1 ()mmary............................................................................................................................ -15 C%apter / * HFM R$le+ he Basics................................................................................................................................ 4-1
5epeating Code...................................................................................................... 4-11 asy "erfor&ance ?&prove&ent > ,ith 67 ................................................................................4-11 Calculating /anager................................................................................................................. 4-12 ()mmary............................................................................................................................ 4-12 C%apter 0 * Creating an# !$il#ing Li+t+ /e&)er !ists............................................................................................................................. 5-1
Creating !ists............................................................................................................................ 5-1
!oading and #tracting !ists .......................................................................................................5- ()mmary.............................................................................................................................. 5-4 C%apter * "%are# "er'ice+ 7ecurity Basics........................................................................................................................... '-1
"rovisioning ;sers and Other 4eatures ................................................................................................ '-12 C%apter 2 * HFM A#mini+trati'e "t$)) 64/ Copy Application > Classic Only ......................................................................................... *-1
64/ ;tilities............................................................................................................................. *-* 64/ Ad&inistration................................................................................................................ *-1, 7yste& /essages...................................................................................................................... *-1, ask and 8ata Audit................................................................................................................. *-11 ask Auto&ation..................................................................................................................... *-1 Other Ad&inistration /enu ?te&s ............................................................................................. *-1' "rocess Control and =alidations................................................................................................ *-1' Creating 8ata ntry 4or&s....................................................................................................... *-1+ 64/ ;ser note this &e&)er O(!I shows the eli&ination entries* not the full )alances. ;sually the final a&ounts going fro& the entity to its parent.
Mem,er+
/e&)ers in 64/ are the uni3ue ele&ents &aking up a di&ension. 7o&e sort of te#t or nu&eric descriptor defines every &e&)er. his is referred to as a la)el. 4or e#a&ple* in a custo&er di&ension* uni3ue custo&er na&es or nu&)ers &ay define the hierarchy of that di&ension. ach of these is a &e&)er. ?n addition* the regions that the custo&ers &ay )elong to @the groupings are also &e&)ers. ?n other words* &e&)ers are all the ele&ents that define the hierarchy of a di&ension. ?t is i&portant to understand that &e&)er na&es &ust uni2ue )e in 64/ within a di&ension. 4or e#a&ple* Cash in Bank and "etty Cash cannot )oth )e la)eled as account 100. 8epending on the di&ension there are various attri)utes or details that the syste& stores and provides different functionality accordingly. he &ost co&&on attri)ute is description* like the description for account 100 &ight )e DCash.E
Hierarc%ie+ & T%e Family Tree
6&&&P.. ,hat were those DchildrenE and DparentE references a)outQ 8i&ensions have a natural hierarchy associated with the&. As an e#a&ple*think of aco&pany that has sales offices in their entity di&ension. he lowest level of &e&)ers would )e the sales office: Charlotte* O&aha* 7an ose. he level a)ove that &ay )e a region: ast* /idwest* and ,est. he top level &ay )e the country. ach lower level of the di&ension is &ore specific. ?n 64/ ter&s the sales offices arechildren of the regions and the regions are parents of the sales offices. Another e#a&ple: this ti&e using the Account di&ension. otal Assets &ay )e &ade of Current Assets and !ong er& Assets. ;nder Current Assets are Cash* Accounts 5eceiva)le* and "repaids. Any &e&)er that does not have a child > the lowest level > is called a base level member. he hierarchy provides &ultiple )enefits. 4irst* the hierarchy defines the rollup. o the right* the children of Current Assets are added together. ?f there was a lia)ility account a&ong the asset accounts* like Allowance for 8ou)tful Accounts* 64/ would pick that up @account type is one of the attri)utes for accounts and do the correct &ath. Also* the hierarchy allows for easy report writing* like DChildren of Current Assets.E he advantage here is that if another child is added later* like ?nventory* then the report picks it up auto&atically. he third advantage is for drilldowns* &eaning a user can look at Current Assets and then click and see the detail underneath. here &ay )e &ultiple hierarchies within a di&ension. ntities are typically rolled up )ased on a legal hierarchy* a &anage&ent hierarchy* and others. Accounts &ay )e rolled together differently for ;7 this ðod is preferred for the initial )uild @like converting an e#isting 2*000 &e&)er chart of accounts into 64/.
!orking with &etadata &anager
he 64/ ,indows client is ,indows software that has to )e installed on the co&puter. his is the sa&e ,indows client where the profile is created. On the left are various tasks. he task involved here is /anage /etadata. he screen a)ove shows an entity structure. 4or Corporate* the highlighted entity* attri)utes are shown on the right. At the )otto& are ta)s for ree =iew @currently displayed and !ist =iew @shows everything in a ta)le > good for sorting and &aking &ore &ediu& scale changes.
Contains di&ensions and associated &e&)ers that are either shared
@availa)le for all applications or local @uni3ue to a specific application. (pplication 4ibrary > Contains and defines applications for the various products in the 6yperion suite.
Data Synchroni:ation> 8efines and controls syncing of data fro& one application to another* including di&ension to di&ension linking and &e&)er &apping. (pplication 9pgrade > Converts a DclassicE application into an "/A application. o )e used only once per application.
imen+ion Maintenance his ne#t section shows the &echanics of working in "/A. his is &eant as an introduction to working within the "/A !i)rary especially for di&ensions where little auto&ation will )e needed. ?n general* these are s&aller* fi#ed di&ensions that do not change fre3uently. )elow is a sa&ple file. (ote that the typical file e#tension is .A87.
(ote that the languages availa)le for the descriptions are handled )y another di&ension* Alias. here is no capa)ility within the software to e#port a fileG however* there is a separate utility that will do this. ?t is installed with the software and shows on the 7tart &enu as 7tart "/A 4ile also allows for the process to )e secured.
here are additional solutions for loading and e#tracting data that are developed* &arketed* and supported )y various Oracle-6yperion partners.
Copying an# Clearing ata ,ithin 64/ is the capa)ility to copy and clear data. hese can )e reached via the Browser =iew )y selecting asks* 8ata asks* then 8ata)ase /anage&ent. Below is the data copy screen. 7ource and destination points of view are selected. (ote that the copy is only fro& a scenario-year-period @&ultiple periods &ay )e selected co&)ination to another scenario-year-period @sa&e nu&)er of periods &ust )e selected. he entities and accounts cannot )e changed @so* this capa)ility would not have helped in the 7alaries-Benefits e#a&ple a)ove. he other options are si&ilar to data loading. A factor can )e applied to the copied data. 4or e#a&ple* if seeding the )udget scenario with e#penses fro& actuals then a factor of .9% could )e used to decrease e#penses %U across the )oard. A separate copy could )e done for revenues with a factor of 1.1 to increase revenue )y 10U. #change rates and cell te#t can optionally )e copied as well.
Copy and Clear only work for the -Entity Currency. #alue member*
o clear data* click on the Clear 8ata ta) at the top of the screen. 4or a selected scenario and year
&ultiple periods* entities* and accounts &ay )e cleared. Once the point of view is set* click Clear 8ata.
his functionality does not delete the ournals that are posted to the entities-accounts. ,hat if the data to )e cleared no longer is listed in the &etadataQ he re&aining ta) at the top is called 8elete ?nvalid 5ecords. ,hen &e&)ers are re&oved fro& &etadata and the data was not cleared first* the data is still there and this process gets rid of it. Ad&inistrators can run a scan to see what is there first )efore running the process for real. Below is the output of a delete > a scan looks the sa&e e#cept the top says D7canning ?nvalid 5ecordsPE
"$mmary
8ata can )e loaded and e#tracted fro& 64/ in a variety of ways. he key is to deter&ine the
C%apter
/ &ost appropriate process@es for the co&pany and apply the&. Once data is in* 64/ also provides tools for copying and deleting.
HFM R$le+
he focus of this Chapter is to review how calculations are created and &aintained in 64/. 64/ uses =isual Basic script for rules. he first part of the chapter reviews the )asic for&at and structure of the rules. (e#t the chapter shows various =isual Basic techni3ues that can )e applied. hroughout the chapter are e#a&ples of the &ost co&&on rule functions and )est practices on rule writing.
T%e !a+ic+= 5ules are written in a plain te#t file. he 64/ 5ules ditor includes integration with the application for validation purposes. Also* the functions are )uilt in and availa)le. (otepad and other te#t editors work ust fine as well* and using the Ad&inistrator "84 guide is reco&&ended to look through the functions for synta# and e#a&ples.
5efer to the )elow screenshot for the following. /ore will follow on each area. •
5ules are organied into parts called su)routines. 64/ looks for specific su)routines for specific purposes. Others can )e used to help organie the calculations.
•
7u) Calculate and 7u) 8yna&ic are two of the De#pectedE su)routines.
•
Co&&ents &ay )e added )y placing an apostrophe in front of the co&&ent.
•
•
otCo is an of ti&es. a varia)le* which is handy for storing soðing once and referring to e#a&ple it &ultiple 67.ntity./e&)er* 67.#p* and 67.8yna&ic are 64/ functions.
•
An ?f-hen state&ent is the &ost co&&on way of restricting when a calculation is run.
Gro$ping R$le+ * "$,ro$tine+ ,ith the su)routines there are several DspecialE ones that 64/ looks for. hese la)els &ust only )e used for the purpose intended. • •
•
•
•
•
•
•
Calculate > runs whenever calculating an entity. /ost rules go here. Translate > used to translate accounts with special rates. 5uns when the currency changes fro& =alue di&ension &e&)ers Nntity Curr otal to N"arent Currency. Consolidation> used to calculate ownership and eli&inations when default )ehavior is not ade3uate (llocation > can )e used to perfor& allocationsG can also )e used for other types of rules > e#ecution is separate fro& the consolidation process $nput > ena)les data input into parent level entities at Nntity Currency value &e&)er > not reco&&ended No$nput > disa)les data input into &e&)ers. 7trict li&its on the functions that can )e
used. Dynamic > used for calculations where the result will vary )ased on the =iew di&ension* like C? C@ CA E
Account Custo&1 Custo&2 Custo& Custo&$ ntity
$ ) S , ! 6
?nterco&pany "artner "eriod 7cenario =alue =iew Iear
A\Current!ia)ilitiesE ,hen using &ultiple to specify datae#a&ple* point* usethe a period @ . state&ent to connect.sets he order in which di&ensions aredi&ensions listed does not &atter.a 4or following one account e3ual to the co&)ination of the account* year* and period di&ensions. 67.#p DA\Beg5etarn Y A\ot5etarn.I\"5?O5."\!A7E
;aria,le+ he e#a&ple a)ove is very straightforward* )ut not fle#i)le. ?n so&e cases* and there are so&e )elow* a co&ponent of a calculation needs to dyna&ically change. &ariables can )e used to hold a string of te#t and then apply it later. Below* otalF is a varia)le. 67.#p DA\otalofFs Y E R otalF =aria)les can )e used a variety of places. One special type of varia)le* called a constant* is used to store a notchanging string that can )e used through all rules. he idea is that the string can )e written once and used throughout. ?f &aintenance is needed then the change only needs to )e &ade once* not every ti&e the constant is used. he cash flow e#a&ple near the end of the chapter de&onstrates this techni3ue.
he a&persand @ R is used to concatenate varia)les and te#t strings. As 67.#p is e#pecting one string to follow* the te#t string within the 3uotations and the varia)le are put together with the a&persand.
Re+tricting 8%en R$le+ R$n ,ithout restrictions* all rules would run for all scenarios* years* periods* value &e&)ers and entities. hat would &ost likely produce )ad results as well as slow down the application. 4or e#a&ple* verifying that the )alance sheet is in )alance only needs to )e done at input levels @the e#ception is currency translation > &ore on that later. Another restriction would )e to calculate soðing differently fro& year to year: in 200F the working capital calculation was changed to include long ter& de)t* for e#a&ple. Below are the &ost co&&on ðods used to restrict. #f $f " Then > the &ost co&&on and straightforward. ?f the entity is ABC then calculate IV. the e3uation is si&plethen a single line can )e usedGelse* &ultiple lines can )e used )y adding an nd ?f. he previous sentence also introduces the ne#t step of ?f-hen > lse. hese e#a&ples calculate ,C and B? &ultiple ways.
Select Case > so&eti&es ?f-hens can get stretched out a )it too far > too &any criteria and lse?fs. ?n those situations a 7elect Case works )etter. his e#a&ple calculates the nu&)er of days in each &onth )ased upon the period nu&)er @assu&es calendar fiscal year.
or " Next > 4or-(e#t is used to loop through a list of ite&s and perfor& soðing on each. his is very handy for &ore co&ple# calculations. his e#a&ple checks all )ase level accounts under (et?nco&e using a )uilt in &e&)er list called LBaseM and adds up @ignoring account type although that could )e acco&odated the a&ounts fro& any accounts that starts with an F. he neat thing a)out this calculation is that no &aintenance is needed whenever an new F account is added > it auto&atically gets picked up.
Custom Dimensions Self 5estricting
4or accounts that have a custo& di&ension assign&ent* calculations can )e written using only the custo& di&ension &e&)ers. ,hile see&ingly opening the calculation up to all accounts* 64/ only runs the calculation for accounts for which the custo& &e&)ers are valid. 67.#p DC1\OpeningBalance Y C1\ndingBalance.I\"5?O5."\!A7E his calculation would only run for accounts that have OpeningBalance and ndingBalance as valid Custo&1 &e&)ers. (ote: if the custo& &e&)ers are assigned to thousands of accounts* this synta#* as is* &ay not have ade3uate perfor&ance. "lacing the line within an 4or-(e#t loop using Open8ata;nit @&ore later to define the loop &ay i&prove perfor&ance. !hen to 5estrict
Tnowing when to restrict is as i&portant as knowing how to do it. Basically* calculations should only run when needed. he &ost co&&on restriction is to calculate things at only )ase level entities. Other restrictions can involve all of the other di&ensions. ,hen using 67.#p* the function used to calculate and store data @&ost co&&only used function* so&e di&ensions cannot )e on the left side: 7cenario* Iear* "eriod* ntity* and =alue. 4or e#a&ple* the rule 67.#p D7\Budget.A\Beg5etarn Y 7\Actual.A\ot5etarn.I\"5?O5."\!A7E has Budget on the left* which is not per&itted. he proper way of doing this rule is to use an ?f-hen to restrict when the rule runs. ?f 67.7cenario./e&)er Y DBudgetE hen 67.#p DA\Beg5etarnY 7\Actual.A\ot5etarn.I\"5?O 5."\!A7E nd ?f ?n the )elow e#a&ple* the calculations in the Calculate su)routine only run for )ase level entities and only at =alue di&ension &e&)ers Nntity Currency* Nntity Curr Ads* or N"arent Currency. Also* no calculations are run at L"roportionM* as &any applications do not re3uire the& at this level in the =alue di&ension* thus lowering the consolidation ti&e a little. ?n the newer versions of 64/ the consolidation rule setting of 5 in Application 7ettings takes care of this.
Common Calc$lation+ ,hile practically i&possi)le to discuss every possi)le type of calculations* there are several )asic and advanced calculations that appear in &any applications. ,here practical* the )asic calculation is shown here with generic la)els to get the idea across. 8epending on the situation so&e tweaking &ay )e re3uired to the )elow to produce the desired results. (ote: the first five are also in the a)ove e#a&ple. > > 7pening Balances> used for &ove&ent schedules* cash flow* )eginning retained earnings. "5?O5 and !A7 are keywords > not &e&)ers > that &ust )e capitalied.
67.#p DA\Beg5etarn Y A\ot5etarn.I\"5?O5."\!A7E ? > 6eartodate net income into retained earnings on the )alance sheet.
67.#p DA\CurrIeararnings Y A\(et?nco&e.,\I8E @ > Balance the balance sheet good internal control and helpful )efore currency translation > run this calc at Nntity Currency and any of the four adust&ent =alue &e&)ers if used.
67.Clear DA\BalanceE 67.#p DA\Balance Y A\Assets > A\!ia)ilities3uityE
A > Dollar 7#errides> used as part of currency translation to hold historical rate a&ounts for accounts where the a&ount should not change* like co&&on stock. (o &atter what the translated a&ount is* replace it with the dollar a&ount stored in the override account. Override
accounts should )e flagged with a type of Balance5ecurring so they don+t translate and so any a&ount entered carries forward to the end of the year. ?f 67.=alue.?sransCur hen 67.#p DA\Co&7tock Y A\Co&7tockOverrideE > Currency Translation (d/ustment> sa&e calc as )alance )ut different target account
?f 67.=alue.?sransCur Y rue hen 67.Clear DA\CAE 67.#p DA\CA Y A\Assets > A\!ia)ilities3uityE nd ?f > $mpact Status> good for causing ne#t year to re3uire calculation when current year data changes. his is i&portant when data is )eing rolled forward @\1 a)ove. ?f 2009 is recalculated then 2010 is i&pacted and re3uires recalculation. he 4?57 and ( are not &e&)ers of the period and year di&ensionsG they are special keywords that 64/ picks up and treats accordingly > they &ust )e uppercase.
?f 67."eriod.?s!ast and 67.ntity.?sBase hen 67.?&pact.7tatus D"\4?57.I\(E he 67."eriod.?s!ast restricts the calculation to run in only the last period of the year. ?f consolidation perfor&ance is an issue then co&&ent this out and co&pare the consolidation ti&es with and without and weigh the difference to the need for the control. > !riteToile > a special su)routine ena)ling co&&ents to )e written to a te#t file during rule e#ecution. Best used )y the ad&inistrator to de)ug new code* it can also )e used to e#tract data into a file or create e&ails )y writing the te#t file of an e&ail into the drop )o# of a &ail server. 4or the code* look in the rules file for the Co&&a application that is provided with the 64/ client software installation in the sa&ple applications. 4I? > there are e#a&ples in the sa&e file of &any other types of calculations. F > Cash low > there are several &oving parts to cash flow. 7tart with net inco&e @ie* C4S(et?nc Y (et?nco&e and then calc line ite&s to )ack out non cash "R! ite&s like depreciation. 4or changes in the )alance sheet* co&pare to last year+s ending )alance and do the &ath one way or the other )ased on account type. One approach is to si&ply list the accounts within the rule for each cash flow line ite&. Another approach is to use a user defined field on the )alance sheet accounts to indicate which line ite& they i&pact and then use a for-ne#t loop to cycle through the& and calculate the change. 7o&e ite&s will need to co&e fro& &ove&ent detail* like capital e#penditures > a change in fi#ed assets does not ade3uately capture capital e#penditures vs. disposals* retire&ents* etc. he net increase in cash is then added to the opening )alance. At the end is a co&parison to cash on the )alance sheet. !astly is a calculation to calculate the currency translation effect within cash flow* as the ending )alance will translate at the end of &onth rate and the cash flow line ite&s translate at the average rate.
7ee )elow for a )asic cash flow e#a&ple. (ote that the 4unction code at the )otto& is e#plained in &ore detail later in the chapter.
G > No$nput > for &any different reasons input &ay )e restricted fro& certain cells* whether related to data conversion* new accounts active for 2010 and )eyond )ut not earlier* etc. ?n this e#a&ple* a (o?nput rule is used to )lock input to the ?C" di&ension &e&)er L?C" (oneM for
interco&pany > data inlistthis &e&)er does not eli&inate> and canchapter cause user confusion. he rule uses a accounts dyna&ic account called ?C"Accounts,ith"lugs see the on creating lists. his rule would )e e#ecuted within the (o?nput su)routine.
>H > 7pen Data 9nit* Open 8ata ;nit is a specific 64/ function that gathers the specific
records that e#ist for a given criteria. 64/ does do a good o) of knowing when to calculate @like if an account e3uals another and no data e#ists in the source account then don+t try. 7o&eti&es though it is useful to li&it the scope of a calculation to where there is actual data. 4or e#a&ple* the e#a&ple a)ove that adds together the accounts that start with F &ight )enefit fro& using Open8ata;nit )ecause the rule would )e li&ited to cycling through only records with data to look for the FSSSS accounts versus cycling through all of the accounts. Below is an e#a&ple of Open 8ata ;nit )eing used to copy data into the current entity-scenario-year-period fro& another scenario.
F$nction+ * Repeating Co#e 4unctions are used to perfor& repetitive steps. A function differs fro& a su)routine in that it takes varia)les passed to it* perfor&s calculations* )uilds a string* etc.* and then returns a result )ack to the code that called it. A su)routine perfor&s the actions without returning a result and is used &ore for organiational purposes. he a)ove code for cash flow in \F shows how a function works. ?n the e#a&ple* the 84B @short for 8ifference 4ro& Base function is used to repetitively )uild a string that is passed )ack to the invoking code that perfor&s a 67.#p calculation. he result of using the function and the varia)les takes the lineP 67.#p DA\C4SAcct"ayE R gC4(ones R D Y E R 84B@DAcct"ayE and when the rule is run it turns intoP 67.#p DA\C4SAcct"ay.?\L?C" (oneM.C1\C4SCalculation.C2\L(oneM.
C\L(oneM.C$\L(oneM Y A\Acct"ay.?\L?C" opM.C1\AllCusto&1. C2\AllCusto&2.C\L(oneM.C$\L(oneM A\Acct"ay.?\L?C" opM. C1\AllCusto&1.C2\AllCusto&2.C\L(oneM.C$\L(oneM."\!A7.I\"5?O5 he code following the e3ual sign @Y is generated )y the function. he varia)les and the function not only &ake things &uch easier to read )ut reduce &aintenance @change the varia)le or function once instead of each instance and the a&ount of code to )e written @the code in the function will e#ecute every ti&e the function is invoked.
Ea+y Per)ormance Impro'ement * 8it% H" here is another way of writing all rules a)ove that use 67.SSSS. he ,ith state&ent tells =B 7cript to open the specified o)ect and keep it open. ,ithout ,ith* the 67 o)ect is opened and closed each ti&e it is used. he synta# looks like this > note the 67 is re&oved fro& each 67.#p line )ut the dot re&ains.
he ,ith &ust )e ended with an nd ,ith. Also* the ,ith-nd ,ith &ust )e added to each su)routine. he results have varied )ut one person has reported a perfor&ance i&prove&ent of over 10U to consolidation ti&es.
Calc$lation Manager ,ith the 11.1.1 release there is a new graphical calculation &anager. Calculations are written and &anaged via the "/ Architect interface and can )e deployed to applications si&ilar to di&ensions. he =B script ite&s a)ove can )e integrated into the graphical calculations.
?n Octo)er 200F several longti&e 6yperion consulting partners reported that they had not perfor&ed any i&ple&entations of this feature at client sitesG accordingly we reco&&end not using this feature for production use and do not include it in the course. here is docu&entation within the product to e#plain the features and usage.
"$mmary
5ules are written in =isual Basic script to create calculations in 64/. 5ules are grouped into su)routines* with 64/ looking for specific ones. A &odular approach > functions* varia)les > is reco&&ended for repetitive co&ponents and to reduce &aintenance and increase Dreada)ility.E 5eferring to the 64/ Ad&in guide chapter for the rule functions and their uses as well as looking through the sa&ple rule files for e#a&ples is very useful.
C%apter
0 Creating Mem,er Li+t+
he focus of this Chapter is to how to create and )uild &e&)er lists. !ists can )e used for a variety of purposes.
Mem,er Li+t+ A &e&)er list can )e created and used for a variety of activities: data e#tracts* data grids and for&s* rules* and filtering when selecting &e&)ers. !ists can )e static* like accounts 100* 110* and 120* or dyna&ic* like all accounts that start with 1. Both have their purposes. /e&)er lists are only created )y the ad&inistrator )ut can )e used )y all users. /e&)er lists are loaded to and e#tracted fro& 64/ in the sa&e &anner as &etadata and rules. /e&)er list files typically use the .!7 e#tension and can )e edited with (otepad or other te#t editor. (ote > changing the e#tension to .5! will ena)le the file to )e opened in the 64/ 5ules ditor with the proper color coding. ,ith 64/ there are so&e syste& &aintained lists. hese do not re3uire &aintenance and are not included in the e#tract-load. he na&es* like LBaseM* start and end with )rackets and have co&&on definitions when repeated across di&ensions. LBaseM* for e#a&ple* will list all of the lowest level &e&)ers in each di&ension @or )elow an optionally specified parent &e&)er. 8o not create lists that start and end with )rackets to avoid confusion with the syste& lists.
Creating Li+t+ /e&)er lists are written using =isual Basic techni3ues. here are two sections* called su)routines. he first su)routine* nu&/e&)er!ists* defines the nu&)er of lists for each di&ension and the la)els for each. he second su)routine* nu&/e&)ers?n!ists* defines the &e&)ers @for fi#ed or static lists or criteria @for dyna&ic lists for each list. Below is a si&ple &e&)er list that defines one list for the Account di&ension and one for the ntity di&ension. e#t preceded with an apostrophe @ ] are co&&ents and have no effect on the code. Co&&ents are reco&&ended for docu&enting the code for )oth rules and lists. he screenshots are divided to separately show each of the two su)routines > these su)routines &ust )e in the sa&e file when loading.
he first su)routine has two parts. 4irst* 8i& state&ents are used to define arrays that will designate how &any lists each di&ension will have. (ote: the syste& generated lists do not need to )e included. he second part creates the na&es for each list. he nu&)er in parentheses will incre&ent to add &ultiple la)els to the array. he 67.7et/e&)er!ists function DsetsE the nu&)er of la)els and la)el na&es in 64/.
he second su)routine is used to define the &e&)ers of each list. he &e&)ers can either )e static @like the account e#a&ple )elow or dyna&ic @like the entities.
he dyna&ic entity list will auto&atically pick up any new entities that are not ;78. he fi#ed account list will re&ain the sa&e until changed. (ote there are two functions used to add &e&)ers to lists: 67.Addntityo!ist and 67.Add/e&)ero!ist. hey do the sa&e thing )ut Addntity is for the ntity di&ension and Add/e&)er is for all other di&ensions. Addntity also allows for a specific parent to )e used for the &e&)er )eing added. here is also a techni3ue that can )e used to )uild a dyna&ic &e&)er list that uses the user+s point of view as input. 5efer to the Ad&inistrator+s others can )e created )y the ad&inistrator. !ists can either specify specific &e&)ers or use criteria to dyna&ically select the &e&)ers.
C%apter
"%are# "er'ice+
he focus of this Chapter is to review the &ain co&ponents of 7hared 7ervices. here are two &ain parts to 7hared 7ervices: security and lifecycle &anage&ent. 7ecurity is &anaged within 6yperion 7hared 7ervices. he chapter discusses provisioning users to log into the application and once they do restricting what they can or cannot do. After provisioning the chapter discusses li&iting the &e&)ers users can see and-or &odify. !ifecycle &anage&ent is a tool used to &igrate ite&s fro& one application to another.
"ec$rity !a+ic+ 9sers and 8roups ;sers are provisioned @&eaning granted access to the application within 6yperion 7hared 7ervices. ;sers are typically provisioned using their network ?8s > the connection )etween 6yperion and the active directory or !8A" server is esta)lished during the software installation. Alternatively* ?8s &ay )e created DnativelyE within 7hared 7ervices. 4or
64/ this ?8 is not use due to 7ar)anesO#ley co&plianceG plus* its one &ore andreco&&ended password for for the production users to re&e&)er. &ore on these )elow. when provisioning users or groups the ad&inistrator grants specific roles to the users. 4or e#a&ple* a user or group &ay )e provisioned to create ournals )ut not post the&. ;sers are
typically divided into groups )ased upon role that reflects )oth the product licensing and the controls-procedures that apply to the users. Classes > Classes are assigned to &etadata ite&s @see the &etadata chapter and we) co&ponents @grids* for&s* etc.. ;sers-groups can then )e granted various access levels to each class. ?f a user has no access to a class* then the user will not see any entities* accounts* grids* etc. that have )een assigned the class* likewise with view and &odify. 4or e#a&ple* a group of data grids &ay )e assigned a class that all users can view )ut not &odify. his ensures that the grids are not changed e#cept )y those with &odify access.
Pro'i+ioning 4+er+ an# Gro$p+ ;ser provisioning is perfor&ed in 7hared 7ervices. he ;5! will )e provided fro& the installation. After logging in with the default ?8 and password* the ad&inistrators should i&&ediately provision their own ?8s to )e 7hared 7ervices ad&inistrators. he screen )elow shows native users @this is a de&o application and not a production environ&ent > if it were production* there would )e a folder at the sa&e level as (ative 8irectory called /7A8 or soðing that would connect to the network users. 5ight clicking opens the &enu shown. (ote the choices will change depending upon the logged in user and the highlighted ite&.
nothing this. ,hen done* click 7ave in the upper left. Access 5ight Choices: • • • • •
None > (o access > user does not see that the ite& e#ists &etadata > 7ees that the di&ension &e&)er e#ists )ut cannot view-edit data )romote > =iew data for the di&ension &e&)er and pro&ote-reect in process control 5ead > =iew data for the di&ension &e&)er )ut not pro&ote-reect in process control (ll > /odify the ite& and pro&ote-reect in process control
he Add Alert )utton ena)les the e&ail notification for process control and interco&pany transactions. 4or process control* the software environ&ent &ust )e set up to send e&ails and these features ena)led on the scenario @set 7upports"rocess/anage&ent to A and on the user 5eceive &ail role. Also* theentity@ies user &ustand )e the assigned a proper review level* Allshort* or "ro&ote access Alerts to the security class assigned to the alert &ust )e ena)led here. ?n e&ails don+t happen unless all co&ponents are ena)led. he last ta)* 7ecurity 5eports* allows for reporting of the groups and users granted access. he reports are useful for docu&enting and reviewing security access as typically re3uired for 7ar)anesO#ley. 7elect the desired choices and click the appropriate for&at for the report.
T%e Ot%er 8ay >)or Cla++ic Application+? ?f working with a Classic application there is another way to do &ost of this. /anually doing everything one at a ti&e through the we) interface could take a while. 7ecurity can )e e#tracted out of the application* &odified in a te#t file* and then reloaded. he e#tract and load &enus and processes are located and work the sa&e way as &etadata load-e#tract* data load-e#tract* etc.
?n the sa&ple to the left* there are three users provisioned for the application and eight classes @including L8efaultM. 4ollowing are the role assign&ents. Only the assign&ents that are ena)led need to )e listed. 4or e#a&ple* de&oad&in is provisioned as the "rovisioning /anager and the Application Ad&inistrator. (e#t are security class assign&ents. On the left* Barry has )een given access to the classes )ut Click on the di&ension to see &e&)ers that are shared @under &ore than one parent. &ember 4ists > 7ee the output of &e&)er lists in each di&ension. ?f applica)le* provide a top &e&)er for the filter.
Base &ember Compare> "ick a di&ension and then select two parent &e&)ers. he utility will show )ase &e&)ers that are under the parent on the left and not under the parent on the right. Duplicates Below )arent> "ick a di&ension and then select a parent &e&)er. he utility will show any &e&)ers under the parent &ore than once. Statistics > "ick a di&ension and see statistics regarding the depth and nu&)er of
&e&)ers. Out of these ite&s the Base /e&)er Co&pare and 7tatistics are the &ost usefulG although* the others can )e the right tool for the right pro)le&. here is no close )utton: click on the in the upper right corner of the window to close and return to the &ain screen. 4ro& the &ain screen* selecting a di&ension fro& the dropdown will ena)le the three )uttons @note > entity does not ena)le the /e&)er !ist Builder. he &ost co&&only used of the three )uttons is /etadata =iewer.
Click on /etadata =iewer to see the di&ension in a tree view.
he one feature used here is to send the &etadata to #cel. here is no need to e#pand the levels first: the utility will do that. 4ro& the a)ove screen* clicking on 7end to #cel will generate the file )elow. (ote > there is a pro&pt to print the file. his pro&pt is for printing to #cel* not printing to paper. he #cel file is a very easy way of distri)uting the &etadata structure to users for review* reference* etc.
HFM A#mini+tration ,ithin the we) interface there is an Ad&inistration &enu that has several ite&s of note. he ne#t several ite&s discuss various pieces.
"y+tem Me++age+ 64/ creates various &essages as tasks are )eing perfor&ed. hese &essages may @&any ti&es they don+t provide so&e insight into pro)le&s when e#perienced. 7elect the &enu ite& and provide a date range and click =iew.
?n this e#a&ple OoogaBooga is an invalid account. ?f we click on the D?nvalid P BoogaE we get the following:
he &essage is rather cryptic )ut on the last line on the far right there is a line fro& the rules file that needs to )e corrected.
Another way to access the sa&e &essages is another utility in the Consultant ;tilities folder: 64/rror!og=iewer.e#e. fro& the application server.his does not re3uire an ?8 or password and is typically run directly
Other &essages will show here. 7o&eti&es the user ?8 is included* so&eti&es not. ,hen re3uesting assistance fro& technical support so&eti&es the infor&ation in this file will )e re3uested. he file is called 6svvent!og.log and is located in the 7erver ,orking 4older of the installation folder on the application server.
Ta+9 an# ata A$#it 4ro& the Ad&inistration &enu there are two audit tasks: ask and 8ata. he ask Audit shows when users log in* where they go* and when they log off. he list &ay )e filtered )y date* server* user* and task. he ask Audit is useful for verifying that users are logging in and doing what they need to do. ?t can also help indicate what was happening within the application at a particular ti&e if a pro)le& occurs.
he 8ata Audit is useful for reviewing changes to data. he feature &ust )e ena)led in &etadata for BO6 scenarios and accounts. 8ata Audit is useful for confir&ing which user changed which data point and how @data load* data entry* ournal entry and when. 7electing 8ata Audit fro& the Ad&inistration &enu opens the screen.
Clicking a record will open the detail and show all of the changes to the cell.
4or )oth ask Audit and 8ata Audit* the reco&&ended practice is to e#tract the records and store offline and delete the online records periodically.
Ta+9 A$tomation ;nder the Ad&inistration &enu is a selection called /anage askflows. askflows allow for steps to )e scheduled to run either ust once or on a regular schedule. he &ost popular choice is consolidations. 7electing /anage askflows opens a window showing a list of any e#isting task flows.
Clicking (ew will open the window to create one. nter the la)el* confir& the application* and enter a description. Click 7u)&it.
he resulting window shows three ta)s at the top that need to )e co&pleted. (ote that each
additional stage will only have two > the third one applies to the first state only. ach step in the process is called a stage. On the general ta)* na&e the stage @or leave it as 7tage1* 2* etc. and provide an ?8 and password.
Click on the "rocessing ta) to go to the ne#t ta). his ta) has a dropdown for the application @not all are 64/ > select the desired application. (e#t* the Action dropdown will display the availa)le tasks for the application.
After selecting an action* the list of para&eters will show the ite&s that need to )e co&pleted. 8epending on the ite&* the choices &ay )e a ;5! @click dit to &ake changes* =aria)le passed fro& another stage @like a filena&e* or "icklist @a second dropdown will appear with choices. ?n the case of consolidations* the ;5! is used for the point of view and a picklist provides the consolidation type.
On the first stage only clicking on 7tarting vent will open the last ta). 7tarting event is used to
schedule the task. ask flows can )e scheduled to occur &onthly* daily* etc. with optional ending infor&ation. ask flows can always )e started on de&and fro& the &ain screen.
ach stage &ust also have a link. A link is used to pass control fro& one stage to another. he link can )e si&ple* like 7tage 2 starts after 7tage 1 finishes. Or* links can conditionally start the ne#t stage. !ike if a data load is successful then run a consolidation. 6ighlight the starting stage and click Add !ink. "rovide a la)el and description for the link as needed and select the receiving stage @what should run ne#t.
On the Condition ta)* use the dropdowns to )uild any conditions that &ust )e &et. A stage can have &ultiple links to it and a stage can have &ultiple links to other stages. 4or e#a&ple* a data load stage &ay have a link to a consolidation stage if the load is successful and a nd task flow if the data load was not successful.
he last stage should have a link to nd. Also* stages should have links to nd if a stage finishes unsuccessfully.
Ot%er A#mini+tration Men$ Item+ 9sers on Systemsi&ply lists the users and provides so&e infor&ation a)out where they are. 4ro& this screen users can also )e logged off )y the ad&inistrator.
5unning Taskssi&ply lists the tasks running at a given &o&entG however* &ost tasks do not show up here. he one key task that does is consolidation. ?f several users call at one ti&e and say their consolidations are taking a long ti&e* 5unning asks would )e where to go. &anage Ser#ers and (pplicationscan )e used to disa)le user logins into the application. he idea is that logins are disa)led* users are then logged off )y ;sers in 7yste&* the ad&in does &aintenance changes* and then ena)les the logins. ,henever &aintenance is loaded the users are auto&atically logged off anyway* )ut this ðod is a )it &ore structured.
Proce++ Control an# ;ali#ation+ ,ithin 64/ there is a process that can )e used to collect an electronic signoff that is used to indicate the data is Dgood.E Called process control* this signoff has a few different &oving parts. Coverage of this topic is in two places: here and in chapter of the nd ;ser section. here are several design 3uestions that &ust )e answered )efore )eginning the setup. •
•
•
•
•
,hich scenarios will re3uire the featureQ /ay)e Actual will use process control and 4orecast and Budget will not. ,hat edits &ust )e passed* if any* )efore signoff can occurQ he &ost co&&on one is that the )alance sheet is in )alance. Are there groupings of accounts that will )e pro&oted on different schedulesQ /ay)e the )alance sheet and profit and loss accounts are pro&oted first and then statistics and &ove&ent detail data are pro&oted later. his feature is called phased su)&issions. ,ho will )e involved in the signoffQ 7ignoff is driven )y the entity structure and parent entities cannot )e signed off unless the children are also. ypically a local accountant signs off first* then a corporate accountant* then a controller-=". ,ill users )e a)le to see a unit+s data )efore signoffQ By assigning or not assigning access to review levels in security* an ad&inistrator can control when a user would see data. 4or
e#a&ple* a corporate controller &ay not see data until the nu&)ers have )een loaded and pro&oted )y the local accountant and the corporate accountant. Or* the controller &ay have access i&&ediately upon loading. he setup of process control is in &etadata and security. ,ithin &etadata* scenarios &ust )e ena)led for process control @the attri)ute is called 7upports"rocess/anage&ent and a &a#i&u& nu&)er of review levels @the attri)ute is called /a#i&u&5eview!evel &ust )e specified. 4or 7upports"rocess/anage&ent the choices are I @yes* ( @no* and A @yes* with generation of e&ails. he Classic version is shown )elow.
he /a#i&u&5eview!evel attri)ute is a nu&)er fro& 1 to 10. (O: 5eview 1 has so&e draw)acks fro& a security standpoint @not fully controlla)le so &ost i&ple&entations skip over it and focus on 5eview 2 through 5eview 10. ?f review levels are needed then the attri)ute for review levels should )e $. ,ithin the application settings* there are settings for the phased su)&issions @one group of accounts now* another group later and the validation account for each. "hased su)&issions can also )e ena)led for the custo&s and ?C" di&ensions. On the account* ?C"* and custo& di&ensions there is an attri)ute called 7u)&ission the period is not open and users cannot load data* see any data that has )een loaded )y the ad&inistrator* etc. he ad&inistrator or review supervisor is responsi)le for starting the period. •
• • • •
•
irst )ass > the period is open and users can load data. 5e#iew >>H > practically 210* users have loaded data and pro&oted. Submitted > the data has reached a su)&itted level. (ppro#ed > data has )een approved.
)ublished > the data has )een Dpu)lished.E Only ad&inistrators can &ake changes. Also* data &ust )e at this level )efore the entity can )e locked. !ocking an entity prevents recalculation-reconsolidation of data after rule @e#cluding dyna&ic accounts or entity hierarchy changes.
?/"O5A( (O > parent accounts and parent custo&s are not locked* as these ite&s are always calculated Don the flyE and are not stored data.
?n a typical setup* the ad&inistrator will start the period* users will pro&ote* and then the corporate accountant will su)&it. !astly* the highest level signoff or the ad&inistrator will pro&ote to "u)lish. his is )y no &eans the only route. 4or infor&ation on the validation account and the actual pro&otion steps go to chapter of the end user section.
Creating ata Entry Form+ 7o&eti&es data cannot )e loaded fro& a file and &ust )e &anually entered. 4or reclasses* accruals etc. a de)it-credit style ournal is preferred @in so&e environ&ents re3uired. 6owever* for headcount* statistics* etc. a data entry for& is the )est approach. ?f ournals were used* users would need the a)ility to create un)alanced ournals: not typically reco&&ended. he data entry for&s can )e created )y the ad&inistrators and sufficiently control the input of data to prevent )alance sheet and profit R loss accounts fro& )eing i&pacted. o prevent input into these accounts* end users should not have the a)ility to create-&odify data entry for&s. As an e#a&ple* the data entry for& )elow is for entering headcount. he point of view is &ostly grayed out* &eaning the di&ensions are locked and cannot )e changed. ,ith this for& the user can only change the scenario* and there the availa)le selections can )e li&ited.
o create a for&* navigate to the /anage 8ocu&ents screen > either fro& the Ad&inistration &enu select /anage 8ocu&ents* the 8ata 4or&s link on the left* or the first icon to the right of #plore on the tool)ar.
Click on the 8ata 4or&s ta). (ote that a&ong the )uttons )elow the ta)s are )uttons to load and e#tract > useful for &oving for&s across applications. ?n addition to creating for&s* fro& here for&sta)s candata alsoentry )e deleted* and addedinto to the user+s favorites &enu. !ike the ite&s on the other for&s edited* can )e organied folders. Click on the (ew )utton to open the for& )uilder. "rovide a la)el* security class @typically a class is assigned that users can view )ut not change* description* and instructions. he instructions will appear when users click an icon on the for&. 6/! tags* such as the N) and N-) can )e used to for&at the te#t > the N) tag puts things bold in type. Click (e#t to go to the ne#t ta).
4ro& the "O= ta) the point of view is controlled. here are two colu&ns. he colu&n on the left* /e&)er* is used to hardcode the di&ension to a single &e&)er. he ite& will show on the point of view )ar and will )e grayed out. he second colu&n* 7electa)le* is used to allow users to select a &e&)er. ,hile a single list &ust )e selected* the list can )e adusted to li&it the selection. 4or e#a&ple* the ZLBaseM[ selection )elow for ntity li&its the selection to all )ase level entities. ?f the selection was Zurope.LBaseM[ then the selection would )e li&ited to only )ase level entities
under urope. 8i&ensions that are not filled in here should )e in either the rows or the colu&ns of the for&. Click (e#t to go to the ne#t ta).
he Colu&ns ta) controls what di&ension@s are specified in the colu&ns. ach colu&n can have a different selection* either a list @col 1 or a specific &e&)er @col 2. Below* each colu&n can )e scaled* for&atted differently* etc. 5efer to the software docu&entation for the options > there are &any functions that can )e used to control the look and functionality of the for&. Click (e#t to go to the ne#t ta).
he 5ows ta) is very si&ilar to the Colu&ns ta). After co&pleting click (e#t to go to the ne#t
ta).
he 8etails ta) provides various settings that control how the for& looks* such as suppression and repeating row-colu&n headers. he )est approach is to leave these set to the defaults and change as needed after reviewing the co&pleted for&. Click (e#t to go to the ne#t ta).
he 6eaders ta) is used to control how the row and colu&n headers are presented. Click (e#t to go to the ne#t ta).
At this point the for& can )e saved. he last ta)* 7cript* shows how the for& is stored. (ote that this script can )e edited directly if desired. ?f the for& needs to )e longer than 99 rows then working with the script is re3uired* as the for& )uilder does not go larger than that.
Capa)ilities within for&s: • • •
•
Basic calculations to )e done on the for& itself Colu&n showing cell te#t. !inking one for& to another. An input for& for sales volu&es &ay have a linked for& for the interco&pany sales account @would )e specified on the interco&pany sales account row on the 5ows ta) of the for& so that when the row header is clicked a second for& launches that lists the ?C" di&ension &e&)ers. he point of view is carried over to the second for&. Bolding* italics* custo& headings* etc.
HFM 4+er Gro$p+ he 6yperion 7olutions 4inancial /anage&ent group on IahooH has over K%0 &e&)ers* &ainly ad&inistrators and consultants. /e&)ers can post 3uestions and receive answers fro& the group. !ogging into IahooH groups is not needed as the correspondence can all )e done via e&ailG however* a free IahooH ?8 will )e needed. Also* the past correspondence is archived at IahooH and can )e searched: there is ' years of history availa)le. he group is &oderated and potential &e&)ers &ust apply @)asically stating that they are a 64/ ad&inistrator for IV co&pany and wish to oin the group. 4or &ore infor&ation go to http:--tech.groups.yahoo.co&-group-hsf& . Other groups e#ist for various co&ponents of the Oracle "/ suite: 48/* "lanning* 4inancial 5eporting* etc. Another source of assistance is local user groups. hese groups &eet regularly and can )e a source of local assistance and networking. )est done in a test application and verified )efore o loading into production. And the sa&e change re3uest for& a)ove should )e used. 5eview updates fro& Oracle and deter&ine the need to install upgrades and o patches. 7o&e patch releases fi# critical issues and should )e installed pro&ptly to avoid pro)le&s. !arger releases are &ore involved in ter&s of upgrading and the need to perfor& such should )e evaluated )ased on the new features. esting the upgrade withenviron&ent. test hardware is highly reco&&ended )efore changing the production
C%apter
3 HFM En# 4+er !a+ic+
he focus of this Chapter is to review the )asic tasks that end users typically perfor&: working with tasklists* data grids* and data for&s* and entering ournal adust&ents. 7o&e of these functions &ay not )e re3uired )y a co&pany* so check with the ad&inistrator for the e#act close process.
Logging In an# Logging O$t he ad&inistrator will esta)lish security for all users* specifying what users can see* change* and do. A user &ay only see part of the co&pany and )e a)le to change only a su)set of that part. Also* so&e features in the software &ay )e disa)led for a particular user. Check with the ad&inistrator for any 3uestions or difficulties. ;sers log into 64/ through the 6yperion ,orkspace. he ad&inistrator will provide the we) address. ypically the sa&e ?8 and password that users use to log into the co&puters and network are used for6yperion. the login. ?f the password is locked or the ?8 is deleted then the user will not )e allowed into
he resulting page will show the 5epository* a listing of reporting docu&ents and folders. he &enu and tool)ar across the top provide navigation to &any different areas and tasks. he first ti&e a user logs in* they should set their "references. he ad&inistrator will provide direction on the selections. hese preferences can )e reached fro& the 4ile &enu Dwithin the windowGE that is* on the 6yperion &enu-tool)ar and not the 4ile &enu that is part of ?nternet #plorer. o access 64/* click on the (avigate &enu* then select Applications* then Consolidation* then the appropriate application. 8epending on the user+s security and the Oracle "/ &odules installed* the ite&s listed &ay )e different and-or not accessi)le.
At the )otto& of the screen* ta)s will appear as a user goes into 64/* runs a report* etc. (avigation across &odules can )e done si&ply )y clicking on the appropriate ta).
,hen ready to e#it* click on the 4ile &enu within the window and select #it. his action will not only close the window )ut will also properly log the user out of 6yperion. here is also a )utton on the tool)ar for logging out.
Ta+9li+t+ ,hen selecting the application* users will )e directed into 64/. 8epending on the security provided to the&* they will &ost likely see a dropdown on the left with a list of tasks. hese tasklists are designed to guide the users through the appropriate steps. Clicking the dropdown will )ring up all availa)le tasklists. Clicking the arrow on the right a)ove the dropdown will change the user into )rowser view* where all ite&s &ay )e found @without the navigation provided )y the tasklist.
he gold arrows a)ove the dropdown on the left will toggle )etween "roect =iew @using asklists and Browser =iew @navigating to all ite&s
he ,82 tasklist is shown in "roect =iew. All availa)le tasks-docu&ents can )e found Any other tasklists would appear in the in Browser =iew. dropdown.
Creating Ta+9li+t+
o create a tasklist* click on the /anage 8ocu&ents icon on the tool)ar or select /anage 8ocu&ents fro& the Ad&inistrator &enu and go to the asklists ta). Click (ew asklist to create a new one or check the )o# on the left of an e#isting tasklist and click dit to view and change the included ite&s.
Below is the detail for the Budget ;ser tasklist a)ove. he ite&s &ay )e reordered )y highlighting
an ite& and using the )lue arrows on the right. Also* a user &ay select a tasklist to )e their default* &eaning when they log in they are auto&atically presented with the tasklist.
A##ing an# "a'ing Ta+9li+t+
he Add dropdown allows for additional ite&s to )e added. he list shows the type of ite& > selecting a type will provide the appropriate window for the user to find and select the desired ite&. (ote that an e#isting tasklist &ay )e included in another tasklist > no need to Drecreate the wheel.E 7aving the tasklist when co&plete will provide a window in which the user provides a la)el and description. A security class &ay )e chosen that will restrict who can view and &odify the tasklist and the tasklist &ay )e &arked as private. /arking as private will hide the tasklist fro& all users e#cept the creator and the ad&inistrator.
ata Gri#+ ?n &any ways data grids are the heart of 64/. 4ro& data grids users can review and analye data* change data @security allowing* consolidate @run the process that adds the children of a parent entity together* and other tasks. And the key to getting the &ost fro& data grids is understanding the di&ensions. ,hen creating data grids users place di&ensions in either rows or colu&ns. Any di&ension not placed such is left in the point of view* &eaning that a single &e&)er will )e used for each di&ension and &ay )e changed at any ti&e to see soðing else.
&e&)ers evenly or )ased on the seasonality of any e#isting data. Cell is an invalid data intersection: listing interco&pany partners for a non interco&pany account* for e#a&ple.
7o&eti&es grids are created for oneoff or ad hoc analysis and then are si&ply navigated away fro& and not saved. ?f the grid for&at will )e useful again then the grid should )e saved. ;se the disk icon on the tool)ar to save the grid. ,hen saving a grid* provide a la)el and a description. A grid &ay also )e assigned a security class* &eaning users that have view or &odify access to the selected class will )e a)le to use and &odify* respectively* the grid. Check with the ad&inistrator for infor&ation on classes. !astly* the grid &ay )e &arked as private* &eaning only the creator and the ad&inistrator can see the grid. he concepts of using security classes and the private setting help to &anage the nu&)er of grids that a user &ay see. 4olders &ay also )e used to arrange the grids. he ad&inistrator will provide guidance on the desired procedure@s.
Common ata Gri#+
4abel
5owDimension
Column Dimension
Accounts
Account
"eriods @/onths
)urpose
used to view-pro&ote-reect entities 7how consolidation detail of data fro& entity to its parent
ata Entry * M$ltiple 8ay+ 8ata entry &ay )e acco&plished a variety of ways. 8ata grids &ay )e used* and have so&e useful spreading across period features that are handy for forecast or )udget input if Oracle "/-6yperion "lanning is not in use. 6owever* internal control and audit policies &ay prohi)it the use of data grids for input due to the possi)ility of changing data loaded fro& the general ledger. ?n &ost cases* general ledger data is loaded and not &anually entered. 64/ provides for two other types of data input. here is a variety of ðods used to load data into 64/ )esides &anual entry. #cept for data entry for&s @ne#t these are not covered in this class. he ad&inistrators will provide guidance in this area.
ata Entr y Form+ 8ata entry for&s look si&ilar to data grids in that there are rows and colu&ns. 4or&s do have several advantages:
•
4or&s are &ore ad&inistrator controlled* &eaning the selection of di&ensions can )e
•
• • •
restricted. A user &ay have the opportunity to input data to a headcount account )ut not cash or revenue. 4or&s &ay )e e#ported fro& 64/ to /icrosoft #cel* data entered there* and then the data i&ported. he #cel work)ook that is e#ported is highly protected @no changes are allowed )ut the input &ay )e worked on offline. ?nstructions &ay )e placed on for&s to provide assistance to the users. 4or&s are easier to print with a satisfactory output. 7i&ple calculations &ay )e placed on the for&s to provide assistance-infor&ation. ,hat for&s lack are the easytochange and analysis capa)ilities of data gridsG therefore* each has their place.
A sa&ple data for& is )elow.
he )uttons on the lower tool)ar allow users to su)&it the data after entering* calculate the entity* enter cell te#t* get instructions provided )y the ad&inistrator* e#port to and i&port fro& /icrosoft #cel* and turn on suppression options. he cells in the for& &ay also )e right clicked to show the cell infor&ation and to enter cell te#t. he i&portant step to re&e&)er withwith data unsu)&itted entry for&s isinput to su)&it the data. heand firstal&ost icon on tool)ar a)ove is 7u)&it 8ata. Cells are dark yellow anythe navigation away fro& the screen will create a warning &essage. he online help provides infor&ation on how to create data for&s. the first co&&on parent. An interco&pany )alance )etween Office A1 and Office B1 will not eli&inate until otal Co&pany. 8ivisions A and B will show these interco&pany )alances when reporting. Along with the account* 64/ uses the interco&pany partner di&ension when storing the data. he partner is used in the consolidation process to know when to create the eli&ination as the data aggregates up the entity hierarchy. li&ination entries are created after translation to the parent entity+s currency. ;sually the interco&pany relationship is a set of one or &ore accounts co&pared to another set of one or &ore accounts* like interco&pany receiva)les vs. interco&pany paya)les. Another type of eli&ination is onesided* where there is no second set of accounts. he co&&on e#a&ple is interco&pany sales* where the sales are eli&inated and an offset is created under cost of sales. ither way* the ad&inistrator will have specified an account to store any out of )alance fro& the relationship. he data in this account DsurvivesE after eli&inations if the relationship is out of )alance. 4or e#a&ple* Office A1 records a receiva)le fro& Office A2 of 100 and Office A2 records a paya)le to Office A1 of 9% > )oth are ;7 dollars. At 8ivision A* the receiva)le will )e eli&inated* the paya)le will )e eli&inated* and the surviving account will )e %. Once the pro)le& is reconciled and the data is reconsolidated then the eli&ination entries will )e re)ooked and the surviving account will )e ero. 64/ refers to this surviving account as the Dplug account.E 64/ provides a special reporting facility for analying interco&pany )alances. Additionally* interco&pany eli&inations &ay )e viewed )y using data grids.
R$nning an Intercompany Report After logging into 64/* go to /anage 8ocu&ents. 4ro& here users select the 5eporting ta) and then ?nterco&pany fro& the dropdown. (ote the sa&e dropdown can select ournal reports fro& a)ove which can )e created* saved and ran directly fro& here.
;sers can create their own reports or use an e#isting one. ypically the ad&inistrator will create and secure reports for each interco&pany relationship. ;sers can override the settings to &eet their needs when running the reports without per&anently changing the settings. ?f a particular group of settings is always used then a user should consider saving their own report. Clicking on the report la)el* like ?CSransS5pt a)ove* will run the report. A popup window will appear allowing the user to select the output for&at for the report. ?f a custo& te&plate has )een i&ple&ented then this &ay )e selected fro& the second dropdown.
(e#t* a window will )e presented where the user can override the settings.
he "O= is usually always overridden to provide the appropriate &onth and year. he )elow screenshot is the sa&e as a)ove* with various settings overridden. he key to the overrides is to check the )o# to the left of each option.
/ost of the options are selfe#planatory. he ones to particularly &ind are: •
=alue di&ension @last part of point of view > shown as ;78 a)ove. Changing this will control the currency that is used on the report. A report that shows a Canadian unit co&pared to a 7wedish unit would not )e useful if each entity is shown in Nntity Currency their local currency. 7electing either CA8 or 7T or even ;78 or ;5 as the currency would )e appropriate.
•
ntity and hese selections of entities and partners that will )e included in "artner. the report. ?n the e#a&pledictate a)ove*the thesetentity list ?C" ntities is used to include all entities flagged to )e interco&pany partners. (ote this is a special type of &e&)er list that is typically created )y the ad&inistrator > if the list does not e#ist then use the syste& generated L6ierarchyM. he other co&&on selection is to use a specific entity as the entity and then the ?C" ntities list for the partners. his is useful when a particular entity is reconciling their )alances with everyone else. Clicking OT will run the report. ,hen generating the interco&pany report* 64/ will allow an entity to see another entity+s data when the re3uesting entity is the partner. 4or e#a&ple* Office A1 typically cannot view Office A2+s dataG however* when running the report* the )alance that A2 has )ooked with A1 will )e visi)le. his )ehavior* while typical* can )e changed* so check with the ad&inistrator if the result works differently. he resulting report shows the details and options in the header. his particular relationship is a onesided eli&ination of interco&pany sales. he line ite&s are shown )elow. he report can )e printed > if wide then change the printing preferences to landscape.
?f set up in the co&pany+s installation of the product* an e&ail &ay )e sent to the appropriate person directly fro& the report. Click on the envelope icon located on the left of each su&&ary row.
CreatingMo#i)ying an Intercompany Report All of the ite&s a)ove regarding running an interco&pany report also apply to creating a report. 4ro& the /anage 8ocu&ents screen click (ew 5eport.
he resulting window is si&ilar to the override options window a)ove with the addition of the for&at and te&plate options at the top and the accounts at the )otto&.
he accounts fields are used to specify the set of accounts that are to )e co&pared. ,hen possi)le* use the plug account. By specifying the plug account a report will auto&atically include all accounts in a relationship and will print additional details on the report. ,ithout the plug* it is possi)le to o&it an account that is eli&inated against the others and the report will not display the entire eli&ination and )e incorrect.
(ote that the plug account also specifies the di&ensions Custo&2* Custo&* and Custo&$ )y the references to C2* C* and C$ &e&)ers. ?f the di&ension is not used or the detail is not needed on the report* it is )est to specify the& here for )etter perfor&ance. ,hen clicking Add* a dialog )o# will walk the user through the account and custo& di&ension choices. Custo&1 is not
placed in this field as its detail is desired for the report. 7uppressing the custo& di&ensions @in the &iddle of the dialog )o# does not produce the sa&e effect. he inclusion of the custo& &e&)ers here restricts the records that 64/ searches through and can greatly i&prove the perfor&ance of the report.
Proce++ Control Once a user loads data @or its loaded for the& and interco&pany )alances have )een reconciled and adust&ents have )een &ade* the data is ready for consolidation into the co&pany+s nu&)ers. "ractically speaking* consolidations are perfor&ed &any ti&es throughout closing with top level analyses )eing perfor&ed while the data is co&ing in and changing. 64/ does provide a final signoff or pro&otion step. his signoff lets the people responsi)le for the parent entity know the data is ready and is considered final. he pro&otion also starts li&iting the users who can &ake changes until the data has )een co&pletely signed off and is in a Dpu)lishedE state. "rocess control can )e perfor&ed either in a data grid @)y right clicking a cell for the appropriate scenario* year* period* and entity and selecting /anage "rocess or in the process control screen: on the left select asks* 8ata asks* and then "rocess Control at the )otto&.
he resulting screen uses a point of view for the scenario* year* and period. One or &ore entities can )e shown in the list )y selecting the top &e&)er. 4or each entity the screen shows the current review level* a pass-fail indicator* validation* calc status* and CA status )y su)&ission phase.
7u)&ission phase is a feature where different accounts and-or custo& di&ensions can )e su)&itted in different groups. 4or e#a&ple* the )alance sheet and profit and loss accounts &ay )e signed on in phase 1 and supple&ental accounts in phase 2. ?f the pass-fail indicator is a s&all # surrounded )y a red circle and not a check &ark surrounded )y a green circle* so&e action is re3uired )efore pro&oting. he reasons for the failure are either a validation edit has not passed or the calculation status is not OT or OT 7C. he CA status
provides a warning if there are any unposted ournals for the entity. ?n the case a)ove* the validation edits are not &et. By clicking on the # in the circle we get a screen showing the validations.
he edits listed will differ fro& co&pany to co&pany )ased on the closing process. ?n the e#a&ple* flash @preli&inary close data has not )een provided for three accounts.
he &issing data has )een provided )ut the validation flag has not changedG also* the calculation status has changed fro& OT to C6* &eaning changed. 6ighlighting the row and right clicking will provide an option to calculate. Also* the tool)ar )elow the point of view provides all processing options.
,ith the status now all good* we can pro&ote. Below uses the tool)ar to find "ro&ote.
he review level is the current level of signoff. ;sers are provided with a specific signoff level. 4or e#a&ple* division accountants &ay )e 5eview * corporate accountants &ay )e 5eview %* and the &ay )e indicates 5eview K. 8ata Dpro&otedE fro& one review level to another. hecorporate initial levelcontroller a)ove* 4irst "ass* that the isperiod is open @otherwise* the status would )e (ot 7tarted and end users could not access the period and no signoffs have )een perfor&ed. After a user pro&otes the data* they lose the a)ility to change the data. he )o# to the left is the pro&otion )o#. he user can enter a co&&ent and attach a file @note: the attach&ent &ust first )e uploaded to 64/ fro& the /anage 8ocu&ents screen on the Custo& 8ocu&ents ta). ?f a parent entity was selected the dropdown at the )otto& allows the user to pro&ote all descendants as well as the entity. ( parent entity C(NN7T be promoted higher than any of its children*
?f one entity out of 100 is not signed off* then the total co&pany cannot )e signed off. his )eco&es very apparent during &onth end* when a corporate &anager goes to sign off the close and one or &ore divisions are delayed. Once pro&oted* the person at the ne#t level can get an e&ail showing the entity has )een pro&oted. hen they can review the entity and either pro&ote it to the person a)ove the& or reect it. A)ove* a pension accrual was noted in the co&&ent field. ?f the accrual was incorrect* then the person could reect the unit )ack to the previous level. All of the pro&otion history is stored for each entity.
On the screens a)ove has 4or )eene#a&ple* a DphaseE of 1. 64/ for 1* data to )e and su)&itted in phases orthere su)sets. theindicator )asic financials &ayallows )e phase headcount sales volu&e &ay )e phase 2* and fi#ed asset &ove&ent detail phase . ach phase &ay )e pro&oted independently and with different validation edits. his capa)ility is used when the data nd for each phase is on a different ti&eline @like )asic financials due on the day 2 of &onth end and headcount-sales volu&e due on theth$day. here are different strategies involved in setting up process control* like whether senior &anagers are allowed to see the data )efore it is pro&oted up to the& or if they have to wait. he ad&inistrator will infor& users a)out the appropriate steps.
Summary
Once data has )een entered* the ne#t steps usually are reconciling interco&pany )alances and signing off on the nu&)ers. 64/ provides tools for )oth of these steps. ?nterco&pany )alances &ay )e researched in any currency and fro& various viewpoints @all entities vs. all entities or one entity vs. all. 4or signoff* 64/ validates the data and ensures calculations have )een perfor&ed )efore allowing pro&otion. 6igher level users can reect the data as needed. All signoffs are stored and can )e reviewed if needed.
C%apter
17 HFM En# 4+er Reporting
he focus of this Chapter is to review two of the reporting tools for end users. he first tool is used for production 3uality* Dprint and distri)uteE type reports* like )alance sheets. he second is /icrosoft Office integration including /icrosoft #cel.
R$nning Report+ 5unning reports is straightforward. ,hen users log into the 6yperion ,orkspace @see chapter 2 they are also logging into the reporting tool.
he ta)s at the )otto& show the user where they are. he OCO(7O! ta) is the na&e of the 64/ application useravaila)le* is in. By choose clicking#plore on the #plore the user can go to the reports. ?f this ta)the is not fro& theta) (avigation dropdown at list theof top of the screen.
4ro& here dou)le click the folders to find the desired report* ust like ,indows #plorer. 8ou)le clicking a report will run it.
8epending on their settings and the report* users &ay e#perience one or two pro&pts. he first pro&pt is to preview the point of view. ust like in 64/* reportinginusing a point;sers of view the di&ensions have )een specified the report. canfor change the point ofthat view andnot rerun the report as needed. ,hether the point of view is previewed is a user preference setting > see chapter 2 for &ore infor&ation.
he second type of pro&pt is )uilt into the report. here &ay )e a specific di&ension which is needed to &ake the report fle#i)le. he pro&pt and the valid choices are deter&ined )y the report writer. Also* the point of view and the pro&pt &ay )e used at the sa&e ti&e. ,hen the is rendered it will in one of)eside two for&ats: or "84. 6/! usefulthe for analysis > report in the report )elow* the)etriangles the row6/! ite&s can )e clicked toisshow children )elow each. "84 is useful for printing* saving* and e&ailing to others. 5ight clicking the report )efore running provides the user with a choice when opening the report. A user preference also controls which for&at is used )y default. !astly* users can click the tool)ar )uttons to switch )etween the&.
A)ove* the report is shown in 6/! for&at and the line DCash fro& Current OperationsE has )een e#panded > the others have not. he point of view at the top can )e changed to run the report for a different entity* period* etc. he report &ay )e e#ported either fro& the link provided at the )otto& or fro& the 4ile &enu. "84 reports can )e saved-distri)uted-etc. as nor&al "84 files. Another type of docu&ent* other than a report* that a user &ay choose @depends on the i&ple&entation is a ,e) Analysis docu&ent. his docu&ent type is an interactive dash)oard that visually presents infor&ation intended &ore for online consu&ption vs. printing and distri)ution.
Hyperion "mart ;ie()or Micro+o)t O))ice 7&art =iew is the addin for connecting to 64/ /icrosoft Office. ;sers can pull data fro& and* if allowed* push data into 64/. /uch of this interaction is perfor&ed with /icrosoft #celG additional capa)ilities are availa)le for /icrosoft ,ord and /icrosoft "ower"oint. (ote that the appearance of the &enus* dialog )o#es* etc. &ay differ )ased upon the version of /icrosoft Office in useG however* the concepts will still apply. ?nstallation of the addin can )e done )y end users )y first downloading the installer fro& the 6yperion ,orkspace. 4ro& the ools &enu select ?nstall* then 7&art =iew. 7ave the file to the local co&puter and then run the file to start the installer.
4ollow the pro&pts for the installed. he )est reco&&endation is to accept the defaults.
After installation there will )e a 6yperion &enu. he first step is to create connections to 6yperion. As /icrosoft #cel is used &ost often* the e#a&ples here will use that. 4ro& the 6yperion &enu select Connection /anager.
his dialog )o# controls the connections to the different 6yperion &odules > in addition to 64/ 7&art =iew can connect to 6yperion ,orkspace @for reports and 6yperion "lanning. Click Add and then select ;5! provider. !eave the first dropdown as 6yperion "rovider and place http:--########-64/Office"rovider-64/Office"rovider.asp# where ######## is the server na&e. ?n the resulting dialog )o#* navigate down to the application na&e. (ote: select the !O,5 level application na&e* not the higher level* as shown )elow.
(e#t* provide a na&e and description for the connection and click 4inish. his connection will )e used each ti&e a connection is &ade to the specific application. A userna&e and password will )e needed. Creating a connection to the ,orkspace is si&ilar. Click Add* then select ;5! provider. ?n the ne#t dialog )o#* change the first dropdown to 6yperion 7yste& 9 B?^ "rovider and enter the appropriate ;5! > as shown )elow.
Click (e#t and enter a na&e and description for the connection and then click 4inish.
he first connection > to 64/ > allows users to pull data directly fro& 64/. he second connection allows users to pull reporting o)ects fro& the workspace. he re&ainder of this section focuses on these capa)ilities.
"mart ;ie( F$nction+ )or Micro+o)t E6cel he &ost fle#i)le part of 7&art =iew allows users to enter for&ulas in cells that pull a specific data point. Cell references &ay )e used to allow one cell to change* like the current &onth* and all appropriate for&ulas update. his capa)ility is very useful for &ost end usersG however* using /icrosoft #cel as a reporting tool is not very 7ar)anesO#ley co&pliant. 4or 7ar)anes co&pliance reporting* running reports via the ,orkspace is preferred due to the greater degree of control of report develop&ent. o get started with a function* open a connection to a 64/ application and then fro& the 6yperion &enu select 4unctions the 4unction Builder.
he dialog )o# guides users through the function choices @67 there &ust always )e one di&ension assigned. ,hen selecting &e&)ers for the point of view* &ultiple choices &ay )e &ade. his allows the dropdowns on the point of view to easily switch )etween the desired choices.
"lace checks in the )o#es on the left of the &e&)ers and click the top arrow to &ove the& to the selection window.
Opening Report+ in Micro+o)t O))ice he 7&art =iew addin also works with reports. By opening a connection to the 6yperion ,orkspaceOffice. @set up provided a)ove users can )asically run a report and have an i&age placed into /icrosoft 4ro& the 6yperion &enu open the connection to the ,orkspace. (e#t* fro& the 6yperion &enu select B? 8ocu&ent* then ?&port.
he resulting window will show the reporting repository. (avigate through the folders and select the desired report. he report will run and then provide a window with a few choices.
he point of view )ar is at the top* allowing changes as needed. Below the report* users can select whether to )ring in all pages or to allow refreshes via the ,orkspace point of view. Clicking OT will insert the report as an i&age @/icrosoft ,ord or /icrosoft "ower"oint or as rows-colu&ns @/icrosoft #cel.
?f the docu&ent is a standard package that is used regularly* the reports &ay )e updated )y clicking the& and selecting 6yperion* B? 8ocu&ent* then dit. he report is rerun and the point of vie w &ay )e adusted.
4+ing "mart Tag+ he last integration is useful when writing co&&entary and needing a nu&)er. ;sing the 7&art ag technology in /icrosoft Office 200 and /icrosoft Office 200K* users can easily link to 64/ and pull a nu&)er. ype the word s&artview and hover the &ouse pointer over it. An icon will appear as )elow > click on it to see the &enu.
8ata &ay )e pulled in )y selecting 4unctions. ?f a connection to 64/ isn+t open then no choices will appear. A report &ay )e pulled in )y selecting B?^ Content. he word s&artview will )e replaced )y the data.
Summary
6yperion provides a variety of reporting tools to &eet various needs. he two &ost co&&on are the financial reports run fro& the ,orkspace and /icrosoft #cel with the 7&art =iew addin. ,ith 7&art =iew there are various options to &eet any type of data need.
C%apter
11 Financial Reporting "t$#io (he Mechanics of )uilding *eports
he focus of this chapter is to discuss the )asic and advanced steps of )uilding a report using 6yperion 4inancial 5eporting 7tudio. 5eports usually start out si&ply and then )eco&e &ore co&ple# as additional features and co&ple#ity are added reiteratively.
Getting "tarte# 5egardless of the version of 4inancial 5eporting that is )eing used* you will need to launch the 4inancial 5eporting client. his is a ,indows progra& that &ust )e installed in order to )uild reports.
he ?8 provided &ust )e provisioned for the 5eport 8esigner role within 7hared 7ervices. After login a screen si&ilar to the following should appear. his is the 5epository that shows all reports and the o)ects which have )een created. ?t is 4inancial 5eporting+s e3uivalent to ,indows #plorer.
4olders can )e created here as needed to organie reports and other content to )e viewed within the ,orkspace. he folder should &ake sense for the users and in the overall design of the environ&ent @shared with "lanning* etc..
Laying O$t a Report ,hen creating a report* it is i&portant to know the desired output. /any ti&es it is useful to use an e#isting report or create a &ockup within /icrosoft #cel. !e)ore ,$il#ing report+B con+i#er laying o$t t%e general )ormat in E6cel. Amoc9& $p o) t%e report (o$l# +er'e to gain appro'al on t%e )ormat an# #etail ,e)ore +pen#ing t%e time to create t%e report an# (ill +er'e a+ a g$i#eline or re)erence.
Other considerations )efore )uilding reports include: •
•
•
•
/ake sure the appropriate data)ase connection@s have )een esta)lished in 4inancial 5eporting )y the ad&inistrator. he report distri)ution ðod should )e considered. !ayout decisions such as the use of point of view @"O= &ay )e different if reports are )eing distri)uted via hardcopy "84 or through the we) interface. sta)lish for&atting guidelines such as co&&on font styles* nu&)er for&ats* headers-footers and )ordering to esta)lish a co&&on look and feel throughout the various reports. /ost* )ut not all* calculations are )est perfor&ed within 64/. 5eport writing is easier and* &ore i&portantlyG the calculations are standardied and are availa)le to all of the 6yperion reporting tools @spreadsheets* 4inancial 5eporting* 64/ grids* etc.. One or &ore calculation &ay need to )e created within 64/ to support the report.
Once you are ready to )egin* create a new report )y selecting the 4ile* (ew* 5eport &enu option or click on the (ew 5eport )utton on the tool)ar.
he resulting screen* shown a)ove* has a few key areas. he large white part is where the report is )uilt. he line across the top shows the header area* and there is another )elow for the footer. he dots are called guidelines and help with spacing: note that this feature can )e toggled on and off under the =iew &enu. he tool)ar contains various icons to access features.
he report properties pane on the left shows infor&ation a)out the highlighted ite&. he pane will change )ased upon the ite& and what a)out it can )e changed. his pane is the first place to
look for settings a)out anything in a report. Before adding anything to a report* change the header space in the properties pane to 1.0. his can )e changed laterG however* any o)ect on the report &ust )e dragged down to allow the header to grow. (e#t* deter&ine the appropriate o)ect for the report. here are four types: grids* i&ages* te#t )o#es* and charts. he &ost co&&on o)ect is the grid* which pulls data fro& 64/. Click the appropriate tool)ar )utton @the first on the right hand tool)ar or select ?nsert initially it is not critical to lay it out e#actly where it will )e. ?n fact* for single grid reports* the place&ent of the grid is generally noti&portant )ecause grids will autosie )y default.
Once the grid has )een inserted* a pro&pt will ask for the connection infor&ation to the source data)ase. 7pecify the data)ase connection* provide and ?8 and password* and click OT. ?f a suita)le connection has not )een created* click on (ew 8ata)ase Connection. 4ill in the ite&s or select fro& the dropdowns and click OT. (ote that once the connection has )een created* any future report can reuse the connection.
After the data)ase connection has )een esta)lished* the 8i&ension !ayout dialog )o# is displayed. At this point di&ensions are placed into rows* colu&ns* or pages. 8i&ensions not placed in any of these three areas re&ain in the point of view. 7croll down to access Custo& and Custo&$.
here are five &ain co&ponents to the grid layout:
•
•
•
•
•
*ows > displayed on the Ia#is of a report as rows. /ultiple di&ensions with &ultiple &e&)er selections can )e selected for any rows. +olumns > displayed in the a#is of a report as colu&ns. /ultiple di&ensions with &ultiple &e&)er selections can )e selected for any colu&ns. Pages > pages are displayed on a report so that the report will repeat for all page selections. he for&atting on pages can display &ultiple reports on one page or on separate pages. /ultiple di&ensions with &ultiple &e&)er selections can )e selected for any colu&ns. 8i&ensions set as "age di&ensions will appear in selecta)le drop down )o#es for a 7preadsheet in the we) client. Point of &iew> "O= di&ensions represent single &e&)er selections for the entire report. Only one &e&)er can )e selected for each "O= di&ension. Books that reference 5eports can create reports "O= &e&)er selections in )ooks. All of the di&ensions initially appear in this section. "ata Area > the data area displays the colu&n-row data intersections in the report. All for&atting is applied to the report in the 8ata Area. his area is not configura)le fro& the 8i&ension !ayout dialog )o#.
8rag the di&ension la)els to the desired areas and click OT when done. (ote that &ultiple di&ensions &ay )e placed in any of the areas. After clicking the OT )utton* the report now looks like the following @Account are in the rows* and "eriod and 7cenario are in the colu&ns.
"electing Mem,er+ he 7elect /e&)ers dialog )o# is the key to selecting the &e&)ers you want in the data)ase. he selections can either )e si&ple @a few &e&)ers or co&ple# @children of CurrentAssets. 4or "O= di&ensions* only one &e&)er can )e selected fro& a di&ension. o select a &e&)er* e#pand the hierarchy and click on it. 4or Colu&n* 5ow* and "age di&ensions* &ultiple &e&)ers are selected or lists are created. •
•
A##ingB Remo'ingB an# Mo'ing Mem,er "election+
/e&)ers are selected )y dou)le clicking on any of the colu&ns or rows in the grid. he 7elect /e&)ers dialog )o# appears.he &ost )asic ðod of selecting &e&)ers to is e#pand the hierarchy on the left window of the 7elect /e&)ers dialog )o#. Click on the &e&)er and select the Add tool)ar )utton. ?te&s on the right will show in the rows-colu&ns-pages. Below adds the Budget scenario to the Actual scenario shown in the grid a)ove.
o re&ove any &e&)ers* select the& in the 7elected area* and choose the 5e&ove )utton. he top )utton &oves a highlighted ite&* the lower )utton &oves all ite&s. he tool)ar )utton )elow the re&ove )utton will re&ove all selections. ?t is possi)le to change the order of the selected &e&)ers with the up and down arrow tool)ars:
Prompt+ an# C$rrent Point o) ;ie(
Along with the &e&)ers shown on the left* there are two additional choices > refer to the a)ove screenshot. Current point of view allows the di&ension to )e placed in the row or colu&n )ut still dyna&ic to )e in the point of view. his treat&ent is re3uired when the row - colu&n needs the di&ension )ut still needs to )e dyna&ic. he pro&pt creates a dialog )o# when the user runs the report to select the &e&)er@s. he developer can li&it the choices provided to the user or allow the& to pick fro& the hierarchy. Placing "election+ into "eparate Ro(+
At the )otto& right of the &e&)er selection )o# there is a check )o# to place the selections into separate rows. ,hile not re3uired* doing so provides two )enefits. 4irst* it is easier to see the contents of the rows-colu&ns in the report. 7econd* the for&atting is generally easier @does not re3uire conditional for&atting. 4or e#a&ple* the total of a group of nu&)ers &ay need to )e
for&atted differently. 6aving the account for the total in a separate row &akes it easier to for&at.
Relation+%ip F$nction "election+
5elationship functions allow reports to )e &ore fle#i)le )y relying on hierarchies within the application. ,elldesigned reports rely heavi ly on relationship unction f definitions* asthey offer the following advantages: •
•
•
•
Minimizes future maintenance. As new &e&)ers are added into the relationship they auto&atically are shown on the report. Minimizes hard,coding of member names. his is i&portant )ecause &e&)er na&es can to change over ti&e and all reports will need to )e updated with the&. Simplifies reports.!arger report selections clicking individual &e&)er na&es would )e cu&)erso&e and i&practical and re3uire an undesired level of &aintenance* not only for changes )ut for new di&ension &e&)ers. Apply comple logic. 7elections using And-Or logic can achieve &ore co&ple# reports.
,hen adding a &e&)er* select the &e&)er and then click the Add *elationship )utton. ?t is the second )utton in the &iddle of the two panes. ?n the following screenshot* DChildren of 110000E is added )y clicking on 110000 and then clicking the Add *elationship )utton and selecting Children.
Mo+t )$nction+ +electe# (ill ,e applie# relati'e to t%e mem,er t%at i+ +electe#. "ome )$nction+ may (or9 in#epen#ently o) t%e mem,er t%at +electe#. i+
he selection now looks like the following:
;se the 5e&ove )utton to &ove L(oneM out of the 7elected area and click OT. he selection in the grid now shows the &e&)er selection ust chosen.
Clicking print preview @)utton on the tool)ar will show the report so far.
here is &ore work to )e done* )ut the report is running. Relation+%ip F$nction Alternati'e+
here are several relationship functions availa)le. 6ere are the )asic functions: • • •
+hildren > all &e&)ers i&&ediately )elow a parent for the selected &e&)er. "escendants> all &e&)ers )elow the selected &e&)er in the hierarchy. )ase > the lowest level &e&)ers )elow the selected &e&)er in the hierarchy.
Parent > the parent of the selected &e&)er. Ancestors > all &e&)ers a)ove a &e&)er in the hierarchy for the selected &e&)er. Sibling > all &e&)ers that share the sa&e parent for the selected &e&)er. • •
•
T%e >Incl$+i'e? )$nction+ (ill incl$#e t%e mem,er c$rrently +electe# t%e in li+t t%at i+ generate#.
?n addition to the selections that are specified in the relationship functions* there are &ore functions availa)le through the 4unctions ta):
7o&e of the functions in this ta) are redundant > they are already included in the /e&)ers ta) such as Children and 8escendants.(ote that thefunctions will change dependingon the di&ension > the a)ove shows the functions for the Account di&ension. ,ith /atch* &e&)ers &atching a specified pattern are shown. #a&ples include: DM > will find all &e&)ers that start with the letter 8. he W serves as a wildcard for any nu&)er of characters. Ning > this is a character wildcard search so that all &e&)ers ending in DingE with any other first letter initiating the word will )e selected > e.g. Bing* sing. he Q serves as a wildcard for a specific character. •
•
A#'ance# "election+
All of the selections can )e co&)ined to &ake &ore co&ple# selection lists. ;sing And-Or-;nion and (ot logical operators* it is possi)le to e#tend the functionality of the 7elect /e&)ers dialog )o#. After selecting the desired &e&)ers* click =iew and then select Advanced.
his selection changes the window to allow for operators to &odify the selection. By adding account 111000 as a second selection* the operators can )e used to e#clude this account fro& the DChildren of 110000E selection. (ote also the check )o# for the first colu&n to indicate D(ot.E
his type of report )uilding is useful when showing different &e&)ers accounts at different levels > so&e in detail* so&e in su&&ary > yet still wanting the report to )e as dyna&ic as possi)le. Li+t+ Ta,
he !ists a) in the 7elect /e&)ers dialog )o# refers to the syste& generated and the ad&inistrator created &e&)er lists for the di&ension. E#iting "election+ Man$ally
A shortcut to changing the selection is to type the selection directly into the selection te#t )o#. his re3uires knowing the e#act &e&)er na&es. C%anging mem,er name+ in t%e +election ,o6 canm$c% ,e )a+ter t%an going t%ro$g% t%e Mem,er "elect #ialog ,o6 ,$t +%o$l# ,e $+e# (it% ca$tion (%en c%anging more comple6 +election+ ,a+e# on relation+%ip )$nction+.
he reason for this is that the relationship function synta# varies per function and can )e tricky. Although it is possi)le to change relationship functions* &e&)er na&es are &ore co&&only edited directly. 6ighlight the la)el to )e changed and type directly into the te#t )o# a)ove the point of view )ar. Once the green check&ark to the left of the )o# &ust )e clicked in order for the changeco&plete* to )e accepted.
"elect t%e c%ec9,o6 to c%ec9 t%e +ynta6 an# +a'e t%e +election. Failing to #o +o (ill not +a'e t%e ne( +election.
he error checker will let you know if a &e&)er is not valid such as in the following where we have typed a &e&)er incorrectly:
Limiting t%e Point o);ie( "election+
here are instances where one or &ore di&ension &ay need to )e hardcoded so that the user does not pick soðing wrong or the di&ension is ust not applica)leG however* the di&ension is not needed in the row-colu&n-page either. ach grid has a point of view that is nor&ally hidden. hese can )e opened up and one or &ore di&ension set to a specific &e&)er. o open the grid point of view* highlight the whole grid* right click* and select shown as 5eport "roperties at the )eginning of the chapter > appears to the right of the report. he 4$ key toggles the sheet on and off as needed. he contents of this dialog )o# will change )ased upon the clicked ite& in the report and the title of the )o# will change accordingly. he different ite&s to click and for&at with the pane are: • • • • •
he report area itself @no o)ect he la)el @as shown he cell in the grid @like A1 he whole row or colu&n he whole grid @the gray )o# where the row and colu&n la)els intersect
he choices for for&atting are different for each selection* and e#peri&entation is the )est way to learn the choices @highlight each and see what the choices are. 4or&atting changes for the whole grid are nu&erous enough to re3uire &ultiple pages. 6ighlighting the whole grid will add a selection of pages at the top of the pane* each with its own set of choices.
7o&e of the &ost co&&only used choices are: •
•
•
•
•
7how la)el or description > click on the row or colu&n &e&)ers and choose )etween la)el* description or )oth. A custo& header is also availa)le which can )e hardcoded te#t and-or a te#t function > &ore on te#t functions later. 7howing row headings )etween colu&ns > click on entire grid and on the click on the row-colu&n and check the radio )uttons as appropriate. here are also suppression options availa)le for the whole grid. here is also a conditional suppress that is covered later. Changing how &issing data is displayed > click the whole grid and on the 7uppression page change the )o#es provided. 5ow and colu&n heights-widths > click on the row-colu&n and change the nu&)er. hese &ay also )e changed si&ply )y clicking and dragging the line in )etween rows-colu&ns as in /icrosoft #cel.
Another type of for&atting is for the te#t: how do things appear on the report. ,hile using the sa&e selections a)ove* click on either the 4or&at tool)ar )utton @has an A on it or select the 4or&at* Cells &enu option.
he choices here will )e fa&iliar to /icrosoft #cel users. ;se the ta)s at the top to navigate to the various areas. here is also a conditional for&at that is discussed later. One of the co&&only used for&atting options here is to place an overline on the su)totals. o put a line )etween a su)total and the ite&s adding up to the total* which &ay )e a Dchildren ofE or other dyna&ic relationship* use a overline @on the )order ta) on the su)total. ?f an underline was placed on the row with the ite&s* then the line would appear on the report under each ite&* not ust the last one.
"orting 7orting and ranking functions are )uilt into 7tudio. 6ighlight the whole grid and on the properties pane check the 7ort )o# and then click 7etup.
?n the result )o# select the rows to sort and )y what colu&n. /ultiple sorts can )e added.
E6pan+ion+ an# Relate# Content #pansions are a significant feature ena)led through the grid properties pane. #pansions ena)le users to drill down fro& parent &e&)ers to their descendants while in the we) interface. his feature is useful for when different users want different ite&s shown in &ore detail. hey can all start with a su&&ary report* drill down their desired areas* and then print. Click the &e&)er la)el and check the )o# to ena)le.
(ote that the user &ay drill down on the &e&)er@s while in we) preview )ut not in "84 or print preview &ode. But* the user &ay drill down in we) preview and then switch to "84 &ode to print the report in the desired e#panded state. 5elated content is si&ilar to e#pansions and ena)led in a si&ilar fashion. he difference is that related content opens another report or docu&ent that relates to the srcinal doc in so&e fashion. 4or e#a&ple* the developer &ay add a related content link to a )alance sheet for the interco&pany accounts that opens a second report showing the interco&pany account )alance )y interco&pany partner. ,ith related content users* in the 6/! view* will click on the actual nu&)er to open the content. he point of view of the nu&)er clicked is passed to the second report. 6ighlight the desired cell or row or colu&n and select 5elated Content. hen click on 7etup to specify the report or ;5! @&ultiple &ay )e chosen that the user should see after clicking the link.
Con#itional "$ppre++ion 8iscussed a)ove is how to use the properties pane to perfor& )asic suppression options: suppress if ero* suppress if no data* suppress if error. 7o&eti&es* suppression is needed )ased on a condition. 6ighlighting a whole row or colu&n changes the properties pane accordingly. hen* check the Advanced Options )o# and then click on 7etupP.
he line of dialog )o#es guides through the thatradio the )uttons on suppression can )e done )asedthe ondeveloper a single condition oravaila)le &ultiple:choices. use the(ote and-or the far right accordingly after adding another condition.
A co&&on use of this feature is to hide one row if another row is suppressed or e3ual to a specific nu&)er.
Con#itional Formatting 7i&ilar to conditional suppression* thereand is the option to conditionally ite&s.the 6ighlight row-colu&n-grid-cell to )e for&atted select Conditional 4or&at for&at @either fro& 4or&at the &enu* the tool)ar )utton* or with a right click.
he resulting dialog )o# is si&ilar to the conditional suppress in that the dialog )o#es and fields guide the developer through the choices. here are two additional features. he first is the 4or&at Cells )utton. Once the condition has )een entered* click the 4or&at Cells )utton to set the for&at for those ite&s &eeting the condition. he for&at cells dialog )o# is the sa&e as seen )efore. (e#t* there is Add 4or&at # and 8elete 4or&at in the upper right. hese allow for &ultiple conditions to have different for&ats. 4or e#a&ple* if a variance is greater than 10U then the row could )e for&atted as green and if the variance is less than 10U then the row could )e for&atted as red. he different for&ats are &anaged )y the ta)s that will e#tend a)ove the conditions.
A co&&on conditional for&at to use is to for&at the first row of a report to have a currency sy&)ol. his for&at is easy if the first row is a single &e&)erG however* if the first row contains &ultiple &e&)ers @ie* as a result of Dchildren of PE then a conditional for&at can perfor& the necessary for&atting.
A##ing Te6t here are a couple of different ways of adding te#t. On the )ody of the report* there &ay )e a need for a te#t )o#: a report title is the &ost co&&on. One of the four o)ect types > grid )eing one > is As a te#t ither the ?nsert e#t &enu option or click on created the e#teither Bo# hard tool)ar )utton. with)o#. grids* thenchoose drag within the report to create the )o#. Once coded te#t or te#t functions can )e added as needed.
6ere is the e#t Bo# properties pane which will appear when the te#t )o# is selected:
Besides the )ordering and shading properties* an i&portant propertyAutosize is > this feature will autosie the height @not the width of a e#t Bo# so that all the te#t fits. he Show (et !unction Errorsshould )e displayed to &ore easily find any report function errors and to indicate potential pro)le&s to the end user.
Te6t Ro(+Col$mn+ (it%in Gri#+
e#t can also )e added within a grid in rows and colu&ns. his te#t could )e a )lank row for spacing* a header* a divider* or a co&&ent. ;sing the new row-colu&n ðod shown a)ove* add a te#t row. his row can either )e left )lank* te#t entered* and-or one or &ore functions entered.
In+erting F$nction+
4unctions can )e added to the te#t )o#es and rows-colu&ns to provide references to report na&es* current dates* page nu&)ers* and &ore. o insert a function in the te#t area* position the cursor where the function should )e inserted and click the ?nsert 4unction )utton.
his will )ring up the function )rowser. 7elect the function and type in the para&eters for the function. 5eference the online help for the synta# of each function.
(ote that so&e functions are for other 6yperion products* such as 6yperion "lanning or 6yperion ss)ase and do not apply to 6yperion 4inancial /anage&ent.
he report )elow shows the application of various functions.
6ere is a su&&ary of the &ost co&&only used function capa)ilities: • • • • •
"age nu&)ering including how &any pages of the total 8ate-i&e -;ser ?8-5eport na&e references 5eferences to data cell values /e&)er na&e or alias references for row* colu&n or page di&ensions 5eferencing the data source na&e
Mo+t implementation+ (ill $+e a +tan#ar# )ooter an# +ometime+ a +tan#ar# %ea#er t%at are applie# to all report+ t%$+ pro'i#ing $+er+ con+i+tent an# common re)erence point+.
A##ing Image+ ?n the sa&e way that grids and te#t )o#es are added to reports* an i&age &ay )e added also. his is &ost co&&only the co&pany+s logo. ither choose the ?nsert ?&age &enu option or click on the ?&age tool)ar )utton. As with grids* then drag within the report to create the )o#. Once created a dialog )o# appears allowing the developer to navigate to and add the i&age.
Once on the report the i&age &ay )e resied. Check the 7tretch )o# on the properties pane to have the i&age resie with the )o#.
"a'e# an# Lin9e# O,ect+ ,ith logos and standard te#t )o#es* these should )e all linked together across all reports* so that if the logo or the standard footer changes* all reports are updated auto&atically. his is acco&plished with the used of saved and linked o)ects. here are two parts to the procedure. he procedure is the sa&e whether the o)ect is a grid* te#t )o#* i&age* or chart. 4irst* the o)ect is saved in the repository. 5ight click the o)ect and fro& the &enu select 7ave O)ectP.
(e#t* navigate to the desired folder in the repository and save the o)ect. nsure that the )o# at the )otto& is checked to link to source o)ect. ,ith this link* the report will )e linked to the o)ect and will pick up any future changes to the o)ect.
(e#t* reports using the o)ect will )ring in and lin- to the o)ect. ?n this &anner* whenever the o)ect is updated* each report will use the updated o)ect. ?n another report* right click the report
area and select ?nsert O)ect* 7aved O)ectP. Alternatively* use the ?nsert &enu.
(e#t* navigate to the desired folder in the repository and select the o)ect. (ote that the type dropdown will need to reflect the desired o)ect type. nsure that the )o# at the )otto& is checked to link to source o)ect. ,ith this link* the report will )e linked to the o)ect and will pick up any future changes to the o)ect.
7aved o)ects are updated )y saving over the o)ect.
Ro( an# Col$mn Template+ ust as o)ects can )e saved to the repository* sets of rows and colu&ns can )e saved and reused. Called te&plates* these can )e )rought into other reports and save ti&e with report )uilding. ?f the te&plates re&ain linked @in the sa&e &anner as o)ects* the report will reflect any changes &ade to the saved te&plate. LIMITE 4"E * T%ere are +e'eral +y+tem limitation+ t%at pre'ent t%e $+e o) ro( an# col$mn template+. T%e+e are li+te# in t%e #oc$mentation . T%e limitation+ are +igni)icant eno$g% to ren#er template+ $+ele++ in many in+tance+.
o create a te&plate* highlight the rows or colu&ns to save out. 5ight click and select 7ave as 5ow and Colu&n e&plate.
(avigate to the appropriate folder within the 5epository and save the te&plate.
!inking to the source o)ect works the sa&e way as with o)ects. After clicking 7ave* a dialog )o# appears to ask how to handle so&e features that can either )e saved with the te&plate or
inherited fro& the grid using the te&plate.
;se the ?nsert 5ow and Colu&n te&plate to )ring a te&plate into a grid. ,hen a te&plate is in a grid and is linked* the rows-colu&ns will )e shaded yellow to indicate their status as a te&plate. ?f the link is re&oved then the rows-colu&ns return to nor&al.
here &ust )e at least one data row and one data colu&n native to each grid. hese can )e suppressed if ust placeholders and the te&plate has 100U of the rows-colu&ns re3uired. ?n the a)ove screenshot row 2 is native and row 1 is a te&plate.
Form$la+ 4or&ulas can )e added to reports to aug&ent the data co&ing fro& 64/. A for&ula could )e a si&ple su)total or could )e a )uilt in function. o add a for&ula* add a new row-colu&n to the data grid and select 4or&ula. (ote the new row-colu&n is added with an e3ual sign in front of the \ signs in the grid. 4or&ulas can either )e added for the whole row-colu&n @)y highlighting or each cell.
?n the screenshot a)ove* a for&ula colu&n has )een added. Also note the dropdown under the &enu and tool)ar: the current value is 7u&@. his dropdown contains the for&ulas that 64/ knows. 4or&ulas &ay )e chosen fro& the dropdown or ust directly entered into the for&ula )ar. he help icon to the right of the dropdown can )e used to see directions and sa&ples for each for&ula. ?n the e#a&ple )elow the "ercentOfotal for&ula is used to show each &e&)er in row 1+s percentage of row 2. he s3uare )rackets @ L and M are used to denote rows-colu&ns-pages and cells as needed.
,hen for&ulas are used* generally custo& headers are also used to provide an appropriate headerG otherwise* the for&ula prints as the header.
5efer to the help for infor&ation a)out each for&ula.
C%arting Charts can )e added to reports to provide a visual display of the data and is particularly infor&ative with trends. (ote that a grid &ust e#ist in the report to support the chart. C%art+ can ,e lin9 e# to one Gri# o, ect. In+erting C%art+ into a report (it% no Gri# o,ect to attac% t%e C%art to (ill re+$lt in a ,lan9 o$tp$t )or t%e C%art. To +ee only t%e C%art (%en r$nningB %i#e t%e Gri#.
o create a chart follow these steps: • • • •
•
• •
?nsert a one m$ltiple or +%eet+?B page+ are al(ay+ #i+playe# a+ #rop #o(n ,o6e+ in t%e (e, client. I) m$ltiple page+ +%o$l# appear in a reportB con+i#er $+ing m$ltiple gri#+ in t%e report #e+igner.
?f there are &ultiple "age di&ensions in the report* then all of the selections co&)inations across the page di&ensions are displayed in concatenated for&. his for& shows the drop down selection as a concatenation of all the selected product and dealer co&)inations:
A+ more #imen+ion+ are a##e# to t%e Page +ection o) a ReportB t%e #rop #o(n ,o6 in t%e (e, client li+t (ill ,ecome a concatenation o) all t%e #imen+ion+. "election+ (it% more t%an aco$ple o) #imen+ion+ can ,ecome cl$ttere#.
(ote that the report was run with the "O= di&ensions set to the current setting fro& the 4inancial 5eporting 7tudio. o change the "O= di&ension selections* select &iew%Preview the /ser Point of &iew&enu option:
he following "O= selections are displayed:
7elect the desired &e&)ers fro& the "O= di&ensions )y clicking the 7elect )utton for that di&ension. Teep in &ind that changes &adeto the "oint of=iews can )e changed later andthe entire report will )e displayed for the selected "O=s. 8e, +election o) PO; mem,er+ )ollo( t%e +ame r$le+ a+ (it% t%e Report+ Client & only one mem,er can ,e +electe# at any one time.
6ere+s the /e&)er 7elect dialog )o# through the we):
he /e&)er 7elect we) dialog )o# offers si&ilar capa)ilities as the 5eports Client. /ost of the ti&e* the selection is done )y clicking through the hierarchy or searching on a known &e&)er na&e. 6owever* all of the functions can )e utilied for &ore co&ple# selections. 7elect a &e&)er and click OT. he report output will change to the new selection.
!oo9+ Books are collections of reports. he &ost co&&on )ook is a &onth end reporting package. he )ook can )e co&prised of &any reports for one or &ore points of view or ust a single report for &ultiple points of view. he results of the )ook can )e output in &ultiple directions. ?t is co&&on to choose &ultiple &e&)ers fro& each "O= di&ension in a report > each report is e#ecuted for all co&)inations of the selected &e&)ers. Lea'e mem,er+ t%at (ill %a'e m$ltiple +election+ repre+enting #i))erent page+ o) report+ a+ PO; #imen+ion+ in a report. I) a report ,e (ill#i+tri,$te# t%ro$g% !oo9+B $+ing Page #imen+ion+ on t%e +ame report only ma9e+ +en+e (%en t%ey are printe# on t%e+ame +%eet.
Creating !oo9+
4ro& ,orkspace* selectFile>New Document::
7elect theCollect 5eports into a Bookradio )utton:
Click (e#t and the report selection dialog )o# will show. Add a report fro& the 5epository )y )rowsing to find it. ither &ultiple or asingle report can )eselected.
?f a )ook has already )een created* add reports )y right clicking and selecting Add 5eports:
eleting Report+ )rom a !oo9
Once reports have )een added to a Book* they can )e deleted selecting the report and selecting *emove from selected)utton:
"electing Mem,er+ )or !oo9+
Once one or &ore reports have )een added to a )ook* the ne#t step is to set the point of view for the reports.
8ou)leclick on the di&ensions to )ring up the &e&)er na&e selector. Alternately* select the 7elect /e&)ers tool)ar )utton.
he /e&)er 7elect capa)ilities for the we) are identical to those shown previously in the 5eports Client. he three ta)s in the report allow selection )etween /e&)ers* !ists* and 4unctions. 7elect &e&)ers fro& each of the "O= di&ensions for each report.
Pre'ie(ing !oo9+
o preview a Book once the reports have )een added and the &e&)ers for the "O= di&ensions have )een selected* choose theFile>Open In>PDF Preview :
Below is a screenshot for all the pages of the reports that will )e displayed depending on what the "O= selections that were &ade. Click on a report in the Book and select Show the *eport )utton:
A "84 report appears with that page of the report displayed:
Alternately* you can push the entire )ook into one "84 )y selecting !ile%0pen #n%+omplete )ooin P"!1
hen* when the )ook is displayed in "84* si&ply choose the Sa#e a copy of the file .
Books can )e previewed in either 6/! or "84. he ordering of the reports in a )ook is as follows: •
•
5eports will )e e#ecuted in the order that the reports are listed in a Book if there are &ultiple reports.
5eport printing will )e run in the sort order of the di&ension "O=s listed. ?n the e#a&ple a)ove* the reports are sorted )y 8ealer and then )y 8epart&ent )ecause they appear that way in the Book..
o change the report e#ecution order in a Book &ove the reports up or down in the )ook. 5eport e#ecution will )e in the order they are listed. 4or each report* it is possi)le to change the di&ension order within a report.o do this* right click on the di&ension and selectMove /p or Move "own:
"a'ing !oo9+
As with reports* )ooks can )e saved in any directory within the 5epository. ?t is pro)a)ly )est to keep it in the sa&e directory where the reports contained within the )ook are stored. 7i&ply select File>Save fro& the &enu option.
!oo9 "et$p
he )ook setup is &uch like the page setup for printing. Book setup controls various aspects of the appearance such as whether the distri)ution will )e )y hard copy* "84* or 6/!. (able of +ontents.Choose this option to display a ta)le of contents Paper Size > the default as with nor&al print options is letter sie 0rientation > choose )etween landscape and portrait &odes Page $umbering> turn on or off the "age nu&)ering feature +ollation > the reports can )e grouped )y reports or )y &e&)er selections. his affects the order that reports are printed out when &ultiple reports are contained in a Book. he order of the pages can )e )y report or )y &e&)er na&e.
o change the Book setting* select File>Book Setupfro& the &enu option in the ,orkspace:
(e#t* select the options to control the properties as shown )elow:
!atc%e+ Batches are used to auto&ate report and )ook e#ecution. Batches allow you to schedule reports and specify the output for&at. ,hen e#ecuting reports through )atches* designers have* a&ong others* the following output options. • • •
•
Hardcopy "rinting to a specified printer. P"! > he )atch will generate a "84 docu&ent that can )e distri)uted via e&ail. H(ML > he )atch will generate 6/! docu&ents that can )e distri)uted via the we). A location can )e specified on the we). Snapshot > his will generate all reports in a preretrieved for&at and is &ost often used when a report will )e distri)uted through the 5eports Client. ?t is i&portant to note that
snapshots represent a pull of the data as of the )atch e#ecution ti&e > they are not dyna&ically pulled when the users interface with the&. o create a )atch* select File>New Document. (e#t* select the Batch radio )utton:
Click the (e#t )utton. Both reports and )ooks can )e added.
Click inish when all the reports and )ooks have )een added. he Batch ditor appears and shows the )ook that we added in the previous step:
7elect the!it>A!! ItemJsK &enu option* if you want to add another report or )ook. Can also choose to delete an ite& fro& the Batch* or change the &e&)er selections for a )ook.
Once all )ooks* reports* and snapshots have )een added* save the )atch )y selecting File>Save As fro& the &enu option:
6ere we give the )atch a na&e and save it in the 12olap5eports folder. "c%e#$ling !atc%e+
Once a )atch has )een created* it is possi)le to schedule the Batch to run at a specific ti&e in the future or i&&ediately. o do so* select Edit%Schedule )atch1
he 7chedule Batch dialog )o# appears. (avigate to a )atch that has )een saved* highlight* and click (e#t.
7elect the$E2( )utton to proceed:
he 7tart i&e dialog )o# appears. ?t is possi)le and often the case to ust run it D(owE or i&&ediately. 6owever* it is also possi)le to schedule the Batch to run at the following ti&es: •
• • • • •
0nce > run the )atch at a specified ti&e. 7elect this if you do not want to run the Batch i&&ediately )ut on a specific ti&e later. ee-days > run the )atch every weekday at a specified ti&e. "aily > 7a&e as weekdays )ut on weekends too. ee-ly > run the )atch only a weekly )asis at a specified day and ti&e. Monthly > run the )atch every &onth at a specified day and ti&e. 3uarterly4 Semiannually4 Annually > these options are not often used )ut will run 3uarterly* two ti&es a year* or once a year at the specified days and ti&es.
(ote that the section at the )otto& specifies the &e&)ers fro& each di&ension for the reports:
?t is possi)le to change the Batch "oint of =iew for each )atch* )ut generally this is not practical. 7elect the ( )utton to continue scheduling the Batch o):
he 8estinations allow you to specify the Batch output. ,hen e#ecuting reports through Batches* designers have the following availa)le options for output: •
•
•
•
•
Hardcopy > 7elect the)rint to option and specify a printer. his will create a hardcopy report to a specified printer. P"! > 7elect theExport as )Doption. he )atch will generate a "84 docu&ent that can then )e distri)uted via e&ail. ?t is possi)le to specify an D#ternal directoryE. his is any directory not in the 4inancial 5eporting repository. H(ML > 7elect theExport as %T&4option. he )atch will generate 6/! docu&ents that can then )e distri)uted via the we). ?f an e#ternal directory is specified* then the report will )e saved to that directory. his is &ost co&&only an intranet site @e#ternal refers to any location outside the repository. Snapshot > Choose the 7ave As 7napshot option. ?t is i&portant to note that snapshots represent a pull of the data as of the )atch e#ecution ti&e > they are not dyna&ically pulled when the users interface with the&. Email > ?f successful* the )atch output can )e distri)uted to a specified list of users. ?f unsuccessful* the details are usually sent to the ad&inistrator@s.
?f selecting this option* select the users to receive the report as )elow.
Click the !#$#SH )utton to finish scheduling the Batch o):
!atc% "c%e#$ler
o view all of the )atches that have )een scheduled* open up the Batch 7cheduler. 4ro& the 5eports ,e) Client* select the(ools%Schedule%)atchScheduler &enu option:
he )atch ust scheduled will )e displayed:
(otice the status shows that the Batch a)ove is currently Successful. he various status options are: • • • •
*unning > a Batch that is currently )eing e#ecuted will display this status. Successful > a Batch has )een e#ecuted without errors will display this status. Error > a Batch that resulted in an error during e#ecution will display this status. Pending > a Batch that is currently scheduled to e#ecute at a future ti&e will display this status.
,hile working with the 7cheduler* refresh to see the latest status settings. 7elect "iew>#e$resh:
o view the details of a )atch especially when errors have occurred* select the )atch in the scheduler and rightclick selectShow "etails:
he details of the )atch e#ecution are displayed:
Canceling !atc%e+
?f a )atch has )een scheduled )ut is pending e#ecution* it is possi)le to cancel it. 7elect the )atch in the scheduler andrightclick on it. 7elect the"elete &enu option:
Confir& to delete the )atch.
!atc% O$tp$t+
,here does the output of "84 go when the #ternal option is not chosen in the Batch schedulerQ ,hen you donot specify D#ternal locationE*the default location isthe repository ho&e directory. A folder with a nu&)er is stored in the 7cheduler Output directory. ach )atch that will run will have a )atch nu&)er associated with it > this nu&)er is incre&ented each ti&e. he folders can later )e rena&ed. 6ere is a screenshot of the "84 output that was generated for the first )atch run on the syste&.
A Vip file will )e created with all the "84 reports ipped into it. his &ay )e opti&al for sending files over e&ail as the files will )e co&pressed. By navigating to the Class 5eports folder* we can see the actual "84 that was created:
Alternately* and &ore likely* it is possi)le to retrieve the output via the ,orkspace. his &ay )e necessary as ad&inistrators typically do not have access to folders on the 5eports server directories. 4ro& the 7cheduler* select the )atch that was run and rightclick on it. Choose the *etrieve 0utput&enu option:
(e#t is a pro&pt to save the Vip file to a specific location. ?t is also possi)le to rena&e the file.
?f this see&s like a lot to go through* consider this: $ring ,atc% creationB it i+ po++i,le to +peci)y an e6ternal #irectory. I) t%e Financial Reporting +er'er i+ +et $p to map to a net(or9e# #irectoryB t%en t%e proce++ o) retrie'ing ,atc% o$tp$t can ,ypa++e# ,e altoget%e r.
"nap+%ot+ 7napshots allow distri)ution of reports without re3uiring dyna&ic retrievals fro& 6yperion. his will i&prove report perfor&ance as all the reports have already )een e#ecuted and saved. ?n addition* consider the following advantage: !eca$+e "nap+%ot+ are +taticB t%ey repre+ent report+ t%at %a'e ,een a$#ite# an# 'eri)ie#. ynamic report+ may ,e e6ec$te # at a point intime (%en t%e #ata,a+e i+ ,eing reloa#e# or calc$late# * t%e pro,lem %ere i+ t%at t%e #ata,a+e may ,e a'aila,le ,$t t%e #ata may not %a'e ,een a$#ite#D
7napshots can )e previewed )y selecting the 7napshot as we have in the following:
o preview a snapshot rightclick on it and select to preview in "84 or 6/!:
A++igning Acce++ to "nap+%ot+
4ro& the destinations section of the 7chedule Batch* select the Privileges )utton:
7elect a user or group and add it to the 7elected ;sers and
View more...
Comments
