Guidelines for Reusable of ABAP Developments

1. Functional Specification to be properly created by the Functional Consultant in Invenio format only across projects.
2. SME to approve FS for the development/report/printout.
3. After testing of the development – make a subsequent document for the development where consultant will explain
how this development/enhancement will work and what are the pre-requisites of that.
4. Technical consultant to make proper document for Technical Specification.
5. Approval of TS to be done by Technical Lead.
6. Person responsible for re-usable COE will have to make sure to take update from all the functional consultants on a
project about the developments can be re-used and make sure that only objects which can be re-used will go in COE.
7. Technical Consultant will have to make sure following points:
a. Avoid hardcoding, wherever possible use Z table or TVARVC (T-code STVARV) variants.
b. Check performance of program.
c. Give suggestions to functional consultant wherever required to make development better.
d. Upload the development in COE Server on timely basis – only reusable (agreed during the project)
e. Technical Lead will have to make sure that all the developments/enhancement/forms/reports which are relevant
for re-usable has been moved to COE Server before completion of project. (It must be a part of their KPI)
 FS Content – Sample 1
Business Background Consultant to provide details of business background for the development which Required
will help others to understand the motive behind this development clearly.

The objective of this document
Why is SAP standard not
appropriate or sufficient?
Alternative Approaches
Considered
Out of Scope
Assumptions
Already covered in BB so this section we can drop off Not Required
Details about what is available in standard and why it can’t be done in standard. Required
Some details to be provided wherever possible to give a view on alternate Required
approaches
NA – As we are creating a FS so it can’t be out of scope NA
For a smooth functioning of development if there is any pre-requisite or Required
something important from user side then we have to maintain it in assumption

Links
Solution Design Yes – Detailed solution with table fields and logic Required
Process Flow Yes – Wherever applicable Required
Data Element Yes Required
How to Test Yes – both positive and negative (if applicable) testing Required
Do’s and Don’t’s
Do Don't

Share complete solutions only. Avoid sharing SAP books downloaded from
Google.
Share contents with complete documentations.
Don’t share Links.
Share standard solutions as well along with ABAP
solutions. Don’t share Client confidential data.

While using any solution from reusable repository, Don’t share incomplete solution.
please provide the details where we are using it.
Please don’t share any obsolete solution or
In case of any update in the object, please share the
process.
new document with the version management.
In case if it’s related to S4 HANA then please make
sure that we align our solution with the latest
release.