FDMEE Errors: Writeback failure
In this series of Blogs, I am going to document few FDMEE errors, especially version 184.108.40.206, which I couldn’t find any reference about or there are no KB articles about.
The following error shows up in FDM, while importing Data from Planning to load to Oracle E-business Suite:
ODI-1226: Step COMM Validate Data fails after 1 attempt(s).
ODI-1232: Procedure COMM Validate Data execution fails.
Caused By: org.apache.bsf.BSFException: exception from Jython:
Traceback (most recent call last):
File “<string>”, line 9, in <module>
File “<string>”, line 4407, in validateData
File “<string>”, line 2622, in validateData
RuntimeError: [u”Error: Data rows with unmapped dimensions exist for Period ‘\u064a\u0646\u0627\u064a\u0631-2016′”]
The Error, although says, is due to Unmapped Dimension, but in fact it is not contributed because of any unmapped dimension, rather, an erroneous dimension mapping, wherein one member is mapped more than once in the mapping table.
On running a visual scan of all Mappings, and deleting the duplicate mappings, this error can be removed.
Additional Log Details:
ERROR [AIF]: Cannot calculate. Essbase Error(1200315): Error parsing formula for [FIX STATEMENT] (line 4): invalid object type
INFO [AIF]: EssbaseService.extractData – END (com.essbase.api.base.EssException: Cannot calculate. Essbase Error(1200315): Error parsing formula for [FIX STATEMENT] (line 4): invalid object type)
DEBUG [AIF]: AIFUtil.callOdiServlet – END
FATAL [AIF]: Error in CommData.extractDataFromSource