EPM FCCS Case-Insensitive
We are migrating from HFM (11.1.2.1.0) to EPM FCCS (FDMEE 24.11.07). I have come across an issue that is painful to say the least. Everything is case-sensitive in EPM FCCS. Meaning if I search in Data Exchange for a mapping with a source key containing 'abc' but the source key is actually 'ABC' then I cannot find the mapping. This also means that validations/exports fail if the source and target keys are not exactly correct.
Is there a specific place I can request our implementation partner to go look at to make our database case-insensitive? Not sure this applies here, but searching has shown something along the lines of setting the NLS_COMP and NLS_SORT fields to LINGUISTIC and BINARY_CI respectively…but I have no clue where that would be located. Any help to make our FCCS application be case-insensitive for Data Exchange mappings would be much appreciated.