Professional Documents
Culture Documents
Version Control
Version # Changed by Date Description of change
Contents
1 Background........................................................................................................................................3
1.1 Assumptions..............................................................................................................................3
1.2 Scope..........................................................................................................................................3
1.3 Out of Scope..............................................................................................................................3
1.4 Glossary.....................................................................................................................................3
1.5 Requirement Mapping..............................................................................................................3
2 Current Functionality........................................................................................................................4
3 Proposed New Functionality............................................................................................................5
3.1 [Sub-section 1 – type heading here].......................................................................................5
3.2 [Sub-section 2 – type heading here].......................................................................................5
3.3 [Sub-section 3- type heading here].........................................................................................5
3.4 Mapping changes......................................................................................................................5
3.5 Navigation..................................................................................................................................5
4 Other Considerations.......................................................................................................................5
4.1 QA Test / System Test.............................................................................................................5
4.2 System Data / Sample Data....................................................................................................6
4.3 Installation..................................................................................................................................6
4.4 Concerns....................................................................................................................................6
4.5 Additional Information...............................................................................................................6
5 Appendix............................................................................................................................................6
6 Documentation Notes.......................................................................................................................7
Documentation Notes...........................................................................................................................7
[Topic Title]............................................................................................................................................7
1 Background
Provide a detailed background regarding the new or amended functionality. This should include the
problem/need statement, a high level description and provide a background to the business process in
terms of the product.
1.1 Assumptions
Provide details of any assumptions that have been made during the functional design phases. Typically
these may be where regulations are lacking in clarity or an expectation of the business process which the
user will follow.
1.3 Scope
Provide a summary of the scope of the development work.
1.5 Glossary
Provide a definition/explanation of any term, abbreviation or acronym used within the FDS. [Remove
these instructions]
Glossary
2 Current Functionality
Assuming that the business requirement is associated existing functionality, provide details. Note, if the
requirement is completely new and has no previous process association, this section will not be required.
3.4 Navigation
[Provide transaction codes and/or navigation paths to all relevant components on each applicable
codeline.]
4 Other Considerations
4.1 System Data / Sample Data
Provide details of any system/sample data that needs to be considered.
5 Appendix
Use this area to attach any additional reference information that may be required for completeness.
6 Documentation Notes
Identify any particular issues, considerations or user instructions that must be included within the release
documentation.
Documentation Notes
Notify Peggy Norman, Documentation Manager, if there are any changes to the Notes Summary
content below:
Special Notes
ENTER INFORMATION TO BE INCLUDED FOR USERS. This should be taken from the BRD.
[Topic Title]
Description
Business Impact
[Provide details regarding the business impact and any special actions that the customer needs to take.]
<< THE TABLES BELOW CONTAIN EXAMPLE DOC PLEASE DELETE AS APPROPRIATE>>.
Example [Description of activities the customer will need to take in order to append, modify their
master data.]
[Description of activities the customer will need to take to perform manual configuration steps.]
URLlink.html
Software Version
Software Version Description of Change
SAP Version(s) SAP Version(s) that the documented modification(s) is/are applicable for.