Sap Business blueprint dummy blueprint for learn project

DUMMAY NAME Business Warehouse

Legacy Business Warehouse Project
Blueprint Specification

Table of Contents:

Execptive Summary

I. Introduction and Project Goals
II. Project Scope
III. Data Content and Design Strategy
IV. Data Access and Reporting Strategy
V. Apthorization and Security Strategy
VI. Change Management and Training Strategy
VII. Technical Environment
VIII. Other Issues

Appendixes

A. Glossery of Business Warehouse Terms
B. Naming Conventions
C. Business Warehouse Project Team
D. Business Warehouse Technical Support Team













Execptive Summary

The Dummay Name project is in reality two projects: the establishment of a Legacy Business Warehouse (DUMMAY NAME) to preserve and provide continuing comppter access to legacy master and detail data; and, the establishment of an DUMMAY NAME Business Warehouse (IBW) providing full access to DUMMAY NAME financial and human resources data for query, reporting and decision support systems, once PT’s DUMMAY NAME transaction processing system has been implemented.

This “Blueprint” addresses only the DUMMAY NAME project. An IBW Blueprint will be developed later in the DUMMAY NAME project. The DUMMAY NAME will “go live” concurrent with the implementation of DUMMAY NAME (April 2, 2001) and DUMMAY NAME data will be frozen at that point in time. No keyed relationship is planned between DUMMAY NAME data and legacy data.

Within the scope of the DUMMAY NAME project is the extraction of legacy data from ten (10) mainframe based data sources, identified by the project team as important for preservation and continued access via comppter. These sources include the University’s financial, grant and contract, purchasing, human resources and payroll data, dating back as far as 1981. The “reverse conversion” of R/3 data, the retroactive adjustment of legacy data, and pre-defined reports beyond templates and examples are beyond the scope of the DUMMAY NAME project.

Data extracted from these sources will be manipulated optside of the BW framework for loading into the DUMMAY NAME as InfoCubes. The DUMMAY NAME will not use any SAP BW delivered structures; all InfoObjects will be designed and developed from scratch by the BW Technical Support team. Special data handling will be required to accommodate legacy data stored in non-positional arrays, situations where the interpretation of a data element is dependent upon the value of a related data element. Full normalization of transaction data in those situations will not be ensured.

The BW Explorer query, decision support and reporting tool will be the data access tool supported for the implementation of the DUMMAY NAME. Additional, non-SAP OLAP tools will be evaluated for selection and use with the DUMMAY NAME and IBW as the DUMMAY NAME project matures.

DUMMAY NAME security will be a “role based” security strategy consistent with DUMMAY NAME security. Four end user roles have been identified: financial query developer, human resources query developer, financial report developer and human resources report developer. Query developers are strategic users identified within the central administration of each business area who will have unrestricted access to all DUMMAY NAME data. These query developers will establish general query templates providing access to financial data that will enable a wide audience of report developers to develop end user queries and reports as they see fit.

End user training and change management will be provided in concert with the DUMMAY NAME Change Management team. Specific BW Explorer training will be provided to a population of DUMMAY NAME end users expected to be relatively small. Only a score or less strategic query developers are anticipated and no more than a two hundred report developers. User training will begin with the BW project team who will participate in the testing and quality assurance activities of the project and continue with the business area strategic users. Report developer end user training is expected to continue well beyond the implementation of the DUMMAY NAME system and encompass and compliment IBW training.

The DUMMAY NAME technical environment provides for development, quality assurance and production server platforms. These environments are UNIX based and structured for the staging of system modifications and changes by the SAP transport system. The production system DUMMAY NAME is on an independent and powerful, IBM RS/6000 S80 server, sized to accommodate many hundreds of users. At this point a BW specific SAPGUI client will be required on each desktop comppter needing access to the DUMMAY NAME as well as BW Explorer.

At least two remaining issues need to be addressed. A facility is needed for non-SAP University systems to have referential access to chart of accounts and payroll employment status data. The strategy is to provide this facility via the IBW, allowing users to extract needed referential data on demand. The second issue is the disposition of legacy data not planned for inclusion in the DUMMAY NAME. At some point this data must be either abandoned or archived.