Data Integration to import data into the Forecast scenario requires which action?

• A. In the Map Members tab in the integration, use an Is Like map type to map all source records to the Forecast member in the target
• B. In the Map dimension tab in the integration, map the column for Scenario in the source to the Scenario dimension in the target
• C. In Category Mapping, map a source category to the Forecast member in the target
• D. In Application Options, enter Forecast as the default member for the Scenario dimension

Answer: (C)

In Data Integration, the way to ensure data lands in the Forecast scenario is to map the source data’s category to the Forecast member using Category Mapping. Your source file typically includes a category that indicates which scenario the data belongs to (for example, Forecast). By mapping that source category to the Forecast target member, the imported values are placed in the correct scenario within the Scenario dimension. This approach is designed to translate data categories into exact target dimension members, enabling accurate loading of data into the right scenario.

Other options don’t fit as well because mapping with Is Like would route all source records to the same Forecast member regardless of their actual category, losing scenario differentiation. Mapping the Scenario dimension in the Map Dimension tab would require the source to already carry a Scenario column that matches the target values, which isn’t always the case. Setting a default member in Application Options would apply only when there’s no mapping and doesn’t translate each category to the proper target member.