FDMEE is case sensitive and the order of rules in mapping tables is determined by special characters in the rule name. When working with scripts in FDMEE, the order of processing stacked expressions depends on whether it is for the amount field or other fields. Additionally, there are specific requirements for load files, script formatting, and mapping tables in FDMEE.

1. Last updated on June 16, 2015
 FDMEE is extremely CASE SENSITIVE in data mapping as well as Import formats.
 FDMEE does not validate the target value for Automap Wildcarding.
 In FDMEE, mapping table sequence has been changed from FDM. The mapping Type (ie. Explicit
or Like) is still the primary sequence. However, the next sort sequence is determined by the
Rule Name in the table. When special characters such as the “underscore” (“_”) is used, the
mapping conversion sequence changes. The following is the EXACT order (example) how FDMEE
evaluates and converts the mapping based on the Rule Name:
W!X!99960
W"X"99960
W#X#99960
W$X$99960
W%X%99960
W&X&99960
W'X'99960
W(X(99960
W)X)99960
W*X*99960
W+X+99960
W,X,99960
W-X-99960
W.X.99960
W/X/99960
W99960
W:X:99960
W;X;99960
W<X<99960
W=X=99960
W>X>99960
W?X?99960
W@X@99960
WX99960
W[X[99960
WX99960
W]X]99960
W^X^99960
W_X_99960
W`X`99960
W{X{99960
W|X|99960

2. W}X}99960
W~X~99960
 Working with Journal Load:
o
 When executing Import format(s), FDMEE appears to process Amount first and other functions
such as script(s) next.
o For all fields except the Amount field, FDMEE processes stacked expressions in the
following order:
1. Script
2. Fill or FillL
For the Amount field, FDMEE processes stacked expressions in the following order:
1. DRCRSplit
2. Fill=EuroToUS
3. Script
4. Sign
5. Scale
6. NZP
 When working with special characters in the script, one might need to get the ascii code of the
character to work within the script.
 Use the following function to generate Log Info for trouble-shooting, “fdmAPI.logInfo("Assigning
global variables...")”. The double quotes can be any statement to help identify where the code
breaks.
 The “Skip” Row feature within Import Format module is only available to “Fixed” file format and
not “Delimited” file format any longer. The solution is to update the TBHVIMPITEMFILE table to
have the Skip Row to the specific format. Once, it’s inserted, it allows the user to update the
parameter within the Import Format module.
 In FDM classic, same Locations can be created in different applications. FDMEE now creates a
single source of applications and thus Locations can NOT be “shared”. New locations and import
formats need to be created for each application.
 Oracle/PLSQL is unique and the FDMEE query definition is stored in FDMEE’s scheme and the
table is “TQUERYDEFINITION”.
 Load file’s name CAN’T have “apostrophe” or special characters
 In Script Editor, spacing and alignment is super critical; each indentation is FOUR blank spaces
 Script name and script’s definition has to MATCH
 Working with mapping table
o “#SCRIPT” has to be in CAP in order for the Edit mode to be activated.
o Download the Excel template (MapLoader.xls)
o Do NOT delete the rows or modify the columns in MapLoader.xls, leave the extra lines
as blanks is fine; there is macro looking for the “range” of data to be imported.
o There is a bug in version 11.1.2.3.500+. Need to scroll to the last record in order to
export the dimension’s mapping table into Excel file.

3. o The Source and Target columns are CASE SENSITIVE; use MAPLoader.xls to replace the
cases and then load back into the system
 Known bugs (not exlcusive):
o Default Fish Icons In FDMEE NOT being Displayed (Doc ID 1985807.1)
o FDMEE Export to HFM Fails with error: "Error in CommData.exportDataTraceback ... in
executeVBScript RuntimeError: -4" (Doc ID 1613234.1)