When using an import data connection to an SAP BW system, the data is copied into an SAP Analytics Cloud (SAC) model (referred to as a dataset in the question). To keep this data current with the source SAP BW system, SAC provides a scheduling mechanism. You can configure a schedule to automatically refresh the dataset on a recurring basis (e.g., hourly, daily, weekly), ensuring the data in your stories and analyses is up-to-date without manual intervention. This is a standard feature for managing imported data.

A. You must create a new dataset. This is incorrect. SAP Analytics Cloud provides built-in data refresh capabilities for existing datasets (models), making the creation of a new one unnecessary for updates.

B. You must manually reimport the data. This is incorrect because of the word "must". While a manual refresh is possible, it is not mandatory, as scheduling provides an automated alternative.

C. You must refresh the story that uses the dataset. This is incorrect. Refreshing a story updates the visualizations with the latest data available in the SAC dataset/model, but it does not trigger a data import from the external SAP BW source.

1. SAP Help Portal

SAP Analytics Cloud

"Updating and Scheduling Models": This official documentation states

"You can update a model with new data from a source file or a data source. You can also schedule a data import job to run at a specific time

or on a recurring basis." This directly confirms that scheduling (Option D) is a valid method.

2. SAP Help Portal

SAP Analytics Cloud

"Import Data Connection to SAP BW": This documentation details the creation of connections and models based on SAP BW data. It outlines that once the model is created

its data is managed within SAC and can be refreshed. The scheduling feature is the primary mechanism for automating this refresh process.

3. SAP Help Portal

SAP Analytics Cloud

"Refreshing Story and Page Data": This source clarifies the distinction made in option C. It explains

"When you refresh a story

you're not updating the model with new data from the source. You're just retrieving the latest saved version of the model." This confirms that refreshing a story does not update the underlying dataset from the source system.