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.

4 comments:

  1. 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.

    ReplyDelete
  2. Key deliverables – QC

    • Review Project Charter and verify completeness
    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”.




    Phase 2 - Business Blueprint
    The purpose of this phase is to create the Business Blueprint, which is a detailed documentation of the results gathered during requirements workshops. Furthermore, the Business Blueprint serves to document the business process requirements of the company. On this basis, you will achieve a common understanding of how the company intends to run their business within the R/3 System.
    Estimated duration: 6-month project; 5-6 weeks

    Activities

    • Project management Business Blueprint phase. The purpose of this work package is to establish a proper cycle of project management activities to ensure that the implementation project is on target. It determines all project planning, controlling and updating activities.

    • Project team training.

    • Develop system environment. The purpose of this workpackage is to install and technically configure the development systems. Within this workpackage you will need to define and test system administration procedures for the development system. You will also need to initialize the enterprise IMG and the project IMG.

    • Define the Enterprise Organizational Structure using SAP organizational units, for example, company codes and sales organizations. When conducting the organization structure workshop, several topics will be discussed, such as:
    • What enterprise areas and business processes will be used in the R/3 system
    • What organizational units within the company will be affected by the implementation

    • Define business processes. The purpose of this workpackage is to define the company requirements based on SAP business processes, in order to provide the required functionality.
    • The goal is to capture the information needed to configure 100% of master files and 80% of business processes.

    ReplyDelete
  3. plz give the clear clarity of functional specification with example wt purpose we use the funcation specification and Z reports give me with example in sap fico reliable screens.I appriciate for ur valubale information and i awaiting for ur response...

    ReplyDelete
  4. Asset accounting depriciation rate change year by year so how we configure and how to excute these scenario ex..one asset first year depreciation rate 10% 2nd year 12% 3rd year 14%..how to do it this scenario in sap plz gv me valuable information for the abv scenario...venkat

    ReplyDelete