6.
xxx
SAP Development/Support Standards and Guidelines
_____________________________________________________________________________
2 Conventions for Development and changes to SAP programs
2.1 General Guidelines
For the SAP upgrade or implementation it is the intention to implement a “vanilla” version of the
SAP system, i.e., changes to the supplied software are to be kept to a minimum and approval for
any changes should be justified by developing a business case scenario.
For the development of new programs or modified versions of SAP programs all changes must be
assigned to a development class and hence to a correction for the correction and transport
mechanism. This rule may be ignored for test programs which are never going to be moved
between SAP systems.
2.2 Conventions for changes to SAP programs using SAP User Exits
To change a SAP program or module , you are advised to use sap provided USER EXITS, if a
user exit does not exist, you can request SAP to develop an user exit for you via OSS .
Types of user exits:
.
Menu exit
Screen exit
Function Module exit
Keyword exit
There are two ways to search an application user exit:
Workbench Menu ->Utilities -> Enhancements -> Project Management
Utilities -> SAP Enhancements (SMOD)
Workbench Menu ->Overview -> Appli Hierarchy -> SAP
Note: An add-on project must be created in order to take advantage of the user exits as follows:
Workbench Menu ->Utilities -> Enhancements -> Project Management (CMOD)
2.3 Conventions for changes to SAP programs using SAP Modification
Assistant
Starting release 4.5, SAP provides a facility called ‘Modification Assistant’ to make it easier to
modify the R/3 system. It automatically registers the changes via an automatic assigned transport
number via ABAP editor. The Modification mode can be turned on and off in the ABAP editor.
The SAP objects still need to be registered via OSS.
_____________________________________________________________________________
Page 6 of 19

7.
xxx
SAP Development/Support Standards and Guidelines
_____________________________________________________________________________
Hints:
SE95, the Modification browser provides a system-wide overview for all the changes that you
have made.
Investigate the program using the Modification mode off, and turn it on when you are ready to
make the changes, The SAP keeps a repository for all the changes by the Modification Assistant.
Modifications using this method can be generally be re-imported during a release upgrade without
manual intervention.
If the SAP module or report program requires mass changes, the Modification Assistant may not
be a good approach.
In this case the SAP program is not modified directly but a copy is made renaming the program by
inserting the lead character with “Z”. Any modified include modules or Sapscripts are similarly
copied.
Note: Previous registered SAP objects need to be registered again in 4.6.
2.4 Conventions for changes to SAP programs using Business Add-ins
Starting release 4.6, SAP provides a facility called ‘Business Add-ins’ to allow you to insert your
own code. This does not constitute a modification to the original object. SAP guarantees the
upwards-compatibility of Business Add-ins.
The Business Add-ins Interfaces are based on ABAP objects.
2.5 Conventions for changes to SAP OSS Notes
Sometimes, OSS notes require changes to SAP modules or objects. The object being changed
must be approved by the team leader before a developer begins to perform the changes:
•
•
•
•
•
•
document the business impact of the changes
register the object via OSS
make the changes to the object as instructed by SAP OSS Notes (select dev. Class
XXXX ..accordingly)
compile, and generate the object
ensure all objects associated are generated as well
follow the standard transport procedure
Documenting Code Header:
*************************************************************************
*
Module heading
*
___________
*
* Date
OSS Note no/Transport No
Initial
_____________________________________________________________________________
Page 7 of 19

16.
xxx
SAP Development/Support Standards and Guidelines
_____________________________________________________________________________
5 IMG Configuration documentation
5.1 Transport Requests
IMG notes and configuration must be assigned to separate change requests, as they must be
transported separately. The menu path for configuration is:
5.2 Menu Path
Choose Tools  Accelerated SAP  Customizing  Edit Project
Select GS1 Project if this is not already defined as the default Project.
5.3 Use of IMG to Document Configuration
For details on IMG documentation standards are described in the IMG Documentation document
stored on I: System Optimization ProjectSOP Team DocumentsBS&BCConfiguration
Documents.
_____________________________________________________________________________
Page 16 of 19

17.
xxx
SAP Development/Support Standards and Guidelines
_____________________________________________________________________________
6 Development Key / SAP Object Registration
All development keys and SAP object registrations will be coordinated through Development
Leader. The TMS Administrator is responsible for creating the keys.
_____________________________________________________________________________
Page 17 of 19

18.
xxx
SAP Development/Support Standards and Guidelines
_____________________________________________________________________________
7 Managing Development Changes
This can be used for SRs and regular projects
7.1 Steps to Manage Development Changes
Development Cycle Step
Evaluate tasks(SR) assignments
Who
Develop programs
Project/Team
Leads
Project/Team
Leads
Developers
Ready for testing (Transport to QA)
Developers
QA Testing
XXXX
Approve testing results
Team
leads/Users
XXXX
Work Assignment
Monthly transfer or emergency
transfer to Production
Action
Review an SR and assign user status
'V' when done
Assign Work in SR and change SR
user status to 'APP'
Create Transport request with
proper objects and update SR user
status to 'D'
Update SR user status to Q
Transport the transport request to
QA and update SR user status to 'T'
Update SR user status to 'P'
Update SR user status to 'A_PR'
7.2 Notes
All Change Requests will be transported on a Monthly basic except for emergency transport
In the text of the Change Request, please describe the contents of the change request, prefixed by
the module name XX (see below). This will assist in tracking transport requests later on in the
project.
XX generally used to denote the module, as follows:
FI
Finance
CO
Controlling
PS
Project System
HR
Human resources
PM
Plant Maintenance
MM Material Management
CA
Cross Application
AP
Accounts Payable
AR
Accounts Receivable
EH
Environment & Health Safety
What to include in a change request? A general rule of thumb is to group together all
configuration or development that are logically related to a task. The recommended method is to
create smaller units of work ( a week or less) in a change request  release them after successful
unit testing. With smaller change requests, it will be easier to find specific configuration changes
later in the project.
_____________________________________________________________________________
Page 18 of 19

19.
xxx
SAP Development/Support Standards and Guidelines
_____________________________________________________________________________
8 Other Topics
To be developed as required
_____________________________________________________________________________
Page 19 of 19