1. Administrator's Guide
  2. About Close Manager
  3. Sample Task Flows

Sample Task Flows

Scenario 1: Power User

The Power User sets up a template and tasks for an upcoming close period.

  • The Power User logs on and opens the Manage Templates page.

  • The Corporate Quarterly Close template contains many of the tasks required for the corporation quarterly close cycle. From the list of templates, the Power User selects the Quarterly Close template and reviews it.

  • The Power User selects the calendar dates on which to line up the template tasks, and creates a schedule from the quarterly template.

  • The Power User then adds a task to the template specifically for Quarter 2.

  • The Power User opens the schedule, which begins the close process.

Scenario 2: Power User

The Power User monitors the status of close activities through the Dashboard.

  • The Power User logs on and opens the Dashboard Status Overview view to check the status of activities through Day 3.

  • From the Dashboard, the user drills down to see the details of incomplete tasks.

  • The Power User reviews open tasks for comments or attachments provided by assigned users.

Scenario 3: Approver

A user assigned as an Approver reviews a current task to determine whether it can be approved.

  • The assigned Approver receives an email notification of an outstanding task––Review MD&A Input for Services submission.

  • From the email, the Approver selects the link for Review MD&A Input for Services Submission.

  • The Task Actions page is launched outlining the process.

  • The Approver reviews the document that the user submitted when completing the task to ensure completeness.

  • The Approver enters additional comments and approves the submission.

  • If another level of approval is required, the task is forwarded to the next approver. If the task was the last requiring approval, then the task completes, and the system runs the next task if it is ready.

  • The Approver can reject a task instead of approving it, and the task is reassigned to the Assignee.

Scenario 4: User

A user logs on to the application and reviews and completes an assigned task.

  • The user logs on and reviews the tasks displayed in the Dashboard in the My Worklist portlet.

  • The user clicks the link for an assigned task - MD&A input.

  • The task page is launched with instructions for the task, and a reference document.

  • The user reviews the instructions and the reference document, processes the updates, enters a comment about the task, and submits it for approval.

  • The system automatically updates the task status and sends a notification to the assigned approver.

Scenario 5: User

A user responds to an email notification of a task to load data, clicks a link in the email, accesses the product from which to load data, and then completes the task.

  • The user receives an email notification of an outstanding task––Load Salary Data through Oracle Hyperion Financial Data Quality Management.

  • From the email, the user selects the link for the page where the required process is documented.

  • The user reviews the instructions for the task and selects the Go to Task link to launch FDM.

  • The user extracts data through FDM and loads it to Oracle Hyperion Financial Management.

  • When the task is completed, the user returns to the application.

  • The user enters a comment about the task and submits it for approval.