Update debugging

Hi,
When i active "update debugging" the new screen dont show me. And a short dump is show in transaction ST22.
DYNPRO_SEND_IN_BACKGROUND
Screen output without connection to user.
Error Analysis
During background processing, the system attempted to send a screen to a user.
Current screen: "SAPMSSY3 " 131.
Are there any configuration for that?
Can Anyone help me?
thanks a lot!
Alexandre

You tried to send screens or lists via an RFC link?
If yes
Check OSS note # 49730
There`re lot of OSS note talks about the "DYNPRO_SEND_IN_BACKGROUND"
Hope thisll give you idea!!
P.S award the points.
Good luck
Thanks
Saquib Khan
"Some are wise and some are otherwise"

Similar Messages

DYNPRO_SEND_IN_BACKGROUND dumps in Update debugging

Hi Experts,
I am getting DYNPRO_SEND_IN_BACKGROUND dumps when I apply update debugging for SAPMV45A (VA01). It should open another session in debug mode, instead it is getting a dumps. I got lot of notes on the dumps, but nothing is useful.
A little Info:
Information on where terminated
The termination occurred in the ABAP program "SAPLV45U" in
"RV_SALES_DOCUMENT_ADD".
The main program was "RSM13000 ".
The termination occurred in line 5 of the source code of the (Include)
program "LV45UV02"
of the source code of program "LV45UV02" (when calling the editor 50).
The program "SAPLV45U" was started in the update system.
Program "RSM13000" is used for opening session in Update debugging and for handline the task.
In this case commit work is not happening and update records are locked.
Thanks in advance.
--Sri.

hi
good
go through this bolg, i hope this ll help you to splve your problem.
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/weblogs/topic/24%3fx-o%3d100
thanks
mrutyun^

Need authoritative (SAP?) answer on BADI breakpoints in update debugging

I'm doing a very simple BADI implementation of:
IF_EX_INSPECTIONLOT_UPDATE~CREATE_IN_UPDATE
called from FM QPBU_LOT_INSERT in QPBU.
Everything is working fine, but here's the problem
QPBU_LOT_INSERT is being called from an update task inside MIGO (the update task for a goods receipt posting.)
When I was doing a customer exit in MIGO, I had to turn on an update debugging session to see a breakpoint in my exit code - the debugger would not go directly to the hard breakpoint in my exit code.
So I assume this is the same for implementations of BADI methods - the regular debugger will NOT go directly to a breakpoint inside the custom implementation of the interface method - you have to turn on update debugging and wait for your method code to appear.
Is this true or not?
If it is, then this seems to me something that would be easy to fix.
After all, if we can have external debugging in WDA, why can't the ABAP debugger be fixed to see a hard breakpoint even if the breakpoint is in customer code that is part of a BADI implememntation method ??????
Thanks for whatever authoritative answer anyone can provide.
djh

hi David,
As you said, normal debugging will not always be possible with BAdIs. i dont know about activating update debugging, but there is a way to go to debugger while the BAdI gets executed. Please follow the steps mentioned below:
step1: Goto sE19 and enter the BAPI implementation name->display
step2: choose the interface tab->double click on the method which
is under consideration
step3: code as below
data lv_flag.
while flag is initial.
endwhile.
step4: Now activate the BAdI and execute the transaction, and do the necessary actions(save/delete etc)
step5: goto transaction sm50->you can see your program there
step6: select your program from the list->choose PROGRAM/SESSION from the
menu->Select PROGRAM->DEBUGGING
you are now in the debugger with the BAdI.

This is an infinite loop inside the BAdI; You should take this out, and re-activate the BAdI, once you are done with the debugging
Hope this helps,
Sajan Joseph.

Difference between system debugging and update debugging

hai guru's can any one tell the difference between system debugging and update debugging
thanx in advance
afzal

hi,
System Debugging
If you set this option, the Debugger is also activated for system programs
(programs with status S in their program attributes). When you save breakpoints, the System Debugging setting is also saved.
Update Debugging
Update function modules do not run in the same user session as the program that is currently running in the ABAP Debugger.
These function modules are therefore not included in debugging.
Only if you select the Update Debugging option can you display and debug them after the COMMIT WORK.
For debugging tutorial:
http://help.sap.com/saphelp_erp2005vp/helpdata/en/5a/4ed93f130f9215e10000000a155106/frameset.htm
http://www.sapdevelopment.co.uk/tips/debug/debughome.htm
http://www.sap-basis-abap.com/sapab002.htm
Reward points
Regards

FM in update task - How do you debug for a user exit (IW32)

Hi,
I am working on user exit IWO10009, fm EXIT_SAPLCOIH_009, transaction IW32.
The user-exit should be called any time an order is saved with parts added to the component tab.
The import structure of the user exit is CAUFVD, which doesnu2019t contain the items in the component. Instead, I have to go into table RESB and get the components.
However, when I go into RESB from inside the user-exit, the added components have not yet been added to the table.
As such, I was thinking of creating a Z function module in update task to process this code after the order is saved & RESB is updated.
2 questions
1 u2013 Is this the best way of accomplishing this?
2 u2013 How do you debug FMu2019s in update task? I have set a breakpoint & have switched system debugging on from inside the debugger, but it doesnu2019t stop inside the fm.
Please help.
Thanks,
John

Hi,
to debug update task you need to switch on "update debugging" not the "system debugging" from the menu Settings->update debugging.
-Ramesh

Debugging a function in UPDATE TASK

Hi All,
I'm debugging a function in UPDATE TASK. I have just actived the flag 'Update Debug'.
My problem is Find how the Function's parameters are passed. The function is called dynamically by a statement like this:
" PERFORM (VBFUNC) IN PROGRAM (TFDIR-PNAME) USING VBID. "
Does someone help me?
Thanks

Hi,
Your question is not clear to me.
wht I understood that you want to get the parameters passing to a function module which is dynamically called.
" PERFORM (VBFUNC) IN PROGRAM (TFDIR-PNAME) USING VBID. "
this statement is not calling any FM it is calling a subroutin which exist in TFDIR-PNAME program variable after USING stat is your parameter.
You can get the name of the form, program and the parameters if you debug at this point.
Thanks,
Anmol.

How to debug the update FM

Hi,
I am facing a problem with the debugging of the update FM. I have enabled the update debugging and the system says that update debuging is on . even though the control did not go into the FM.
Do i need to check in any other transaction . Please give me the details steps on how to see the what is happening in the update FM.
Full marks are guaranteed.
thanks
sankar

Hi
I have got a clue from SAP help on how to debug the update FM see the below information from SAP
When you debug a program that calls function modules using the IN BACKGROUND TASK addition, they are processed in a background work process (additional internal session). If you set the In background task: Do not process option, the system collects the function calls, but does not start the background work process. The Debugger assigns a transaction ID, which identifies the background work process uniquely. You can now start the Debugger for the background work process using transaction SM58. You can select the function module concerned here, and then execute it via the Edit menu.
I have done everything that is said above , but could not find any entries in SM58
any suggestions
thanks
sankar

Debugging - in update task

Hi,
in one of the exits of transaction VA02 (change sales order) during saving, i have a call of a Z-function module in update task.
When i have reached the call of this function during debugging, i'm setting the update debugging on. After saving, the system says 'Update debugging has been triggered', but i'm not getting a debugging session of the Z-function module.
How can i debug the z-function ?
regards,
Hans

Hi hans,
1) Update function modules do not run in the same user session as the program that is currently running in the ABAP Debugger. These function modules are therefore not included in debugging. Only if you select the Update Debugging option can you display and debug them after the COMMIT WORK.
Update function modules do not run in the same user session as the program that is currently running in the ABAP Debugger. These function modules are therefore not included in debugging. Only if you select the Update Debugging option can you display and debug them after the COMMIT WORK.
2) 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.
Thanks
Sudheer

Unable to debug an exit in CALL CUSTOMER FUNCTION 003

Hi Guys,
I have an exit EXIT_SAPMV45A_003 that is called by CALL CUSTOMER FUNCTION 003. I had placed a break point at
CALL CUSTOMER FUNCTION 003 and the debugger stops here but i am unable to debug inside this to reach into
the code in EXIT_SAPMV45A_003 even after setting the system debugging on & Update debugging
ON.
Can someone help me with this?
thanks
Dan

You have to include that Enhancement of that exit in the Project and Activate that project in the CMOD.
The Enhancement for the exit EXIT_SAPMV45A_003 is V45A0003.
Create a project in CMOD
And inclue V45A0003 in the project.
Activate the Project.
Now, it will stop at break point.
Regards,
Naimesh Patel

Middleware debug problem for BP's from CRM to ECC

I tried few steps to debug BP changes from CRM to ECC but nothing is working ...
I deregistered the Queue thru SMQS, made changes to BP.. went SMQ1 select the Queue name Double Click 2 times.. then select the Tool bar (Debug LUW).. I'm getting "Nothing was selected"
When is see SMW01, BDOC is processed green and data is transferred to ECC.
I want to do debug the BP queue and go to ECC system as some of my custom EEWB fields are not passing to ECC correctly.
Any help is highly appreciated.
Thank you.

Hi,
Put a break point in FM SMW3_MFLOW_UPDATETASKBDOC.
Create a BP and before save type /h to activate debug, mark update debugging option.
When stops in FM SMW3_MFLOW_UPDATETASKBDOC you must be sure to set header-dbgmode = 'X' this will make the bdoc stay stopped in SMW01.
Go to SMW01 and type /h and process the bdoc.
Put a break in FM CRM_UPLOAD_AFTER_MAP_HANDLER and be sure to change LV_SYNCHRON = 'X' this will allow you to connect in ECC.
Put a break-point in the "CALL TRANSACTION" command. Change the mode of call transaction and you be able to debug XD* update.
Best Regards,
Caíque Escaler

Update was terminated SAPSQL_ARRAY_INSERT_DUPREC

Hi,
We are trying to make our custom calculations in VA01, VA02 and because of this we need to update VBUP table. We updated the fields of xvbup and yvbup, but we receive an error "Update was terminated SAPSQL_ARRAY_INSERT_DUPREC".How

Hi,
Check in SM13.
The update termination will be shown. Put a break point at that step and in update debugging check the entries which are being populated in your internal tables.
The issue might be that there is already and entry in the database table and someone is passign value in XVBUP with update indicator as 'I'
If XVBUP is correct then check if someone has wrongly modified YVBUP.
We had faced a similar problem and in that case the culprit was wrong entries in YVBAP internal table.
Regards,
Ankur Parab

Relating debugging of program.

hi experts.
i want to learn
how to do debug of program.
how to use break point.
how to use watch.
how to debug selection-screen and module pool programming.
please help it is very urgent.
give some link also.

HI
    Debugger
The Debugger is a programming tool that you can use to execute ABAP programs, by line or by section. With this tool, you can display data objects and check the flow logic of programs.
Two types of debugging are currently possible: Debugging with the classic Debugger for release levels up to and including 6.40 or debugging with the new Debugger, which is available for all releases after 6.40. The main differences between the classic and the new ABAP Debuggers are described below:
·         The Classic ABAP Debugger runs in the same roll area as the application to be analyzed (debuggee). It is therefore displayed in the same window as the application. However, this technology also has some restrictions. For example, some ABAP programs (such as conversion exist) cannot be analyzed in debug mode for technical reasons. However, the most significant restriction is that no ABAP technology can be used for designing the Debugger interface and it is therefore not possible to create a modern user interface.
The New ABAP Debugger, on the other hand, is executed in a separate external session (Debugger), while the application to be analyzed (debuggee) uses a second external session. With this technology, the user interface of the Debugger can be designed freely by ABAP means.
The new Debugger provides the user with a flexible interface that can be configured as required and has more than eight desktops. Here it is possible to place and arrange up to four tools - depending on the user's selection. For example, it is possible to display source texts or structures. In this way, the user can design the Debugger interface according to his own individual requirements.
As of Release 6.40, you can select the debugging type as you wish by choosing the classic Debugger or the new Debugger in the ABAP Editor from the path Utilities ® Settings. It is also possible to switch the Debugger at any time during a session under the menu option Debugging.
As of Release 7.00, the new ABAP Debugger is the default.
Breakpoints
Apart from being able to execute an ABAP program in the Debugger, you can also start the Debugger call by the choosing 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 Debugger is activated when the program reaches this point.
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 more information, refer to the chapter Watchpoints.
Breakpoint Variants
The Debugger contains different breakpoint variants:
Static
A user-specific breakpoint is inserted in the source code as an ABAP statement using the keyword BREAK-POINT. A non user-specific breakpoint is set in the ABAP Editor using the BREAK user name statement.
Directly set
dynamic breakpoints
Can be set in the ABAP Editor or the Debugger by double-clicking a line, for example. Dynamic breakpoints are always user-specific, and are deleted when you log off from the R/3 System.
Breakpoints
at statements
The Debugger stops the program immediately before the specified statement is executed.
Breakpoints
at subroutines
The Debugger stops the program immediately before the specified subroutine is called.
Breakpoints at function modules
The Debugger stops the program immediately before the specified function module is called.
Breakpoints at methods
The Debugger stops the program immediately before the specified method is called.
Breakpoints at exceptions and system exceptions
The Debugger stops the program immediately after a system exception, that is, after a runtime error has been intercepted.
Static Breakpoints
Static breakpoints are always user-independent if there is no specification of a user name. 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 program execution is always to be interrupted at the same place. For more information, refer to the chapter 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 more information, refer to the chapter 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 remain in effect during the entire user session if they are saved by choosing the menu path Breakpoints ® Save in the ABAP Debugger. For more details on the subject of user sessions and modes, 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.
For further information on special breakpoints, refer to:
Breakpoints at Statements
Breakpoints at Subroutines
Breakpoints at Function Module Calls
Breakpoints at Methods
Breakpoints at System Exceptions
    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 under which a watchpoint is to become active.
·        You can specify a logical link for up to five (conditional) watchpoints.
See also Specifying Logical Links.
·        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
REWARD IF HELPFUL
vivekanand

OUTBOUND IDOC DEBUGGING

I have Output type defined for the application V3
i.e meant for Billing.and the output type is custom development with name ZD00 for invoice-Bill to.
This output type is defined for edi processing.
Now the problem is when invoice is created and this
outputtype is selected the quantity field in idoc and invoice differs.just get double in idoc.but if the same output is fired again data in idoc gets corrected.now i want to debug the idoc outbound processing.what i did i run the transaction we41 and find the process code and find the function module that is running in the background for collection of data of invoice and
filling the idoc.but but but the problem is i put break point in the function module to check the value at run time but this is not triggered . iam confused tell me how to debug the outbound idoc.
Help me out i will be waiting for the response.

Hi,
You can use the Update Debugging. If you know the prognam name/function module of your source code, upon saving your document, a new screen will pop up if the Update Debugging mode is on. From this, you can then hit F8 to stop on your break-point.
Let me know if you need further help.
Thanks,
Eric

Debugging field-exit with the new debugger

Hi everyone,
I could debug a field-exit with the new debugger, but I cannot do it anymore. I chose the options "system debug" and "update debug" in the configuration menu that time but it's not working now.
Before you answer "FIELD-EXIT CANNOT BE DEBUG!", take a look first at the The New ABAP Debugger 7.00 Presentation where it mentions that's possible.
And also I saw a post: Re: activation of field exit for particular sereen
where Ramesh Kashigari said that it's possible too.
Anyone knows How can I configurate the new debbuger for this?

Hi Florian,
I agree that it should now be possible. I saw this on a SAP Java Development Day at the start of '04 when NetWeaver 04 was launched.
I saw it being used in the NetWeaver Development Studio.
It seemed very clever indeed. You could debug the Java code then jump to the ABAP debugger when the BAPI is called then jump back into the Java code when the BAPI call is completed. It seemed to work very well and did not have any issues.
Hope this helps.
Kind regards
Colin.:)

Update debugger is not working

Hi All,
My problem is "Update debugger is not working" is not working.
In VA02, I am creating a EDI output type, before saving it i am going into debug mode activating the 'Update Debugger'.
But after that a message is coming as 'Update debugging has been triggered' but debugger screen is not coming up.
Please let me if you have inputs on this.
Thanks
Satyamkumar Jha

>
Satyamkumar Jha wrote:
> Hi Saravraj ,
>
> Even if 1 session is opened then also it is not going for update debugging.
>
> Thanks
> Satyam
Did you check if a COMMIT statement is getting triggered(you can do that by placing a break point in the debugger at the statement COMMIT)? Click on F5 once the control reaches COMMIT statment and wait for a new session to
get opened for debugging.
Not sure, about the debugger that you are using(classical/New), lately, I have faced issues with update debugging while using new debugger, it would be a good idea to cross-check in classical debugger.
-Rajesh.

Update debugging

Similar Messages

Maybe you are looking for