Oracle Report Manager Business User Flows

This chapter covers the following topics:

Publishing Reports

Prerequisites

Steps

  1. From the Oracle E-Business Suite Navigator, select the type of report you want to publish: Financial Report, Ad Hoc FSG, Variable Report, or Standard Report.

  2. For Financial, Variable, or Standard reports, select or search for the name of the report you want to publish. For Ad Hoc FSG reports, select the report components.

  3. Specify the parameters needed to submit the report as a concurrent request.

  4. Specify the publishing parameters.

    When the report XML data is generated, it is sent to the Oracle Report Manager repository where it is stored and available for presentation to viewers. Parameters include:

    • Security options for viewing the report.

    • Layout template to apply. Note that the template can be changed at any time when viewing the published report from the repository.

    • Expansion values or timeframes.

    • Reviewers to approve the report before it is presented.

    • Date to automatically mark the report for archive.

  5. Determine the location in the repository to store the report. If the report exists in the repository you can choose a new location or overwrite it.

    Note: If a folder is secured with repository security, then you must have owner privileges for the folder to publish reports to that folder. See Defining Repository Security.

  6. If you wish to publish the report to a menu item on the Oracle E-Business Suite Home page, you can apply presentation parameters to define where in the menu structure the report appears.

    Place a Summary Income Statement under a responsibility called Financial Reports that was created by your system administrator.

  7. Review all of your report parameters.

  8. Submit the report.

    A confirmation page displays your concurrent program request ID. You can monitor this request until it has successfully completed.

    Note that when you submit the report, two requests are submitted to the concurrent manager: the request to generate the data and the request to publish the data. The request ID displayed after confirmation corresponds to the Publish and Presentation Program. When you monitor your report you will see your submitted request and the Publish and Presentation Program. Your report will not be available for viewing until both requests have completed successfully.

  9. If you chose a reviewer for the report, the reviewer views the report and approves it, making the report available to all others with access.

  10. If you chose to publish the report to a menu item of a responsibility, then all users who have that responsibility and menu will see the report listed.

    Following the same example in step 6, users with access to the Financial Reports responsibility can navigate to that responsibility and view the Summary Income Statement.

    Timeframes and expansion values (for example, department) are available in lists. The viewer selects the time and expansion value to view. Security can restrict the expansion values a particular user can view (for example, department 100 only). The viewer can also select to output the report to HTML, Microsoft Excel, or PDF.

    If you published the report using a complex content set, then when users view the report, they can either view the individual reports for each segment by selecting the appropriate expansion value, or they can view the entire report data at once using the ALL option in the Expansion Value list. When users select the ALL option and view the report in Microsoft Excel, Oracle Report Manager displays the report in multiple worksheets, with the individual report for each segment in a separate worksheet.

Creating User to Value Security

User to Value security is applied to financial reports that use a content set or standard reports that contain a valid expansion value. Use the Security Workbench to give users access to specific values. See Overview of User to Value Security for more information.

Prerequisites

Steps

  1. Add value sets to the security workbench. For example, Department is a value set.

  2. Optionally, assign users to a selected value contained in a value set. Set privileges for each user in relation to the value. For example, John Jones and Jane Smith have Viewer privileges for department 100.

  3. Optionally, assign values contained in a value set to a selected user. Set the user's privileges for each value. For example, John Jones has Viewer privileges for departments 100, 500, and 600.

  4. Optionally, run the Security Listing Report to review all security assignments.

  5. A user who is publishing a financial report or a standard report that uses an expansion value assigns user to value security when submitting the report and selects the content set or value set to be used when determining user privileges for viewing the report. For example, an Income Statement report is assigned the Department value set.

  6. The report appears in the menu under the responsibility to which it was published. A user who has that responsibility can view the report for the values the user has privileges to access. For example, John Jones can view the income statement for departments 100, 500, and 600 while Jane Smith can only see the income statement for department 100.