BUSINESS REQUIREMENTS

Project Name:

Warehouse Reports Enhancement (Division)

Primary Author:

Christine Sisti

Reference RFS#:

To be provided upon Business Approval

Project Tier:

None

Version Control
Version

v.1

Version
Description

Version 1

Date
Completed
(MM/DD/YYYY)
7/14/15

Author

Description of
Change

Business
Approval

Date Approved
(MM/DD/YYYY)

Rivka
Golding

Warehouse
Reports
Enhancement
(Division code)

Eddie
Skrzyniarz
or Luis
Lopez

Pending

Page 1 of 7

Table of Contents
A.

Introduction ........................................................................................................................ 3

B.

Definition of Terms ............................................................................................................. 3

C.

Stakeholder Business Requirements................................................................................ 4-6

D.

Business Impact................................................................................................................... 6

E.

Cost Estimates, Resource Requirements and Duration Estimates. (If Applicable) ............. 6

F.

Approvals ............................................................................................................................ 7

Page 2 of 7

A. Introduction
Serves to introduce the client to the purpose of the document and provide an executive
summary of the requirements.
Purpose of the Document
o Describe why this project is being undertaken
o The statement of the problem, opportunity or need
o The history, situation or issue that led to the decision to proceed with the project
Executive Summary
o Project Definition, Mission Statement, High Level Goals, Business Objectives
Background: Division is significant in that it drives retail store cycle counts, and plays a major role in
AX. All orders placed in AX are based off of Division.
Issue: The Operations Team wants to restructure the cycle count process at the stores so that the
count is completed by division. Stores currently cannot locate an item by division using the cycle
count report. It is important that discrepencies between Retail Pro and AX be minimized.
Solution: A division field will be added to the ASN Report, Slips Report and Vouchers Report. The
division field will help align Retail Pro reporting and AX reporting. The Division field will aid in
projecting what the warehouse should be expecting in terms of returns back to stores.
The division field will also enable operations to create return transfer orders for returns once items
are already in transit, and help predict the volume of returns coming to DC by Division for the outlet
channel.
B. Definition of Terms
Functional describes the behavior and information that the solution will manage.
Non-Functional describes the environmental conditions under which the solution must remain
effective.
Priority Definitions (MoSCoW)
1= MUST Have (Showstopper) Core functionality and/or discretional functionality that will halt
business if not implemented. No workarounds available. Requirement must be satisfied to be
considered a success.
2=SHOULD Have (Critical) non-core functionality and discretional functionality that is logical
corollary for core functionality. Manual workarounds available. Requirement should be satisfied if
possible.
3= COULD Nice to Have (Value Add) non-core and discretional functionality that does not impact
the business process. Manual workarounds available. Requirement could be satisfied but not
necessary.
4= WONT Requirement wont be satisfied in this release, but may be considered for the future.

Page 3 of 7

C. Stakeholder Business Requirements

The Stakeholder Business Requirements section should describe what the system will deliver in
terms of functionality, features, and/or capabilities. When utilizing the table below indicate the
primary subject with X.0 and then the detailed requirements of that subject as X.1.,X.2, etc.
Req.
No
1

Requirement
Priority
Description
Add Division
Column to
ASN Report
Add Division
Column to
Slips Report
Add Division
Column to
Vouchers
Report
Add Division
Parameter to
ASN, Slips,
Vouchers
Reports

Functional / NonFunctional

Owner/Source

Functional

Operations
Team

Functional

Operations
Team

Functional

Operations
Team

Functional

Operations
Team

Comments

Dropdown box with ability

to select all

Page 4 of 7

Req. No 1
The below reports need Division added as a column header and as a parameter
Retail Pro>Reports>Category:Receiving and Transfers>ASN Report
Retail Pro>Reports>Category:Receiving and Transfers>Slips Report
Retail Pro>Reports>Category:Receiving and Transfers>Vouchers Report
A. ASN Report

B. Slips Report

Add Division as
column header and
parameter

Add Division as
column header and
parameter

Page 5 of 7

C. Vouchers Report

Add Division as
column header and
parameter

D. Business Impact
Identify the impact of the requirements to the business. This should include an exploratory
component to reveal any vulnerability, and a planning component to develop strategies for
minimizing risk.
Business Area
Operations
Other Business Areas

None

Budget

IT

Training

None

Headcount

Major process change

None

Responsibilities

Not applicable

Ongoing support

Service Desk procedures in place

E. Cost Estimates, Resource Requirements and Duration Estimates. (If Applicable)

This section of the document displays the breakdown of effort and cost deliverables and/or time
frame as appropriate. Note that this section will be updated after the technical analysis has been
completed.
Deliverable
Effort / Cost
Time
Added column header to
existing reports
Added parameter to existing

Page 6 of 7

reports
TOTAL

Not applicable

Not applicable

F. Approvals
List the names of the individuals who formally signed off on this document. Include their
department/business unit, title, and the date they gave their approval to proceed. For
individuals who sent an e-mail approval, this should be explicitly stated with a copy of the e-mail
attached for reference purposes.
I have reviewed the requirements presented in the document above and approve that they are
fully and correctly represent the needs of our business.
Signature or
Business
Date of
Name & Title
E-mail
Unit/Department
Approval
Approval
Eddie Skrzyniarz, Retail Logistics
Operations
Manager or Luis Lopez, Retail Logistics Pending
Pending
Project Manager

Page 7 of 7