Writing a Good SAP Functional Specification Document
SAP Functional Consultants | eImplement
Functional-specification documents address business requirements and highlight changes that are to be made in SAP-implementation projects. A good functional-specification document ensures that the technical-design phase of an SAP-implementation project runs smoothly, without delays due to incomplete or inaccurate information. Bad functional-specification documents, on the other hand, often cause significant problems during the later phases of SAP implementation, especially those directly following the drafting of the document. Taking the time to detail the specific aspects of a functional-specification document is one of the best ways to make the document useful and clear to people who utilize it in the later phases of SAP implementation.
When drafting a functional-specification document, it is vitally important that one identifies the areas of the business process that will require the attention of technical designers later. Abnormal processing requirements, for instance, such as potential issues with running the report, should be mentioned in the document along with recovery steps to follow in the event of their occurrence. Also, a functional-specification document needs to be written in a manner suitable for the project it is describing. The vastly different tasks encountered in SAP-implementation projects each merit their own type of functional-specification document. Above all else, functional-specification drafters need to keep the information requirements of those using the documents in mind.
Tags: Functional Consulting, SAP Consulting, SAP Functional Consultants