Wper

SAP Archive & Purge

# 30327

Archive enabled WPER (# 5)

Jira 7410

Reports Design Document

1/31/2013

Version 1.5

Prepared by:

Thomas Langner

Table of Contents

1 Report Overview 4

1.1 New Report or Existing Report 4

1.2 Report Location 4

1.3 Report Scheduling 5

1.4 Processing Dependencies and Constraints 6

1.5 Criticality of Report 6

2 Report Design 6

2.1 Business Rules Catalog 6

2.2 Field Definitions 7

2.3 Selection Criteria 7

2.4 Data Mapping 7

2.5 Sorting 8

2.6 Grouping 8

2.1 Special Data Requirements 8

2.2 Report Layout 9

2.2.1 Report Header Layout 9

2.2.2 Report Body Layout 9

2.2.3 Report Footer Layout 9

3 Non-Functional 10

3.1 Security 10

3.2 Performance Goals 10

3.3 Monitoring 10

3.4 Compliance 10

3.4.1 Payment Card Industry 10

3.4.2 Sarbanes Oxley Considerations 10

3.4.3 Data Security 10

3.5 IT Technology Services Considerations 10

4 Report Design Approvals 11

Appendix A - 12

Revision History

Major version number (X.0) should be updated each time changes are made to the document and the document is being published to an individual or group outside of the BA Team. Minor version numbers will not be tracked.

Date | Version | Description | Updated By |

01/24/2012 | 1.1 | Initial Draft | |

| | | |

| | | |

| | | |

Glossary

Define ALL acronyms, business terminology, definitions, and calculations that are relevant to the RFS or project.

Business Term | Acronym | Definition | Formula or Calculation |

| | | |

| | | |

| | | |

| | | |

1 Report Overview

The “Reports Overview” section should be used to briefly describe the business reason for the requested Report. It should contain a brief explanation of the report along with the primary areas that will utilize the report. This should describe what the report will be used for as well as why the report is needed.

The report will enable the user to lookup for a given date / IDOC number / Store# /...