by Doug Correa | 10 28, 2015 | EPM, FDM, FDMEE
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....
by Doug Correa | 10 27, 2015 | EPM, FDM, FDMEE
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....
by Doug Correa | 10 23, 2015 | EPM, FDM, FDMEE
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...
by Doug Correa | 10 23, 2015 | EPM, FDM, FDMEE
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. ...
by Doug Correa | 10 23, 2015 | EPM, FDM, FDMEE
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. ...
Recent Comments