Scribd
Upload
166 views

FS - SM-C03-Serialized Equipment Master - Functional Specification Conversion 12

This document provides a functional specification for converting legacy serialized equipment data into SAP. It includes an overview of the conversion project, descriptions of the conversion requirements and process, mapping of fields between the legacy and SAP systems, and test conditions. The conversion will create equipment master records in SAP from the legacy system and populate the records with serialized equipment data including equipment attributes, materials, and customer information. The fields to be converted are defined in an attached design document. The conversion is planned to be an automated process to convert a large volume of legacy equipment records into SAP.

Uploaded by

darapu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
166 views

FS - SM-C03-Serialized Equipment Master - Functional Specification Conversion 12

This document provides a functional specification for converting legacy serialized equipment data into SAP. It includes an overview of the conversion project, descriptions of the conversion requirements and process, mapping of fields between the legacy and SAP systems, and test conditions. The conversion will create equipment master records in SAP from the legacy system and populate the records with serialized equipment data including equipment attributes, materials, and customer information. The fields to be converted are defined in an attached design document. The conversion is planned to be an automated process to convert a large volume of legacy equipment records into SAP.

Uploaded by

darapu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 10

FUNCTIONAL SPECIFICATION

PROJECT IDENTIFICATION

Project Name CPI/Project Number Project Type


(CBI, Implementation, CSS, Upgrade, Internal, other)

BEST
Customer Name Customer Number Planned Start/Finish
Black Box
SAP Customer Partner Project Sponsor Program Manager

SAP Project Manager Customer Project Manager Partner Project Manager

How to use the Template


This document is intended to specify RICEFW object from a functional perspective. It will be followed by a technical
specification during Realization. A Functional Specification has three main sections
 General Object information, to be filled in for all RICEFW objects
 Object specific details
 Test conditions and considerations

This document builds and refers to two preceding documents


 Requirements - BPR
 Solution design – BPD

In addition, all RICEFW object are consolidated in the RICEFW list


[Please note: The project manager and the quality manager have to revise this template before it is used for the project
and especially before it is given to the customer. Sometimes instructions, guidelines, explanations, hints, and tips are
provided. It should always be removed from the template for the project.
Top-level chapters may not be deleted or inserted; required additions should be made as sub-chapters to existing
chapters to provide a consistent representation of this document to the customer. ]
TABLE OF CONTENTS
How to use the Template..................................................................................................................1
General Object Overview..................................................................................................................3
Process Requirements Reference.......................................................................................................5
Generic WRICEF Descriptions............................................................................................................5
Object Specific Design......................................................................................................................7
Data Conversion / Historical Data.......................................................................................................7
Test Conditions..................................................................................................................................9
Document History............................................................................................................................10

2
General Object Overview

OBJECT OVERVIEW

117 Business SERVICE MANAGEMENT


Object ID
Process

SAP SERVICE MANAGEMENT


SAP Release
Module
( ) Report
( ) Interface
( X ) Conversion
Object Type ( ) Enhancement
( ) Form
( ) Workflow

Object Title Serialized Equipment Master

Object Description CONVERT LEGACY EQUIPMENTS

Mock Up ID / Name

Required
Cycle of Testing / C1 DDMONYY
Development
Sprint Cycle
Completion Date
Medium MEDIUM
Complexity of Object Priority

SAP Transaction IE01 SAP Program


Name Name

Similar SAP Similar SAP


Transaction Program

FS CONTROL

<Customer>
Functional Consultant
BANNANJE,ARAVIND Process Owner MEDAI,TOM
– Author and Phone
and Phone
Number
Number
Last Name, First Name DDMONYY
FS Approved By FS Approval date

Other Contact and Other Contact and


Phone Number Phone Number

3
Process Requirements Reference
PROCESS REFERENCE
Requirement ID 117
Requirement Serialized Equipment Master
Description
Gap to be CONVERSION
addressed
Alternative SAP
Standard Solution

Generic WRICEF Descriptions


JUSTIFICATION

SAP has been defined the System of Record.

Black Box Inventory that is serialized will be created in SAP as an equipment Record.
The Equipment is associated to a Site and a contract is attached.  The Asset table in
SN is the equivalent to the Equipment Record.
The information that is contained in the legacy Asset table and CMDB Table are
brought into a single SAP object ‘Equipment Master’ Record.

For fields that are needed in the equipment master, please refer to the ‘Equipment
Conversion Design.docx’ in the section ‘Functional Description / Design’

FUNCTIONAL DESCRIPTION / DESIGN

4
The conversion program will read the template (attached) and create an equipment master record in
the system. Equipment will have category Z AND X.

CATEGORY Z = BLACKBOX SERIALIZED PARTS


CATEGORY X = NON BLACKBOX

The word document that is attached lists the fields and in the SAP screen shots. The Black Box
business owners responsible for Equipment Conversion provided the field list.

FS _S M- C0 3 -
S e r ia liz e d

TRANSACTION VOLUME

5
FREQUENCY & TIMING
One Time

DEPENDENCIES
 Material Master against which equipment record is created in the system.
 Material Master against which equipment record is serialized in the system.
 All Sold-To and Ship to are in the system.
 All sales area is configured in the system.

AUTHORIZATION REQUIREMENTS

No authorization requirements are set up in the system for conversion of the equipment.

RELATED DOCUMENTATION (ATTACH OSS NOTES, EMAILS, DOWNLOAD OF EXISTING


REPORT, ETC)

6
Object Specific Design
Data Conversion / Historical Data
<Note all master and transactional data conversion requirements. Please note specific fields that are unique to this
design and the business requirement that drives that design. Note whether manual and automated data conversion
requirements. Provide details of all data required from Legacy Systems (Consider System name, level of detail, time
dimension). Identify requirements for historical data conversion mandatory for the process. This is not meant to be an
exhaustive functional spec but a place to list conversions related to this process.>

CONVERSIONS
WWRI Conversi Source Conversio Conversion # of Owner
CEF-ID on n Method Objects to
Object Activities (manual / be
(e.g. automated) converted
cleansing)
117 EQUIPM Legacy AUTOMATE Tom
ENT D Medai
1MAPPING SAP FIELDS TO SOURCE / TARGET

 SAP Transaction
 SAP Screen number
 SAP Table name
 SAP Field name (functional)
 SAP Field name (technical)
 SAP field length
 SAP field type
 Mandatory / Optional flag
 Source / Target Field ID
 Source / Target Field Name (functional / technical)
 Source / Target Field length
 Source / Target Field type
 Mapping Details
 Implementation Comments

7
RECONCILIATION PROCEDURES & AUDIT REQUIREMENTS

Error Handling

8
Test Conditions
BUSINESS TEST CONDITIONS (TO BE FURNISHED BY THE FUNCTIONAL CONSULTANT)
[Please indicate the business level test conditions that should be used to verify successful operations
of the Report]

[Document all technical scenarios associated with this development. Examples would include 1)
testing an error-free run; 2) testing the exception processes; 3) testing the error handling.]

[Document all control scenarios associated with this development. Examples would include 1)
Rounding of dollars and cents; 2) Audit trail processing; 3) Reconciliation reporting]

Scenario # Input Selection Criteria Expected Result

9
Document History
AUTHORS & PARTICIPANTS
Role Name
Business System Analyst Aravind Bannanje

Project Process Owner

Business Unit Process Owner Tom Medai

Consultant Aravind Bannanje

Workshop Participant Tom Medai

REVISION HISTORY
Date Document Version Document Revision Author
Description
07.03.2017 1.0 Draft for customer << Name >>
review
08.22.2017 Draft for customer
review

REVIEWED AND APPROVED BY


Name Title Date Approved

<<NAME>> Business System Analyst


<<NAME>> Project Process Owner
<<NAME>> Business Unit Process
Owner
<<NAME>> Corporate Process Owner
<<NAME>> Internal Audit

10

You might also like