Functional Specifications

[Former Member]

Hi All,

I want to know about functional specifications and how they are written as i am new to it. I would want some samples to get a better idea of it.

Could any body help me on this.

-Shikha

[sreeramkumar_madisetty · Accepted solution]

Hi

Generally Each Company and each Project(Client) will have their own Functional Specifications and Technical Specification Templates.(Provided by clients)

In General Functional Consultants will fill up those templates with relevant data and send to their leads and after to the tech team.

Regards,

Sreeram

[Former Member · Accepted solution]

Hi Sreeram,

Can i have one such template so that i will have a better practical idea.

-shikha

[sikindar_a · Accepted solution]

updat ur contact info or check mine

[Former Member · Accepted solution]

Hi sikindar,

i have sent a mail to your contact info. please check n revert.

thanks

[Former Member · Accepted solution]

Hi Sikindar,

Appreciate, if you can send me functional specs template on "maildetail85@gmail.com".

regards,

Amit

[former_member47879]

FUNCTIONAL SPECIFICATION

Reports

Section I: Object General Information

Title (RICEF No): FNS001 Date: 14.03.2008

Short description: Pay Slip Format

SAP Module/Team: HR Release/Region:

Business process owner Tel no:

Email:

Business Contact: Tel no:

Email:

SAP ABAP Developer: Tel no:

Email:

Priority: 0 High 1 Medium 0 Low

Complexity Level 0 High 1 Medium 0 Low

Program Type 0 User-Exit 0 BADI 0 Dialog program 0 Modification 1 Others

Mapping Doc. Name N/A

Change History

Mode Of Execution 0 Scheduled 1 Manual

SL. No Date of Change Description of Change Author Authorized by

Section 2: Detailed Business Purpose & Process:

2.1 Purpose:

PIL & PEL run payroll for all its employees from Head Office located at Mumbai. The payslips are generated after sucessfully running the payroll.

This Report is required. Otherwise:

1 Legal requirements not fulfilled

1 Lack of essential business information

1 Lack of functions compared to legacy system

0 Others: Scheduling Program will not work without this information

2.2 Process: (Explain the detailed To-Be business process. Also mention details of relevant DER docs):

PIL and PEL run centralised payroll at Mumbai (HO) for Non workers on a monthly basis and for workers on a bi-monthly basis. The remuneration statement is printed at the end of each payroll period. These paysilps are then provided to the employees. Paysilps are generated by running remuneration statement report at the end of every payroll period i.e. monthly and bi-monthly.

Section 3: Detailed functional design

Reference Label Position Name

W1 X

Y LOGO-1

W2 X

Y LOGO-2

W3 X

Y Employee detail

W4 X

Y Location Detail

W5 X

Y Employee Category

W6 X

Y Salary Details

W7 X

Y Earnings

W8 X

Y Deductions

W9 X

Y Others

W10 X

Y Take Home Pay

W11

X

Y Payable Month

Field Mapping

Data Dictionary Requirements

< Please provide the data dictionary requirement details, which include table names and field names along with the primary keys. If required attach the excel spreadsheet with details. >

< Responsible person: IBM Interface Analyst in consultation with Functional Analyst. >

Field Field

Description Functionality Table Name Font Font Format Window

1 Name Employee Name PA0002-VERNA+ PA0002-CNAME 10 Helve W3

2 ID Personnel Number PA0001-PERNR 10 Helve W3

3 Pay Period Payroll Period VERSC- FPBEG u2013 FPEND 10 Helve W3

4 Location Employee Location PA0001-WERKS 10 Helve W4

5 Department Employee Department PA0001-BTRTL 10 Helve W4

6 Pay Area Payscale Area PA0008-TRFGB 10 Helve W4

7 Co. Code Company Code PA0001-BUKRS 10 Helve W5

8 Emp. Grp Employee Group PA0001-PERSG 10 Helve W5

9 Emp Subgrp Employee Subgroup PA0001-PERSK 10 Helve W5

10 Account No. Employee Bank Account No. PA0009-BANKN 10 Helve W6

11 Amount Net Amount RT/560-BETRG 10 Helve W6

12 Earnings Gross Earnings for the month SUM 10 Helve W6

13 Deductions Total Deductions for the month SUM

10 Helve W6

14 Adjustments Salary adjustments for the month RT/432-BETRG

10 Helve W6

14 Earnings Earning Components RT/1001,1002,1003,1004,1006-BETRG 10 Helve W7

15 Deductions Deduction Components RT/3FI,3EI,/460,1009,1010-BETRG 10 Helve W8

16 Perks/other income/exemptions/rebates Perks/other income/exemptions/rebates for the month RT/130,/314,/330-BETRG 10 Helve W9

17 Take Home Net Take home salary for the month RT/560-BETRG 10 W10

18 Header Header TEXT+Month/Year 18 W11

19 Oscar Logo Oscar Logo As Provided W1

20 Co. Logo PIL / PEL Logo As Provided W2

The Format is as per the enclosed excel file :-

Section 4: Report Output Detail

4.1 Error /warning/info messages at various processing stages ( also include required validations and corresponding error messages required):

Not Applicable

4.2 Error Handling u2013 Processing options:

Not Applicable

0 All or nothing u2013 if there is an error, roll back any processed data and stop processing

0 Only good data u2013 if there is an error, skip the erroneous record and continue processing

0 Stop processing u2013 run until there is an error, then stop, but donu2019t roll anything back.

0 Other:

4.3 Error Processing:

Specify what action to take upon encountering each kind of error u2013 print a report, save records to a file, recovery requirements, send an email as notification, etc.

Not Applicable

Possible error Processing requirements

1.

2.

3.

4.

4.4 Audit reports / Logs /Completion Requirements:

What activities should be started upon normal completion of an interface or conversion run? (e.g. notification, logging, reconciliation, etc.) Also provide the report layout here if applicable.

Not Applicable

This Report should be an ALV report.

Section 5: Input/Output Data Format (Where applicable)

Input File Name

Input File Format

Sample Input File

Output File Name

Output File Format

Sample output File

NOT APPLICABLE

Section 6: Additional Details

6.1 Risks:

No risks identified.

6.3 Reconciliation procedure: How can we make sure that the data transferred is an accurate reflection of the original data? Specify programmatic and manual processes, and what has to be done at extract time vs. after loading.

Not Applicable

6.4 Dependencies:

Not Applicable

6.5 References:

Not Applicable

6.6 Re-run requirements:

Do you want this interface to re-run and process records that had not failed? Or roll back and start over?

Not Applicable

[sikindar_a]

Ex

if have a issue where the client needs a report which is not there in SAP Standrad reports

than u have to write the report stateing from which IT the date is stored and and from where we can get that data

all these inputs has to be listed in FS and give it to the ABAPER

i

[sreeramkumar_madisetty]

Hi

To speak at macro level that is at projet manager or at senior levels. The Functional Spec (Specification) which is a comprehensive document is created after the (SRS) Software Requirements Document. It provides more details on selected items originally described in the Software Requirements Template. Elsewhre organizations combine these two documents into a single document.

The Functional Specification describes the features of the desired functinality.. It describes the product's features as seen by the stake holders,and contains the technical information and the data needed for the design and developement.

The Functional Specification defines what the functionality will be of a particulat area that is to be precise a transaction in SAP terminology.

The Functional Specification document to create a detailed design document that explains in detail how the software will be designed and developed.

The functional specification translates the Software Requirements template into a technical description which

a) Ensures that the product feature requirements are correctly understood before moving into the next step, that is detchnical developement process.

b) Clearly and unambiguously provides all the information necessary for the technical consultants to develop the objects.

At the consultant level the functional spects are preapred by functinal consultants on any functionality for the purpose of getting the same functinality designed by the technical pepole as most of the times the functionalities according to the requirements of the clients are not available on ready made basis.

Let me throw some light on documentation which is prepared before and in a project:

1) Templates

2) Heat Analysis -

3) Fit Gap or Gap Analysis

4) Business Process Design

5) Business Process Model

6) Business Change & Impact

7) Configuration Design, which is just 5 % of Total SAP- have different names -

😎 Future Impact & Change Assessement

9) Functional Design (Module Wise)

10) Risk Assessement

11) Process Metrics and Many More-- Which has impact on Business and its work flow

Note * This documents are preapared in Vanilla SAP Standards -- Things differ from one implementation to another, and it always depends on the type of business which is opting for SAP.

Regards,

Sreeram

[sikindar_a]

Functional Spec (Specification) which is a comprehensive document is created after the (SRS) Software Requirements Document. It provides more details on selected items originally described in the Software Requirements Template. Elsewhre organizations combine these two documents into a single document.

The Functional Specification describes the features of the desired functinality.. It describes the product's features as seen by the stake holders,and contains the technical information and the data needed for the design and developement.

The Functional Specification defines what the functionality will be of a particulat area that is to be precise a transaction in SAP terminology.

The Functional Specification document to create a detailed design document that explains in detail how the software will be designed and developed.

The functional specification translates the Software Requirements template into a technical description which

a) Ensures that the product feature requirements are correctly understood before moving into the next step, that is detchnical developement process.

b) Clearly and unambiguously provides all the information necessary for the technical consultants to develop the objects.

At the consultant level the functional spects are preapred by functinal consultants on any functionality for the purpose of getting the same functinality designed by the technical pepole as most of the times the functionalities according to the requirements of the clients are not available on ready made basis.

Let me throw some light on documentation which is prepared before and in a project:

1) Templates

2) Heat Analysis -

3) Fit Gap or Gap Analysis

4) Business Process Design

5) Business Process Model

6) Business Change & Impact

7) Configuration Design, which is just 5 % of Total SAP- have different names -

😎 Future Impact & Change Assessement

9) Functional Design (Module Wise)

10) Risk Assessement

11) Process Metrics and Many More-- Which has impact on Business and its work flow

Functional spec is then converted into a Technical Spec and Unit Test Plan. The test plan

becomes part of the String and/or Integration Test Plan to validate the

functions actually work. Hope this helps.