07/11/2014

SAP FICO: SAP: Functional Specification for FI , SD, MM, PP

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
http://sap-f2.blogspot.in/2009/07/sap-functional-specification-for-fi-sd.html

1/3

07/11/2014

SAP FICO: SAP: Functional Specification for FI , SD, MM, PP

becomes part of the String and/or Integration Test Plan to validate the
functions actually work.
Recommend this on Google

4 comments:
Narri March 3, 2010 at 2:54 AM
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.
Reply

Narri March 3, 2010 at 3:59 AM

Key deliverables QC
Review Project Charter and verify completeness
http://sap-f2.blogspot.in/2009/07/sap-functional-specification-for-fi-sd.html

2/3

07/11/2014

SAP FICO: SAP: Functional Specification for FI , SD, MM, PP

The Project Charter needs to address the project mission statement, business drivers, and business and project measurements.
Verify that an implementation strategy has been chosen.
Ensure that the project team room has all necessary components.
If needed, review the Project Room Requirements White Paper.
Verify that are needed project team roles have been filled.
Review the project plan components for completeness.
The project plan consists of three different parts: the work plan, the budget plan, and the resource plan.
Review the project team-training plan.
At this point, the project team should be scheduled for both level one and level two training. If possible, it is recommended that level two training begin before
Business Blueprinting. This will help the team visualize their business processes using R/3.
Validate that all project management standards and procedures have been created.
The standards for project communication, documentation, issue and scope management, team building, project planning and monitoring, and quality
assurance need to be reviewed. Make sure that owners have been identified for issue and scope management and that procedures have been put into place
for how issues and changes in scope will be addressed.
Validate that all implementation standards and procedures have been created.
Standards for system configuration, end-user training and documentation, testing, post-implementation support, and system authorizations need to be
reviewed. Also, the system problems and errors handling and system enhancement and modification approval process needs to be reviewed.
Make sure the project kick-off has occurred or is scheduled to occur.
Verify that the system landscape strategy has been determined.
The landscape strategy will include the number of required systems, client deployment strategy, release strategy, and transport system strategy.
Validate that the initial system is installed and remote connection has been ordered.

Tips: Use the Concept check tool for verifying the phase Project preparation.

http://sap-f2.blogspot.in/2009/07/sap-functional-specification-for-fi-sd.html

3/3