Debugging standard transaction MB1C - Queries

Hi Experts,
SAP standard transaction MB1C is not updating the database table MSEG.
Please help me in finding the cause of this issue.
1. I have checked the ST22 for any errors - no errors logged.
2. How is the transaction insert entries into the trans. table MSEG. ( any update, modify queries)
3. How to debug the MB1C tx to find the issue..
When I post the documents, it says "Document #### posted". When I go and check the table.. I get "No table entries found".
Please provide me some ideas where is the problem.

> SAP standard transaction MB1C is not updating the database table MSEG
I don't know MB1C, but if you use the normal transaction MB03 (?) to display the goods receipt (or whatever its name is), does it display normally? (ask the functional people if you don't know the transaction)
If yes, then maybe it's normal that MSEG is not filled (sorry if it makes some people howl). In that case, you should trace MB03 transaction via ST05 and other techniques (see Brad's answer) to check from which tables the data comes from.
If you can't see the goods receipt using any transaction, then it's probably a bug and you have to contact SAP support.

Similar Messages

Debugging of standard transaction(screens)

Hi,
How can I debug standard transactions and screens.
I have program name and screen number.
How can I go ahead for debugging.
Regards
Sasi

Hi,
Debugger is the best weapon an Abaper has. SO go ahead and debug.
Find what the program does.
If you know the program name.. GO to the program. Keep the breakpoint where it is necessary. and run the transaction
Else type /h on the prompt press enter.
Then enter the tcode in the prompt and press enter
Regards
Vijay
Edited by: Vijay on Jul 3, 2008 11:13 AM

Debugging ZdriverProg when attached toa Standard Transaction code

Hi all,
iam doing with SAP Standard smartform
initially the ZProgram and Zform are attached
to standard Program : RV56TD00 for the transaction VT02N
(ApplicationV7 - Shipment : Bill of Lading)
+
Zform
Now iam working on Modifying the ZProgram to Zprogram1 + Zform1
where Zform1 is modified version of Zform
Zprogram1 + Zform1 both are saved in LOCAL OBJECT
please let me know ..that
1) How can i test and Debug my Zprogram1
if possible Provide an example .. for the above said things ..
In Short : for a standard transaction ( VT02N ) where Zprog + Zform are attached . how to debug Zprog ????????????????
for appropriate answer Points will be rewarded instantly..
Looking for ur answer...
Thanks
Aslam...

Hi,
Open the ZPROGRAM and put the breakpoint in that and go to VT02N transaction go with print prieview now it will display in debugging mode .
If you want to degug in smartforms open the smartform and create a program lines and in the input parameters give the variable you need to check in the debugging mode and go with print preview in the vt02n .
Thanks,
NN

Wrong portions of code being executed in standard transactions

Hi guys,
I've recently come accross some weird errors in a standard transaction in a system and thought you might have a clue. I was getting an ugly dump in F110 in a fresh system that it can't do a READ TABLE with index 0. After investigating it and debugging it for a while, I got in the PAI of a screen, where two procedures were important:
1) WERTE_PRUEFEN was being executed in a loop...endloop (that's where the error supposedly occurred). The thing is in the debugger it didn't go into this module inside the loop, as it should if there are no entries.
2) After that, WERTE_LOESCHEN. When I got here and pressed F5 to see what's going wrong in it, guess where the debugger redirected me: you're right, to the WERTE_PRUEFEN thingy. So a statement like MODULE WERTE_LOESCHEN. gets me to a completely different procedure. This is crazy!
I'm not at my first experience with this. BEx applications would do this if you'd change the ABAP source code and the people wouldn't reconnect again. Even if in the debugger I'd see the new code, the system would execute the old one, probably some caching issues. Always worked when people disconnected / reconnected.
However, in the actual situation, no matter how many times I log on/off, the dump is there.
This is not the only example of this kind, there are more module statements gone crazy in F110 in this system, but only this one dumps instantly.
What do you think it could be the cause of that/ what is a good solution for this?
I was thinking it has something to do with the program's generation and I asked the Basis guys to run an SGEN, hopefully that would help.
Thanks in advance,
George

Hi Vikranth,
Nope, just pressing F5 trying to get into WERTE_LOESCHEN and being redirected to that module inside the LOOP...ENDLOOP, WERTE_PRUEFEN. Well, I didn't say this happens in every system, only in that specific one. Of course, if I logon in another system, everything looks fine.
Another person suggested that it's the GUI to blame and that I should get the newest version. Still, the error was reported by a person that has the latest version of the GUI. I still think it's a generation/ installation issue but got no reply from the Basis admin so far.
Regards,
George

Dump issue in standard transaction

I am getting a dump error in a standard transaction while clicking save option,
could you please confirm me whether the issue is with SAP standard transaction path fill missing or some thing else since when we will do the same steps in same transaction to some other server its not giving dump error.
Should I've to do any code changes in the standard transaction by registering access key request or is there would be any basis related issue.
Also, I debugg a lot and not sure from where the issue is comming.
Please suggest.

I'm done with the debugging and found the reason for the problem.
Secondly as I said it a pure slandered transaction and we have not done any code changes, enhancement, BDT/BRF etc
so there in no way to get into depth for debugging since every line of code would be correct but the we need to find out where and why its getting stuck and throughing the dump.
Where
                In DSAVE BRF event only its giving error as error message = E once no entry found in the internal table. however it has to get some data from some where but unfortunately its not collecting the data so it remain initial and its result error type and E which indicate dump with logical (feeder) system not determine
Why
             SAP insurance module consist of CD, CM, ISM, Banking and where BP will act as a central component,
so there would be by default integration between BP and CD,CM,ICM,Banking. But I think the default connection between these all is not exist in our server, therefore once we are clicking save option in our process its not getting the path for interconnection with CM.
Final conclusion the integration between BP and CM is not establish hence its giving dump.
So could any one please tell me how to establish the integration between BP an CM, it might be related to BASIS issue but I welcome all who ever can provide the solution. (Might be we have to do some configration or something in SPRO-cross application - SAP BP - etc. )
Edited by: Helpfriends on May 23, 2011 10:15 AM

How to debug standard report

plz tell wt are the different way to debug standard report

Best way to debug is :
Take the message number and message id .
now goto Program ( When you go transaction -> system->status -> here you get program name).
click on find -> enter message number ( Select main program ) -> here you get message number ,now keep the break point ).
some times they call messages as like dynamically.
goto transaction -> enter all the data -> /h in command bar -> now create watch point -> use varaible as message id and value as message number ) ,operator is =
now it stops exact area
Rewards if useful.

Data retrival from standard transaction

hi all,
i have to get the material list from stadard t-code ca80 i have debugged the program and the whole material list is in tmapl internal table so if any one can find me a solution thats ll be very helpful. and points are rewarded
thanks in advance
anupama

hi,
You can call transaction and send the data to it.
call transaction mm01 and skip first screen.
set parameter ID 'MAT' FIELD P_matnr.
Here you are passin gthe selection screen parameters to the standard transaction MM01 and skip the screen..
you start recording like in BDC and execute it here.
so you will be having the data in the internal table that you can update in the Database table.
Regards,
Madhavi

Ways of debugging standard program

ways of debugging standard program to find out the solution!

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 add function key to a menu exit in a standard transaction

Hi all,
I have a requirement to add a function key for a menu item in a standard transaction.
In Menu bar we have an option Extras->Other->Repricing . Now my requirement is if i click a function key (ex. F9) the code under the menu exit (Repricing) should trigger. For that i had a function exit EXIT_SAPLJHPA_011 and in this the menu exit SAPLJHPA +CU7 is defined.could anyone suggest me the procedure in detail to add a function key..
Thanks in advance,
Uday.

Hi
for this u have to edit standard PF-status, that particular transaction is using. becarefull as the same pf-status may be used for many programs.
get the PF-status for that program. you can get the pf-status via se80, give the program name and u can get the the list of all the objects of that prigram, there you can edit the standard status and can add the function key to your menu item.

Add button to RF Standard transaction

Hello,
Is it possible to add a push button to an RF Standard transaction? and How?
Thx

Hi,
SAP has provided Dummy screens to each RF screen for you to enhance it. They usually named as 'SAPLXLRF' and screen number would be 9XXX . 'XXX' being the original screen number. Then you need to activate the corresponding user exit that starts with MWMRF* for the corresponding screen. Also in the RF Screen Management you need to add an entry with Variant '1'.
Hope that helps.
Thanks
Vinod.

How to create F4 for the standard transaction

Hi all ,
How to create F4 for the standard transaction for a particular field .
Bye

Santosh,
You can create F4 values for a field in a standard Transaction .
1. First search for a standard search help meeting your requirement .
2. If you don't find one, create your own custom (z) serach help .
( 1 is preferable )
After that, include that serch help to the standard field in the transaction .
For this u need to go to the screen
( F1->F9-> screen-> Field )
Click on the property of the field and include the search help .
You ll require the access key from the basisi guys as u r changing standard .
Hope it helps,
~ laxmi
Reward for helpful answers

Calling custom dialog screen from Standard Transaction(user Exit)

Hi, I'm calling Standard Transaction from a Custom Screen. I'm calling a custom screen again with in standard transaction (implemented custom screen thru user exits using macros). But when I click 'continue/cancel' in the custom screen, control is going back to main cutom screen rather go back to standard transaction. Could anyone please help me out how to come back to standard transaction from custom screen rather going back to main cutom screen.
***INCLUDE LZ_R_FORWARD_FORWARD_LOADI01 .
*&      Module USER_COMMAND_9000 INPUT
MODULE user_command_9000 INPUT.
CASE sy-ucomm.
    WHEN 'EXEC'.
      PERFORM validate_popup_data.
      IF flag_error_screen NE 'X'.
        MOVE-CORRESPONDING ZFFL_POPUP to var_ZFFL_POPUP.
        clear flag_return.
        SET SCREEN 0.
        LEAVE SCREEN.
      ENDIF.
    WHEN 'CANC'.
      flag_return = 'X'.
      SET SCREEN 0.
      LEAVE SCREEN.
    WHEN OTHERS.
ENDCASE.
ENDMODULE.                 " USER_COMMAND_9000 INPUT
*&      Module exit_9000 INPUT
MODULE exit_9000 INPUT.
CASE sy-ucomm.
    WHEN 'CANC'.
*      MOVE perf_flag TO lbpla_exist_flag.
      flag_return = 'X'.
      SET SCREEN 0.
      LEAVE SCREEN.
ENDCASE.
ENDMODULE.                 " exit_9000 INPUT
Thanks in advance.

Hi
So the command SET SCREEN 0. LEAVE SCREEN. should "place" the program just after the calling of the popup so here:
FUNCTION z_call_screen.
* Call the Pop up screen
    CALL SCREEN 9000 STARTING AT 35 05.
"<------------------------- The program should be here after going back from popup 9000
ENDFUNCTION.
Is it true?
Max

How to get information from a text editor in the SAP standard transactions

Hi SAP gurus I have a requirement in which it is required to gte the information from a text editor(which is not a field) in mm02 (click on) goto Purchase Order Text in this view there is a text editor there is some text in te the text editor i have to get that information in a table can it be done if so please give example and steps
Points will be given to useful information

Ah yes, excellent question, and not really a clear cut answer. In my experience, the easiest way to find this information is to simply create the text using the standard transaction, in this case MM02. Then go to transaction SE16, using table STXH, do a query on this table, entering your user name, and today's date as the creation date. The results should show the text that you just created, now you can see the object, id, and the way the name is being used here.
I also understand that in some cases, there is a button next to the editor in the screen which gives you some idea of these values, but this is not implemented everywhere, and I believe that I've only seen this in one place, can't remember where, but the first solution above will always work for you.
Regards,
Rich Heilman

HOW TO PASS THE DATA FROM SELECTION SCREEN TO STANDARD TRANSACTION?

HI,
HOW TO PASS THE DATA FROM SELECTION SCREEN TO STANDARD TRANSACTION?
thanks,
samba.

By selection screen, what do you mean? There is no selection screen in WDA as there was in classic dynpro. Do you mean you are using the Select-Options reusable component? Are you wanting to call a standard transaction via ITS - SAPGUI for HTML? Please provide more details to your question.

Standard transaction CG02 is not saving the data through F4 help.

Hi Guru's,
I have a standard transaction CG02 for this i need to maintain the data for few of the fileds like Heat sensitive, Thermal energy hazard etc for updating Derived C-Alpha code. So for i can able to maintain data in two ways either directly or through F4 help. when i supply data through F4 help, on the F4 help window im providing the value and clicking on continue button. when i press on the contine button it has to update the Derived C-Alpha code if all the required fields filled. If suppose i do nt fill the required fileds it has to through the error message on the status bar like 'Invalid Data Combination'. Now the problem is when i clicking on continue button of F4 help window im displaying error message. when i try to change the value or try to fill the required fields so for im clicking on F4 button then its directly taking me out from the transaction. If i press on any key also samething is happening but the same is not happening when i supplied the value directly and saving. Please let me know the reason and help me for the same with needful solution. If anyting required plz ask me i wil provide u.
Here we are using the user-exit EXIT_SAPLC107_001 and is used in FM C107_CUSTOMER_FUNCTION_CALL.
Thanks in advance.
Yours,
Somu.

Hi Guru's,
I have a standard transaction CG02 for this i need to maintain the data for few of the fileds like Heat sensitive, Thermal energy hazard etc for updating Derived C-Alpha code. So for i can able to maintain data in two ways either directly or through F4 help. when i supply data through F4 help, on the F4 help window im providing the value and clicking on continue button. when i press on the contine button it has to update the Derived C-Alpha code if all the required fields filled. If suppose i do nt fill the required fileds it has to through the error message on the status bar like 'Invalid Data Combination'. Now the problem is when i clicking on continue button of F4 help window im displaying error message. when i try to change the value or try to fill the required fields so for im clicking on F4 button then its directly taking me out from the transaction. If i press on any key also samething is happening but the same is not happening when i supplied the value directly and saving. Please let me know the reason and help me for the same with needful solution. If anyting required plz ask me i wil provide u.
Here we are using the user-exit EXIT_SAPLC107_001 and is used in FM C107_CUSTOMER_FUNCTION_CALL.
Thanks in advance.
Yours,
Somu.

Debugging standard transaction MB1C - Queries

Similar Messages

Maybe you are looking for