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...

Incredibly Simple Things You Can Do in FDMEE – Tip 8

Tip 8 – Define a Member Mapping Based on Multiple Source Values Using Multi-dimension Mapping Forget using a script to derive a target member based on more than one source field value.  FDMEE now has multi-dimensional mapping. See the following screenshot for an example.  Using multi-dimension mapping, we can easily derive a Planning Smart List member based on source account and a custom field value....

Incredibly Simple Things You Can Do in FDMEE – Tip 7

Tip 7 – Use Query by Example to Filter Data One of the features that makes FDM such a hit with end users is its visibility into transformation logic.  You can easily navigate to the Data Load Workbench and investigate imported data and associated target system mappings in the data grid. Now, FDMEE has made it even easier to explore data grid information using Query by Example. With Query by Example you can easily filter on data that’s most important to you by typing in the filter text box above a given column. Take a stroll around the FDMEE user interface and you will find that Query by Example is just about everywhere, including Data Load Workbench, Data Load Mapping, and Process Details.  Essentially any UI component that uses a data grid (columns and rows) to display information incorporates the Query by Example feature....

10 Incredibly Simple Things You Can Do in FDMEE

One of my seven year-old daughter’s favorite phrases is “easy, peasy, lemon squeezy”.  She said it recently and I thought, You know, who doesn’t like when something goes as expected or when a product or service just works? Ultimately, technology exists to make life easier, right?  Oracle EPM software is no different.  This got me thinking about how FDMEE makes transforming and loading data in the Oracle EPM world easier than ever. Over the next couple of weeks, this series will show you 10 Incredibly Simple Things You Can Do in FDMEE. Tip 1 – Register a New Target Application Tip 2 – View an Execution Log Tip 3 – Download Metadata to Excel Tip 4- Use Lifecycle Management Tip 5 – Schedule a Job with Batch Processing Tip 6 – Map Blank Record Values Tip 7 – Filter Data Using Query by Example Tip 8 – Define Target Members Based on Multiple Source Values Using Multi-dimension Mapping Tip 9 – Use Advanced Search Tip 10 – Override Default Location Settings with Data Load Rules...

Incredibly Simple Things You Can Do in FDMEE – Tip 6

Tip 6 – Mapping Blank Record Values Sometimes incoming source records don’t have a value for every field (column).  For example, Company X tracks its revenue and expenses by product.  Each income statement record for Company X has a corresponding product, while all other account records do not have a product, that is, the product field is blank. To manage this scenario in FDM Classic, you could use a custom import script.  The script would evaluate the product field of each source record and if a record had no value (was blank), the script would assign a dummy value – e.g., NO_PRODUCT. FDMEE finally introduced an easy way to handle this to the FDM world with the <BLANK> notation.  Using the <BLANK> notation in a Like map, you can easily map source fields with no value to a target member. A number of legacy FDM users have been waiting on this for a long time.         (Note: <BLANK> interprets a blank character or space, for example ” “.  It cannot be used for mapping NULL or no value.  Additionally, when interpreting blank characters, it’s important to make sure the import file agrees with the specified file character set under System...

Incredibly Simple Things You Can Do in FDMEE – Tip 5

Tip 5 – Scheduling a Job with Batch Processing Anyone familiar with FDM Classic knows the power of Batch Loader. Batch Loader is used to automate data loads. With FDM Classic, you had to use the Windows clients, FDM Workbench and FDM Task Manager, to create and schedule batch jobs, respectively. With FDMEE, setting up and executing a batch job is way easier. You simply use the Batch Definition component to build your job and then you use the Batch Execution component to execute and/or schedule the batch. That’s it.                  ...

Incredibly Simple Things You Can Do in FDMEE – Tip 4

Tip 4 – Using Lifecycle Management Want to save a file back up of FDMEE for disaster recovery purposes? Need to synchronize your FDMEE apps across environments? FDMEE makes this easy with Lifecycle Management. Lifecycle Management – commonly referred to as “LCM” – provides a mechanism for migrating application content across environments and even operating systems. You can access Lifecycle Management via Shared Services. In Shared Services, navigate to your FDMEE application. Select your FDMEE application to display a list of migration artifacts. Choose your artifacts and click the Export button to name and generate your LCM package. When the export is complete, your LCM package (a collection of XML files) will appear in the File System group in Shared Services. From there, you can download the LCM zip file to a network share.        ...