This chapter covers the following topics:
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 E-Business Suite reports available to your responsibility.
Variable Report
Submit variable reports with attribute sets and publishing options defined in Oracle E-Business Suite.
Upload File
You can upload any kind of file, such as a Web page, an image, or a business document.
Select parameters and submit financial reports as concurrent requests.
Submission Parameters Region Notes
Report Name: Choose any available Financial Statement Generator (FSG) report.
Period: Choose an accounting period. Accounting periods were defined in the calendar for the ledger.
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, Oracle General Ledger User's Guide.
Note: Assign the display type PE (Page/Expand) to the segment for which you want separate reports for each segment value.
You can use any display type in a content set, including Row/Total (RT), Row/Expand (RE), Row/Both (RB), Column/Total (CT), Page/Expand (PE), and Page/Total (PT). You can also use complex combinations of these display types for an account assignment in a content set definition.
You can select a complex content set with a combination of Page/Expand and Page/Total display types to generate your report. When users view the report in the Report Display page, 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 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.
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's 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's Guide.
Rounding Option: 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: 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: Select a date and time for the report to be submitted to the concurrent manager or choose to submit it now.
The Financial Statement Generator (FSG) is a powerful report-building tool that enables you to define custom financial reports in Oracle General Ledger without programming. FSG supports reusable and interchangeable report components, such as row sets and column sets so that you can mix and match your existing rows and columns to create an entirely new report in seconds.
Report Manager's Ad Hoc Financial Reports feature enables you to create an FSG report on demand by selecting the components at the time of submission.
For detailed information on FSG report components, see Financial Reporting, Oracle General Ledger User's Guide.
Submission Parameters Region Notes
Report Title: Assign a title to your report.
Row Set: Select the Row Set to include in your report. For more information, see Defining Row Sets, Oracle General Leder User's Guide.
Column Set: Select the Column Set to include in your report. For more information, see Defining Column Sets, Oracle General Ledger User's Guide.
See Submitting Financial Reports for descriptions of the remaining parameters.
Optionally enter Control Values for your report. For information on control values, see Including Budgets, Encumbrances, and Currencies in an FSG Report, Oracle General Ledger User's Guide.
You select parameters and submit reports as concurrent program requests. The parameters depend upon the type of report and its definition. When you select the name of the report the parameters defined for that report appear on the page.
Submission Parameters Region Notes
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.
You can upload any kind of file and then apply the Report Manager publishing parameters.
Use the Browse button to locate the file, then continue through the process train.
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 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. For more information, see Archiving Reports.
Expansion Value: With standard and variable reports, you can use the expansion value feature to restrict access at the user level. For example, you may want to publish the report to a responsibility that many users have access to, but only some should see the report. Assign an expansion value that exists in a value set to the report and ensure that the users have access to this expansion value in the Report Manager Security Workbench. For more information, see User to Value Security.
For File Upload: An uploaded file does not require parameters. It can use the timeframe value to produce and display multiple iterations of the same file to information consumers. It can also use the expansion value feature to secure access to the file at the user level.
Security Region Notes
Three content security methods restrict user access to certain values.
Note: You can also define repository security to restrict the users who can view and manage a report or folder in the Reports Repository. See Defining Repository Security.
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.
Your Financial report is submitted with a content set.
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.
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 My Oracle Support Knowledge Document 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.
If you publish a summary income statement for departments 100 to 120 and you only have access to departments 100 through 110, then your report will produce a summary income statement for departments 100 to 110.
If users are restricted to departments 100 to 105, then they can only view information in the same report for departments 100 to 105.
A user is restricted to departments 100 to 105 and accounts 1000 to 2000. The published report is restricted by the department value set. The user can only see departments 100 to 105. However, the accounts in the report are unrestricted. Even though the user is restricted to accounts 1000 to 2000, the user can view all accounts in this report.
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.
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.
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.
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.
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 (See Storage 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. See the Overview of Repository Management.