Home > Ask the SAP software/management Experts > Questions & Answers > Making changes to SAP programs
Ask The SAP Expert: Questions & Answers
EMAIL THIS

Making changes to SAP programs

Matthew Billingham EXPERT RESPONSE FROM: Matthew Billingham

Pose a Question
Other SAP Categories
Meet all SAP Experts
Become an Expert for this site
>
QUESTION POSED ON: 16 August 2001

What are the standards for making changes to programs created by SAP? Please include points related to OSS source code corrections.


>

First, SAP will not support customer modified objects. Having said that, often it is necessary to make such changes to make the system behave as required by the business. The only supported changes are those made when applying OSS notes. I'll address the two issues seperately.

1) SAP Authorised Changes (OSS Notes etc.).

The note will document what objects need changings. You should make sure you download all notes you have applied, and store them somewhere safe. Having applied a note, make sure you syntax check and generate all the objects affected by the note. For example, if an include is changed which is part of a function group, then generate the entire function group, to make sure it is OK syntactically.

With programs, I always include a comment header, explaining the reason for the change, the date and the fact that it was me who changed it. Where small areas of code are changed, I use in-line comments thus:

Inserting a line - " I 99999 MB 30/8/2001
Deleting a line - " D 99999 MB 30/8/2001

Where 99999 is the number of the note. Of course, if the note specifies a line should be deleted, you comment it out - don't actually delete it!

For large code changes, i.e. bulk inserts and deletes, use comment blocks to indicate what is happening.

2) Customer specific changes (Not authorised by SAP!)

Think again! Can this be achieved by changing config, business practices, or supplied user-exits?

Follow the same rules as applying OSS notes. However, in your off-line documentation, you must include instructions on how to apply the change - in exactly the same way as OSS notes do.

Make minimal changes to the SAP objects. I usually put my code in a form, which exists in a seperate include, whose name is in the customer name space. That way, the only extra code in the SAP program is PERFORM myclientname_meaningfulformname. (I always put the client name as the first part of the form name for easy recognition.

Test very very thoroughly.

If you follow these standards and documentation, you will find that when you come to upgrade your SAP system, or apply hot packages, the process will be far smoother.


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   



RELATED RESOURCES
2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
Search Bitpipe.com for the latest white papers and business webcasts
Whatis.com, the online computer dictionary



Search and Browse the Expert Answer Center
Search and browse more than 25,000 question and answer pairs from more than 250 TechTarget industry experts.
Browse our Expert Advice



SAP White Paper Topics
About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of technology-specific websites, events and online magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Site Map




All Rights Reserved, Copyright 2000 - 2009, TechTarget | Read our Privacy Policy
SearchSAP.com is a search service provided by TechTarget and is completely
independent of and not affiliated with SAP AG.
  TechTarget - The IT Media ROI Experts