SAP BW–Report Dispositioning Process

LEDGER

D1 – Is the documentation complete (Information Request Form)?

D1a - Is this really a reporting need or a "want"? This is determined by looking at the current operation environment and the role the requestor has in the organization.

D2 - Is the data going to be in BW at a frequency that solves the user's request (intraday reporting)? This is driven by user’s need as well as technical

feasibility of being able to load the data in a timely manner. In general, intraday reporting may be better suited to come from R/3.

D2.5 - Is the data needed for this report already in our BW scope? If the data is already in-scope, the delivery of the requirement may be easy

("low-hanging fruit”).

D3 – Are there significant number of users? BW development is easier to cost-justify when a large number of users are involved.

D4 – Is the report resource intensive. If the report is often executed against R/3 and have many users. If that is the case, a driver can be to free up transactional resources by moving the report to BW. (having 40-60% of the CPU resources being used for reporting is not abnormal in a transaction system).

D5 – Does standard R/3 content exists. (Are there already a report available in R/3 )? If content exists, it is an indication that R/3 may be considered.

D6 – Does standard BW content exists? If content exists in BW, there is a lower cost of deployment of BW than if custom content has to be developed.

D7 – Is it less expensive to create in R/3. If there are custom formatted reports that are transaction oriented, it may be more cost effective to create it in R/3.

D8 – Is BW cost effective. This is a holistic total cost of ownership analysis that includes licensing costs, development costs, support costs, upgrade costs and cost of future development. It may also include opportunity costs of not developing the system.