Need tips on debugging standard programs

I am a beginner and my first project is a maintainence project. Debugging standard programs is getting too tough for me. Is it with everybody? Can you please suggest me some ways to make my task easier.
The comments are in german and there are no explanation of ne step newhere. I cant even remember which program or include file i'm in.

Hi,
You can refer the below links to develop the debugging skills.
debugging in standard progrms
debugging
http://help.sap.com/saphelp_nw04/helpdata/en/b3/d322540c3beb4ba53795784eebb680/content.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9cbb7716-0a01-0010-58b1-a2ddd8361ac0
http://www.sappro.com/downloads/Settings&SystemAreas.pdf
Hope this will help to start with.
Regards,
Ferry Lianto

Similar Messages

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

Purchase order need to add to Standard program

Hi Folks,
i have standard program RFDEPL00, i have to copy this one into Zprogram and need to add the purchase order number and text into the output display(purchase order number will take from VBAK-BSTNK),
could any one help me how to bild the logic for this and where to build?
thanks in advance

In include program FDEPL00_SHOW line 18, call the alv function module.The out put internal table is gt_data.I think you can debug the program and add find the right position to add new field to the gt_data table.
But i found include program FDEPL00_READ use LDB method to get the vendor information.So i think it is not very easy to add code in FDEPL00_READ.
Maybe you can add code before call alv function.
Regards Chris.

How to Debug Standard Program & Customised Scripts in Cheque Printing

Hii
Am working on APP Cheque Printing...
here am using standard driver Program 'RFFOUS_C'
and two customised script for Cheque print and payment advice print..
please let me know , How to dubug my cutostomised script while printing through F110 .....
its not working evenif am activating Debugger in Script or also through RSTXDBUG Prgm
Note : In APP , when am Processing through F110 , In background mode processing takes place and finally Spool is generated....
Awaiting for ur reply...
Thanks in Advance

Hi,
yes offcource you have to activate debugger for script ....but additionally
1. The point in the program where your script is triggered put an external breakpoint.
2. Before giving the Print Preview or whichever button put '/h'
3. After putting /h and pressing the button it goes in Debug mode then you can F8 and it will reach the point where you have set the Breakpoint or External breakpoint.
Thanks,
Neha

How to Debug Standard Program & Custom Scripts in Cheque Printing

Hii
Am working on APP Cheque Printing...
here am using standard driver Program 'RFFOUS_C'
and two customised script for Cheque print and payment advice print..
please let me know , How to dubug my cutostomised script while printing through F110 .....
its not working evenif am activating Debugger in Script or also through RSTXDBUG Prgm
Note : In APP , when am Processing through F110 , In background mode processing takes place and finally Spool is generated....
Awaiting for ur reply...
Thanks in Advance
Edited by: LU JACK on Sep 19, 2008 1:18 PM

Hi,
Go to SE71 , give form name ZXXX and go utilities activate debugger
Go to SE38 give driver program name 'RFFOUS_C' .and execute click OK button give printer name like LP01 and see print preview or print
it will go debugger mode.
it will help ful you.
Regards,
Bhupal.
Edited by: bhupal reddy on Sep 19, 2008 1:34 PM
Edited by: bhupal reddy on Sep 19, 2008 1:35 PM

Resume sometimes results in unresponding laptop. Need tips to debug.

Hi all,
I have a major problem with 2 MacBook Air's that I hope someone can help me debug.
This issue is not reproducible all the time. It sometime happens. Sometimes everything works as expected.
The problem:
After resuming (from hibernate not suspend) the laptop becomes unresponsive to any and all events. The only thing that works to my knowledge is to press the power key for several seconds and hard reboot it that way.
This issue has been there for some time. So I can't pinpoint it to a specific kernel or set thereof.
Hardware:
MacBook Air 6,2 with the Intel i7-4650 CPU
Software:
up-to-date ArchLinux (64 bit)
Windowmanager: one laptop i3, the other xfce
Screenlock on booth laptops: i3lock executed by this systemd unit
$ cat /etc/systemd/system/[email protected]
[Unit]
Description=User resume actions
Before=sleep.target
[Service]
User=%I
Type=forking
Environment=DISPLAY=:0
ExecStart=/usr/bin/i3lock -c 000000
[Install]
WantedBy=sleep.target
On the i3 laptop hibernation is invoked by logind.conf
$ grep hibernate /etc/systemd/logind.conf
HandlePowerKey=hibernate
#HandleHibernateKey=hibernate
HandleLidSwitch=hibernate
On the xfce laptop hibernate is started by xfce power manager.
Both laptops use the mba6x backlight driver from aur
Both systems do not have acpid installed.
What happens when the issue appears:
1) Open lid and press power key
2) Screen turns on and reaches i3lock (I can tell that, because the xfce laptop set a wallpaper for i3lock which is displayed)
3) No reaction to any input. Pressing keys (including Fn+Ctrl+F1 through F9) does not result in any reaction. Closing the lid again does not result in any action (it just stays as it is with the i3lock and display backlight on). I can't ssh into the machine.
How do I find the cause for this problem? As far as I can tell, there is nothing in the logs because it does not get written to disk before rebooting the laptop (and I have no idea which log to check. On a running system I would check dmesg, X11-log, and journalctl -f...)
Please ask for any information that I missed. I really want to resolve this problem and learn how to find the cause.
Yes, I googled and searched the forum and read quite a couple other posts to no avail...
P.S.
I just tuned off the i3lock unit on the i3 laptop the see whether the issue goes away - but this doesn't seem likely to me.

Ok, the problem did not appear since I turned of the i3lock unit.
Does anyone see a mistake I made in the unit file, or has another solution on how to lock the laptop once it goes into suspend/hibernate?

Help neede in changing standard program CN41

Dear all,
I am working on a requirement in PS module.
The requirement is I need to copy the standard program RCNST000 of CN41 and I need to add some extra fields.
Here in initial display project object, project object.
when I select duration and Order cost plan 000 from the list It will display duration and order cost plan in the report.
My requirement is when they select that I need to display cost per day and cost for currect month.
Can anybody help me.
Thnaks and regards
Anil

Dear all,
I am working on a requirement in PS module.
The requirement is I need to copy the standard program RCNST000 of CN41 and I need to add some extra fields.
Here in initial display project object, project object.
when I select duration and Order cost plan 000 from the list It will display duration and order cost plan in the report.
My requirement is when they select that I need to display cost per day and cost for currect month.
Can anybody help me.
Thnaks and regards
Anil

Addition of standard programs in Schedule Manager Flow definitions

Hello Experts,
I want configure schedule manager for month end closing.
In that I am creating flow definition. In the flow definition I want to insert one program RKAZCO43COWL which is standard program & which is also entered in the table SCMAPROGRAMS in the reaspective appplication.
But still I am unable to find it in the input help for creating program in the flow definition.
Please help. Is there any other way where in I need to register the standard program ? How can I find it in the input help ?
Thanks in advance.
Abhishek

Dear All,
I am still facing below issue.
While creating flow definitions , when I try to attach program I face below issue.
e.g. I want to attach program RK_PEP_WL_SEL_SAL which is in the application CO-PC-OBJ-SALESORD but when I created flow definition I gave application as Controlling , so how to add program in the flow definition which has different application ?
If I try to attach application CO-PC-OBJ-SALESORD in flow definition itself then I cannot add programs in Controlling application .
Kindly help how to add different programs from different application.
Thanks in advance.
Abhishek.

Calling the standard program in program and getting its output in int table

Hi there,
I have a requirement, where I need to call the standard program (of transaction CJI3) in my Y program. CJI3 transaction produces a ALV GRID output. I need to use that data for further processing. I am getting following problems:
1. I tried to use SUBMIT ... EXPORTING TO MEMORY statement. I need to pass the company code for the selection, but the company code is in the dynamic selection. So not getting how to pass them.
2. Just a doubt. Can we export the ALV GRID to the memory an retrieve it back using import?
3. I did tried to use SUBMIT ..... statement using only the parameters which are on the selection screen. However the control went to CJI3 transaction and gave an error message 'Please select "from database" or "from archive" '. Did not understood that, any IDEA?
Or is there any other way with which I can accomplish my requirement of getting the data in my program to manipulate, other than SUBMIT.
Points will be rewarded.
Thanks,
Ganesh Khumse

Hi,
point 1:
SUBMIT ... EXPORTING TO MEMORY will never work, because it displays the information in an ALV grid and that grid is waiting for user interaction for manipulating the information.
point 2:
no, you cannot export the content of an ALV grid to the memory
point 3:
must you get records in an internal table or must you feed the transaction, so that this one performs a task ?? for first option read below and for the other option you might work with BDC and Transaction Recorder.
what you have to do is read the code of transaction CJI3 in order to understand what it does, where the information is read from and what is the internal table that passes the values to the ALV Grid. You might find a user exit in the code for manipulating that information or you might create an enhancement point if there´s no user exit.

Error in VL10I Standard Program

Hi All,
          I was asked to debug standard program VL10i where not all deliveries are getting created when done together.
some of them misses out.When I run then individually it works. Sometimes if you run in small batches it works..sometimes it wont. The behaviour is so strange.
The error is " Transfer Paramaters are not complete ".
Can anyone suggest me any OSS notes to solve this issue or known solution.
Regards,
Anand

Dear All,
Thanks you all for the reply and support.
The Issue is been resolved.
As per SAP's reply We tries to do the Transport of Copi of certain program which we where getting DUMP like :
Program Name           SAPLS38E
INCLUDE Name         LS38EU26
INCLUDE Name         LS38EU24
This got transported with out any error and the issue got resolved.
Thanks & Regards,
Pradeep Alex Luke.

Calling standard program

Dear Experts,
I have writen a Z program which converts the format of the output file, i need to execute the standard program rfebck00 after execution is completed i need the final output values back in my Z program for further process..
I tried with the submit and return ...but it is not working ,
I'm getting the output but after I pressed the back button its going to my program but user is not willing to press back button Is there any other way to do the above requirement...
thanks in advance
Hema

Hi,
Please try to use FM ABAP4_CALL_TRANSACTION to call transaction FCKR (report program RFEBCK00). Perhaps you can setup the table parameter USING_TAB for BDCDATA of back button.
Regards,
Ferry Lianto

Standard program saving

hi,
I need to modify a standard program /1BCDWB/IQG000000000038SSCR.I got the access keys and it got edited.
but while i am trying to save that program,the following error occurs
Object PROG /1BCDWB/IQG000000000038SSCR cannot be assigned to package ZPACKAGE
Whether we cant modify this kind of programs or is there any opther way to modify and transport this object.

Ramya,
I guess you are trying to edit a query prorgram generated by the system. These generarted program cannot be assigned to Z Package - besides they do not have a package assignment first place.
If you need some simple queries to be created; you can try SQVI. You can use this directly and helps to generate adhoc queries.
Regards
Kathirvel

How to Debug SAP standard Program SAPMM07I

Hi All
Please tell how to debug an SAP Standard Program for MI07 T-code.
In this Transaction I would like to change the Unit of Measure filed to Alternate Unit.
Please, Help me out .. how to debug this program and how to change this field.
Thank you
Prasead K

Hi Myline
Thanks for your reply. My Issue is that I would like to Diplay "Difference Qty" VM07I-DIFMG and Base Unit
of Measure (ISEG-MEINS) in MI07 Tcode as Unit of Issue (MARM-AUSME) which is defined on Material Master Plant Data View.
Till Now, I did is I copied MI07 Standard Program SAPMM07I to ZSAPMM07I. And Assigned this Z program to MI07 in SE93. Now, I need to make modifcation in this Zprogram such that I display: Unit of Issue and Difference Qty fields on MI07 instead of Base unit of Measure.
Here, Base unit of measure is EA and Unit of Issue in ICS (Imperial Cases). IN MI04 we enter in ICS(unit of Issue.. which is converted to EA. and MI01 its in EA. (Base unit of Measure).
Please if this not clear.. please let me know.
Waiting for your reply.
Thanks once again.. !
Prasead K
Edited by: Prasead K on Feb 19, 2008 9:15 AM

Hi how to debug the stand form and standard program of credit demo......

hi , i could find find the credit memo in FI standard form and standard program at the given path
SPRO->IMG->Financial Accounting->Accounts Receivable & Accounts Payable->Customer Accounts->Line Items->Correspondence->Carry out and check settings for correspondence->define Form Names for corresponding print> here u can c ur program along with the Form assigned to it...
I copied the standard form to z form and assigned to standard program, now to know the elements in a write form which are triggered , i need to apply breakpoint in standard program and run the application to view the elements.. But , to apply breakpoints in the standard program, no form routine is given...Then how to identify where to apply breakpoints to identify the elements....
i will be very thankfull for the reply..
thanks..

Hi,
Activate debugger as above for FORM, or copy the Standard print program name and open it in SE38 in display mode, Look for OPEN_FORM or WRITE_FORM fm in the Main print program and put break point. when you run the application it will stop at the break point.
Regards
Bala Krishna

Need to add field to standard program.

Hi all
I need to add a field to standard program whic is from the Ztable. How do I do it and where should i add the field.
Plz help.
Regrds
Mona

My queries is I need to create a ztable and using that ztable field I need to get data. I need to change the output of the standard program that output shud have that field.
for eg. Company code specific data. this company code field i need to have in program output that means i need to use this ztable in standard program.
If not clear plz tell me
mona Please respond to the same thread.
so everyone could answer for your query.
if it is a report program copy it as a Zprogram.
create a ztable in se11 .
add fields and data entries finish all those work there.
and in the copied std pgm
add select-options: s_new_f1 for ztable-f1.
or u can also use parameters: p_f1 type ztable-f1.
under : at selection-screen output.
<perform select query operation for the new ztable.>
select singe * from table ztable wa_ztable where f1 = p_f1.
so that the new field willl also come along with the standard output.
Please check this

Need tips on debugging standard programs

Similar Messages

Maybe you are looking for