Skip to Content
author's profile photo Former Member
Former Member

How to prepare a functional spec.

Dear all,

As per our business requirement we need to develop a custom report, Out ABAP consultant asking me to prepare a spec, for which I am not aware of how to prepare.

Could any of you brief me what is functional spec and how to prepare it.

Your suggestions will be highly appreciated.

Thank you

Raghu Ram

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jan 19, 2008 at 11:39 AM

    follow and prepare as per below contents,

    TABLE OF CONTENTS

    1. Program Information

    2. Functional Specification

    3. Detail description

    3.1 The Functional Solution - Detail Logic

    3.2 Programme Type / Timing

    3.3 Impact of change on the system

    3.4 Assumptions

    3.5 Authorisation

    3.6 Other Issues

    3.7 Error Processing

    3.8 Additional Information

    3.9 Testing

    3.10 User Acceptance Criteria

    4. Technical implementation

    4.1 Inputs:

    4.2 Outputs:

    4.3 Reporting:

    4.4 Validation:

    4.5 Technical Flow

    4.6 Transaction for enhancement

    5. Authorization checks

    5.1 Objects which should be checked

    5.2 Sensitivity of Report

    Above 1 to 3.1 is very important to us.

    Check this forum link:

    functional-spec

    Reward if it helpful.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 19, 2008 at 11:48 AM

    Func Spec basically contains the information about the business process which needs to be mapped on to the IT system (SAP). It encompasses all the related function points which will be part of the business process.

    It also mentions the programs or utilities which can be enhanced/modified/copied to achieve the end result (in case the functional consultant is aware of the program/utility)

    Function Specs is a document which a functional consultant prepares to be given to Abaper. This Document contains details like Tables & fields name, Table joints, Logic for development, along with test case in sand box / test server to verify the development.

    Format for Functional Specs:

    Document Control

    Change History

    Issue No

    Date

    Name

    Change

    Initial Draft

    Authorizations

    Role

    Name

    Signed

    Date

    Business Process Lead (customer)

    Functional Analyst (specification author)

    Technical Lead

    Developer (if known)

    Select program type below and then use menu option tools > unprotect to

    open other fields for input

    Type

    Table of Contents

    Document Control 1

    Overview. 3

    1.1 Short Description. 3

    1.2 Business Process. 3

    1.3 Terminology. 3

    1.4 New Custom Objects Required. 3

    1.5 Impacted SAP Transactions/Tables. 4

    Process Decomposition. 5

    2.1 Process Flow. 5

    2.2 New Tables/Structures Required. 5

    2.3 Sub-Process Description. 5

    2.4 Error Handling. 5

    2.5 Security Considerations. 5

    2.6 Database Considerations. 5

    2.7 Conversion Implications. 5

    2.8 Batch Processing. 6

    2.9 Functional Test Requirements. 6

    Overview

    1.1 Short Description

    1.2 Business Process

    1.3 Terminology

    1.4 New Custom Objects Required

    Include all new tables, key new fields/domains, new lock objects, new

    match-codes, new transaction codes, new authorization objects, new

    function groups, reports and module pools (transaction programs). Don't

    specify all includes, function modules, routines etc. here.

    Type (table, transaction etc.)

    Description

    Naming convention

    1.5 Impacted SAP Transactions/Tables

    List SAP objects updated/impacted by this specification (do not include

    read only impacts)

    Object(s)

    Type (table, transaction etc.)

    Description of Impact

    Process Decomposition

    2.1 Process Flow

    2.2 New Tables/Structures Required

    Specify new tables and structures required. If appropriate, you may

    defer detailed field list/specification to the technical specification

    (e.g. for secondary tables and structures).

    Table id

    Description

    Type

    Master, transaction, customizing, staging

    Expected size

    Maint. dialog

    None, SM30, custom

    Fields

    Key

    Domain/data element names

    Domain format (if new)

    Description

    2.3 Sub-Process Descriptio

    2.4 Error Handling

    Specify what to do if a condition passes AND fails (e.g. - what happens if a customer record is found, or is not found). Specify messages and type.

    Specify any special error logging or table storage, including use of standard application log where appropriate.

    Field

    Validation

    Message type/no.

    Message text

    2.5 Security Considerations

    2.6 Database Considerations

    2.7 Conversion Implications

    2.8 Batch Processing

    2.9 Functional Test Requirements

    Consider all the conditions that need testing for this enhancement and document below. For each logic branch in theory both (or more) conditions of the branch should be tested. For each scenario that could impact program execution, all situations must be tested.

    No.

    Test condition

    Expected result

    Data set-up reqt.

    Dependencies

    Regards.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 20, 2008 at 01:59 PM

    Functional Specification Format

    Authorization Name- Tech Consultant Approval Date

    Approval Name- Functional Consultant -


    1. Solution Information

    a) Company-

    b) Release-

    2.Object Information

    a) Object field

    b) Functional Specification type- Reports/Interface enhancement

    c) Status- Approved/Not Approved

    d) Test Scenariao-

    e) Priority- High/Low/Medium Or 1 2 3

    f) Complexity--

    g) Cleint start Date--

    h) Clent End Date--

    3. Revision History--

    Rev No Rev Date User--Description

    4.Description or Purpose

    a) Description or purpose---Here follows a complete description what Functionality this specification is going to perform

    b) Business proess details-- Here follows the description of business process onvolved

    c) Current Functionality--

    d) Decide Functionality---

    Replay

    Regards

    Sunil Rathod

    Functional SD

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.