Cannot edit the Abap program

Hello everybody
Im new in SAP, I run the minisap when user bcuser and ddic but tell me no have permision for create, I need other user please tell add new user for work in edit abap

Hi ,
when u try to chANGE THE sap standard ddic or program it will give u this popup.
Please try to create the program or ddic start with Z or Y then i think u will not have problem.
Hope it helps u,
<b>Reward pts if found usefull :)</b>
Regards
Sathish

Similar Messages

Termination occurred in the ABAP program "RK2APA00_POST" - in

Hi everybody...I have a cancelled job when run only in applications servers , I see a dump "message typeX" , but when job run in Central Instance not cancelled and finish ok.
The name Job is Zcupon and attach to continue dump info , sorry for extended but I want send all information possible.
know if you can add a file with the abstract and not have to paste the text of the dump, thanks for the help they can deliver.
Regards....Freddy Solar....
Errores tiempo ejec.   MESSAGE_TYPE_X
Fecha y hora           18.11.2008 06:35:30
Texto breve
The current application triggered a termination with a short dump.
¿Qué ha sucedido?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
Anál.errores
Short text of error message:
RFC_ERROR 4 Conversation 93690218 not found / CPIC-CALL: 'ThSA
Technical information about the message:
Message classe...... "KE"
Number.............. 628
Variable 1.......... "RFC_ERROR"
Variable 2.......... 4
Variable 3.......... "Conversation 93690218 not found / CPIC-CALL: 'ThSA"
Variable 4.......... " "
Last error logged in SAP kernel
Component............ "SAP-Gateway"
Place................ "SAP-Gateway on host SCPAPP1 / sapgw03"
Version.............. 2
Error code........... 728
Error text........... "Conversation 93690218 not found"
Description.......... " "
System call.......... " "
Module............... "gwxxrd.c"
Line................. 6156
The error reported by the operating system is:
Error number..... " "
Error text....... " "
Notas para corregir errores
Probably the only way to eliminate the error is to correct the program.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
please use the following search criteria:
"RK2APA00_POST" "MESSAGE_TYPE_X"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
Entorno sistema
SAP-Release 700
Application server... "SCPAPP1"
Network address...... "10.1.40.130"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x AMD64 Level"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 3
Shortdump setting.... "full"
Database server... "BALTICO"
Database type..... "DB400"
Database name..... "SCP"
Database user ID.. "R3SCPDATA"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Jun 30 2008 00:10:07"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "DB4_53"
Patch level. 167
Patch text.. " "
Database............. "V5R3, V5R4, V6R1"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 16192
EM...... 159213920
Heap.... 0
Page.... 5660672
MM Used. 145143664
MM Free. 5680112
Usuario y transacción
Client.............. 400
User................ "ZUSRTARJETAS"
Language key........ "S"
Transaction......... " "
Program............. "RK2APA00_POST"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Info posición de cancelación
Termination occurred in the ABAP program "RK2APA00_POST" - in
"INSERT_CE4_FLUSH_BUFFERS".
The main program was "ZVI_CUPON ".
In the source code you have the termination point in line 100
of the (Include) program "RKEVRK2A_POST_COMMIT__FIX".
The program "RK2APA00_POST" was started as a background job.
Job Name....... "ZCUPON"
Job Initiator.. "ZUSRTARJETAS"
Job Number..... 02044200
Detalle código fuente
Lín.
Txt.fte.
70
subrc = sy-subrc.
71
CLEAR: g_t_ce4a_dbbuf[], g_t_ce4_dbbuf[].
72
73
case subrc.
74
when 1.
75
    Records were to be inserted into the acct.ref. table CE4xxxx_ACCT
76
    but the acct. reference numbers were already occupied. Most likely
77
    This problem is due to a explicit or implicit change to the
78
    number range COPA_OBJ (subobject is the operating concern)
79
    e.g. caused by illegally transporting the contents of CO-PA
80
    transaction data table contents (CE4xxxx / CE4xxxx_ACCT).
81
    Please check OSS for notes with keywords RKEVRK2A_POST, KF216
82
    and CE4XXXX_ACCT. If you do not find any applicable notes please
83
    log an OSS message.
84
MESSAGE x216(kf) WITH gc_ce4acct_name.
85
86
when 2.
87
    Records were to be inserted into the segment table CE4xxxx
88
    but the segment numbers were already occupied. Most likely
89
    This problem is due to a explicit or implicit change to the
90
    number range COPA_OBJ (subobject is the operating concern)
91
    e.g. caused by illegally transporting the contents of CO-PA
92
    transaction data table contents (CE4xxxx).
93
    Please check OSS for notes with keywords RKEVRK2A_POST, KF203
94
    and CE4XXXX. If you do not find any applicable notes please
95
    log an OSS message.
96
MESSAGE x203(kf).
97
98
when 3 or 4.
99
    Communication error in RFC-Call
>>>>>
message x628(ke) with 'RFC_ERROR' subrc msg_text.
101
102
endcase.
103
104
ENDFORM.
105
Edited by: freddy solar on Jan 2, 2009 8:39 PM

Hi,
it looks like you have some problem with RFC. It stopped on the following line:
* Communication error in RFC-Call
message x628(ke) with 'RFC_ERROR' subrc msg_text.
Ask your basis guy to check it. The job on application server tried to connect to the central instance and it failed. The job run on central instance does not need to make any RFC call. Hence there is no problem in this case.
Regards

How to debug the abap program ?

how to debug the abap program ?Can anybody explain me in details.

Hi
Debugger
This section of the ABAP Workbench documentation provides information on how to use the Debugger as a test tool for finding errors in the source code of an ABAP program.
Functional Overview
Use
The ABAP Debugger is an integrated test tool within the ABAP Workbench. You use it to check the program logic and to find errors in the source code of an ABAP program. In the Debugger, you can step through the source code of a program. The running program is interrupted after each step, allowing you to check its processing logic and the results of individual statements.
As of Release 6.10, you can also run Business Server Pages (BSP) in the debugging mode. You can also display and set breakpoints here. Business Server Pages can be displayed in the Object Navigator when you select an appropriate application under BSP Application.
Features
The Debugger provides an efficient means of identifying errors in ABAP programs. It contains the following functions:
Ways of starting the Debugger
Choosing different views
Choosing different execution options in the Debugger
Displaying source code in the Debugger
Setting and deleting breakpoints
Setting and deleting watchpoints
Stopping a program at a particular statement or event
Displaying and changing field contents at runtime
Displaying ABAP Objects and references
Displaying and positioning strings
Setting and deleting database locks
Opening the ABAP Editor, or Object Navigator
System settings and runtime warnings
Starting the Debugger
There are two possible strategies for starting the Debugger in the ABAP Workbench:
By setting breakpoints then running the program
By running the program in debugging mode.
Setting Breakpoints
A breakpoint is a signal in a specific line of the program source code. This signal indicates to the ABAP runtime processor to stop the program at the relevant line and start the ABAP Debugger. A distinction is made between static and dynamic breakpoints. For further information about the different types of breakpoints and how to use them, refer to Breakpoints.
Direct Processing
You can start the Debugger without previously having set breakpoints. This is the best procedure to use when you want to test a program right from the beginning. It is also a useful procedure if you are not overly familiar with the program and therefore are not sure where best to set breakpoints. You can start the Debugger as follows:
From the Object Navigator
Select a report or transaction and choose Program ® Test ® Debugging.
From the ABAP Editor
Choose Program ® Execute ® Debugging (or the Debugging pushbutton).
From any screen
Choose System ® Utilities ® Debug ABAP.
From any screen
Enter /h in the command field.
Display Modes in the Debugger
When you are debugging a program, there are various display modes that you can use. All of the display modes have the same structure. The top part of the screen displays an extract of the program source code. The bottom part displays the information specifically available in that display mode. There are also pushbuttons on the screen allowing you to switch to the most frequently-used display modes.
Display Modes Available Using Pushbuttons
Fields
The scrollable field display contains the contents of up to eight fields. The contents of the three most important system fields are always displayed. This is the default display mode in the Debugger. See also Processing Fields
Table
Displays the contents of an internal table. This mode allows you to display and edit the entries in an internal table. See also Processing Internal Tables
Breakpoints
A scrollable display containing up to 30 breakpoints. Next to each breakpoint is a counter. You can also delete breakpoints in this display. See also Managing Dynamic Breakpoints
Watchpoints
You can set a watchpoint for a field so that the program is interrupted whenever the value of that field changes. This display mode contains a list of watchpoints, the fields and programs to which they are assigned, the current values of the fields, and the conditions upon which the watchpoint is activated. See also Setting Watchpoints
Calls
This mode displays the current sequence of events, and the sequence of calls up to the current breakpoint. The last active call is displayed at the top of the list; previous calls are listed in reverse chronological order. When an event (for example, START-OF-SELECTION) concludes, it is deleted from the display.
Overview
This mode displays the structure of the program. It lists its events, subroutines, and modules, and shows which sections belong to which events. It also displays the section currently being processed.
Settings
This mode displays the current Debugger settings. You can change the settings by selecting or deselecting various options. For further information, refer to Settings and Warnings
Other Display Modes
You can access other display modes by choosing Goto ® Display data object.
Single field
Displays the contents and technical attributes of a field.
Structured
field
Displays the components of a structure, along with their contents and attributes. If you double-click a component, the system displays detailed information for it.
Strings
Display the content and current length of the string. You can also display part of the content by means of offset and length.
Internal table
Displays the type, line numbers and contents of an internal table.
Object
Displays the structure of an ABAP Object.
For further information on these displays, refer to Displaying Attributes and Displaying ABAP Objects
Checking System Programs for Errors
To check a program or program component that is part of the ABAP Workbench (for example, the Screen Painter), you must use the system Debugger. To start the system Debugger, choose System ® Utilities ® Debug System from any screen. To stop the system Debugger, choose Debugger ® Debugging off.
Displaying Program Attributes
You can display the attributes Fixed Point Arithmetic, System Program, and Unicode Checks of the program that has just been executed by choosing Goto ® Further Information ® Program Attributes.
Restarting the Debugger
If you choose Debugging ® Restart, debugging mode is stopped and the system takes you to the initial screen of the last transaction you called. If, for example, you started an ABAP program in debugging mode from transaction SE38 (ABAP Editor), choosing Debugging ® Restart will take you back to the screen titled ABAP Editor: Initial Screen. If you want to restart the program in debugging mode, choose Debugging.
Breakpoints
Apart from direct execution of an ABAP program in the Debugger, it is also possible to start the Debugger call by the exact setting of a breakpoint. This is achieved by setting one or more of these breakpoints in the program. A breakpoint is a signal at a particular point in the program that tells the ABAP runtime processor to interrupt processing and start the Debugger. The program runs normally until the breakpoint is reached.
There is also a special kind of breakpoint called a watchpoint. When you use watchpoints, the Debugger is not activated until the contents of a particular field change. For further information, refer to Watchpoints.
Breakpoint Variants
The Debugger contains different breakpoint variants:
Static
The BREAK-POINT statement in an ABAP program. Static breakpoints are not normally user-specific. However, you can make them user-specific.
Directly-set
dynamic breakpoints
Can be set in the ABAP Editor or the Debugger. Dynamic breakpoints are always user-specific, and are deleted when you log off from the R/3 System.
Breakpoints
at statement
The Debugger stops the program directly before the specified statement is executed.
Breakpoints
at subroutine
The Debugger stops the program directly before the specified subroutine is called.
Breakpoint at function module
The Debugger stops the program directly before the specified function module is called.
Breakpoint at method
The Debugger stops the program directly before the specified method is called.
Breakpoints at system exceptions
The Debugger stops the program directly after a system exception, that is, after a runtime error has been intercepted.
Static Breakpoints
Static breakpoints are not normally user-specific. Once a user has inserted the statement BREAK-POINT or BREAK name in an ABAP program, the system always interrupts the program at that point for that user or only for the user name. This procedure is only useful in the development phase of an application, when the program execution is always to be interrupted at the same place. For further information, refer to Static Breakpoints.
In HTTP sessions, a static breakpoint is skipped if you did not set additional dynamic HTTP breakpoints in the editor of a BSP page. Instead, a corresponding system log entry is written, which can be checked using transaction SM21.
Dynamic Breakpoints
Dynamic breakpoints are user-specific. Therefore, you should use them if you only want the program to be interrupted when you run it yourself, not when it is being executed by other users. All dynamic breakpoints are deleted when you log off from the R/3 System.
Dynamic breakpoints are more flexible than static breakpoints, because you can deactivate or delete them at runtime. They have the following advantages:
You do not have to change the program code
You can set them even when the program is locked by another programmer
You can define a counter that only activates the breakpoint after it has been reached
Special dynamic breakpoints are useful when you want to interrupt a program directly before a particular ABAP statement, a subroutine, or an event, but do not know exactly where to find it in the source code. Event here is used to refer to the occurrence of a particular statement, for example, or calling up a method. Special dynamic breakpoints are user-specific. You can only set them in the Debugger. For further information, refer to Dynamic Breakpoints.
In HTTP sessions, the system stops both at static and dynamic breakpoints if a dynamic breakpoint was set in the editor of a BSP page before program execution.
Lifetime and Transfer of Breakpoints
A static breakpoint remains intact as long as the BREAK-POINT or BREAK-POINT name statement is not removed from the source code. Without saving, dynamic breakpoints only remain intact in the relevant internal session. However, they are effective during the entire user session, if they are saved by choosing Breakpoints ® Save in the ABAP Debugger. For more details on the subject of sessions and user sessions, refer to Modularization Techniques in the ABAP keyword documentation.
If you call an HTTP session during a user session, only the HTTP breakpoints are loaded when the HTTP session is started. You activate HTTP debugging in the ABAP Editor by choosing Utilities ® Settings ® HTTP Debugging. Depending on the setting, the system then displays either the HTTP or standard breakpoints in the Editor.
If you call an update session during a user session, breakpoints that were defined beforehand in the calling processing unit are copied to the new update session, where they can be displayed under Breakpoints. If, in the ABAP Debugger, you check Update Debugging under Settings and then, for example, call the update module func using CALL FUNCTION func IN UPDATE TASK, a new window is opened in which you can debug this function module in the update session. All the breakpoints that were set in the calling processing unit can also be processed here.
Breakpoints at Statements
You can use this special kind of dynamic breakpoint to interrupt a program directly before an ABAP statement is processed.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint at an ABAP statement:
1.Choose Breakpoint ® Breakpoint at ® Statement...
The following dialog box appears:
2.Enter the ABAP statement.
The system sets a breakpoint at all points in the program at which the ABAP statement occurs.
3.Choose ENTER.
The breakpoint applies to all lines containing the specified statement.
Result
The system confirms the breakpoint and adds it to the list in the display. When you finish your debugging session, the breakpoint is automatically deleted unless you have explicitly saved it.
Breakpoints at Subroutines
You can use this special kind of dynamic breakpoint to interrupt a program directly before a subroutine is called.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint for a subroutine:
Choose Breakpoint ® Breakpoint at ® Event/Subroutine.
The following dialog box then appears:
Enter the name of the subroutine before which you want to interrupt the program. By default, the Program field contains the name of the program that is currently active. The system sets a breakpoint wherever the specified subroutine occurs in the program code.
Choose ENTER.
Result
The system confirms the breakpoint. The breakpoint is added to the breakpoints displayed.
Breakpoints at Function Module
You can use this kind of dynamic breakpoint to interrupt a program directly before a function module is called.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint for a function module:
Choose Breakpoint ® Breakpoint at ® Function module...
The following dialog box appears:
Enter the name of the function module before which you want to interrupt the program. The system sets a breakpoint wherever the specified event, module pool, or subroutine occurs in the program code.
Choose ENTER.
Result
If you entered a valid function module name, the system confirms that the breakpoint has been set. If the function module exists in the system, the new breakpoint is added to the display list.
Breakpoints at Methods
You can use this special kind of dynamic breakpoint to interrupt a program directly before a method is called.
Prerequisites
You must be already running the program in the debugger.
Procedure
To set a breakpoint for methods:
1. Choose Breakpoint ® Breakpoint at ® Method...
The following dialog box then appears:
2. Enter the name of the method and class before which you want to interrupt the program. A breakpoint is then set each time the specified processing block appears in the source code.
3. Choose ENTER.
Result
The system confirms the breakpoint. The breakpoint is added to the list in the display.
Breakpoints at System Exceptions
You can use this special form of dynamic breakpoint to interrupt a program immediately after a runtime error has occurred.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint at a system exception:
Choose Breakpoint ® Breakpoint at ® System exception.
Result
The system confirms the breakpoint. The breakpoint is added to the breakpoints displayed.
When a system exception is triggered, a warning triangle appears in the line containing the statement that caused it. If you double-click the warning triangle, the internal name of the runtime error appears.
Static Breakpoints
You should only use static breakpoints during the development phase of an application. You must remove them from your program before you transport it.
Setting Breakpoints
To set a static breakpoint, use the ABAP statement BREAK-POINT . Place the breakpoint in the line at which you want to interrupt the program.
program RSDEBUG_01.
if SY-SUBRC 0.
break-point.
endif.
When you run the program, the runtime processor interrupts it when the breakpoints occur. You can number your breakpoints to make them easier to identify ( BREAK-POINT 1, BREAK-POINT 2 ).
Static breakpoints are not normally user-specific. The program is, therefore, always interrupted as soon as the runtime processor reaches the line containing the breakpoint. The program is interrupted regardless of the user who executes it.
However, you can set user-specific static breakpoints using the BREAK statement followed by your user name. For example, if you use the statement BREAK SMITH , the program is only interrupted when user Smith runs it. Although user-specific breakpoints appear in the program code, they are not active when other users run the program. You should, however, be careful if an application is being used by several users with the same name.
Deleting Breakpoints
Since static breakpoints apply to all users, you must remove them from the program once you have finished testing it. In the ABAP Editor, you can find breakpoints quickly by choosing Utilities ® Global search. You can also use the Extended Program Check to find them.
If you do not remove static breakpoints from your program, they will be transported to your production system. This could cause serious problems in the production system.
Dynamic Breakpoints
You can set up to 30 dynamic breakpoints without changing the program code. Dynamic breakpoints can be set either in the ABAP Editor or directly in the Debugger.
Setting Dynamic Breakpoints in the ABAP Editor
You can set dynamic breakpoints in the ABAP Editor regardless of whether you are in display or change mode. You can also set breakpoints directly from within the Debugger at runtime. To set a dynamic breakpoint in the ABAP Editor:
Position the cursor on the line of the source code at which you want to set the breakpoint.
Choose Utilities ® Breakpoints ® Set or the Stop icon. The system confirms that the breakpoint has been set.
To display a list of all dynamic breakpoints in a program, choose Utilities ® Breakpoints ® Display. You can use this list to navigate to a particular breakpoint or to delete one or more breakpoints from the program.
Setting Dynamic Breakpoints in Debugging Mode
To set a dynamic breakpoint in the Debugger:
Position the cursor on the line in which you want to set the breakpoint.
Select the line by double-clicking it or choosing Breakpoint ® Set/delete.
The system sets the breakpoint, and displays a small stop sign to the left of the relevant line. If the line already contained a breakpoint, it is deleted.
When you finish your debugging session, the breakpoint is automatically deleted unless you have explicitly saved it.
Saving Breakpoints
If you want to leave the Debugger temporarily, you can save your dynamic breakpoints so that they are still active when you return to the Debugger within the same terminal session.
To save the breakpoints that you have set in the Debugger:
Choose Breakpoint ® Save.
The system saves all of the breakpoints that you have set in the current program. These breakpoints will remain active until you either explicitly delete them or log off from the system.
You can also delete breakpoints that you have saved:
By deleting individual breakpoints from the display and then saving again. In this case, only your selected breakpoints will be deleted.
By choosing Breakpoint ® Delete all. In this case, the system deletes all dynamic breakpoints.
Managing Dynamic Breakpoints
The ABAP Debugger provides a convenient user interface for managing breakpoints. To open the breakpoint display, choose Breakpoints, or, from the menu, Goto ® Control debugging ® Breakpoints.
Example
Functions
This display mode contains the following functions for breakpoints:
Breakpoint Display
The scrollable breakpoint display contains up to 30 dynamic breakpoints. For breakpoints that you set directly, the program name and line number at which the breakpoint occurs are displayed. For special breakpoint forms, the list displays the statements, events, subroutines, and module calls at which the relevant breakpoints are set.
Counter
In the breakpoint display, you can specify a counter. When you use a counter, the breakpoint is not activated until it has been reached a specified number of times. For example, if you enter 5 for the counter, the breakpoint is not activated until it is reached for the fifth time. After the breakpoint has been activated, it remains so, and the counter no longer appears in the breakpoint display.
Deleting Breakpoints
Position the cursor on the breakpoint that you want to delete, and either double-click the line or choose Breakpoint ® Set/delete. To delete all breakpoints, choose Breakpoint ® Delete all.
Activating and Deactivating Breakpoints
Position the cursor on the breakpoint that you want to activate or deactivate and choose Breakpoint ® Activate/deactivate.
Watchpoints
Like a breakpoint, a watchpoint is an indicator in a program that tells the ABAP runtime processor to interrupt the program at a particular point. Unlike breakpoints, however, watchpoints are not activated until the contents of a specified field change. Watchpoints, like dynamic breakpoints, are user-specific, and so do not affect other users running the same program. You can only define watchpoints in the Debugger.
Use
You set watchpoints in the Debugger to monitor the contents of specific fields. They inform you when the value of a field changes. When the value changes, the Debugger interrupts the program.
Features
You can set up to five watchpoints in a program.
See also Setting Watchpoints.
You can also specify the conditions on which a watchpoint is to become active.
You can specify logical conditions between up to five conditional watchpoints.
See Specifying a Logical Expression.
You can define watchpoints as either local or global. If you define a global watchpoint, it is active in all called programs. Local watchpoints are only active in the specified program.
You can change and delete watchpoints.
See Changing Watchpoints.
You can use watchpoints to display changes to the references of strings, data and object references, and internal tables.
See Memory Monitoring with Watchpoints
Setting Watchpoints
If you want to interrupt a program when the contents of a field or structure change, use a watchpoint. You can set up to five watchpoints, including watchpoints for strings.
A watchpoint can be either local or global. Local watchpoints are only valid in the specified program. Global watchpoints are valid in the specified program, and also in all the other programs it calls.
Procedure
To set a watchpoint, start the Debugger and proceed as follows:
Choose Breakpoint ® Create watchpoint or the corresponding pushbutton. The Create Watchpoint dialog box appears:
Decide whether you want to set a local or global watchpoint.
Enter the program and the name of the field for which you want to set the watchpoint. In the Program field, the name of the program currently running is always defaulted.
If you want your watchpoint to be activated each time the contents of the field change, the definition is now complete, and you can return to the Debugger by pressing ENTER .
To create a conditional watchpoint, that is only activated when a particular situation arises, choose one of the following relational operators.
Operator
Meaning
<
Less than
<=
Less than or equal
=
Equal
<>
Not equal
=
Greater than or equal
Greater than
You can use the Comparison field option to specify whether the comparison is to be carried out with a value that you specify or with the contents of another field. Depending on your choice from step 6, enter a value or a field for the comparison.
Result
The system confirms the watchpoint and adds it to the list in the display. When you finish your debugging session, the watchpoint is automatically deleted unless you have explicitly saved it.
Specifying Logical Links
If you have more than one conditional watchpoint, you can specify a logical link between them:
OR
Only one of the specified conditions must be met
AND
All of the conditions must be met.
Changing Watchpoints
Choose Goto ® Control debugging ® Watchpoints or the Watchpoints pushbutton to display the watchpoint list. The following dialog box appears:
Choose the pencil icon in the line containing the watchpoint you want to change.
Change the watchpoint attributes in the Create/Change Watchpoint.
Choose ENTER .
Deleting Watchpoints
You cannot delete watchpoints by choosing Breakpoint ® Delete or Breakpoint ® Deactivate/activate. Instead, proceed as follows:
Choose Goto ® Control debugging ® Watchpoints or the Watchpoints pushbutton to display the watchpoint list.
Choose the trashcan icon in the line containing the watchpoint you want to delete.
Memory Monitoring with Watchpoints
You can use watchpoints to display changes to the references of strings, data and object references, and internal tables. By placing an ampersand (&) in front of the object name, you can display the reference in question in hexadecimal format. With internal tables, you can also display the table header by placing an asterisk (*) at the beginning of the name.
&objectname
Displays the references of strings, internal tables as well as data and object references
*itab
Displays the table header of the internal table itab
Example
If a watchpoint is set for the object in question at runtime, the program is stopped as soon as the reference is changed. A short dump can be intercepted in this way to stop the program being terminated when the memory is overwritten.
Analyzing Source Code
The Debugger contains an extensive range of functions that help you to analyze the source code of a program. You can step through the source code of a program in four different ways. For further information, refer to Stepping Through the Source Code
For information about functions within the source code display, see Displaying the Source Code
There are also different display modes that provide various information and display the contents of individual fields, tables, and so on:
Reward if usefull

How to list the abap programs order by updated date in ECD

Hi experts,
how to list the abap programs order by updated date in ECD?
thanks.

I wrote a custom program for displaying Z* development work into an ALV report. 2500 character limit prevents me from posting, message me your email and I'll send you source code.
Edited by: Brad Gorlicki on Feb 18, 2010 11:25 PM

Error out the ABAP program execution

I have an ABAP program which transfers data from a file to a database table thru function module in packages of 50,000 records.
Upon the successful completion of this ABAP program, I start dependent processes.
Sometimes the function module does not transfer the data and returns the exception back to the ABAP program - which is an expected scenario. Currently when ever an exception is received in the function module, I stop the ABAP program with a STOP statement.
The ABAP program stops, which meets my first objective. But what happens is, if you look at the job log --> it is Completed in terms of program execution and the dependent processes automatically start - which is not meeting my second objective.
My second objective is to force the ABAP program to error out in such a way that .........
1) The program execution is stopped
2) If I look at the job log it should not be Completed (I am looking for something like Cancelled so that the dependent process do not get started automatically)
Is it possible to error out the ABAP program execution by raising an exception or something, so that when i look at the job log - it shows Cancelled and not Completed?
Let me know if you have any questions.
Thanks,
RK.

Adrian,
Thanks - This is exactly what I was looking for, it works.
For some reason Messages skipped my mind and I was looking at raising Exceptions
Solution:
if sy-subrc NE 0.
message id 'abc' type 'E' number 000.
endif.
Thanks,
RK.
Edited by: RK on Jan 17, 2010 7:47 PM
Edited by: RK on Jan 17, 2010 7:50 PM
Edited by: RK on Jan 17, 2010 7:52 PM

I have an iMac, and have a Verizon DSL account. Recently, my Mac Mail keeps requesting the passwords on my account every few minutes, and will not allow me to send messages using Mac Mail. I cannot edit the outgoing server; how can I send emails?

I have an iMac, and have a Verizon DSL account (3 email addresses). Recently, my Mac Mail keeps requesting the passwords on my accounts every few minutes, and will not allow me to send messages using Mac Mail (the message says that the outgoing server was rejected. I cannot edit the outgoing server, and the keychain will not save my passwords (the ports are valid). How can I change the outgoing server to send emails, and how can I avoid having Mail request my passwords every 2 minutes? Verizon, as usual, will not provide support to iMacs.

Is there an email saved in your drafts or outbox folder? I suspect that Mail is continually trying to send it, and each time Google is rejecting the email message.
You can open the message and then delete it from your Outbox folder. Then try removing all @gmail email addresses from it and seeing whether you can send to the other folks. I suspect that will work.
With email, if an SMTP server *can* verify email addresses, sometimes it will and it will refuse to send messages. If a message has to be relayed across servers, no verification is done, and you'll get a bounce if an email address is bad.

When I get an ICS from Outlook that is a multi-day event it populates my iCal as a single day and since I am not the owner I cannot edit the ICS.

When I get an ICS from Outlook Express (Office is PC based) that is a multi-day event, it populates my iCal as a single day and since I am not the owner I cannot edit the ICS. I have to delete it and send a "decline notice" to the sender and re-enter it so I can put in multiple day events. Help!

If you are running Tiger, you don't have time machine.
You need to get something like SuperDuper! or Carbon Copy Cloner (sorry, I don't have a handy link for CCC but you can Google it to get their site) to make a clone of your drive on the external and then do incremental backups. The free versions do a lot and you can upgrade to the full-service versions for small change if you need more. The one time I used SuperDuper! for cloning a volume it worked just fine.
(My backup application is the last PPC capable version of Retrospect, which does a credible job, or has over the past ten-twelve years.)

Issue with the ABAP program to find BI lookups and code Patterns

Hello dears,
I'm trying to use the ABAP program LOOKUP_FINDER:
http://wiki.sdn.sap.com/wiki/display/BI/ABAPprogramtofindBIlookupsandcodePatterns
But I have the following issue:
Runtime Errors
RAISE_EXCEPTION
Short text
    Exception condition "NO_FIELDCATALOG_AVAILABLE" raised.
Error analysis
    A RAISE statement in the program "CL_GUI_ALV_GRID===============CP" raised the
     exception
    condition "NO_FIELDCATALOG_AVAILABLE".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
Source Code Extract
Line SourceCde
    1 method set_sort_criteria.
    2
    3 *... (1) Trace?
    4   if not mr_trace is initial.
    5     call method mr_trace->add_trace_item
    6       exporting
    7         i_trace_item = 'SET_SORT_CRITERIA'
    8         ir_variant   = m_cl_variant
    9         it_data      = mt_data
   10         it_info      = mt_info.
   11   endif.
   12
   13   if m_cl_variant->mt_fieldcatalog is initial.
>>>>>     raise no_fieldcatalog_available.
   15   endif.
   16
   17   m_cl_variant->mt_sort = it_sort.
   18
   19   call function 'LVC_SORT_COMPLETE'
   20        exporting
   21             it_fieldcat = m_cl_variant->mt_fieldcatalog
   22        changing
   23             ct_sort     = m_cl_variant->mt_sort.
   24
   25 endmethod.
This issue is located in the FM 'REUSE_ALV_GRID_DISPLAY' called at the end of the program.... maybe because the catalog is empty?
For your information, I called the program 'ZLOOKUP_FINDER'.
Can you help me to fix this issue?
Regards,
Vince.

Hi Vince,
If a table is empty field catalog usually return no error it just display your field catalog with headers .
I think the issue is with building of field catalog .
May be some settings are missing there .
Please check FM REUSE_ALV_FIELDCATALOG_MERGE where field catalog is getting generated.
Regards,
Jaya Tiwari

BEx Login error - Termination occurred in the ABAP program "CL_GUI_FRONTEND

Dear All,
I am having error when i am trying to login in BEx Analyser / Quary Designer 7.0
i am using the same user ID password as when i used to login to SAP BW through Logon pad.
but still i am having the error "Name or Password is incorrect. (repeat logon)"
I did try RRMX in BW, i got
Runtime Errors         RAISE_EXCEPTION
Information on where terminated
    Termination occurred in the ABAP program "CL_GUI_FRONTEND_SERVICES======CP" -
     in "GUI_DOWNLOAD".
    The main program was "RRMX_START_EXCEL ".
    In the source code you have the termination point in line 89
    of the (Include) program "CL_GUI_FRONTEND_SERVICES======CM012".
the program in the error dump as
CALL FUNCTION 'GUI_DOWNLOAD'
       EXPORTING
            BIN_FILESIZE              = BIN_FILESIZE
            FILENAME                  = FILENAME
            FILETYPE                  = FILETYPE
            APPEND                    = APPEND
            WRITE_FIELD_SEPARATOR     = WRITE_FIELD_SEPARATOR
            HEADER                    = HEADER
            TRUNC_TRAILING_BLANKS     = TRUNC_TRAILING_BLANKS
            WRITE_LF                  = WRITE_LF
            COL_SELECT                = COL_SELECT
            COL_SELECT_MASK           = COL_SELECT_MASK
            DAT_MODE                  = DAT_MODE
            CONFIRM_OVERWRITE         = CONFIRM_OVERWRITE
            NO_AUTH_CHECK             = NO_AUTH_CHECK
            CODEPAGE                  = CODEPAGE
            IGNORE_CERR               = IGNORE_CERR
            REPLACEMENT               = REPLACEMENT
            WRITE_BOM                 = WRITE_BOM
            TRUNC_TRAILING_BLANKS_EOL = TRUNC_TRAILING_BLANKS_EOL
            WK1_N_FORMAT              = WK1_N_FORMAT
            WK1_N_SIZE                = WK1_N_SIZE
            WK1_T_FORMAT              = WK1_T_FORMAT
            WK1_T_SIZE                = WK1_T_SIZE
            SHOW_TRANSFER_STATUS      = SHOW_TRANSFER_STATUS
       IMPORTING
            FILELENGTH              = FILELENGTH
       TABLES
            DATA_TAB                = DATA_TAB
            FIELDNAMES              = FIELDNAMES
       EXCEPTIONS
            FILE_WRITE_ERROR        = 1
            NO_BATCH                = 2
            GUI_REFUSE_FILETRANSFER = 3
            INVALID_TYPE            = 4
            NO_AUTHORITY            = 5
            UNKNOWN_ERROR           = 6
            HEADER_NOT_ALLOWED      = 7
            SEPARATOR_NOT_ALLOWED   = 8
            FILESIZE_NOT_ALLOWED    = 9
            HEADER_TOO_LONG         = 10
            DP_ERROR_CREATE         = 11
            DP_ERROR_SEND           = 12
            DP_ERROR_WRITE          = 13
            UNKNOWN_DP_ERROR        = 14
            ACCESS_DENIED           = 15
            DP_OUT_OF_MEMORY        = 16
            DISK_FULL               = 17
            DP_TIMEOUT              = 18
            FILE_NOT_FOUND          = 19
            DATAPROVIDER_EXCEPTION = 20
            CONTROL_FLUSH_ERROR     = 21
            OTHERS                  = 22.
IF SY-SUBRC <> 0.
    case sy-subrc.
      when 1.
        RAISE FILE_WRITE_ERROR.
      when 2.
        RAISE NO_BATCH.
      when 3.
        RAISE GUI_REFUSE_FILETRANSFER.
      when 4.
        RAISE INVALID_TYPE .
      when 5.
        RAISE NO_AUTHORITY.
      when 6.
        RAISE UNKNOWN_ERROR.
      when 7.
        RAISE HEADER_NOT_ALLOWED.
      when 8.
        RAISE SEPARATOR_NOT_ALLOWED.
      when 9.
        RAISE FILESIZE_NOT_ALLOWED.
      when 10.
        RAISE HEADER_TOO_LONG.
      when 11.
        RAISE DP_ERROR_CREATE.
      when 12.
        RAISE DP_ERROR_SEND.
      when 13.
        RAISE DP_ERROR_WRITE.
      when 14.
        RAISE UNKNOWN_DP_ERROR.
>>>>when 15.
        RAISE ACCESS_DENIED.
krish

Hello,
the same type of problem was solved today this way (it´s due to a local client problem):
Start users local SAP GUI
In the left upper corner of SAP GUI select the menue and -> options.
Delete all cache files of SAP GUI and browse the local SAP GUI download folder of the users workstation. Rename the files in the download/workdir folder for example to *_old.
Logon to SAP system again, run RRMX again -> confirm download of bex config file -> Excel sheet should open now.
Important: also the end user has to configure some excel addin options (bex) otherwise the excel sheet will be blank / empty.
BR,
Alessandro

When I convert a PDF to a Word doc, it "converts" as a picture and I cannot edit the document. What can I do to get the PDF to convert properly?

When I convert a PDF to a Word doc, it "converts" as a picture and I cannot edit the document. What can I do to get the PDF to convert properly?

Hi conversionnewbie,
Are you able to select the text in Word by triple-clicking inside the text box? (Sometimes text selections can be tricky in converted files.) If you can't select the text, then I'm guessing that the PDF was created from a scanned file (so the text becomes images). Make sure that OCR is enabled when you convert the file to Word. OCR is enabled by default in the ExportPDF web interface, but can be disabled in Adobe Reader. If you're converting to Word from within Adobe Reader, make sure that OCR is enabled and that the correct language is selected:
Please let us know that works for you!
Best,
Sara

How to call the abap program in workflow

HI Exeprts,
I need to call one abap program in workflow.
can any tell me how to call the abap program in workflow.
thanks &regards
ramesh

Dear Ramesh,
U can use REPORT business object.
Method : EXECUTE_2
Regards,
Sagar

In iTunes I click on a song and when I click on the "get info" tab, it opens up but everything is gray - locked, therefore, I cannot edit the year or genre of the songs. Not every song is locked, only certain ones for some reason. Any help?

In iTunes I click on a song and when I click on the "get info" tab, it opens up but everything is gray - locked, therefore, I cannot edit the year or genre of the songs. Not every song is locked, only certain ones for some reason. Any help?

I ran into the same problem, I think that, If you tab on a song that is on your IPOD, and the song data is grayed-out, I think it means that the song is probably twice on your IPOD and that the iTunes directory can not edit THAT song data for two (or more) files @once. Check if this is the case, sinceI have the same problem,am looking for a way to have One and the same song in more playlists but only keep the song once on the IPOD.

Cannot Edit The Report

Hi All,
Please help me, I created an interactive report and made some modifications. THE PROBLEM IS that I cannot edit the records.
http://apex.oracle.com/pls/apex/f?p=49631:1
user: dev
pwd: dev
Thanks in advance.

Thanks Ta,His handle is trent by the way, I m afraid you picked his salutation ;) .
have to delete the auto-generated process. And now how can I make Edit works again.Go to "*Create Page Process -> Data Manipulation -> Automatic Row Processing (DML) -> give some process name -> Specify Tablename,Primary Key column, Item with PK , Check/uncheck required DML operations -> Specify button conditions*"

Table Name where the ABAP program names get stored

Can any 1 tell me the table name where the ABAP programs get stored

try TRDIR,TRDIRT,TADIR
regards
shiba dutta

Where does Abap Dataflow create the Abap program

Within Abap dataflow properties i have to give program name: which i gave as : Z_MaraXtract
The abap dataflow extracted data perfectly fine. it created a dat file in working folder and also populated data to template table.
Where does this Abap program "Z_MaraXtract: gets created?
Thanks a lot for the helpful info.

Hi Raj,
You are probably looking for Z_MaraXtract on your DS box. This is the same thing I was looking for, for a long time.
This is the Abap program name. The file that DataServices uses is in the folder you defined in the data store, advanced, Generated ABAP directory.
To the the OS filename on your DS server , rightclick on the ABAP Dataflow, properties, select the tab options and you will see a "Generated Abap filename" field. The name you put there is the physical filename on, say Windows. If you open that file (with notepad) you will see the ABAP program name Z_MaraXtract.
Norbert

Cannot edit the Abap program

Similar Messages

Maybe you are looking for