Document1 1 of 8 - 8/30/2014 12:07 PM

Functional Design Specification

3_IM_F_004 Customer Shipping Label Form










Table of Contents

1. Ownership
2. Document Version Control
3. Final Functional Specification Approval
4. Functional Specification
4.1. Identification
4.2. Related Documents
4.3. Terminology
4.4. Business Requirement
4.5. Development Requirements
4.6. Business Process Re-engineering
4.7. Assumptions
4.8. Dependencies/Pre-Requisites
4.9. Legacy System(s)
4.10. Security Requirements
4.11. General Processing Requirements
4.12. Performance Considerations
4.13. Alternatives/Work-Arounds
4.14. Attachments
5. Change Management
5.1. Change Requests
5.2. Change Detail
6. Test Scenarios


Document1 2 of 8 - 8/30/2014 12:07 PM
Functional Design Specification
3_IM_F_004 Customer Shipping Label Form
1. OWNERSHIP
The Business is responsible for the content contained within the Functional Design Specification document. Please specify the
business author below.
Please note, the business author identified within the FD is also responsible for execution of the Functional User Test (FUT) to
ensure that delivered solution meets the business requirements identified within specifications outlined in the FD.
NAME: EXT:
AUTHOR: ISFL Laurie Mussi 6404

2. DOCUMENT VERSION CONTROL
To track changes made to the specification after it has been reviewed and approved.
VERSION
NUMBER
DATE
MODIFIED
MODIFIED BY BRIEF DESCRIPTION OF CHANGE
1.0 11/27/13 Laurie Mussi Document created
1.0 12/06/13 Laurie Mussi Add Approval

3. FINAL FUNCTIONAL SPECIFICATION APPROVAL





















Document1 3 of 8 - 8/30/2014 12:07 PM
Functional Design Specification
3_IM_F_004 Customer Shipping Label Form

4.1. IDENTIFICATION
RICEFW ID Business Requirement IDs SAP Modules (QM, PP, MM, PP, LE, IM)
3_IM_F_004
IM115
IM (Inventory Management)
Object Type (RICEFW) Short Description of Object
Report Interface
Conversion Enhancement
Form Workflow

Legacy/Bolt-on
Customization
Customer Shipping Label Form
PRIORITY
Mandatory (Required by law)
Essential (Business critical-valid business case)
Important
Nice to have

4.2. RELATED DOCUMENTS
Include all documents referenced or documents that the reader may need to refer to while reviewing. Documents referenced here
must be stored in the appropriate Shared Documents Folder on the Carhartt One Project Portal.
DOCUMENT NAME VERSION
BPD-IM54 -EMEA Label 1.0

4.3. TERMINOLOGY
Include all terminology, acronyms, and system names that are ambiguous or may cause confusion for the reader
TERM/ACRONYM/SYSTEMS DEFINITION


4.4. BUSINESS REQUIREMENT
Provide an overview of the business need this project intends to satisfy.
IM115: Customer Shipping Label










Document1 4 of 8 - 8/30/2014 12:07 PM
Functional Design Specification
3_IM_F_004 Customer Shipping Label Form
4.5. DEVELOPMENT REQUIREMENTS
Provide a summary of how the solution is intended to be utilized and/or executed. For instance, if the requirement is a report, is
the report required for specific plants?
Printer, SAP Order#, and Case# should be passed in as parameters


Plant address should be retrieved based on the plant assigned to the sales order



Address should be retieved from the sales order partner function = WE



PO# associated to the sales order


-------------------------------------------- 4 --------------------------------------
---
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-



6

-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-


Document1 5 of 8 - 8/30/2014 12:07 PM
Functional Design Specification
3_IM_F_004 Customer Shipping Label Form

System generated carton ID


XXX = Customer material x-ref associated to the item on the sales order
Barcode is the UPC scanned


Quantity scanned into the carton for the UPC


4.6. BUSINESS PROCESS RE-ENGINEERING
Identify business processes that need to be modified, the business group/department responsible for the process, and how the
process will be modified.
Business Group Process Impact


4.7. ASSUMPTIONS
List all the assumptions taken during the functional design process. These may relate both to business issues and system
design issues.
Printer will be available

4.8. DEPENDENCIES/PRE-REQUISITES (TRANSLATION RULES)
List all dependencies and/or pre-requisites that must be satisfied either in conjunction with or prior to the completion of this
project.
None Identified
4.9. LEGACY SYSTEM(S)
List the Legacy systems from which data will be converted, including a summary of the data that will be converted
None Identified
4.10. SECURITY REQUIREMENTS/CONTROL/AUDIT PROCESSING
List all security, control, and/or audit processing requirements needed in the design. This includes who (users/user goups/etc)
that need access, special permissions, etc...
None identified


Document1 6 of 8 - 8/30/2014 12:07 PM
Functional Design Specification
3_IM_F_004 Customer Shipping Label Form
4.11. GENERAL PROCESSING REQUIREMENTS
General processing requirements for the execution procedure
PROCESSING MODE FREQUENCY EXPECTED DATA VOLUME
Batch (Background)
Online
SAP Direct Update Program
Not Applicable
Other (Specify): RF On-Line
Annually
Quarterly
Monthly
Weekly
Daily
One Time
Other (Specify): On-Demand
Not Applicable
Low One at a time

4.12. PERFORMANCE CONSIDERATIONS
Define performance objectives that, when met, would be considered to have achieved optimal design and overall reliability of the
desired solution. Examples include loading conditions, consequences of failure, as well as reliability expectations.
None Identified
4.13. ALTERNATIVES / WORK-AROUNDS
List any and all alternatives and/or work-arounds identified for this RICEFW requirement.
None Identified
4.14. ATTACHMENTS
The following attachments are required based on the development object type:
REPORT INTERFACE CONVERSION ENHANCEMENT FORM
RLD
OTHER
N/A
<Type Here>
FMD
OTHER
N/A
<Type Here>
FMD
OTHER
N/A
<Type Here>
ENHANCEMENT DOC.
SCREEN SHOTS
OTHER
N/A
<Type Here>
Please include transaction
codes as appropriate
FIELDS
LAYOUT
(Included within this document)
FORMAT
PRE-POPULATED
INPUT/OUTPUT
SAMPLE
OTHER
N/A
<Type Here>







Document1 7 of 8 - 8/30/2014 12:07 PM
Functional Design Specification
3_IM_F_004 Customer Shipping Label Form
5.1. CHANGE REQUESTS
Any change request submitted after the final sign off of the functional and technical specifications will be logged as a change
request and will be subject to approval through the Carhartt One Change Management Program.
DATE
CHANGE
REQUEST #
BRIEF DESCRIPTION OF
CHANGE REQUEST
IMPACT OF NOT CREATING
THE CHANGE
APPROVED
BY CHANGE
MGMT Y/N
ALTERNATIVE


5.2. CHANGE DETAIL
Provide a detailed description of approved changes to be made to the functional and technical specifications. Provide
attachments as needed.
CHANGE
REQUEST #
DETAILED DESCRIPTION OF CHANGES TO FUNCTIONAL AND TECHNICAL SPECIFICATIONS


6.1. TEST SCENARIOS
Please include all the applicable test scenarios in the space below
Test scenarios will be included in 3_IM_E_035: RF Build Customer cases / Generate Shipping Labels

GENERAL INSTRUCTIONS

A unique Functional Design Specification Document (FD) is required for each of the RICEFW objects identified
during the blueprinting process.

The Business (BTL and SME) is accountable for the content contained within the FD, and will be required to sign-off
on the documented specifications before development can begin. ISFLs, SMEs and BTLs will work together to
complete the requirements of the FD.

Each FD will be reviewed by the Development team to ensure accuracy, completeness and understanding of the
functional specifications prior to creating the Technical Design Document (TDD).

Fields highlighted in on the FD are REQUIRED fields. Required fields must be filled in prior to submission (Yellow)
of the form to the Development team for review.

Each requirement will be assigned a unique tracking number known as the RICEFW ID. The RICEFW ID originates
from the RICEFW Log on the Carhartt One Portal, and will be used for reference, testing, bug-tracking, and approval
processes.

In addition, each requirement must also relate back to the original business requirement documented on the
Traceability Matrix. Requirements that fall outside of the original requirements will be subject to approval through
the Change Management Process.

Illustrative attachments and references required for submission by the functional teams in addition to the FD are as
follows:

Reports: Report Layout Document (RLD)

Interfaces: Field Mapping Document (FMD)


Document1 8 of 8 - 8/30/2014 12:07 PM
Functional Design Specification
3_IM_F_004 Customer Shipping Label Form
Conversions: Field Mapping Document (FMD)

Enhancements: Enhancement Document, Screen-shots

Forms: Need to see field requirements, layout, input/output expectations, what should be pre-populated


After final approval has been received on the completed Functional Design Specification Document, all change
requests will be considered for approval through the Change Management Process. If changes to the specification
are approved, they will be logged onto the Change Request Log on the Carhartt One Portal, and the associated
reference number will be documented in the Change Request section of the FD.

Requirements identified by Technical Design (Development) as being customizations will be routed through Change
Management for approval as part of the initial approval process.