Functional Specification Sample

This is a functional specification template sample you can use to create your own functional specification for a report program. 1. Business Requirements. In this section you have to describe the development process in a plain English, specify the program purpose and back ground. 2. Functional Specification. 2.1 Functional Design. In this section you should give an overview of the functional design, indicate a short description of the program and any alternative processes if any.) 2.2 Test Scenario. Provide test scenario for the ABAPER so that they can cover all the scenarios that you want to catch in the program. 2.3 Authorization 2.3.1 SAP Authorization Object. You should describe the security requirements in terms of level of information and sensitivity, authorization restrictions, for example perform authorization check based on plant. 2.3.2 ABAP authorization Object. You should describe the security requirements in terms of level of information and sensitivity, authorization restrictions that SAP doesnt provide and can be only carried out in the program, e.g perform authorization check on repeat printing. 2.4. Assumptions In this section you should specify important assumptions. 2.4.1. Custom Formula If you have any custom calculation, then you should put the indicator here, for example you have a total formula calculation by specific customer request. 2.4.2 Expand/Collapse Function If you have any expand/collapse function then you should put them in this section. 2.4.3 Partner Logical System If your program has a requirement to link to partner logical system or fax system then you should describe them here.

2.5 Selection Criteria In this section, you should describe the program logic and also the selection screen parameters for the program. For example, the field name, description, field name type (single parameter, select option), SAP source field, default value. 2.5.1 Form Fields In this section you should map the report layout with the tables columns name, for example you have 5 columns in your report, then you should stated 1fst column = tablename-fieldname, etc. Functional Specification Posted: Nov 30, 2006 4:33 PM in response to: sourav bhaumik check sap sd flow...u will understand everything abt specifications... SD Process Flow: The sales documents you create are individual documents but they can also form part of a chain of inter-related documents. For example, you may record a customers telephone inquiry in the system. The customer next requests a quotation, which you then create by referring to the inquiry. The customer later places an order on the basis of the quotation and you create a sales order with reference to the quotation. You ship the goods and bill the customer. After delivery of the goods, the customer claims credit for some damaged goods and you create a free-of-charge delivery with reference to the sales order. The entire chain of documents the inquiry, the quotation, the sales order, the delivery, the invoice, and the subsequent delivery free of charge creates a document flow Reply or history. The flow of data from one document into another reduces manual activity and makes problem resolution easier. Inquiry and quotation management in the Sales Information System help you to plan and control your sales. Transaction Codes: Inquiry - VA11/VA12/VA13 Quotation - VA21/VA22/VA23 Sales Order - VA01/VA02/VA03 Delivery - VL01N/VL02N/VL03N Billing/Invoicing - VF01/VF02/VF03 Also please check this links. http://www.sapgenie.com/sapfunc/sd.htm http://www.sap-basis-abap.com/sapsd.htm http://www.sapgenie.com/abap/tables_sd.htm SD Workflow: http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMSD/BCBMTWFM SD.pdf http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMLO/BCBMTWFM LO.pdf

Hi SD Gurus,What does a functional specification document contains? How do we work with Functional Specification Document? What is Business Knowledge/ Process review? Please give examples from your real time data from your project.Please answer this question asap.... Looking forward for your express reply...I have interview within 1-2 days. So, give reply to this query asap.. Thanks in advance. Regards Answer #1

functional sepcifications are the details that the functional guys send to the technical team based on which the technical team build tha tables and report on wihch the complete sap priocess is configured The information from the funcationla team to technicalteam is called as funcational specificationand business procces refres to the the businnescycle that runs for the any particular organisation that starts from sales inquiry to that of posting the values in accounting for profitability analyusis
Is This Answer Correct ?

1 Yes 0 No 0 Subha Re: Hi SD Gurus,What does a functional specification document contains? How do we work with Functional Specification Document? What is Business Knowledge/ Process review?Please give examples from your real time data from your project.Please answer this question asap.... Looking forward for your express reply...I have interview within 1-2 days. So, give reply to this query asap.. Thanks in advance. Regards Answer #2

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 that 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 specs 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 SAPhave 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
SAP: Functional Specification for FI , SD, MM, PP
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 stakeholders, 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, that 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 spec 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 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.

Va05 Display sales documents

Business Blueprint in Implementation Projects

Definition
Implementation projects are projects to select and implement business processes in an SAP landscape. A Business Blueprint documents these business process requirements of a company. Collaborative business processes involve several companies.

Use
The Business Blueprint provides a common strategy of how your business processes are to be mapped into one or more SAP systems. The Business Blueprint documents in detail the scope of business scenarios, business processes, process steps, and the requirements of an SAP solution implementation.

Structure
A Business Blueprint comprises the following structure elements in a hierarchy: Organizational Units Master data Business scenarios Business processes Process steps

You assign content, for example, project documentation, Business Configuration Sets or transactions, to individual structure elements, in the SAP Solution Manager. You can create structure elements for organizational units and master data, below a business scenario. You only use these structure elements if the organizational units and master data are only relevant to the business process above them in the structure.

Integration
The Business Blueprint is the prerequisite in the Solution Manager for configuration and test organization: Configuration: You configure your business processes with reference to the Business Blueprint project structure. You can also display and edit the project documentation from the Business Blueprint phase. Test Organization: You base all test plans that you create during test organization, on the Business Blueprint project structure. The transactions which you assign in Business Blueprint process steps, are put in test plans when you generate them. You can run these transactions as transaction function tests. If you use the SAP Quality Center by HP, send the selected Business Blueprint data to the Quality Center. In the Quality Center the system automatically replicates each selected structure node with business test requirements, and creates a folder in the process structure. The quality manager can create test cases, automatically or manually for this structure, from the business test requirements, or assign test cases to the business test requirements.