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

Functional spec

Hi sap gururs,

In support project, the consultants Create functional specifications for the changes;what is it exactly . Plz do clarify clearly

and they will also carry out functional testing before releasing the changes to customer.

Plz explain clearly

Add a comment
10|10000 characters needed characters exceeded

Related questions

5 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Dec 04, 2007 at 09:06 AM

    Hi,

    In support we work maximium on RICEF after incidents.

    So as a functional consultant we need maintain functional spec. for these ricef for the purpose of techinal consultants as well as for feature reference because these are Z ricefs.In functional spec. we need to documnet purpose,layout and validations etc.

    generally user will do testing in Quality system after through testing from our end. once we get UAT from the user then we release this chages into live environment.

    Hope this will give clarity to you.

    Regards,

    Chandra

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 04, 2007 at 09:07 AM

    Hi,

    Functional specification is to document what is to be done and what are the changes to be incorporated in the configurations.

    Functional Specification contains:

    Document control

    Document Owner

    Summary of changes

    Document change Approvers

    1.Introduction:

    Summary

    Objective

    2.Business study

    Process Overview

    Process flow

    3.Requirement

    Description of the functionality

    4.Approvals

    I hope this input will be useful.

    Regards,

    vimal

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 04, 2007 at 09:31 AM

    Hi,

    Functional spec are prepared by the consultants, if there is any process change.

    The client some times ask for a change in process, so the consultants needs to validate the requirement by preparing a spec.

    As in the earlier mail, the structure of the funstional spec varies from company to company.

    Objective, Current process, Required process, Target users, etc.. will be common.

    Prase

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 04, 2007 at 09:39 AM

    hi,

    Functional specification

    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

    CHAN

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 04, 2007 at 12:41 PM

    dear sabina

    Functional Spec: FS is a document written by the functional guy to communicate to the ABAPer, to say what development needs to be carried out and what are the tables and fields involved. The basic reason for a functional spec would be that of documentation and reference and importantly the technical guys wouldn’t really know the business process but only the tables and fields involved. So the functional guy communicates the business requirement in technical way through a functional spec. Features of a FS would be that it will have a version number which would change depending on the modifications made to that particular object there after. There would be a pseudo logic which outlines what needs to be done for data extraction, tables and fields to be used, validations, testing info .,

    A functional spec is a document which provides the logic to carry out the development. This document contains logic to be followed & the table from which the data is to be picked. It also contains details of which are the connecting table & how the fields are to be mapped

    what are Functional Specification in SAP?

    To speak at macro level that is at project 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. Elsewhere organizations combine these two documents into a single document.

    The Functional Specification describes the features of the desired functionality.. 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 development.

    The Functional Specification defines what the functionality will be of a particular 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, which is technical development process.

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

    At the consultant level the functional sects are prepared by functional consultants on any functionality for the purpose of getting the same functionality designed by the technical people 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 -

    8) Future Impact & Change Assessment

    9) Functional Design (Module Wise)

    10) Risk Assessment

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

    rewards if it helps

    siva

    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.