Starting the Budget Review Process
The administrator initializes review processes by placing planning units in the First Pass state. Data is typically promoted for review after users enter data, calculate, and save. When users promote planning units, they enter annotations that record assumptions and select the next owners or reviewers. Promoting planning units:
Assigns ownership to the selected user
Overrides access permissions on the planning unit to read-only for non-owners
Changes planning unit status from First Pass to Under Review
Updates status for upper-level (or lower-level) planning units to Under Review as necessary
Records an audit entry in the process history
Optionally sends e-mail notifications to the application owner and new planning unit owner
Reviewers can make modifications and annotations. Read-only users can enter planning unit annotations and account annotations, but cannot enter data values. Users can keep a personal copy of the original data to track modified data. When planning units are promoted, the reviewer is the new owner and typically:
Receives e-mail notifications and is directed to the Process Definition page
Sorts the status page by entity, process state, or current owner
Reviews annotations and planning unit history
Opens data forms and reviews, analyzes, modifies, and calculates data
Makes annotations (including account annotations)
Promotes or rejects the planning unit, with iterations until the planning unit is approved
After planning units are approved, the application owner becomes the planning unit owner. Only administrators can reject planning units. To close the review cycle, the application owner or administrator changes the scenario or version to read-only for all users.
Table 13. Starting the Budget Review Process
Users | Tasks |
|---|
Administrators | Starts the planning unit for the planning cycle |
Users with access | Enters data |
Users with access | Calculates data |
Users with access | Optionally, creates a copy of submissions |
Users with access | Promotes data for review |
Users with access | Enters annotations to support the review process. Until an owner is established for a planning unit, multiple users can update it. Access permissions for non-owners are changed to read-only when the planning unit is promoted to the next reviewer. |
Users with access | Notifies reviewers that the planning unit is ready for review |
Users with access | Reviews data in the promoted planning unit |
Users with access | Reads and modifies promoted data through data forms |
Users with access | Runs business rules |
Users with access | Reads promoted data using Financial Reporting, Oracle's Hyperion® Web Analysis, Smart View, or third-party reporting tools |
Users with access | Modifies data values, enters annotations, signs off on planning units, and promotes, rejects, and approves planning units |
Administrators | Checks the planning process status |
Administrators | Reads supporting annotations |
Administrators | Views the audit trail |
Administrators | Completes the planning cycle |
Administrators | Changes user access of scenarios and versions in Essbase to read-only |
Administrators and interactive users | Publishes reports using Financial Reporting |