Finit - what would happen greatest hits and disasters

3. ©2016 Why is Finit here? Page 3 Finit takes pride in being a company of makers and Doers; people who dig in and get their hands dirty We make and deliver personalized financial reporting solutions and experiences …Not Company to Company, but Person to Person By listening, questioning, and analyzing

4. ©2016 The Finit Family Page 4 Fully aligned with our clients, not just bottom line $ No debt or external ownership Work with Finit employees, no subcontractors Compensation based on CLIENT SATISFACTION PRIVATELY OWNED CLIENT SATISFACTION NO SUBCONTRACTORS DEBT FREE

5. ©2016 Finit Values Page 5 Our values on which we ask you to provide consultant feedback: • Approach & Collaboration • Integrity & Honesty • Client Betterment • Self Betterment • Colleague Betterment • Finit Betterment • Work Effectiveness • Impact & Innovation • Proactiveness & Passion Service Solutions Betterment

6. ©2016 Finit Customer Success Page 6 Our values, culture, and approach to becoming a trusted advisor to our customers has led to 100% customer success for every Finit client (250+) and for every Oracle Hyperion project (500+)

9. ©2016 About the Presenter Page 9 Chris Barbieri (cbarbieri@finitsolutions.com) Certification/Education • Oracle ACE • HFM Certified Consultant, all releases • Hyperion Enterprise Certified • MBA – Babson College, Concentration in Information Systems and Entrepreneurship • BS – Boston College, major in Finance, minor in Accounting Experience • 15+ years with HFM • 17+ years with Enterprise • 4 years as Product Issues Manager for HFM, Shared Services, Smart View, and DRM Client Testimonial By Tuesday you accomplished everything we planned to cover this week and then you blew us away! Finit has gone beyond simply "teaching" how the applications work, they have provided a context to how best (and how NOT) to utilize the applications. I knew I could count on the Finit team!

18. ©2016 About that Journal… Page 18 • Is now posted as EUR data, not GBP • Is this what you want? • 1,000 EUR is not the same as 1,000 GBP… • Either go back, translate offline from GBP to EUR and recreate the journals • Or leave it if you intended it to be EUR from the start • What about the loaded data?

19. ©2016 Consolidate EastRegion • GBP status is still TR • Is not the entity’s currency • Is not the parent’s currency • Translate EUR to GBP • Original GBP data is replaced • USD changes accordingly • Time to re-load all data! Status after change Original data Re-load as EUR *

24. ©2016 Transaction Type? • Dp*_InputTransType tells HFM what sort of number it is • Input 16 • Calculated 32 • Derived 128 • Dp*_Input stores YTD amount • Each record holds 12 months, numbered “0” through “11” • NoData 2 • Prior to a period that has data • NoData 96 • After a period that has data

26. ©2016 Change Flag to IsCalculated • IsCalculated does two things: • Built-in No Input rule • HFM automatically clears the values prior to Sub Calculate, Sub Translate • Enable IsCalculated • Rules are independent of this setting • A rule can write to an input account • Nothing forces you to have a rule when it’s IsCalculated

27. ©2016 Load Metadata Change • Database still shows Input (16) • Metadata change does not alter existing data • Grid shows “no input” • Data extract still includes “CalculatedAccount” • … because the InputTransType = 16

28. ©2016 This is Critical to Understand The InputTransType stores the metadata attribute at the time the number is written to the database! If the ‘IsCalculated’ attribute changes on the Account/Custom, this is not automatically updated in the data tables! …until a new number is written to that cell

29. ©2016 Consolidate Data • HFM automatically clears only cells with type “32”, not “16” Despite the IsCalculated flag • Must clear it manually afterward • Using HS.Clear in rules or Database Clear, or some other means • Or remove data before adding flag • Can load “NoData” value

33. ©2016 Changed the Zero View settings? • “How should I treat missing data?” • Zero YTD • HFM will derive a periodic value so we arrive at zero on a YTD basis, reversing out the entire YTD balance from prior period • Zero Periodic • HFM adds the periodic zero to prior period YTD, essentially carrying prior period forward • Applies only to Revenue, Expense, Flow type accounts Scenario settings

39. ©2016 Merge vs. Replace Mode Page 40 • Merge: leaves existing metadata in place and adds new members • Replace: removes existing metadata and adds incoming • We’ll use this, and is most widely used • Only for dimension(s) included in the file • Leaves all other dimensions alone

45. ©2016 Table: After the Change Page 46 • Account_Item table • ItemID 130 is gone • New ItemID 176 is in its place • DCE: data table • Data for ItemID 130 remains • Data for ItemID 176 also exists, from the journal entry Records for ItemID 130 are invalid

46. ©2016 The Data Page 47 • No way to recover “Sales” data • Must re-load the data, but into “Revenue” • Must manually update objects that use the label “Sales” • Rules and MemberLists • Grids and forms • Reports • Metadata re-load will create a new itemID, perhaps 177 • *EPMA will preserve the data • But you still have to manually update objects

49. Thank you for attending! Questions? Email us for a copy of the slides or link to the recording insights@finitsolutions.com Past webinars: www.finitsolutions.com/webinars Presenter: Chris Barbieri CBarbieri@finitsolutions.com General Questions: Cathy Lawton clawton@finitsolutions.com Joe Mizerk jmizerk@finitsolutions.com

Finit - what would happen greatest hits and disasters

Du liest eine Vorschau.

Hier ansehen

Finit - what would happen greatest hits and disasters

Weitere Verwandte Inhalte

Diashows für Sie (20)

Andere mochten auch (20)

Ähnlich wie Finit - what would happen greatest hits and disasters (20)

Aktuellste (20)