© Copyright 2019 PartsWatch Solutions, LLC.

All rights reserved.

This software-related document contains proprietary information of PartsWatch Solutions, LLC; it is provided under a license agreement containing restrictions on use and disclosure and is protected by copyright law.

Due to continued product development this information may change without notice. The information and intellectual property contained herein is confidential between PartsWatch Solutions, LLC and the client and remains the exclusive property of PartsWatch Solutions, LLC. If you find any errors in the documentation, please report them to PartsWatch Solutions, LLC. PartsWatch Solutions, LLC does not warrant that this document is error-free.

No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of PartsWatch Solutions, LLC.

No patent liability is assumed with respect to the use of the information contained herein. Although every precaution has been taken in the preparation of this document, the publisher and author assume no responsibility for errors or omissions. Neither is any liability assumed for damages resulting from the use of the information contained herein.

PartsWatch® is a registered mark of PartsWatch Solutions, LLC.
Exploris is a customization of the PartsWatch system for General Parts, Inc. (GPI).

Microsoft® Office, MS-DOS®, Windows®, Windows® NT, Windows® 95, Windows® 98, Windows® 2000, Windows®2003, Windows® XP, Windows® Vista, Windows® 7, Windows® 8 and Windows® 10 are trademarks or registered trademarks of the Microsoft Corporation in the United States and/or other countries.

PartsWatch Solutions, LLC
83 Spring Street
Suite 303
Newton, NJ
07860
(973) 300-0606
Website: http://www.PartsWatch.com

Table of Contents

1. Document Information. 3

1.1.        Publication Record. 3

1.2.        Document References. 3

1.3.        iTrack Information. 3

2. Scan Session Validation Report Process Overview.. 4

2.1.        Purpose of Changes. 4

2.2.        Detailed Description of Changes. 4

2.2.1.         Changes to Scan Session Report Screen. 4

2.2.2.         Changes to Scan Session Variance Report Screen Option. 4

2.2.3.         Scan Session Variance Report 6

2.2.4.         Record Retention. 8

3. Performance Considerations. 9
4. Impact to Other Modules. 9
5. Development Details. 9
6. Client / Data Center Implementation Considerations and Tasks. 9
7. Deferred Functionality. 9
8. Approvals. 10

1.    Document Information

1.1.    Publication Record

Upon approval of this document, Revision 1.3 is the current version of the iTrack#54816 57.16 GPI Exploris Scan Session Validation Report Functional Specifications Document (FSD).

The graphics illustrated in this document represent the proposed design. Modifications made during development may alter the final de sign without changing intended functionality.

Numbers, currency, dates, and times in this document are written in English (United States) format; however, the application supports other languages and formats for numbers, times, and dates.

1.2.    Document References

The following document has been referenced in the preparation and creation of this FSD.

1.3.    iTrack Information

The following table provides information about iTrack issues that have been referenced in the preparation and creation of this FSD.

2.    Scan Session Validation Report Process Overview

2.1.    Purpose of Changes

The ability to report variances between the ASN quantity vs the quantity shipped is needed by the stores. Quantities shipped against Purchase Orders for vendors that do not send ASNs will continue to be handled by existing scan receipt functionality.

The purpose of this document is to define the changes needed to the Scan Session Variance Report in order to alert the stores to the differences in product shipped vs product received.

2.2.    Detailed Description of Changes

2.2.1. Changes to Scan Session Report Screen

1. Reduce the number of rows in the upper grid used to select scan sessions from 9 rows to 6 rows for both Quick Reporting Options.
2. Move the SORT BY and SHOW VARIANCES ONLY fields from above the upper grid to below the lower grid. The fields are used for report output when the SCAN SESSION VARIANCE REPORT is selected. The fields will not display when the SCAN SESSION REPORT is selected.
3. Add a DISPLAY button below the PRINT button on the right side of the screen that will be used for the SCAN SESSION VARIANCE REPORT only and will be unavailable for the SCAN SESSION REPORT.
4. When the SCAN SESSION REPORT or the SCAN SESSION VARIANCE REPORT is selected, all statuses of scan sessions will continue to display, whether complete, incomplete or in-progress.

2.2.2. Changes to Scan Session Variance Report Screen Option

1. Reduce the number of rows in the lower grid from 8 rows to 6 rows for the SCAN SESSION VARIANCE REPORT.
2. Add a new “ASNS” tab to the right of the CONTAINERS tab.
3. With the ASNS tab selected for the SCAN SESSION VARIANCE REPORT:

• Add START DATE and time and END DATE and time fields above the lower grid that can be used to filter the rows displayed. Default both date fields to the current date, and the time fields to 12:00:00 AM (start) and 11:59:59 PM (end).
• Add a new multi-select VENDOR field that will be used to filter the grid choices by vendor. Line Codes with/without the USE AS VENDOR flag checked will not be available; only suppliers will be able to be selected. The field will default to blank to indicate all vendors.

4. When the ASNS tab is selected, the START DATE and END DATE will use the PO Receive Date to filter the rows displayed in the lower grid.
5. When the ASNS tab is selected, clicking the DISPLAY button will show the results in the bottom grid, depending on the search filters. The DISPLAY button will be unavailable when the MANIFESTS, PACKSLIPS or CONTAINERS tab is selected.
6. Since only completed scan sessions can be used for the SCAN SESSION VARIANCE REPORT, should the user check one or more scan sessions in the upper grid that are not complete (in-progress or incomplete status), when the DISPLAY button is clicked, the system will prompt “Only completed scan sessions can be reported.” OK closes the prompt. The user must uncheck any scan sessions that are not complete and retry.
7. Add the check-all checkbox to the lower grid header to allow users to check / uncheck all displayed rows when the ASNS tab is selected.

Note: No changes will be made to the MANIFESTS, PACKSLIPS or CONTAINERS tab functionality.

2.2.2.1.       ASNS Tab

1. The ASNS tab is used to select the ASNs to output in the report and includes only vendors that send ASNs.
2. Depending on the filters, ASNs will display in descending (newest to oldest) order. The user will be able to click the column headings to re-sort the data.
3. Only received ASNs will display with POs that have been received.
4. If the ASNS tab is clicked, display the following columns in the grid:

• ASN #
• ASN CREATE DATE
• VENDOR
• PO #
• PO RECEIVED DATE

5. If an ASN has multiple POs, a separate row will display for the ASN for each received PO. An ASN row will not display for POs or back order POs that are not yet received.
6. Since only completed scan sessions can be used for the SCAN SESSION VARIANCE REPORT, should the user check one or more scan sessions in the upper grid that are not complete (in-progress or incomplete status), when the PRINT or PREVIEW button is clicked, the system will prompt “Only completed scan sessions can be reported.” The user must uncheck any scan sessions that are not complete and retry.

Menu Path: Reports, Purchasing, Scan Session Reports, SCAN SESSION REPORTS screen, SCAN SESSION VARIANCE REPORT button, ASNS tab

2.2.3. Scan Session Variance Report

Note: No changes will be made to the SCAN SESSION VARIANCE REPORT when output from the MANIFESTS, PACKSLIPS or CONTAINERS tabs.

1. A report named “SCAN ASN VARIANCE REPORT” will be output in portrait orientation when the ASNS tab is in focus and the PRINT or PREVIEW button is clicked.
2. The selected date range will be output below the report name following reporting standards.
3. Show the following header information:

• LOCATION: Store #(s) and name(s).
• ASN: ASN #(s)
• SCAN ID: Scan Session(s)
• SHOW VARIANCES ONLY: Yes / No

4. The following columns will be output:

• LINE
• PART NUMBER
• SCAN QTY (total of all selected sessions per part)
• ASN QTY (total of all ASN ship quantities per part)
• VARIANCE (variance quantity per part)
• ASN # (ASN number)
• SHIP QTY (ship quantity per ASN)
• VENDOR (vendor per PO)
• PO# (purchase order number)

5. If necessary, the ASN number will wrap.
6. The LINE and PART NUMBER will display once per part, outputting the total quantity scanned and the total quantity shipped.
7. The report will compare the scanned quantity from the selected scan session(s) to the ASN ship quantity to validate the ASN quantity against the physical product received and output the results in the VARIANCE column.
8. The ASN a part is found on will be output on the part row and if the part is on more than one ASN, each additional ASN will display on a separate row without re-displaying the LINE, PART NUMBER, SCAN QTY, ASN QTY or VARIANCE.
9. If an ASN has multiple POs, a separate row will display for the ASN for each received PO. An ASN row will not display for POs that are not yet received.
10. For variances, output ‘over’ quantities as a positive value and ‘short’ quantities as a negative value.
11. If the SHOW VARIANCES ONLY flag is checked, then only applicable parts with a variance will be reported. Following is an example of the SCAN ASN VARIANCE REPORT output with the SHOW VARIANCES ONLY flag checked:
12. If the SHOW VARIANCES ONLY flag is unchecked, then all applicable parts will be reported regardless whether a variance exists or not. Following is an example of the SCAN ASN VARIANCE REPORT output with the SHOW VARIANCES ONLY flag unchecked:

2.2.4.  Record Retention

1. Since scan sessions are saved until manually deleted by the user, the ability to remove sessions in the completed (CMP) status will be added to the Record Retention functionality. Open sessions in the in-progress (INPROG) or incomplete (INCMP) status will not be included and will remain available until completed or deleted by the user.
2. Add “SCAN SESSIONS” to the RETAIN THESE RECORDS FOR… section of the RECORD RETENTION SETUP screen opened from the Utility Options, Record Retention menu that will be used to determine how long to keep scan sessions.
3. The PERIODS will be “DAY”, the ACCEPTABLE RANGE will be “1 TO 90 DAYS”, defaulting to HOW MANY of “30”.
4. The WHEN RUN will be “DAILY”.
5. All existing Record Retention functionality will be used to delete scanned sessions.

3.    Performance Considerations

N/A

4.    Impact to Other Modules

N/A

5.    Development Details

N/A

6.    Client / Data Center Implementation Considerations and Tasks

N/A

7.    Deferred Functionality

The ability to select Line Codes with the USE AS VENDOR flag checked from the VENDOR field when the ASNS tab is selected for the SCAN SESSION VARIANCE REPORT is deferred.

8.    Approvals

In order for the project development to proceed, signatures are required to indicate acceptance of the documentation. The approval signature can be in the form of a hand-written signature on a printed copy of the document, or an e-mail confirming approval from the approver (the e-mail must contain the full document name, including revision number).