Business Requirement Document

Revision History

Authors and Contributors

Document Approvals

In order to meet the needs and expectations of the company, it is imperative that all parties involved have a clear and defined requirement to follow. The purpose of this document is to outline the business requirements for Exploris and the possible touch points throughout related systems and applications.

By approval of the Business Requirements Document, you indicate that you agree with the contents herein.

Projects that have regulatory, middleware, SIB or IRS touch points will require additional approvals from those areas.

Approvals, Business  Stakeholders

Table of Contents

1.0        Project Impacts to Business / Systems. 4

2.0        Summary Analysis. 5

2.1                 Glossary of Terms 5

2.2                 Project Summary. 5

2.3                 Project Scope. 5

2.4                 Business Objective. 5

2.5                 Current Process 5

2.6                 Problem Statement 6

2.7                 Proposed Solution (or Process) 6

3.0        Functional Requirements. 7

3.1                 Scan Receipt Functionality. 7

3.1.1             Variance Report Screen Changes 7

3.1.2             Scan Session Changes 7

3.1.3             Superseded Parts 7

3.1.4             Scan Variance Report Changes 7

3.1.5             Case Lots 8

4.0        Assumptions, Constraints, Dependencies and Risks. 9

4.1                 Assumptions 9

4.2                 Constraints 9

4.2.1             Systems 9

4.2.2             Environments 9

4.2.3             Support 9

4.2.4             Business 9

4.3                 Dependencies 9

4.4                 Risks 9

5.0        Attachments. 10

1.0                  Project Impacts to Business / Systems

This sub-section is used to list those business areas and/or applications that would be impacted by this project. Include other systems or processes dependant on data feeds.

2.0                  Summary Analysis

2.1                   Glossary of Terms

2.2                   Project Summary

Scan functionality was re-introduced by PWS as a roadmap item in 57.12.  The functionality has been tested and has yielded similar results in the stores.

This project is specific to the store scan receipt process and introduces new functionality that will allow stores to handle our more complex business model, accurately check-in their orders, be more process efficient and improve usability of the scan application functionality.

2.3                   Project Scope

The project scope is specific to the store scan receipt process and provides for a new user report.

2.4                   Business Objective

The business would like enhancements to current functionality to better handle the complexities of the Independent Store business model so the stores can accurately check in their freight using scanners and have it match the ASN’s they receive.

Some of these complexities include:

1. Superseded/Replaced Parts
2. Multiple shipping DC’s and stores
3. Backorder fulfillment
4. Case Quantities
5. Cross Order by Availability

2.5                   Current Process

CurrentScan Receipt Variance Report

2.6                   Problem Statement

1. The stores needsa report to see the variance between the ASN’s and the scan results. This would allow for the store to see what is short shipped from the DC..

2.7                   Proposed Solution (or Process)

Enhanced Layout

Sort by Line and then Part Number:

3.0                  Functional Requirements

This section is used to describe the actual business requirements in detail. It should be broken down into “Functional” and “Non-Functional” requirements.

3.1.1              Variance Report ScreenChanges

1. Exploris will provide another selection of ASN’s and the ability to select a date range that would show posted ASN’s on that date or a range of dates.
2. Exploris will provide / add another selection of PO. This would enable a store to compare a scan session to a PO from another vendor.

3.1.2              Scan Session Changes

1. We would like some changes to the scan session process so the user can tell what the last part was. Right now, if you scan part A, then B, then C, then another A, the cursor jumps up to the row for A and changes the qty. to 2.  It can be difficult to tell was the last part scanned the A or the C?  I think we almost need it to add a second entry to A in the order you scanned and then have the ability to combine and total all like part numbers when the scan session is completed.

3.1.3              Superseded Parts

1. Exploris will recognize the Superseded part shipped by the DC as contained in the ASN when the TM scans the “New Part” but the PO has the “Old Part”.

3.1.4              Scan Variance Report Changes

1. Location will be that Store’s Store Key
2. Pack slip will be the ASN(s) selected
3. Sort by Line and then Part Number
4. Ability to show all parts or just the parts with a variance.
5. Ability to print /export the report.

Example Grid

3.1.5              Case Lots

1. Need the UPC code file in Exploris updated from PIM team to handle case qty’s so that the variance report accurately shows the qty. scanned vs the ASN so that all case lots are not a variance.

4.0                  Assumptions, Constraints, Dependencies and Risks

This section is used to describe any physical restrictions, limitations and/or constraints that could impact the implementation of the enhancement/new functionality.

4.1                   Assumptions

1. The graphics illustrated in this document represent current application or the proposed changes / design. Modifications made during development may alter the final design without changing intended functionality.
2. Unless otherwise stated, all defined functionality will be available to JV and Independent stores in the USA and Canada.

4.2                   Constraints

4.2.1              Systems

3. None

4.2.2              Environments

1. None

4.2.3              Support

1. None

4.2.4              Business

1. None

4.3                   Dependencies

1. None

4.4                   Risks

1. None
2. None

5.0                  Attachments

Attachments from Mark