Functional specification documents

[Former Member]

what is functional specification documents? How can we prepare functional specification documents?

[Former Member · Accepted solution]

hi gopala,

functional spech means which can created by functional people for the particular object and it can moved to technical people to make that report, program or someother object.

following is the one ex for functional spech:

Project Name: Reconciliation Report for customer and vendors related to Pickup

Document ID: ABT_ENPT_FS_0140 Version: 1.0

Revision History

SR.

NO. DATE OF

REVISION SECTION

NUMBER DESCRIPTION OF CHANGE CHANGE MADE BY

Initiating process (pre-requisites):

Make the selection at least one check box on the selection screen

Selection screens/ Screen design:

Processing logic/ Data gathering / Consistency checks:

1. Checks for the pickup completion date: Date validation

2. Checks for check boxes: At least one check should be selected on the selection screen.

3. Select the pickups, which are in process, Ready for billing, Closed and it, should be relevant for PO generation based on the completion date, which is given on the selection screen, if not given select all the pickups.

4. Get the Vendor payment details based on the PO numbers that are selected.

5. Get the Customer Payment details based on the pickup activities, which are done for the customer.

6. Display the Customer and vendor details based on the check box, which is given on the selection screen.

Output Format of the Report:

this is going to be word format with tables and boxes

but text is the functional spec text only...

Payment received from customers but not paid to Vendor

Customer Customer Name Bill No Bill Date Amount

Field Customer Name1 BILL_NO

Table ZPRM_REQ_HEAD LFA1 ZPRM_REQ_BILL

Payments to be received from customer

Customer Customer Name Bill No Bill Date Amount

Field Customer Name1 BILL_NO

Table ZPRM_REQ_HEAD LFA1 ZPRM_REQ_BILL

Paid to Vendor Not Received from customer

Vendor Vendor Name PO Number Invoice Number Invoice date Amount

Field Vendor Name1 PO_NUMBER

Table ZPRM_REQ_PRT KNA1 ZPRM_REQ_PRT

Vendors to be paid

Vendor Vendor Name PO Number Invoice Number Invoice date Amount

Field Vendor Name1 PO_NUMBER

Table ZPRM_REQ_PRT KNA1 ZPRM_REQ_PRT

Note: If invoice id not received from the vendor then column will be empty

Control totals for end of processing:

NA

Design constraints:

It will not work unless a check box is not maintained on the Selection Screen

Authorisation:

NA

Security (Distribution info.)

regards..

seshu

[Former Member]

Dear Gopala Rao,

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.

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.

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

Reward points if this is helpful.

Regards,

Naveen.

[Former Member]

Hi Gopal,

Suggest you perform a search in the forum, there are several threads which have dealt with the same topic and several useful links have also been given

Thanks

Janani

[Former Member]

Functional specs is an document prepared by functional Consultant to be provided to Abaper. This document contains details of tables & fields, table joints & logic which is required for development.

Functional Specs format avaries from company to company based on the documentation pattern.

<u>Overview on gross level is as under:</u>

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

Regards,

Rajesh Banka

Reawrd points if helpful.

[Former Member]

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

REWARD if helpfull

Thanks & Regards

Narayana

[Former Member]

when we want some program to write or changes in programs, we write functional spec to ABAPer. this is in word format and we give why we require that change and wat is out we want and required table..

Reward if it helps..

Ramki

[Former Member]

HI Gopala Rao,

Sent mail.

Reward if it helps

regards

Srini

[Former Member]

Hi srini,

I was not recived u r mail for this question.

Gopal

raoyaradesi@rediffmail.com

gopal_tele@hotmail.com

[Former Member]

Hi gopal .,

Sent mail check

REWARD i helpfull

Thanks & Regards

Narayana

[Former Member]

Hello gopal,

Will you please forward the material regarding BW functional specification to my mail id .

will reward points

Thanks in Advance

Regards,

Seema