[TC] - [Amount=NN] in FDMEE

User_2E55J

Dear Gurus,

While generating a write back file for 12 months in the process log I find the below messages for number of lines and also it shows the number of rejected records:

DEBUG [AIF]: EPMFDM-140274:Message - Exception while applying CURKEY mapping on the row:["E_100","P_00000","S_No","B_101","FY19","L_No","M2_No","C_00001","M1_No","Bud","Working","ACC_1208",#,#,#,#,#,66666.6667,100000.0000,133333.3333,166666.6667,200000.0000,#,286666.6667]

[TC] - [Amount=NN] "E_100","P_00000","S_1001","B_101","FY19","L_000","M2_No","C_00000","M1_No","Bud","Working","ACC_5130",2300.0000,#,#,#,#,#,#,#,#,#,#,1100.0000

On premise FDMEE:11.1.2.4.220

But the data load rule execution shows completed successfully. Request your suggestions on this to fix this issue.

Thanks in Advance.

Jeo123

[TC] - [Amount=NN] means Type Conversion - Amount is Non-Numeric.

The Amount field in FDMEE has to be a number(unless you changed that in the import format).  If you're actually loading # as an amount, it'll cause problems unless you deal with it in an import script.

User_2E55J

Thank you @Jeo123    for the information. Yes,for some periods data is coming as # and for write back I have created the custom application and the source is a planning application.

It would be helpful if you can throw some light on scripts to handle this issue.

SH_INT

You don't need to fix this issue unless it is causing a failure in the data load rule or the integrity of the data you are trying to write back. # generally represents missing data i.e. there its no data present for that period. It is the equivalent of 0 but doesn't consume unnecessary space in the source application e.g. Essbase. FDMEE will naturally exclude these records from the import as they have no value. Even if you converted them to a numeric zero FDMEE would still ignore them as that is it's default behaviour.

What is your source application for this process? Do you need a zero value for the empty periods in your write back file?

User_2E55J

Thank you for your input. As of now the process is getting successfully completed and the write back is between Hyperion planning and Fusion.

SH_INT

In that case I'd probably just take those log entries as info only. It won't be a problem those records are getting stripped out in the FDMEE import process as long as you have no requirement to write zero values into Fusion