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^

Similar Messages

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"

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

DYNPRO_SEND_IN_BACKGROUND Dump due to Update Control Screen

Hi All,
I have a smartform which is being attached to a SO while creating from Idoc. Due to this smartform processing in update task, it is giving a update control screen and it is giving dump DYNPRO_SEND_IN_BACKGROUND.
My question: how to suppress this "Update Control" screen ? is there anything can be controlled from user status profile ?
Thanks,

What is the type of user?
Can you try with Dialog user or System user?

Short dump in update rules

I removed from my comm structure some objects that I didn't need there.
Some of them are not connected in the datasource to any field, they just get filled in the update rules by routines. Others just weren´t used anymore and already out of the cube. Since that when I extract the info to the cube, the requisition freezes in the end of update rules waiting for final response.
I re-activated the comm structure, the datasources, the cube, but the update rules gives me a short dump:
Message type x
Msg classe RSAU
N.º 001
Var 1 " "
Var 4 " "
The termination occurred in the ABAP program "%_T0ITS2" in "INSTANTIATE".
the main program was "SAPMRSAU"
The termination occured in line 0 of the source code of the (Include)
program " "
of the source code of program " " (when calling the editor 00).
Did this happen to someone?! Or knows what could bwe the problem?!
Thank you
Joã

Thank you for forcing me to go there once again.
I was looking at my routines, and forgot to check the formulas.
Had a calculated key figure with one of that objects. By correcting this I also correct other error. 2 in 1 :-D
Thankx

Shot Dump while updating record in ETTIFN using the FM ISU_DB_ETTIFN_UPDATE

Hi All,
Am getting shot dump while trying to update an entry in ETTIFN database table using the FM ISU_DB_ETTIFN_UPDATE.
If this FM fails to update then it tries to raise error message using the macro
MAC_MSG_PUTX CO_MSG_PROGRAMMING_ERROR '016' 'E9'
       'ETTIFN' SPACE SPACE SPACE
       SPACE .
Runtime Errors         MESSAGE_TYPE_X
Error analysis
    Short text of error message:
    Error in changing table ETTIFN
    Long text of error message:
     Diagnosis
         An error occurred when one or more table entries were being
         changed. This error was reported by the database system.
     System Response
         The system does not permit changes to one or more table entries.
         It is possible that an SAP short dump has been written from the SAP
         basis system.
     Procedure
         Find out if the SAP short dump provides additional information.
         You can view SAP short dumps using Transaction SM21.
    Technical information about the message:
    Message class....... "E9"
    Number.............. 016
    Variable 1.......... "ETTIFN"
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
Please advice inorder to fix the same.
Regards,
Deepthi

Hi Deepthi,
Updating database using statement update can give dumps because of below issues:
"At least one line was not able to be changed, either because no appropriate line was found, or because the change would generate a line that leads to double entries in the primary key or a unique secondary index in the database table."
I would rather suggest you to call the FM in Mode 'M', i.e. Modify so if entry in table is not there to update, it will insert that record and also won't give dump.
Thanks.
Ravi

DYNPRO_SEND_IN_BACKGROUND dump while processing delivery

Hello,
We have placed a BDC logic to create Invoice in MV50AFZ1 user exit of delivery. BDC session method is being used to create session for Invoice creation using transaction VF01. This isession is later executed in background job using program RSBDCSUB.
Although delivery gets processed successfully and Invoice also gets created, but we are getting a dump in ST22 with and error DYNPRO_SEND_IN_BACKGROUND. We are also getting an error in SM58 "Screen output without connection to User".
Can somene please help how this error can be removed.
Thanks & Regards,
Rohit

Hi,
This BDC logic has been placed in the Fuction Module. This Function Module is called as saperate unit in background task through MV50AFZ1. In this Function Module, VF01 batch session is created.
These batch sessions are later executed by a background job program RSBDCSUB. This batch job runs every 5 minutes.
Kind Regards,

DYNPRO_SEND_IN_BACKGROUND dump workflow

Hello,
I have made a upgrade to ECC6 and when i try to run workflow and it stay stuck on a task and gives the follow dump:
Runtime Errors         DYNPRO_SEND_IN_BACKGROUND
Short text
    Screen output without connection to user.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPMSSY0" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    During background processing, the system attempted to send a
    screen to a user.
    Current screen: "SAPMSSY0 " 0120.
I already check the logical connections in SM59 and i have rfc destination WORKFLOW_LOCAL_010 with user logon WF-BATCH, i run also SWU3 transaction to configure workflow.
Anyone could help me.
Best Regards,
Eduardo Paiva

Hi,
In SWEL find out for which step this Error is being raised. Most probably this step or activity is set as a background process, so get into the task and uncheck the 'Background processing' under section Execution.
Regards
Anik
Edited by: ANIK SIRCAR on Sep 21, 2011 1:09 PM

DYNPRO_SEND_IN_BACKGROUND dump when workflow executes a background task

Hi,
My project is currently in version 4.6. I have a custom version of the PO release workflow and in here I created an activity calling a Custom Task, which then calls a Custom Business Object Method and then calls a program (using Submit RSWUWFML2). Unfortunately everytime the workflow goes to the said activity it hits a dump -- DYNPRO_SEND_IN_BACKGROUND.
I've tried unchecking the flag "Advance with Dialog" inside the task but it didn't work. I know RSWUWFML2 most of the time should be scheduled in background but it just so happens that we have a certain scenario in which it should have a different body and subject. This is the reason why I opted to call it inside the workflow.
Do you have any idea what caused this? Thanks!

Hello Dan,
DYNPRO_SEND_IN_BACKGROUND is an exception which occurs when system tries to call screen in background. Calling screen in background is not possible.
Report RSWUWFML2 creates LIST at the end of this report which is nothing but a special type of screen. If you run this report as background task, definitely above exception will occur.
Schedule this report as job instead of using it in task.
Regards,
Sagar

Short dump for update function module

Hi Folks,
   If I try to raise exception in Update Task function module which is in turn called in Custom BAPI function module. When I test the BAPI stand-alone using explicit COMMIT WORK (For testing)I can see the error in SM13 and it processes further in BAPI. Now when I am using this BAPI for ALE Inbound processing function module to SAP, when I test using testing tool WE19 it crashes when it passes the update FM inside BAPI, and encounteres BAPI_TRANSACTION_COMMIT, the update Function module is executed as encountered and gives me dump at the raised exception and does not show error in SM13. Please suggest how I could overcome this dump.
Regards,
Tim

Hi there,
Yes. I know that I can details from ST22 Analysis. And I did go through that.
Here's the Section that explains:
How to correct the error
    Try to find out why the number of decimal places of the field should be
    2.
    There are various possible options:
    1. The number of decimal places of the imported field has changed in the
       Data Dictionary. Make sure that the number of decimal places of the
       imported field matches the number of decimal places of the field in
       the Data Dictionary.
       If the data cannot be restored from another source, the data of the
       'old' structure must be read by the 'old' structure, converted und
       again eported with the new structure, so that future IMPORTs will
       always function with the new structure.
    2. A new program version is active, which no longer fits the dataset.
       Try to solve the error generating the program
     "ZFI_FM_GET_STD_COSTS==========FT" again. This
       works as follows: Select transaction SE38 in the SAP system. Enter
       the program name "Z_GET_COSTS==========FT". Then activate the
     function 'Generate'.
1. I made sure that the decimal places matches.
2. I did re-generate the program.
But still got the same dump. Interestingly, the program where I am using this FM is working absolutely fine.
Thanks.

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

DYNPRO_SEND_IN_BACKGROUND dumps in Update debugging

Similar Messages

Maybe you are looking for