There are Descriptive Flex fields (DFFs) for Treasury in Oracle Fusion that are not flowing to the Fusion Data Intelligence (FDI) system for some reason. These DFFs are essential for us in building Treasury reports. 

Note: SR 3-37725214561 was created for this issue. Workaround of data augmentation was offered, which is sub-optimal. DFFs should interface directly to FDI. Concerns include FDI performance considerations when data augmentation is used; and manual intervention needed to augment data.

Business case: Cleveland Clinic uses the ‘Program’ segment (segment 5) in our Chart of Account value (8 segments) to track Treasury Funds.  A Treasury Fund represents a donation (gift, endowment, etc.) made to the Cleveland Clinic to advance the organization’s mission.  Often these donations are for specific purposes and can stipulate certain restrictions.  As the steward of these donations, the Cleveland Clinic needs to associate attribute values (aka, DFFs) with each Treasury Fund to support the management and required reporting that are unique to Treasury Funds.  For example, DFF ‘Fund Type’ defines if the fund is unrestricted, temporarily restricted, or permanently restricted.  Knowing the ‘Fund Type’ is critical to the proper management and usage of the fund.  When Oracle Fusion ERP was implemented, there was no delivered solution to support Treasury Funds, so Cleveland Clinic developed the DFFs to support these management and reporting needs.  As Cleveland Clinic implements Oracle FDI, in conjunction with our implementation partner PwC we’ve determined that leveraging the Treasury Fund DDF values for reporting and security is necessary for our business requirements.

Below is the list of the Treasury DFFs that did not interface to FDI: