Viewing a Scenario in Smart View

You can look at a scenario in Smart View from the Essbase web interface, or from a Smart View private connection.

From the Essbase Web Interface

You can launch Smart View from a scenario in the web interface. When you do this, because you enter from the scenario, you can only work in Smart View in the sandbox member associated with the scenario from which you entered. The sandbox member is implicit. You do not see it in the Smart View grid.

Note:

A specific scenario is associated with exactly one sandbox member.

1. In a web browser, log in to Essbase.

2. On the Applications home page, expand the application to show the cube row for the outline that you want to modify, then click Scenario .

3. On the Workflow tab, click the Excel icon next to the scenario you want to view.

4. Select to open the file.

5. This launches Excel with a Smart View connection to the scenario.

When you do this, the slice of data for that specific scenario is in the worksheet. You can submit data only to that scenario (When you submit data to a scenario, you are submitting data to one sandbox member).

From a Smart View Private Connection

You can open Excel and make a private connection to your cube, without starting from the web interface:

When you do this, the sandbox dimension will be in the worksheet, so you can submit data to any sandbox member to which you have access. This is helpful when you are a participant in more than one scenario, but you must explicitly know which sandbox you want to work in.

Note:

To see which sandbox member is associated with a scenario, on the scenarios page, select the scenario, choose Edit, and view the General Information tab.

1. Open Excel.

2. Make a private connection to your scenario-enabled cube. See Accessing the Cloud Service from Smart View.

3. Do an ad hoc analysis.

4. Drill into the Sandbox dimension to view the sandbox members.

Examples

This is a Smart View grid including the Base member and a sandbox member. Sandbox values have not been updated, so they reflect the Base values. Those values are stored only in the Base, not in the sandbox members:

The changed sandbox value, 500, is stored in a sandbox member. The remaining sandbox value, 271 that was not updated is stored only in the Base:

This is a grid with multiple sandbox members. If you have the Database Update user role, you can create or work within multiple scenarios simultaneously: