<insert client logo>

<Insert project name>

Functional Specifications (Conversion)

<Insert release date>

Functional Specifications (Conversion)

Document Control Information

Document Information
Document Identification <Insert document ID>

Document Name Functional Specifications (Conversion)

Project Name <Insert project name>

Client <Insert client name>

Document Author <Insert author name>
Document Version <Insert version number>
Document Status <Insert document status>
Date Released <Insert release date>

Document Edit History

Version Date Additions/Modifications Prepared/Revised by

<Version <dd-mmm-yyyy> <Provide additional details about this <Name>
#> document version.>

Document Review/Approval History

Date Name Organization/Title Comments

<dd-mmm-yyyy > <Name> <Organization/Title> <Comments>

Distribution of Final Document

The following people are designated recipients of the final version of this document:

Name Organization/Title
<Name> <Organization/Title>

i
Functional Specifications (Conversion)

Contents

1 Conversion Overview ...................................................................................................................... 0

1.1 Objective ............................................................................................................................... 0
1.2 Business Needs ....................................................................................................................... 0
1.3 Major Features ........................................................................................................................ 0
1.4 Module Involved...................................................................................................................... 0
1.5 Systems Involved .................................................................................................................... 0
1.6 Assumptions ........................................................................................................................... 0
1.7 Dependencies and Prerequisites ................................................................................................ 0
1.8 Related Documents ................................................................................................................. 0
1.9 Nomenclature ......................................................................................................................... 0

2 References to Requirements ............................................................................................................ 2

3 Functional Approach/Process Description .......................................................................................... 3

3.1 Source and Target Systems Description ..................................................................................... 3
3.2 Process Flow Diagram .............................................................................................................. 3
3.3 Process Steps Description......................................................................................................... 3
4 Application Setup Requirements....................................................................................................... 4
4.1 Core Application Module Setup .................................................................................................. 4
4.2 System Parameters ................................................................................................................. 4
4.3 Lookup Definitions ................................................................................................................... 4
4.4 Value Sets .............................................................................................................................. 4
4.5 Profile Options ........................................................................................................................ 4
4.6 Cross Reference Lookups ......................................................................................................... 4
4.7 Programs and Parameters ........................................................................................................ 4

5 Detailed Functional Specifications .................................................................................................... 5

5.1 Conversion Template ............................................................................................................... 5
5.2 Data Mappings ........................................................................................................................ 5
5.3 Data Criteria Specifications ....................................................................................................... 5
5.3.1 Data Selection and Filtering Criteria .................................................................................. 5
5.3.2 Pre Extract Clean up Criteria............................................................................................. 5
5.3.3 Post Extract Clean up Criteria ........................................................................................... 5
5.3.4 Pre Conversion Cleanup Criteria ........................................................................................ 5
5.3.5 Post Conversion Acceptance Criteria .................................................................................. 5
5.4 Business Rules ........................................................................................................................ 5
5.5 Validation Rules ...................................................................................................................... 5

6 Other Requirements ....................................................................................................................... 6

6.1 Volume and Performance Requirements ..................................................................................... 6
6.2 Initiation, Frequency, and Scheduling Requirements .................................................................... 6
6.3 Security and Controls Requirements .......................................................................................... 6
6.4 Conversion Validation .............................................................................................................. 6
6.5 Rollback Approach ................................................................................................................... 6

7 Exception and Error Handling .......................................................................................................... 7

7.1 Log Output ............................................................................................................................. 7
7.2 Restart Procedures .................................................................................................................. 7

8 Open/Closed Issues ........................................................................................................................ 8

8.1 Open Issues ........................................................................................................................... 8
8.2 Closed Issues ......................................................................................................................... 8

9 Appendix – Misc. Attachments ......................................................................................................... 9

ii
Functional Specifications (Conversion)

1 Conversion Overview
1.1 Objective
<Describe the purpose of the Functional Specifications Document.>
This functional design document is intended to provide the developer all the key information, assumptions,
rules, and logic that are required to write accurately the <conversion program name> to efficiently convert
the relevant data from <<legacy system>> to the future <<platform>>.

1.2 Business Needs

<Provide overview of the Conversion Data Object from the Business standpoint.>
Data Migration is a process of converting required volumes of data from our clients' <<legacy system>> to
<<platform>>. Files are extracted from legacy system and transferred to <<platform>> using the below
 Data file
 DB links
 Informatica
1.3 Major Features
<List out the major features expected by the business out of the Conversion.>

1.4 Module Involved

<Description of the modules involved/impacted by this conversion should be provided here.>

1.5 Systems Involved

<Description of the systems involved/impacted by this conversion should be provided here.>

1.6 Assumptions
<List out the assumptions made as that impact the conversion design, build and execution.>
1. It is assumed that a legacy system data clean-up will be performed to eliminate or reduce errors in the
destination.
2. Most recent snap shot of the legacy system would be made available for extraction
1.7 Dependencies and Prerequisites
<Specify the prerequisites and dependencies for this conversion.>

1. Required configuration / setup would be available for conversion

2. All related master data would be converted prior to this conversion
3. All data translations would be identified and mapped before Technical design
1.8 Related Documents
<The following documents are related to this document>

Document Name Revision Document Description

1.9 Nomenclature
<Define any company/project-related definitions or acronyms. Use the following if relevant else delete.>

0
Functional Specifications (Conversion)

Acronym Meaning Description

API Application Programming The interface that a computer system, library or
Interface application provides in order to allow requests for
services to be made of it by other computer
programs, and/or to allow data to be exchanged
between them.

1
Functional Specifications (Conversion)

2 References to Requirements
<Give all references that are related to the conversion>

2
Functional Specifications (Conversion)

3 Functional Approach/Process
Description
3.1 Source and Target Systems Description
<Describe the Source System/Application from which and the Target System/Application to which the subject
data is being converted. Ideally this section should describe the System/Application, Database, Tables of
Source and Target involved in the subject conversion.>

3.2 Process Flow Diagram

<Insert a process flow diagram built using MS-Visio tool for the conversion end-to-end process with identified
steps.>

3.3 Process Steps Description

<Describe each steps identified in the conversion process flow diagram.>

3
Functional Specifications (Conversion)

4 Application Setup Requirements

4.1 Core Application Module Setup
<Core application module setups specifically impacting this conversion such as System/Application/Module
Parameters, Profile Options etc. should be listed here. May provide reference to BR100 or Configuration
Document>

4.2 System Parameters

System Parameter Application Value

4.3 Lookup Definitions

Lookup Type

Application

Description
Lookup Code Meaning Description

4.4 Value Sets

Value Set Name

Type & Size

Validation
Value Meaning Description

4.5 Profile Options

Profile Option Name Application Accessibility Level Value

4.6 Cross Reference Lookups

<Any cross reference lookups required for cross reference values between the source and target systems’
referential data should be detailed here>

4.7 Programs and Parameters

<Describe the requirements for programs and parameters for this conversion.>

4
Functional Specifications (Conversion)

5 Detailed Functional Specifications

5.1 Conversion Template
<Template will be designed by functional consultant basing on customer’s business and the requirements for
migrating a specific conversion objects. This template will form the basis for subsequent data mapping at a
field level >

5.2 Data Mappings

<List the details of Source to Target data field mappings, including logic and rules to be applied for the target
system fields.>
<If you do not have data mapping readily available, please at least capture a screen shot of the legacy screen
or an extract from the legacy system where the data is being converted from and also the corresponding
Oracle screen>

DataMapping.xls

5.3 Data Criteria Specifications

5.3.1 Data Selection and Filtering Criteria

<Define the criteria and rules that should be applied for data selection and filtering from the source system.>

5.3.2 Pre Extract Clean up Criteria

<Define the criteria and rules that should be applied for cleansing the data in the Source System before
extracting.>

5.3.3 Post Extract Clean up Criteria

<Define the criteria and rules that should be applied for cleansing the data after extracting from the source
system.>

5.3.4 Pre Conversion Cleanup Criteria

<Define the criteria and rules that should be applied for cleansing the data before converting in the target
system.>

5.3.5 Post Conversion Acceptance Criteria

<Describe the criteria for acceptance of data after conversion into the target system.>

5.4 Business Rules

<Describe the business rules that should be applied as part of the logic for each data field during the
conversion process.
Identify each business rules with a unique business rule ID (e.g. BR01), and the business rule ID should be
referred in the logic for applicable data fields in the data mapping layout.
Business rules should include validation rules, calculations, default values, cross references, derivations etc.>

5.5 Validation Rules

<Describe the validation rules applicable in the conversion.>

5
Functional Specifications (Conversion)

6 Other Requirements
6.1 Volume and Performance Requirements
<Describe the requirements with regards to data volume and performance of the conversion process.>

Description Country 1 Country 2 Country X

LOB1

Estimated # of records /
batch
Average size / record

LOB2

Estimated # of records /
batch
Average size / record

6.2 Initiation, Frequency, and Scheduling Requirements

<Describe the initiation mode, frequency of run of the conversion and scheduling if necessary.>

6.3 Security and Controls Requirements

<Describe the security and controls requirements for the conversion.>

6.4 Conversion Validation

<Describe the parameters for validating converted data. Include any verification tools that may be used. Also
specify if any automation is involved in the validation. If manual validation is to be performed, identify the
process involved in the same. Specify any reports that will be produced as part of the overall validation>

6.5 Rollback Approach

<Describe the rollback plan for removing converted data from a productions system. If the target system is a
staged system, specify how you will run the conversions that already have some live data. Identify the
mitigation plan to ensure data in production system does not get corrupted.>

6
Functional Specifications (Conversion)

7 Exception and Error Handling

<According to business needs mention under which conditions interface status is error/warning/successful.
Also mention the exception handling.>

Error/Exception Error/Exception Description

S.NO. Handler
Code Type

1.
2.
3.

4.

7.1 Log Output

<Attach a sample log output for the conversion program.>

7.2 Restart Procedures

<Describe the restart procedures for the conversion program.>

7
Functional Specifications (Conversion)

8 Open/Closed Issues
<List open and closed issues specific to this object. Broader or escalated issues should be logged in the
project Issues Log.>

8.1 Open Issues

<Describe open issues here>

Issue Id Description Opened By Responsible Due Date

1.

2.

3.

8.2 Closed Issues

<List the closed issues here.>

Issue Id Description Resolution Signoff Closed Date

1.

2.

3.

8
Functional Specifications (Conversion)

9 Appendix – Misc. Attachments

<Include ER dump and comments, table structures, column listing and joins etc.>

9
 About Deloitte
As used in this communication, ‘Deloitte’ means Deloitte Touche Tohmatsu
Limited and its member firms.

Deloitte refers to one or more of Deloitte Touche Tohmatsu Limited, a UK

private company limited by guarantee (“DTTL”), its network of member firms,
and their related entities. DTTL and each of its member firms are legally
separate and independent entities. DTTL (also referred to as “Deloitte Global”)
does not provide services to clients. Please see www.deloitte.com/about for a
more detailed description of DTTL and its member firms.

Deloitte provides audit, consulting, financial advisory, risk management, tax and
related services to public and private clients spanning multiple industries. With a
globally connected network of member firms in more than 150 countries and
territories, Deloitte brings world-class capabilities and high-quality service to
clients, delivering the insights they need to address their most complex business
challenges. Deloitte’s more than 220,000 professionals are committed to making
an impact that matters.

This communication is for internal distribution and use only among personnel of
Deloitte Touche Tohmatsu Limited, its member firms, and their related entities
(collectively, the “Deloitte Network”). None of the Deloitte Network shall be
responsible for any loss whatsoever sustained by any person who relies on this
communication.

© 2018. For information, contact Deloitte Touche Tohmatsu Limited.

10