Acme Pick Slip Md050 Draft
Acme Pick Slip Md050 Draft
ACME WMS
Enhancements
PICK SLIP REPORT
Author:
Mohammed Khan
Creation Date:
30-OCT-2015
Last Updated:
Last Updated by:
Version:
File Naming:
Versions = V1 Draft
ACME_PICK_SLIP_MD050_DRAFT
10/30/2015
Page 1 of 16
DOCUMENT CONTROL
CHANGE CONTROL
Date
Author
10/31/2015
Mohammed Khan
Versi
on
1.0
Change Reference
Initial Version
REVIEWERS
Name
Position
Date
Signature
APPROVERS
Total Workflow Approval on each document is due within 3 Business
Days.
Name
Position
Date
Signature
10/30/2015
Page 2 of 16
10/30/2015
Page 3 of 16
TABLE OF CONTENTS
Document Control................................................................................................................... 2
Change Control.................................................................................................................... 2
Reviewers............................................................................................................................ 2
Approvers............................................................................................................................ 2
Introduction............................................................................................................................. 5
Scope................................................................................................................................... 5
Out of Scope........................................................................................................................ 5
Definitions........................................................................................................................... 5
Report Functional Process and rules........................................................................................6
Business Requirements........................................................................................................ 6
Requirement 1.................................................................................................................. 6
Requirement 2.................................................................................................................. 6
Requirement 3.................................................................................................................. 6
Assumptions........................................................................................................................ 6
Process Flow / Description................................................................................................... 7
Business Rules..................................................................................................................... 7
Security Requirements......................................................................................................... 7
Report Specifications Pick slip.............................................................................................. 8
Report Description............................................................................................................... 8
Report Title and Use............................................................................................................ 8
Report Headings.................................................................................................................. 8
Column Heading.................................................................................................................. 8
Report Sample format.......................................................................................................... 8
Report Parameters............................................................................................................... 9
Report Validations................................................................................................................ 9
Mappings............................................................................................................................. 9
Concurrent Program Description........................................................................................... 10
concurrent Program Description........................................................................................10
10/30/2015
Page 4 of 16
Appendix A............................................................................................................. 13
10/30/2015
Page 5 of 16
INTRODUCTION
ACME requires a change to the seeded Pick Slip Report that can be generated in Oracle
during the Pick Release Process. The current Pick Slip Report is hard to read due to a small
font, has a poor overall layout, has some un-needed fields, and is missing some required
fields.
The Pick Slip Report will be used by the organizations that utilize paper based picking
processes.
This is a modification to a standard Oracle Report.
SCOPE
The scope of this document covers changes to the seeded Pick Slip Report only.
OUT OF SCOPE
DEFINITIONS
The following table contains a list of unique terms and their definition:
Term
VICS
DFF
AFF
API
Definition
Voluntary Interindustry Commerce Solutions
Oracle descriptive flexfield
Accounting Flexfield
Application Programming Interface
10/30/2015
Page 6 of 16
REQUIREMENT 2
Perform format and layout changes to make the report easier to read and more logically
group the fields together.
These changes include: enlarging and bolding the font size, and moving fields such as
Sales Order and Pick From Location to a more visible position or into a more logical
grouping.
Font: Times New Roman
Font Size: 10pt Bold
REQUIREMENT 3
Add additional fields to the report.
ASSUMPTIONS
The existing logic driving the seeded Pick Slip Report will be used
10/30/2015
Page 7 of 16
BUSINESS RULES
SECURITY REQUIREMENTS
2010 2011 ACME Consulting Corporation.
All Rights Reserved
10/30/2015
Page 8 of 16
10/30/2015
Page 9 of 16
REPORT HEADINGS
COLUMN HEADING
The following section details the additional fields that need to be added to the
seeded Pick Slip Report
<Ship From:> Warehouse street address
Warehouse city, state, zip code, and country code
<Part Number>
MTL_SYSTEM_ITEMS_B.SEGMENT1
[ Add Bar Code for Task Id]
* The Barcode field should have a Code128 Barcode format for the Task Id number
Add barcode for Order Number (The Barcode field should have a Code128 Barcode format)
10/30/2015
Page 10 of
16
Note: the Barcode on the report mock-up is for illustration purposes only
REPORT PARAMETERS
The custom Pick Slip Report will print with the Pick Release document set. Alternatively, you run
may the Pick Slip report from the Standard Report Submission form.
10/30/2015
Page 11 of
16
REPORT VALIDATIONS
The custom Pick Slip Report will be validated against the seeded Pick Slip Report in
Oracle.
MAPPINGS
1. Ship From Address: Link the Seeded Report Warehouse Location ID to: HR_LOCATIONS
2. Part Number: Item Description is already seeded. Link to:
MTL_SYSTEM_ITEMS_B.SEGMENT1 for the Part Number.
10/30/2015
Page 12 of
16
LAUNCH PARAMETERS
This report will launch with the Pick Release process and be part of the Pick Release
Document set. Additionally, the report can be launched form the Standard report
process.
LOG OUTPUT
The log output consists of .
RESTART PROCEDURES
10/30/2015
Page 13 of
16
PREREQUISITES
[List out all of the prerequisites for the custom form or report]
10/30/2015
Page 14 of
16
Issue
Statu
s
Resolution /
Comments
Owner
Target
Resolution
Date
1
2
10/30/2015
Page 15 of
16
APPENDIX
1. APPENDIX A
10/30/2015
Page 16 of
16