Part 2 – FDM Migration Utility: The Secret Sauce

The FDM Migration Utility is implemented using Oracle Data Integrator (ODI). For those new to FDM Enterprise Edition, if you get under the hood of FDMEE, you will find ODI. ODI is the Extract Transform Load (ETL) engine of FDMEE. See the Oracle Data Integrator homepage for Oracle’s pitch on why ODI is a best-in-class ETL tool. The Utility consists of two (2) ODI Scenarios. The FDMC_EXTRACT_SETUP Scenario is used to migrate FDM Classic metadata objects, such as import formats and locations. The FDMC_EXTRACT_DATA Scenario is used to migrate historical data from Legacy FDM to FDMEE. (This scenario also creates data load rules.)   FDMEE comes with its own limited use license to ODI.  So, when setting up the Utility, you can use the instance of ODI installed with FDMEE.  There’s no need to license and download full-blown ODI. Next: Part 3 – FDM Migration Utility: Turn Classic to EE with a Push of a Button? Blog Series: Choose the Best Way to Migrate FDM Classic to...

Part 1 – FDM Migration Utility: System Requirements

Okay, so this is an easy one to get out of the way. Considering your Legacy FDM application version and setup, are you eligible to use Oracle’s FDM Migration Utility.  Here are the source system requirements for the Utility: FDM Classic Only – Source Version must be 11.1.1.x and 11.1.2.x. FDM Classic with ERPi: Source Version – If you’re using FDM Classic with the Enterprise Resource Planning Integrator (ERPi) module, only 11.1.2.x is supported.  (Note: The Utility will only update ERPi content via an in-place upgrade.) FDMEE: Target Version – FDMEE release 11.1.2.4 or higher. If you’re FDM Classic application system doesn’t meet the above criteria, or you’re going to FDMEE 11.1.2.3, re-building your application is your only route to FDMEE.  If you do meet the above criteria, both the rebuild and Migration Utility are viable options for your upgrade. Next: Part 2 – FDM Migration Utility: The Secret Sauce Blog Series: Choose the Best Way to Migrate FDM Classic to...

Choose the Best Way to Migrate FDM Classic to FDMEE

Time is running out for legacy FDM users. Oracle officially retired FDM Classic in favor of its successor, FDMEE. With your next Oracle EPM upgrade cycle Oracle requires you to migrate to FDMEE. Don’t worry; you will want to make the leap to take advantage of the many enhancements that FDMEE has to offer. (Click here for a few reasons why you will want FDMEE.) Before migrating to FDMEE, administrators (with the assistance of a seasoned consulting partner) have an important decision to make – Which migration method is right for us? Two Migration Options: Rebuild vs. Migration Utility   When FDMEE was introduced in 2013 with Oracle Enterprise Performance Management (EPM) System Release 11.1.2.3, going from FDM Classic to FDMEE was a rebuild.  Last fall, however, the Oracle FDM development team released the FDM Migration Utility to complement FDMEE Release 11.1.2.4. Since considering your journey from FDM Classic to FDMEE, you’ve probably browsed the Internet for nuggets of information.  Our guess is you’ve heard a lot about the rebuild approach and not a whole lot about using Oracle’s FDM Migration Utility. Our objective with this blog series is simple – Help you decide which migration method is best suited for your upgrade project based on your Legacy FDM application(s), which method is best suited for you.  This series is less how-to and more which way. Which path provides the smoothest road to your ultimate destination – FDMEE. Part 1 – FDM Migration Utility: System Requirements Part 2 – FDM Migration Utility: The Secret Sauce Part 3 – FDM Migration Utility: Turn Classic to EE with a Push of...

Incredibly Simple Things You Can Do in FDMEE – Tip 10

Tip 10 – Use Data Load Rules to Override Default Location Settings With FDMEE, instead of having a location for every import file, you can group related source file loads under a single location and use individual data load rules for each source file. About Data Load Rules For those new to the concept of a data load rule or “DLR”, think of a data load rule as a data import and data export profile. You use DLRs to define the data extract and data load instructions associated with a specific location and source data set. In the example below, you can see how easy it is to override the default import format associated with a location using a data load rule....

Incredibly Simple Things You Can Do in FDMEE – Tip 9

Tip 9 – Use Advanced to Take Your Search to the Next Level Throughout your FDMEE application, you will find the search button on various user interface (UI) components. By clicking this little guy, you can perform simple searches. Additionally, some UI components (like Select Point of View and Location Details) have the Advanced Search button. With advanced search you can take your investigation to the next level. With one click of the Advanced button, you get additional search operators, such as “Starts with” and “Contains”.           You’re also given the option to add fields to view and/or search on.           Just look for the Advanced...