By Dwight Davis on March 21st, 2017
When companies integrate FDMEE with an ERP system, they often find that they can no longer massage data using scripting in an import format. The good news is Oracle added SQL in FDMEE. It allows you to do more than just mapping, and as a result you can use it to solve the data scrubbing problem that comes with the FDMEE and ERP integration. In this blog post, I will walk through a scenario where I did just that.
By TopDown Team on March 14th, 2017
When it comes to Oracle Planning and Budgeting Cloud Service (PBCS), the question we are consistently asked is: Can DRM publish metadata for consumption into Oracle Cloud? The answer is yes, with a couple of asterisks. Read on to find out how.
By Hoa Pham on June 13th, 2016
Recently, we’ve implemented FDMEE version 188.8.131.52 at a major client. This client has been using FDM classic version 11.1.2.x for many years and needed to upgrade to version 184.108.40.206 for compliance and maintenance support reasons. When we started this project, we installed the base version of FDMEE 220.127.116.11 with the .100 patch. Through the course of our implementation we ran into some noteworthy findings that we’ll discuss in this blog post. Our guideline for the FDMEE build was to use built-in functionality and be fairly vanilla, so avoid any custom coding.
By Thomas Thuresson on April 6th, 2016
FDMEE comes installed with variety of standard reports, just like in FDM. Most of the reports that came with FDM are ported to FDMEE. The big difference is that the embedded engine that renders the reports now is Oracle BI Publisher. The core data tables remain the same, making it easier to convert old custom…
By Patrick Kiernan on March 8th, 2016
What do you do when one line item provides more information than only one destination Point of View? For instance, assume that all of the trial balance accounts from an extract will load to a custom dimension member of “END”. However further assume that the trial balance has multiple members, typically in a custom dimension, for the balance sheet accounts that record movement.
By Patrick Kiernan on March 1st, 2016
In old FDM if there was ever a need to source two fields for an exception mapping, it was required to write a script to resolve this issue so that the scripted member would then be able to be mapped accordingly. For instance, there might be a Long-Term liability account in HFM, “AccruedTax”, that in almost all instances is sourced from a G/L account, 290100. Let’s say however, that there is one exception to this based upon the Entity, “WestSales”, where instead of being a long-term liability, this instead is a long-term asset for HFM, “LongTermDefTaxAsset.”
By Patrick Kiernan on February 24th, 2016
Let’s discuss the basic fundamental purpose of FDMEE. That is to say mappings. FDMEE has come a long way since its origins, and is at this stage is an ETL-like tool (Extract Transform Load). Mapping is the “T”, Transform, part of this acronym. This is where source system, typically General Ledgers, metadata members are transformed to a destination EPM application dimension member. Think of these as accounts, entities, cost centers, product members, and so on.
By TopDown Team on January 21st, 2014
When creating ODI Repository Login connections within the ODI Studio to Master/Work repositories, the saved Login connections are user specific, so if another Windows user account logs into the same machine to use ODI Studio for the first time, there will be no defined Login connections.
By TopDown Team on November 11th, 2013
Check out this handy FDM Account Mapping Script Sample.
By TopDown Team on June 11th, 2013
Check out this hand script for the times when you want to use SQL instead of Jython.