ReportRequestForm.doc

Purpose and Context of this Document This document is intended to capture the basic business requirements and layout of a proposed report from the business users. The document should be used to reach agreement by the requesting parties (i.e. business users) on the layout and detailed characteristics of the report. The request process has four basic steps. The request is initiated: The person making the request fills out Section 1. The request is reviewed: The request is then sent to Susan Empey and/or Bill Roden via Email. The request is given an initial review. The initial reviewer determines if the request is accepted or rejected. The initial reviewer logs all accepted requests. Section 2 is filled in with the reviewer’s, comments and an initial estimate of how much effort is involved to help in prioritizing the request. If accepted, the reviewer will review the request with the Business Owner. The Business Owner must approve the request for the report to go into the Report Development Queue. The Report Request Queue is reviewed and prioritized by the appropriate committee (SA/HR, Distributed Users Reporting Strategy Group (for distributed reports) or Oracle Financials Business Owners (for central office reports)). The report is assigned for development: Once the request is scheduled for development, ITSS/Reporting Analyst(s) uses Section 3 as a guideline to develop a detailed Functional Specification. The ITSS/Reporting Analyst will work with the report requestor, and/or the other Business Resources specified in Section 1, to define the Functional Specification. The Functional Specification is assigned to the Programmer/Analysts to develop a Technical Specification from which to code the report. The report is finalized. The report is published/migrated for use. Business Requirements Report Layout and Description If possible, provide a printed copy of the layout you are proposing for this new report – what does the report look like? Remember - reports can have