In earlier versions of FDMEE/FDM, you could not setup multiple instances of the same target application. Locations in the same application in FDM that existed on a lagged calendar had to be loaded to different months than locations with a non-lagged calendar. Starting in version 220.127.116.11.220, a new feature was introduced to allow duplicate target applications via adding a prefix to the target name. This feature unlocked the capability to load non-lagged locations to the same month as lagged-locations in the same target application. Non-lagged locations exist in one prefixed target application and lagged locations exist in another. Each of these prefixed target applications point to one physical application, but will have different period mappings. The user is able to load to the correct month, regardless of whether the location is on a lagged or non-lagged calendar. All while maintaining a single month in the point of view.
Prefixed Target Applications Process
Let’s walk through an example. Application “CB_2” is on a lagged calendar so we copied that application but added a prefix, “STND_CB_2” to represent the non-lagged calendar. To do so, under Target Application in the Setup tab, find the application you would like to create a copy of. Click Add.
Next click on the Type drop-down menu. Find the type of application you are trying to copy. The application in our example is a Planning application.
You are then able to specify what the prefix of the copied application will be. We chose “STND_” to signify the copied application is on a non-lagged calendar year, or a standard calendar year. For example, the month of March is period 3 for a standard calendar year.
Once you click OK, go back to your Target Applications. Find your new prefixed target application. As seen below, the dimension details are the same for both.
Now create different period mappings for each of these target applications. For example, in “CB_2”, the month of March will be mapped to target period month 4, since the “CB_2” application is on a lagged calendar.
Conversely, in the STND_CB_2 application, March will be mapped to target period month 3. When loading files for locations with the target applications “STND_CB_2” and “CB_2”, both will be able to load to March but have that file go to its respective target period month.
Although this technique is most commonly used to allow applications to use different period mappings, it can be applied similarly using different category mappings, calculations, loads, application settings, etc. Any difference you want to attain within one specified application can be applied!
Questions? Comments? Feel free to reach us at:
Brittany Peterson, email@example.com
Amy Stine, firstname.lastname@example.org