ModifedMerge: HFM / FDMEE

Many customers who use HFM have a typical close cycle where G/L data is first loaded using FDMEE and statistical/supplemental data is then loaded via FDMEE or is entered directly in HFM. If the customer reloads G/L data after the statistical data, what happens to statistical data? If the FDMEE data load mode is set to either Merge or Replace, it’s very possible that the statistical data is going to be overwritten. This would require previously loaded data to be reloaded or re-input. If there are multiple FDMEE locations, this can become a data load nightmare. ModifiedMerge is a dynamic solution to this problem.

ModifiedMerge leverages the default FDMEE data load process to dynamically clear only data intersections from the most recent data load. You no longer have to worry about other data intersections outside of the data file being cleared.

How does it work?

When data is loaded via FDMEE, FDMEE creates a data file in the standard HFM format that is stored in the FDMEE Outbox. ModifiedMerge will dynamically copy all the data lines in that previous data load file and change the data amounts to the special HFM code “NODATA”. All those data lines will be appended to the new data load file.

This new data load file is then loaded into HFM using the FDMEE Merge load option. The built in functionality of the Merge option overwrites the data in the application with the data in the load file. Only the specific data intersections in the new load file will be overwritten. Data intersections not included in the file will not be modified.

ModifiedMerge can be deployed to impact specific FDMEE Locations to give you flexibility when you have special instances when you do not want to overwrite the previous data load.