This does look like a bug to me.
1 person found this helpful
Tested this on a 126.96.36.199.000.264 FMDEE and experienced the exact issue with the Customs(UD1 ,UD2 etc) for the HFM dimension and also checked on a few planning apps and saw the issue as well so this does appear to be a bug with FDMEE.
Certainly let us know what Oracle says(they should provide a bug number) in regards to if this is fixed in a future patch.
I reviewed the latest patches and none specially address the issue but it could have been an undocumented bug so you could apply the latest Patches and see if the issue goes away.
Mark the response as helpful if it was..
Thank you for replicating and verifiying the issue.
I am going to create a SR and will keep you guys posted.
Bug seems to be fixed with 100 patch. It is not listed explicitly as Fixed Bug within ReadMe though.
However...mapping import validation works now.
I think its because it was never actually reported as a bug therefore there was no official recognition that it was a bug, however somehow it has been inadvertently fixed with the 100 patch, hence it will not be listed in the readme as a fixed bug because it was never deliberately fixed
That makes sense...
We reported the bug actually 2 months ago. But you are right, we never received a confirmation that this has been recognized as a bug.
That was the case since version 9 I think...
The validate was not working when you were loading the mappings. It was working only when you were creating the mappings.
Glad the fixed that...