By Juan Porter
June 20th, 2017
Handling text data in a Hyperion Planning application is relatively easy and straightforward. Planning metadata is stored in a relational database. This textual information is accessible via web forms, HFR, and Smart View out-of-the-box. On the other hand, managing and reporting on text data is not quite as simple in the Essbase technology. Essbase handles dates and smart lists but can’t handle freeform text values. The situation is further complicated by the fact that your smart lists need to be synchronized between Planning and Essbase for the data transfer to be accurate. In this recorded webcast, Handling Textual Data in Planning and Essbase—A Starbucks Case Study, Rhonda Brigham, Starbucks, and I (Juan Porter, TopDown Consulting) discuss how they used a creative approach to get text data in three different forms—smart lists, dates and freeform text data—to flow from Planning to Essbase. We also discuss the overall project goals, technologies, POCs, and the reason for choosing the solution they did, including design and results. They will then describe the solution in detail which included Smart Lists being managed in DRM; sent to Planning via the Outline Load Utility from a relational source, and sent to Essbase using a Jython ODI Procedure, and an Essbase Java API program.
Want to find out more? Check out this recorded webcast (part of the TopDown Kscope17 Encore Series) by me and Rhonda Brigham, a case study on handling textual data in Essbase.
TopDown’s experts presented all of their Kscope17 during our Kscope17 Encore Series. We covered the gamut of topics. You can find all the recordings here.
Handling Textual Data in Planning and Essbase—A Starbucks Case Study – Juan Porter and Rhonda Brigham, Starbucks