Which statement is true about the Currency dimension for Modules and Custom application types?

For Module-based and Custom Planning applications, Oracle EPM Cloud does not seed a Currency dimension. To work with multiple currencies you must manually add a new dimension, set its dimension type to Currency, and then load the currency members yourself. Until you do so, the dimension is empty and behaves exactly like any other custom dimension; rate-type members reside separately in the HSPRATES dimension. Therefore, the only statement that accurately describes the Currency dimension for these application types is that it is delivered without content and must be set up as a custom dimension.

A. Exchange-rate-type members (Average, Ending, etc.) exist in the HSPRATES dimension, not in Currency.
C. “Local” plus reporting-currency members are created only after you build the Currency dimension; they are not supplied automatically.
D. The Input/Reporting hierarchy is auto-generated only in legacy (Classic) on-prem Planning, not in Module or Custom cloud applications.

1. Oracle EPM Cloud: Creating and Managing Planning Applications, “Enabling Multi-Currency in Modules and Custom Applications,” Sec. 7.4, p. 7-23, Rev. Jan-2024.

2. Oracle EPM Cloud: Working with Planning, “Managing Exchange Rates,” p. 9-2, Jul-2023.

3. Oracle EPM Cloud: Administering Planning, “Currency Dimension in Classic Applications,” p. 14-4, Feb-2022.