If the system administrator has enabled outgoing emails from Essbase, then the appropriate scenario participants receive email notifications for scenario changes.

To set up SMTP email notifications:

1. Log in to Essbase as a system administrator.
2. Click Console.
3. Click Email Configuration.
4. Click the SMTP Configuration tab.

   SMTP controls outgoing email.

5. Enter your company’s SMTP host and port.
6. Enter your company email address and password, of the sender of the notification email.
7. Click Save.

When SMTP mail is set up, scenario participants begin receiving emails when their scenarios change status, ownership, priority, or due date.

When users are added to the system, email is an optional field. If it has not been filled out, then that user cannot receive emails even if they participate in scenarios.

An existing scenario can be updated (see Update action in the table) to change the owner, the priority, or the due date. If, for example, the scenario’s due date is changed, then the participants will receive an email indicating the new due date. The old due date will appear in strike through text, so that it is clear what information about the scenario was updated.

To create a scenario, you specify general information about your scenario, including creating a scenario name, selecting a due date, selecting an application and cube, and choosing whether to use calculated values. Then you add users and define whether each user is a participant or an approver.

1. In Essbase, login as a user with database update (or higher) permission to at least one application.
2. Click Scenarios.
3. Click Create Scenario.
4. On the General Information tab, enter a scenario name and select a Priority (optional), Due Date, Application, and Database (cube). You will only see applications for which you have minimum database update permission.
5. Turn on Use Calculated Values if you want to merge calculated values to base values when running calculation scripts on scenarios.
6. (Optional) Enter a description.
7. On the Users tab, click Add for a list of users.
8. Add the users that you want.
9. Close the Add Users dialog box.
10. For each user, keep the default (Participant), or select Approver.
    Scenario user roles determine the workflow for the scenario.
11. Save your changes.

As a scenario user, you can model data slices in your own scenario.

1. In the Essbase web interface, on the Applications page, click Scenarios.
2. On the Scenarios page, locate the scenario in which you want to model data.
   • You can search for the scenario by name in the Search field.
   • You can select your application from the All Applications drop-down list and search within that application.
   • After selecting the application, you can further narrow your search by selecting the database (cube) from the All Databases drop-down list and searching within that specific cube.
3. Launch Smart View by clicking the Excel icon before the scenario name.
4. Make data changes and perform your what-if analysis in Smart View.

   If you change and submit values and decide you want to go back to the base values, you can revert to the base by typing #Revert in the changed cells and choosing Submit Data on the Smart View Essbase ribbon.

   If a cell in the base has a value, and you want the corresponding cell in the scenario to be #Missing, you can send #Missing to the scenario or you can delete the value in Smart View and select Submit Data on the Smart View Essbase ribbon.

5. Continue this process until you’re ready to submit data for approval.

After you submit a scenario for approval, no one will be able to write to that scenario.

1. In the Essbase web interface, log in as the application owner or the scenario owner.
2. Click Scenarios.
3. Under Actions, click Submit .
4. (Optional) Enter a comment.
5. Click OK.

After the owner of the scenario submits for approval, the approver has the option to approve or reject scenario changes, and the scenario owner is notified of the action. You must be logged in as an approver to have the options to approve or reject a scenario.

1. In the Essbase web interface, click Scenarios.
2. Next to the submitted scenario, under Actions, click Approve or Reject .
3. Enter a comment on the Approve or Reject dialog box.

You can apply data changes from the Scenario page in the Essbase web interface, or by using the DATAMERGE calculation command.

When you apply data changes, the changes stored within the scenario overwrite the base data.

1. In the Essbase web interface, click Scenarios.

2. Next to the approved scenario, under Actions, click Apply.

3. When prompted, leave an optional comment and confirm your selection.

• You can also apply data changes using the DATAMERGE calculation command.
• After a scenario is applied, you can delete the scenario to reuse the sandbox for that scenario.
• Database managers and higher can execute a calculation script to perform a DATAMERGE. They do not need to be designated as scenario approvers in order to do so.
• After a scenario is applied, it can be re-applied, but it cannot be changed.

If you have the service administrator role, or if you are a scenario user (participant, approver, or owner), you can copy a scenario. You can copy scenarios at any point in the scenario workflow, prior to Delete Scenario. The approval state of the copied scenario is reset to In Progress.

1. In the Essbase web interface, click Scenarios.
2. Click the Actions menu for the scenario you want to copy, and click Copy.
3. Enter the scenario name and select what scenario components to copy from Approvers, Participants, Comments, and Data.
4. Click OK.

You can delete a scenario in the Essbase web interface.

1. In the Essbase web interface, click Scenarios.
2. Click the Actions menu for the scenario you want to delete, and select Delete.

You can review a scenario using an optional approval workflow.

Scenario user role assignments determine the workflow for scenarios. You must have at least one approver to enable the scenario workflow. Without an approver, participants do not have the option to submit the scenario for approval, for example, and there is no option to approve or reject the scenario.

The only action for scenarios without at least one approver is Apply. Without an approver, the scenario owner can still change data values in the scenario and apply data changes to the cube (or reject them), without going through an approval process.

Participants can participate in a what-if analysis. They must have Database Update or Database Access user role. Adding participants is not mandatory.

Approvers monitor the process, and approve or reject scenarios. They must have Database Access or higher role. Scenarios can have multiple approvers, in which case each one must approve the scenario before it can be submitted.

Participants and approvers with the Database Access user role cannot write to a scenario until they are granted write access through a filter.

Participants and approvers are not mandatory. The scenario owner can change data values in the scenario and commit data changes to the cube (or reject them) without designating participants or approvers.