All About Oracle Applications.....: Oracle Report Manager User Guide

Oracle Report Manager User Guide

Note:Refer Oracle Report Manager Configuration Guide article in this my blog before referring this user guide

Oracle Report Manager is an online report distribution system that provides a secure and centralized location to produce and manage point-in-time reports.

Oracle Report Manager Users can be either report producers or report consumers. Report producers submit, publish, and set security for reports. Report consumers view and approve reports.

Reports can be published and presented to certain responsibilities without additional security or a variety of security models can be applied, allowing only authorized users to view entire reports or parts of reports. In addition, you can use your templates to integrate reports displayed by Report Manager using your organization's individual style.

Oracle Report Manager:

· Provides a centralized report distribution system for point-in-time reports.

· Enables information producers to submit and publish Financial Statement Generator (FSG), Ad Hoc FSG, Variable Format, and Standard reports to a central repository.

· Enables information producers to present reports in the repository to information consumers via menu items on the Oracle E-Business Suite Home page or portal.

· Is accessible by any Oracle Applications user using a Web browser.

· Offers approval requirement before making reports available for general viewing.

· Permits report availability in a future timeframe.

· Allows you to view spreadsheets or PDF files for further analysis.

· Secures reports by utilizing three security paradigms: User to Value, custom, and flexfield segment.

· Provides an archive facility to maintain reports for future reference that no longer need to be displayed to report consumers.

· Enables the publishing of reports that have been submitted as part of request sets or report sets.

· Enables you to upload any type of file and publish it to a central repository. Reports in the repository can then distributed to the Oracle E-Business Suite home page.

You have the following options for submitting and publishing reports:

· Financial Report

Submit any of the Financial Statement Generator (FSG) reports available to your responsibility.

· Ad Hoc Financial Report Submission

Define the Financial Statement Generator report components at runtime, if a predefined FSG report does not exist.

· Standard Report

Submit any of the standard Oracle Applications reports available to your responsibility.

· Variable Report

Submit variable reports with attribute sets and publishing options defined in Oracle Applications.

· Upload File

You can upload any kind of file, such as a Web page, an image, or a business document.

Process Flow for publishing reports through Oracle Report Manager-

Prerequisites:

• Your user responsibility has been granted access to report submission.

• A layout template exists for the report you want to publish

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 are 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.

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

Example:

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.

Example

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, Excel, or PDF.

Publishing FSG reports from General Ledger Responsibility

Refer Oracle Report Manager Configuration Guide article in this my blog before referring this user guide

Log into Oracle Applications and navigate to your personal homepage. Under
Navigate, click GL_RUN REPORTS ALL responsibility. Under this responsibility, click Financial Report Submission.
Responsibility
Desktop Integration
Navigation
Personal Homepage > GL_RUN REPORTS ALL > Financial Report Submission

Below ‘Submission Parameters’ page will get opened.

Select FSG report name from LOV of Report Name. Then select period from LOV. Enter all required parameters.

Submission Parameters:

Notes

• Report Name: You can choose any available Financial Statement Generator (FSG) report.

• Period: Choose an accounting period. Accounting periods were defined in the calendar for the set of books.

• Date: The effective date for the report must fall within the chosen period.

• Currency: The values in the report will use the selected currency.

• Content Set: Defined in Oracle General Ledger, the content set allows users to generate multiple report outputs by segment. For example, if a content set for departments is applied, then the report will create a separate report for each department. See "Defining Content Sets" in the Oracle General Ledger User Guide.

• Display Set: The Display Set allows users to hide or show specific columns and rows. See "Defining Display Sets" in the Oracle General Ledger User Guide.

• Row Order: Defined in Oracle General Ledger, the Row Order controls how detail rows appear in the report. See "Defining Row Orders" in the Oracle General Ledger User Guide.

• Rounding Options: You can specify whether calculations are performed before rounding or if numbers are rounded before calculations are done.

• Flag Exceptions: Select the box to flag any exceptions in the report. If this box is checked, then only the rows that meet the exceptions defined in the column set for the report will be displayed.

• Segment Override: The submitter can select a segment of the accounting flexfield to use as an override and use it to fine-tune the report to include less or more information.

• Scheduling Options: You can either select a date and time for the report to be submitted to the concurrent manager or choose to submit it now.

For example-

Report Name: Trial Balance - EI
Period: AUG-13
Date-31-Aug-2013
Currency: USD
Flag Exceptions: Unchecked
Content Set:
Display Set:
Row Order: ACCT VALUE and DESC
Rounding Option: Calculate Then Round
Segment Override: 150…………
Scheduling Options: Now

Click Next ‘Publishing Parameters’ page will get opened

Publishing Parameters:

Note-

The publishing parameters determine the template to be applied to format the report,the security to restrict access to the report, and when the report becomes available.

Publishing Parameters Region Notes

• Default Template: Assign a template to the report or accept the default template.The default template is the last template you applied to this report. The template determines how the information in the report appears on the page. Templates are stored in the Oracle XML Publisher Template Manager. Templates are XSL:FO based, but can be created as RTF files using Oracle XML Publisher. Excel can be used to edit financial report templates provided in Oracle Report Manager. See Templates, page 5-1 for more information.

• Timeframe: Use the timeframe feature to publish multiple iterations of a report to the same self-service menu item. For example, during month-end close you may be generating versions of a report on a daily basis. You can assign each iteration of a report a timeframe value, publish it to the same location, and when information consumers view the report online, they will be able to select the iteration of the report they want to view in the "Timeframe" list.

• Set Auto Archive: To automatically mark this report for archive, select "Yes" and choose the date. This option may already be set to a default value.

Security Region Notes

• Three security methods restrict user access to certain values:

• User To Value Security is defined in Oracle Report Manager and is available for financial reports, variable, and standard reports. Select the content set or value set to be used for security. User to Value security requires the following:

Note: If user to value security is used to secure expansion values,flexfield segment security will not be enforced.

1. Your financial report is submitted with a content set.

2. Exactly one segment value in the content set has a display type of PE (Page/Expand). The value set that is assigned to this segment must be selected on this page.

3. You must assign an expansion value when publishing standard or variable reports. The expansion values must exist in the value set you identify on this page.

• Custom Security uses any PL/SQL security packages defined in the system. Enter the name of the security package. For information on setting up custom security, see Oracle MetaLink Note 333304.1: How to Apply Custom PL/SQL Based Security with Oracle Report Manager.

• Flexfield Segment Security is available only for financial (FSG) reports. The rules available to select were created in Oracle General Ledger and are assigned to the responsibility you are logged in under. The report must contain a content set and one segment value in the content set must have a display type of PE. Security applies to the expanded segment values.

Availability Region Notes

• Availability restricts when a report is available to users who have access to the responsibility under which the report is published.

• Specific Date and Time: If you select a specific date and time when the report becomes available, then you can also specify one or more reviewers to approve the report. A reviewer can change the date and time the report will be published.

• On Hold: If you select On Hold, then you must also designate one or more reviewers.

• Reviewers: Reviewers can be assigned to reports that are on hold or scheduled for a specific date and time. The user publishing the report is always set as a reviewer. When a reviewer approves a report with expansion values, the approval extends to all expansion values including those the reviewer cannot view. When a reviewer approves a report with a time frame, only the time frame being viewed is approved.

Default Template: Generic FSG Template

Timeframe: AUG-13

Set Auto Archive: No

Security: No Security

Availability: Now

No Reviewer

Click on Next, ‘Storage Location’ page will get displayed

Storage Location

Designate where to store the report in the repository. If the report name and time frame for the report are the same as a previously published report, then select Next to publish your report to the same location and overwrite the existing report. If the report name is the same but the timeframe is different, then when you select Next the report is added to the existing report. When the report is viewed the viewers will see the additional timeframes in their timeframe selection list. This applies to the report types: single report over time and expanded report over time. Expand the hierarchy to find and select the folder or previous version of the report.

Select New and select path.

Click on Next ‘Presentation’ page will get populated

Presentation:

Determine which responsibility will have access to a report. Users will access reports by selecting menu items under their responsibility. One or more reports can be stored under the same location in the repository. When a menu item is created, it is associated with the repository location, regardless of whether one or many reports are stored in that location.

Example

A single report over time may actually consist of 12 distinct instances of a Summary Income Statement, one for each month of the year. It is likely that each of these distinct reports are stored in the same repository location and assigned only one menu item. In this scenario, when users attempt to view the Summary Income Statement report, they will see the report with a dropdown list in the header region allowing them to select a different timeframe to view (from January to December in this case).

Since multiple reports can be stored in one Repository Location, there may not be a need to create a menu item for a report that is stored in the same location as a report with a menu item already associated with it. To bypass this step, select Next on the Presentation Page.

In much the same way, by selecting Next you can choose not to create a menu item for a report that is being published. By doing this, the report is still stored in the repository; however a menu item will not be associated with it, rendering it unviewable for users who do not have access to the Repository Management screens.

If you decide not to create a menu item for a report during the publishing flow, you can create one later using Repository Management.

Check ‘Create menu for this report’

Menu Item : Trial Balance Report Aug-13

Responsibility: GL_SUPERUSER

Select GL_SUPERUSER

Template: