topic Re: Hi in Application Development and Automation Discussions

Hi

Former Member — Wed, 05 Jul 2006 18:01:58 GMT

Hi,

Iam new to the world of programming and for ABAP too, can any one please explain me the concept of change request in ABAP in detail , the basic purpose of it, what does it actually do in real world of SAP, is there any case we have to create it r change it,r it is created automatically by the system, is it the same as transport request , r any basic difference between them , these questions r killing me , please can any one explain r provide any basic stuff to get clear of this concept, and the next thing DEBUGGING, how we do that, the basic idea for doing debugging, pleae please

help me in both these issues

with regards

cheryl

id: cheryl_toe@yahoo.co.uk

Re: Hi

Former Member — Wed, 05 Jul 2006 18:17:16 GMT

hi Toe,

Check this out for debugging ...

Change Request

ABAP allows you to divide work on large projects among several programmers. Consider an accounting application project with an accounts payable module and an accounts receivable module. The ABAP environment helps you to create a work area in the system for the project. You can then assign tasks to each programmer and follow their work as it progresses.

The tool you use for tracking development projects is called the Transport Organizer. The Organizer tracks changes to existing SAP development objects and the creation of new objects. If you create a new object, the Organizer asks you for a package when you try to Save the object:

The Transport Organizer uses the package to determine whether a change request is required. A change request records the changes made to one or more development objects. The $TMP package contains local objects, which are not transported. Local objects are not transported and so the Organizer does not monitor them.

If you specify a non-local package, the system prompts you to enter a change request. The system also queries you for a change request the first time you attempt to change an existing non-local object. The query dialog appears as follows:

When you associate a change with a request, the system creates a task for you under that change request. The organizer creates a task for each programmer making a change under a change request. You can think of a change request as a container for change tasks.

Once you associate an object with a change request, the system views the objects as under development. The object is locked for changes by casual users. When you have finished creating or changing an object, you release your task. To transport your changes to a production system, you release the change request that held your task.

Change Request as the word itself says that a request to change an existing task ... so consider a case that you have developed a report and the enduser starting using that report ... sometime in the near future he feels that he needs some enhancements to be added to the same so the addition of enhancement becomes a change request ... I Guess now you might have got some idea of what i am trying to emphasize...

Reward if it helps,

Regards,

Santosh

Re: Hi

Former Member — Wed, 05 Jul 2006 18:17:49 GMT

Hi cheryl,

change request is the need to make some changes to the existing code as per the requirements.

Debugger

The Debugger is a programming tool that you can use to execute ABAP programs, by line or by section. With this tool, you can display data objects and check the flow logic of programs.

At the moment, two types of debugging are possible: Debugging with the classic Debugger for release levels prior to 6.40 or debugging with the new Debugger, which is available for all releases after 6.40. The main differences between the classic and the new ABAP Debuggers are described below:

The new ABAP Debugger is executed in its own external mode (Debugger), while the application to be analyzed (debuggee) uses a second external mode. So far, the application to be analyzed and the debugger itself shared the same roll area of an external mode. For this reason, each action of the Debugger could influence the program flow of the application. Therefore, the classic Debugger cannot use any ABAP statements for designing the user interface. The path for designing modern UI techniques is not available for it.

· With the classic Debugger it is generally not possible to analyze programs in debugging mode that run in an ABAP processor unit and are called recursively from a subordinate unit. For example, a conversion exit cannot be analyzed using the Debugger if it runs within a WRITE statement. However, with the new Debugger this is possible.

The new Debugger provides the user with a flexible interface that can be configured as required and has more than eight desktops. Here it is possible to place and arrange up to four tools - depending on the user's selection. For example, it is possible to display source texts or structures. In this way, the user can design the Debugger interface according to his own individual requirements.

As of Release 6.40, you can select the debugging type as you wish by choosing the classic Debugger or the new Debugger in the ABAP Editor from the path Utilities ® Settings. It is also possible to switch the debugger at any time during a session under the menu option Debugging.

There are plans to make the new Debugger the default option as soon as it contains the following functions, which are currently not available:

Watchpoints

Debugging special types (http, BSP, RFC, update task)

Display of memory consumption

Display of system areas

also check this link:

http://www.saplinks.net/index.php?option=com_content&task=view&id=24&Itemid=34

regards,

keerthi.