Functional Specs

[Former Member]

Hi,

Could anyone mail the SAP SD Functional specs with example to un_non_touch@yahoo.co.in.

Thanks & Regards,

Raja

[Former Member · Accepted solution]

Hi

Refer below

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

<b>"Please do not use email id's to exchange information"</b>

[Former Member]

hi raja

please do a small search in the forum u will get tonnes of information which u have never expected

The Functional Specification is a comprehensive document created after the 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.

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 Description

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

Functional specification: The Functional Specification is a comprehensive document created after the 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.

You will specify the the selection screen, authorizations, and logic needed to fetch the data.

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

It also contains the data regarding change history, if any.

Functional Spec is mainly prepared for the purpose of developing the new reports (this happens only when SAP standard report not achieve the client purpose) using the ABAP Program. for ABAPers you need to give the details of the Tables , Fields and the logic how to pick the value and get the report.

e.g. (this is just an example it can be possible in standard SAP report) I need one new report like in the output i need only company code, Vendor number and recon.account assigned. like as below:

Company Code Vendor Recon account

1000 90000001 156001

1000 90000002 156001

2000 90000001 156002

for the above requirement with the input selection criteria like as below

Company Code ( ) ( )

Vendor ( ) ( )

if you give input selection as above as required you will get the output as given above

Logic should be as below:

for input selection

Company Code - BUKRS is the ABAP field for the company code

Vendor - LIFNR

for the output

Company Code - LFB1-BUKRS

Vendor - LFB1-LIFNR

Recon account - LFB1-HKONT

You will get the recon account details in the LFB1 table , if you give the logic as above , ABAP er will write the program for the same.

Visit the following links:

http://www.sap-img.com/general/what-are-functional-specification-in-sap.htm

http://www.epri.com/eprisoftware/processguide/funcspec.html

Functional specs is like a templeate document, hence it will be same whether it is AR or AP or CCA. Basically functional specs is a document which explains the requirements with technical details, so that technical consultant or any other person can read and understand what is the background of the report or an extension done in SAP.

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 specs should have the following details:

Background: Information why this report is required and Business process involved in that.

Selection Parameters: This should what fields should be selection fields, which are optional and which are mandatory etc.

Layout of the report: What information is required in the output of the report. This should also indicate the technical names - Table and field names from where the data needs to be fetched.

Detailed Description: This should explain the logic of the report - what calculations needs to be done etc.

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

It also contains the data regarding change history, if any.

Functional Spec is mainly prepared for the purpose of developing the new reports (this happens only when SAP standard report not achieve the client purpose) using the ABAP Program. for ABAPers you need to give the details of the Tables , Fields and the logic how to pick the value and get the report.

What Are Functional Specification in SAP?

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

[Manoj_Mahajan78]

Raja,

Read Rules of engagments before posting any query on SDN..

This sending on personal mail id will not meet objective of this forum..

Regds

MM