How to overcome the standard program check that changes my input file data?

Hi
when we r uploading PO thru bapi_po_create1, we give tax codes in the input file...but when the code gets into this MM06EFKO_PREISFINDUNG include of SAPLMEPO, there is a logic that changes the tax code (ekpo-mwskz = tkomv-mwsk1) and hence it gets reflected in the PO created...is there any way where i can by pass this one for the POs that i create thru my prog...pl shed some light on this
Sathish R

enter the program name in the SE38 editor
click on copy button
then it will ask you for the new name
when ever you click on the copy transfer buton
then it will raise a pop and saying that what ever you want from the program like
1) INCLUDES
2)SCREENS
3)USER INTERFACES
4)VARIANTS
5) DOCUMANTATION
ETC..
hat ever you clcik on that check box
thats all
rewar dif usefull

Similar Messages

How to call the Standard Program in our ZPROGRAM?

Hi Frieds can you tell me the procedure how to call the Standard program
in z----
program and we have to get the data from standard one to our customer program.
Thanks in advance,
madan mohan.

Hi,
*Submit report but export resultant list to memory, rather than
*it being displayed on screen
SUBMIT zreport EXPORTING LIST TO MEMORY.
Once report has finished and control has returned to calling
program, use function modules LIST_FROM_MEMORY, WRITE_LIST and
DISPLAY_LIST to retrieve and display report.
*Example Code (Retrieving list from memory)
DATA BEGIN OF itab_list OCCURS 0.
        INCLUDE STRUCTURE abaplist.
DATA END OF itab_list.
DATA: BEGIN OF vlist OCCURS 0,
        filler1(01)   TYPE c,
        field1(06)    TYPE c,
        filler(08)    TYPE c,
        field2(10)    TYPE c,
        filler3(01)   TYPE c,
        field3(10)    TYPE c,
        filler4(01)   TYPE c,
        field4(3)     TYPE c,
        filler5(02)   TYPE c,
        field5(15)    TYPE c,
        filler6(02)   TYPE c,
        field6(30)    TYPE c,
        filler7(43)   TYPE c,
        field7(10)    TYPE c,
      END OF vlist.
SUBMIT zreport EXPORTING LIST TO MEMORY.
CALL FUNCTION 'LIST_FROM_MEMORY'
TABLES
    listobject = itab_list
EXCEPTIONS
    not_found = 4
    OTHERS     = 8.
CALL FUNCTION 'LIST_TO_ASCI'
EXPORTING
    list_index         = -1
TABLES
    listasci           = vlist
    listobject         = itab_list
EXCEPTIONS
    empty_list         = 1
    list_index_invalid = 2
    OTHERS             = 3.
IF sy-subrc NE '0'.
WRITE:/ 'LIST_TO_ASCI error !! ', sy-subrc.
ENDIF.
Regards
Sudheer

How to find the Standard Program associated with a Standard IDOC

Hi,
I am going work on enhancing the standard IDOC. Any body can suggest how to find a standard pogram associated with a Standard IDOC. And can any body send some exaple code for extending a standard IDOC and to implement the logic in the standard program .....

Hi,
For outbound IDoc the program can be found:
1) For master IDoc via transaction BD60. Here for the message type you can find the function module used to generate the IDoc. Within this function module you can find the user exit where you can code your logic.
2) For IDocs with message control (output control) we maintain settings for proces code in WE41. This process code will lead to outbound IDoc generation program.
For Inbound IDoc the program can be found:
Via WE42 where inbound process and its related inbound function module is maintained.
In each cases above we can go the function module and find the customer exit where idoc enhancement logic can be coded.
For extending IDoc look at the following links:
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7d6243d711d1893e0000e8323c4f/content.htm">Extending IDoc - SAP help</a>
It can be summarized as follows:
Enter transaction WE30 (ALE->Extension-> IDOC types->Maintain Idoc type)
- Type in your name of the extended IDOC type (usually starting with 'Z') and click on the Basic IDoc type, click the create icon.
- Click on Create new and enter a description and press enter.
- Click on ZIDOCTYPE01 and then on the Create icon.
- Enter ZIDOCTYPE as the segment type, click on Segment Editor.
- Enter a description for your segment type and create.
- Enter a description for your segment, enter each field required in your IDoc and press enter to validate.
- Save and generate, press back
- To release the segment choose Goto, Release from the menu.
- Check the box on the line of your segment.
- Save, back and enter.
- Your Idoc type structure should be displayed with your new segment.
- Save and back.
- To release the Idoc type choose Extras, Release type from the menu and Yes.
Hope this helps.
Regards,
Gajendra.

I have changed computers and installed iTunes on my new computer. I want to sync my iphone now but the "sync" program indicates that it will remove all data on my phone and replace it with the newly installed itunes that does not have my information.

I have a new computer and have installed iTunes on it.
Now I want to sync my iphone but the new itunes on the new computer wants to remove everything on my niphone and replace it with what's on the newly installed itunes data but it does not have my data.
How can I sync the new itunes with my iphone and not have my phone data wiped out?
Thanks,
hscllc

hscllc wrote:
How can I sync the new itunes with my iphone and not have my phone data wiped out?
There is no way to stop iTunes from doing exactly what it is designed to do.
The iPhone is designed to sync with one and only one computer.
If you have moved/copied your iTunes library from your old computer to your new one, then iTunes wiping your device is no problem. You would simply sync and iTunes will put all the content back.

How to get the custom program generated in Background

Dear Freinds,
I have written a below code in my submit program ( zreport) .
REPORT ZHRRPCPRRU0_SUBMIT NO STANDARD PAGE HEADING MESSAGE-ID zhr_msg.
SUBMIT RPTQTA00 VIA SELECTION-SCREEN
WITH pnpbegda = sy-datum
WITH pnpendda = lv_date
with pnppernr = '99007057'.
As per your logic i have used the submit program and i am able to default the dates in the Standard program RPTQTA00 , that is perfectly correct . Now if run the standard report it is giivng me the ouput ..so the foreground concept is working correctly.
Now if iam scheduling the Z report of the custom report (z program) where iam calling the submit program
it is just scheduling and further when i look at the sm37 i can see the job getting finished . However , i dont find any spool because the standard report has not been executed , with my custom report (using the logic with submit program above in zprogram ) i am calling the standard program (RPTQTA00).
so could you please let me know how the standard program will execute and get the spool genereated? in the case of background
because when i have executed only the standard report in background i can see that it is being exceuted spool as well, however when iam calling from custom program no spool is created because my custom program only submiting the standard report and it is not executing the standard report in the case of backround ...because when iam running the custom program in the Foreground it is calling the standard program and getting the values defaulted based on the parameters which i passed , so it gets defaulted later iam running the standard program manually .
So please could you let me know how will the standard program also gets genereated in the backgroung along with my custom report.
Thanks in advance
regards
madhuri,

Hi Can you try the following?
Hope this helps... (Taken from help)
Example
Scheduling a submitable program as a background task with the number number in a background request name. After scheduling, the background task is completed by function module JOB_CLOSE and released immediately.
DATA: number TYPE tbtcjob-jobcount,
      name TYPE tbtcjob-jobname VALUE 'JOB_TEST',
      print_parameters TYPE pri_params.
CALL FUNCTION 'JOB_OPEN'
EXPORTING
    jobname          = name
IMPORTING
    jobcount         = number
EXCEPTIONS
    cant_create_job = 1
    invalid_job_data = 2
    jobname_missing = 3
    OTHERS           = 4.
IF sy-subrc = 0.
SUBMIT submitable TO SAP-SPOOL
                    SPOOL PARAMETERS print_parameters
                    WITHOUT SPOOL DYNPRO
                    VIA JOB name NUMBER number
                    AND RETURN.
IF sy-subrc = 0.
    CALL FUNCTION 'JOB_CLOSE'
      EXPORTING
        jobcount             = number
        jobname              = name
        strtimmed            = 'X'
      EXCEPTIONS
        cant_start_immediate = 1
        invalid_startdate    = 2
        jobname_missing      = 3
        job_close_failed     = 4
        job_nosteps          = 5
        job_notex            = 6
        lock_failed          = 7
        OTHERS               = 8.
    IF sy-subrc <> 0.
    ENDIF.
ENDIF.
ENDIF.

Urgent: How to modfy the Report program Corresponding to a Infoset

Hi Friends,
I have done an infoset. I have used TCURR table for Query. I saw the Standard program of that Query having select statement like Select single * from Tcurr where Gdatum = RDD.
Where RDD is the value having Statndard date where Gdatum is Converted Date format using some conversion routine ...So the select statement is failing in
the standard program AQ50MPL=========COS_EE========.
When i tried to add an conversion routine before the select statement to convert the date to that Specific statement...When i tried to go to Change mode i got an error message like
"Standard SAP Program Status is not modifiable" can i change the Standard program which is not asking for Access key for change..
PLease help me how to change the standard program or How to make a copy of standard program into a Z program and how to call that z program instead of that standard program..
Please help me..

hi Gokul,
It's not possible to edit the standard AQ programs that you create using Infosets rather these AQ programs are generated when you generate the Infoset and the Query.
Secondly there's a point to be taken care of when we work on Queries and Infosets. There are two areas of Queries and Infosets namely, Global Area and Client-specific area. At this point, it's better to rush up with the jargons as you're running out of time. All you need to do is follow the steps below:
1) Goto SQ02 *infoset* -> *give in your infoset name*change
2) Goto EXTRAS tab or Press F5.
3) Goto CODE tab
4)from the drop-down CODING SECTION *you can choose from the list wherein you need to place your code or change the existing code by traversing the list*
5) Generate the code.
6) Repeat steps 1-5 for Client-specific area as well *choose Environment ->Query Areas -> Client-specific* to change the code there.
7) Generate the corresponding Query(SQ01) in a similar fashion *Global Area and Client-specific area as mentioned in step 6*
Reward points if your requirement is met!!
Thanks,
Vaishnavi

How to change call to the function module in the standard program

Hi Guru,
My requairment is to create the new Z function module ZJ_1B_IM_NF_DOCUMENT_FUNCTION in the MM07MFJ1 program.
I have created the Z Funtion module,
plz provide me the info how to change the call to the new custom FM from the standard program.
Points will be given to the ans.

You use SE38 to change out the code. When you try and change it you will get a popup asking you for a Key, since you are changing SAP Code. If you have a Developers key you have to go to the SAP Service Marketplace and tell SAP that you are changing this code in order to get they key. After this every time you do support packs you run the risk of this getting overlaid and you will have to change it back, also if you have a problem and SAP sees that you customized this code they probably won't spend any time on your problem.

How to find the standard smartform,sap scripts and theur driver programs

Hi friends,
can any one tell me how to find the standard smartforms and their driver programs and same for scripts also.
bye
sasi

Hi sasidhar,
1. Either standard or Y sapscript layouts,
   we can check their standard programs
   in this manner also.
2. goto se71
   open the layout in DISPLAY mode.
3. FORM------> CHECK -
> TEXTS
4. a small window will come.
    click ok (tick button)
5. Again a new window will come
which will list out all the DRIVER programs,
which use this layout.
regards,
amit m.

How can i code in the "FORM USEREXIT_......" in the standard programs?

I see sap have many userexit subroutines in the standard programs?
Like Include 'MV50AFZ1'.
How can i customer my code in these subroutines?
It always message me Access key!
Thank you very much!~~

Hi,
To implement code in Form exits you have to get the Access key, Your Admin/Basis can help you get the access key. Other way around is to use the implicit enhancement option.
Regards
Karthik D

HT1386 Sry for disturbing, but i would to ask that how to overcome the problem of synchronising ? Itune showing me that the sync session is failed to start with my Ipad mini. Any ideas about what is going on ?

Sry for disturbing, but i would to ask that how to overcome the problem of synchronising ? Itune showing me that the sync session is failed to start with my Ipad mini. Any ideas about what is going on ?

What are you trying to sync?
I see you are on ios 7.
I also had upgraded my iPad Mini to ios 7 & then the 1st time I tried to open a Numbers file that was set up to sync w my MacBookPro, I got a warning that I would not be able to sync it any more w my Mac until I upgraded to Mavericks.
So if you are trying to sync Numbers, Pages or Keynote files between your iPad mini in ios 7 and a Mac that hasn't been upgraded to Mavericks that could be the problem.
I was very shocked to get that message since I bought Numbers on the iPad so that I could have a particular file on both devices & keep them synced. I had no clue when I upgraded to ios 7 on the iPad Mini that it would make it so the files in the iWorks apps woudln't sync any more.
So I finally decided to go ahead & upgrade to Mavericks after carefully preparing & updating other software so that it would work w Mavericks. But I got error messages so haven't even been able to download Mavericks & now having 2nd thoughts about doing so.
iPad mini ios 7
MacBookPro Mid 2012 Mountain Lion
iphone 4S ios 6

How do I rid the User Account Control - "Do you want the following program to make changes to this computer?" - FireFox Helper pop-up that shows after every log in?

The following pop-up is displayed after every log-in, even after it is clicked yes after previous log-ins. Several students log-in the computers daily. How do I rid THIS?:
User Account Control
"Do you want the following program to make changes to this computer?
Program Name: FireFox Helper
Verified Publisher: Mozilla Corporation
File Origin: Hard Drive on this Computer

In Windows 7, Microsoft updated UAC in several ways. By default, UAC does not prompt when certain programs included with Windows make changes requiring elevated permissions. Other programs still trigger a UAC prompt. The strictness of UAC can be changed to either always prompt, or to never do so.
[http://windows.microsoft.com/eN-US/windows-vista/What-is-User-Account-Control What is User Account Control?]
[http://windows.microsoft.com/en-US/windows-vista/Turn-User-Account-Control-on-or-off Turn User Account Control on or off]
It is the same on win7.
[http://en.wikipedia.org/wiki/User_Account_Control User Account Control]
thank you
Please mark "Solved" the answer that really solve the problem, to help others with a similar problem.

How to find the outbound program for standard IDoc

Hi Folks,
Can anyone tell me how to find the outbound program/tcode for a standard IDoc? For e.g. IDoc - MATMAS05 can be generated & distributed using tcode BD10. Similarly how do I find the outbound program/tcode for any standard IDoc? Is there any procedure to find the same.
I have tried to search based on the package name, but unfortunately I didn't find the information for IDoc: COND_A04.
Thanks in advance.
Somu

You can do following steps if the idoc is generated based on change pointer concept (for masters)
- Identify the message type associated with idoc type (table EDIMSG).
- Function module for generating the IDOC will be available in table TBDME (pass message type as input).
Refer to the standard Outbound IDOC generation program RBDMIDOC for more details.
If the idoc is generated based on the process code concept (transaction data), get the process code information from table TMSG1 (pass message type as input), get the function module associated process code from table TEDE1 (pass process code as input).
Regards, Vinod
P.S: There is no standard way to find out the associated program / Tcode for generating idoc. The above process will be helpful to find out the underlying function modules to generate the idoc. For generating idocs based on change pointers the generic program RBDMIDOC can be used.
Edited by: Vinod Kumar on Jul 13, 2011 2:15 PM

How to get the standard texts available in a smartforms

Hi Experts,
How can we find out the standard texts that are exist in a particular smartform . is there any table/function module available to get those standard texts? I am finding the table STXFTXT, from that I am getting only textline. But I need the standard text names that are used in a smartform.
Thanks & Regards,
Suresh

hi,
1,Use SO10 Tcode to write standard text in Smartform.
2.For long text
method1
Create TEXT node- general attributes change text type to include text
then you can input text name/text object/text id/language
method2
create PROGRAM LINE node - use FM READ_TEXT to read it to a internal table
then use LOOP or TABLE node to display it
For TEXT module(For foreign language)
Tr-code:smartforms -- choose Text module(not choose form)--create a text module object
then enter smartform Create TEXT node- general attributes change text type to text module
input the text module name which created by above
3.
1. take function module name of the smartform.
2. goto se37 and type that fm name.
3. goto attributes tab
4. double click on either program or include .
5. There u can find all the subroutines used inside smartform.
6. search for "perform %move using %textkey-name".
4.Standard Texts are created in SO10 Tcode and stored in STXH table with OBject ,ID and NAME parameters. We can use Read_Text FM to read the text.
check the tables STXH & STXL.
5.
How to CAll Standard Text in Smart Forms
In SFs you can insert the standard tests using the TEXT node. Create a TEXT NODE. Then in the GENERAL ATTRIBUTES of this TEXT node select INCLUDE TEXT in the TYPE option. Then you have to enter the text name, object , ID and language in the provided fields. Then if you dont want any error if there is no text in the corresponding text then CHECK the check box "No errors if no text available.

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 track the standard function code eg. PRI

Dear All,
I have a requirement that says that I will execute a report. Now when the user will click on the print button may be customized or can be taken from menu (Standard PRI) I want to update a table when the printout has been taken. I am not able to track down the print functionality through AT USER-COMMAND. Can anyone please help me out.
Thanks and regards,
Atanu

open the standard program in se80
check the standard menu items in GUI status.
check the function code there..
regards.
santhosh reddy

How to overcome the standard program check that changes my input file data?

Similar Messages

Maybe you are looking for