Dump when run in background

Hi All,
I have a z-report which displays a ALV report. when I run this in background it gets canceled. when i see the log , it has dump and dump is as shown below.
A RAISE statement in the program "CL_GUI_CONTROL================CP" raised the exception condition "CNTL_ERROR".
Since the exception was not intercepted by a superior
program, processing was terminated.
What could be the problem, suggest me a solution if i have to add some code into my program or is it an application error which can be solved by SAP Notes.
Regards
Divakar Goud,

Are you using GUI_UPLOAD or GUI_DOWNLOAD in the report then they will not work there.
Use OPEN DATASET instead to read or write.
Also, check weather there is a Container for OO ALV on the Report then use Docking Containe when SY_BATCH = 'X'.
If its an normal ALV then Change the GRID to LIST layout for Backgroud. Its not that we cannot display grid in background we can do that but we require some layout handling there.
ALV Grid in background job?
Regards,
Amit
Reward all helpful replies.

Similar Messages

Program giving dump when run in background

Hi All,
I have an ALV report in which I am using REUSE_ALV_GRID_DISPLAY.
The report works perfectly in foreground. But when I execute in background I am getting dump.
Dump details are given below.
ShrtText
    Unable to fulfil request for 134217728 bytes of memory space.
What happened?
    Each transaction requires some main memory space to process
    application data. If the operating system cannot provide any more
    space, the transaction is terminated.
What can you do?
    Try to find out (e.g. by targetted data selection) whether the
    transaction will run with less main memory.
    If there is a temporary bottleneck, execute the transaction again
    If the error persists, ask your system administrator to check the
    following profile parameters:
    o ztta/roll_area            (1.000.000 - 15.000.000)
           Classic roll area per user and internal mode
           usual amount of roll area per user and internal mode
    o ztta/roll_extension       (10.000.000 - 500.000.000)
           Amount of memory per user in extended memory (EM)
    o abap/heap_area_total      (100.000.000 - 1.500.000.000)
           Amount of memory (malloc) for all users of an application
           server. If several background processes are running on
           one server, temporary bottlenecks may occur.
           Of course, the amount of memory (in bytes) must also be
           available on the machine (main memory or file system swap).
           Caution:
           The operating system must be set up so that there is also
           enough memory for each process. Usually, the maximum address
           space is too small.
           Ask your hardware manufacturer or your competence center
           about this.
           In this case, consult your hardware vendor
    abap/heap_area_dia:        (10.000.000 - 1.000.000.000)
           Restriction of memory allocated to the heap with malloc
           for each dialog process.
    Parameters for background processes:
    abap/heap_area_nondia:        (10.000.000 - 1.000.000.000)
           Restriction of memory allocated to the heap with malloc
           for each background process.
    Other memory-relevant parameters are:
    em/initial_size_MB:         (35-1200)
           Extended memory area from which all users of an
           application server can satisfy their memory requirement.
    Make a note of the actions and input which caused the error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
Error analysis
    More main memory area was requested.
    However, all the available space has been used up.
    Possible reasons:
    - Many (large) internal tables.
    - Many (large) programs active.
    - Deep nesting of subroutines with a lot of local data.
Can you please help on this ?

Hi,
Check you code properly.
The dump is because of an infinite loop which is running when you run the program in background and it is keeping appending or inserting the same table.
Check teh same.
regards,
Ankur Parab

Report program when run in background job getting cancelled immediately

Hi
When i run a program in foreground i am able to see the output. But when run in background not able to run the job successfully. The job is getting cancelled immediately.
I am using the below function module for output display. Should i need to pass any parameters in the below function module so that i can run the program in background successfully.
CALL METHOD DETAIL_GRID->SET_TABLE_FOR_FIRST_DISPLAY
      EXPORTING
        IS_LAYOUT         = IS_LAYOUT
        I_SAVE            = 'A'
        IS_VARIANT        = GS_VARIANT
      CHANGING
        IT_FIELDCATALOG   = IT_FIELDCATALOG
        IT_OUTTAB         = BLOCKED_STOCK_TAB_ALV[].
Please suggest.
Thanks and regards
Rajani Yeluri

Hi Rajani.
ALV require the DRYPOR(screen) for display but incase you run in back ground which have to write to spool but in spool we can only write in format of LIST REPORT not inter-active report like ALV. That why
system cancelled your process immediately.
Hope it helps.
Sayan.

RMMR1MRS-When run in background cause update failure errors looking

hi,
RMMR1MRS report when run in background cause update failure errors .
There are few below reason for the error log.
1. for the PO invoice already generated - (its right if already invoice generated. should not happen again)
2. In MIGO, entire quantity has been reversed and also invoice generated with zero value - ( its right , should not happen invoice again )
3. Particular PO line item deleted - (its right if the PO line item deleted. ERS settlement not require)
For the all above reason, the update error occurs. But the mean time the program "RMMR1MRS" should not through the update error log.
Note: The job was not terminated due to this update error and also no harm because of the error log
can you please help on this update failure why it occurs.

Have you found a solution already? If so, please, share it with the community and close this thread.

The number of rows per page is greyed out when running in background?

Hi,
For a customized transaction the number of rows per page cannot be set when running in background.
While a background job is created in SM36 after entering the report name and the selection variant name in the properties of Format the rows and columns field is greyed out.It was not editable.
Is there any settings to be done or in the custom program any code change needs to be done?
Thanks in advance.
Regards,
Sharon.

Hi Gabriel,
After double clicking the format only the rows field is not set to edit.It was greyed out.Is it anything related to the printer settings that will be maintained for a user?
Regards,
Sharon.

Error in BIM when running in background mode

Hi,
I am facing an error when running a BIM in sm35.
The BIM runs fine with my userid in all three modes( foreground,display error mode, background mode)....but fails when the functional person is testing in background mode. The BIM runs fine in all other modes.
It gives the message when running in background mode
"No batch input data for screen SAPLMGMW 4008"
What should I check or do to correct it.
Please help.
Regards
Rashi

The BIM runs fine in Foreground mode and in Display error mode even for the functional..It is giving error only for Background mode.
I also did the following
1. Created the BIM in my id and tried running( in background) it using the other id ...it was successful
2. Created the BIM in other id and ran ( in background) using my id....it failed.
I will check again for authorisations also.
Regards,
Rashi

GUI_GET_DESKTOP_INFO is not worked when run in background

Dear all,
I want to retrieve the computer name using this function module. It is working fine in foreground but it returns no result when I run in background. Is there any other method to get the computer name in background? Thanks in advance.

Problem solved using the following method:
DATA: BEGIN OF usr_tabl OCCURS 10.
          INCLUDE STRUCTURE uinfo.
DATA: END OF usr_tabl.
DATA th_opcode(1)                    TYPE x.
data: size type i.
CONSTANTS: opcode_list LIKE th_opcode VALUE 2.
CALL 'ThUsrInfo' ID 'OPCODE' FIELD opcode_list
    ID 'TAB' FIELD usr_tabl-sys.
describe table usr_tabl lines size.
read table usr_tabl index size.
write usr_tabl-term.
while usr_tabl-term is the computer name. It works in background as well.
Edited by: Chiew Ngee Ho on Mar 12, 2009 9:36 AM

System is showing time out when run in background

Dear all,
We have two systems: One R/3 and EBP. We have made one report where the remote function module will be called from R/3 to EBP. There are 4 lakhs data in SAP. We are sending 10000 data as package in internal table and getting the corresponding output. But the system is showing time out when the report has run in background. Can you please suggest how the process can be improved so that the timeout can be avoided.
Thanks and regards,
Atanu

Hi,
Try to fetch records in smaller chunks and process them. For example, if you are trying to fetch records for one year, instead of single query, try to fetch in 12 sets for each month. Fetch first month and process the records and put them in the output internal table. Then go for next month and so on. Anyway your program is running in background. There will not be any user complaint also. The solution might sound bit funny. But it works.
Regards,
Hema

Amount field getting rounded up when run in background

Hello All,
when i run a report in foreground the amount value(KBETR) is displaying properly with the value 12.78.But when the same report is run in background it is displaying 13.what should be done?
Thanks,
Rakesh.

Hi,
Try to fetch records in smaller chunks and process them. For example, if you are trying to fetch records for one year, instead of single query, try to fetch in 12 sets for each month. Fetch first month and process the records and put them in the output internal table. Then go for next month and so on. Anyway your program is running in background. There will not be any user complaint also. The solution might sound bit funny. But it works.
Regards,
Hema

ABAP dump when running an ALV report in a portal

Hi,
I have an ABAP report created in SAP R/3 4.7. Am using the ALV function module REUSE_ALV_GRID_DISPLAY to display the output. The programs runs correctly when run in R/3 using the SAP GUI.
When the report is run in the portal, I get a runtime error 'MESSAGE_TYPE_X'.
Please let me know if anybody has faced such issues.
I checked the OSS note 702732 which talks about increasing the threshold value of the start parameter. But this is not agreed by the BASIS team.
Thanks,
Best regards,
Ajith
The ST22 error log is as follows:
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
Short text of error message:
Data volume (84.550.400 bytes) is too large. (abap/alvgrid/size_nodod_mb
Technical information about the message:
Diagnosis
     You tried to send a data record to the front-end that contains
     84.550.400 bytes. However, the data volume is restricted to
     52.428.800 bytes.
System Response
     The running application program was terminated with a runtime
     error.
Procedure
     Restrict the data selection if possible or contact your system
     administrator.
Procedure for System Administration
     You can set the maximum size of these data volumes using the kernel
     parameter 'abap/alvgrid/size_nodod_mb' (in megabytes).
Message classe...... "S>"
Number.............. 890
Variable 1.......... "84.550.400"
Variable 2.......... "52.428.800"
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"MESSAGE_TYPE_X" C
"SAPLAWRT" or "LAWRTU22"
"ITS_CHECK_ALV_DATA_SIZE"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
   To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
   To obtain this, call the system log with Transaction SM21
   and select the "Print" function to print out the relevant
   part.
3. If the programs are your own programs or modified SAP programs,
   supply the source code.
   To do this, you can either use the "PRINT" command in the editor or
   print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
   or which actions and input led to the error.
Information on where terminated
The termination occurred in the ABAP program "SAPLAWRT" in
"ITS_CHECK_ALV_DATA_SIZE".
The main program was "Z_BW_RECON_INV_RPT ".
The termination occurred in line 25 of the source code of the (Include)
program "LAWRTU22"
of the source code of program "LAWRTU22" (when calling the editor 250).
Source code extract
000010   FUNCTION ITS_CHECK_ALV_DATA_SIZE.
000020   *"
000030   ""Lokale Schnittstelle:
000040   *" IMPORTING
000050   *"     REFERENCE(DATA_TABLE) TYPE TABLE
000060   *"
000070
000080     data n type i.
000090     data currsize type i.
000100     statics maxsize type i.
000110     data par_value(56).
000120     if maxsize is initial.
000130       sy-subrc = 0.
000140       CALL 'C_SAPGPARAM' ID 'NAME' FIELD 'abap/alvgrid/size_nodod_MB'
000150                           id 'VALUE' field par_value.
000160       if sy-subrc ne 0.
000170         maxsize = 52428800.       " Default 50 MB
000180       else.
000190         maxsize = 1048576 * par_value.
000200       endif.
000210     endif.
000220     describe table data_table lines n.
000230     currsize = sy-tfill * sy-tleng.
000240     if currsize gt maxsize.
     >       message x890(s>) with currsize maxsize.
000260     endif.
000270   ENDFUNCTION.

HI,
This is a Memory problem.
System is allocated with a Max Memory of 50 MB,(see the dump code, in the last it is hardcoded in the std code)
The data of your report is coming around 83 MB.
Restrict your selection criteria of the Object and run the same report and see. it will work.
Regards,
Anji

Reading hierarchies when running in background.

Currently we have an abap that captures the hierarchy information via the function K_HIERARCHY_TABLES_READ. We then use the results to collect additional data. The report works in the foreground but gets different results when running in the background. We traced the issue back to the function read. We checked with SAP and SAP's response is that the function K_HIERARCHY_TABLES_READ cannot be used in the background. Does anyone run any reports in the background which reads hierarchies? If so, how do you do it?
thanks,
Larry

Paul,
Starting new task will start a new LUW in dialog process and not in background. This is the reason you are having a problem. While technically STARTING NEW TASK is used for parallel processing, you need to consider whether the program will be run in foreground or background mode.
In case of background, you need consider using multiple jobs via job open, submit, job close. This way you can initiate more than one process in your server group to do the work.
You will need to consider the # of background WP available and the # of WPs you can use for this program.
So if there are 100 WPs available and you can use only 10 at any give time, then you should schedule 10 jobs and then check the status of the 10 jobs before you can start scheduling the next jobs.
You can use the FM SPBT_INITIALIZE to check the # of WPs that are currently available in the server group.
Hope this helps.
Thanks,
Vikram.M

Error when running in background

Hi,
When i run the pgm in foreground its working fine but if i run in background the job is getting cancelled with the error message "Code page couldnt be determined".I checked in background the value in the o/p is coming but the job is getting cancelled.What is the reason for it?

Hi,
In your program are you using any cl_gui_frontend_services methods. That means
any cl_gui_frontend_services=>gui_download
cl_gui_frontend_services=>gui_upload
If you are using frontend services background job. The job will not work
Hope it will helps

Core dump when running the Proc Application

I have client that has decided to upgrade from Oracle 10g to Oracle11g version. Presently the client code is compiled with Oracle version 11.1.0.7. We have tuxedo version as 9.0 patch02. When running the ProC application, I am getting the core dump. The stack trace for dump is as follows :-
core 'core' of 7784: bp_Customer -C dom=KenanFX -g 5 -i 225 -u dsesun10 -U /users/denver/pc
ffffffff6e8d9bbc kill (2, ffffffff7ffe002c, 1, ffffffff7de3b9a0, ffffffff7ffe0028, ffffffff7e10b5a0) + 8
ffffffff7d27b1f4 skgesigCrash (ffffffff7ffe09a8, ffffffff7e10a070, 1a0c00, ffffffff7dfdbc40, d60a7c, 1) + 34
ffffffff7d27b81c skgesig_sigactionHandler (ffffffff7d6fb9a0, ffffffff7ffe1800, ffffffff7ffe0990, ffffffff7e10b578, ffffffff7ffe0998, ffffffff7ffe09a8) + dc
ffffffff6e8d62e0 __sighndlr (b, ffffffff7ffe1800, ffffffff7ffe1520, ffffffff7d27b740, 0, a) + c
ffffffff6e8c9e44 call_user_handler (ffffffff75f00200, ffffffff75f00200, ffffffff7ffe1520, 8, 0, 0) + 3e0
ffffffff6e8ca03c sigacthandler (0, ffffffff7ffe1800, ffffffff7ffe1520, ffffffff75f00200, 0, ffffffff6ea3c000) + 54
--- called from signal handler with signal 0 (SIGEXIT) ---
ffffffff7c24bb24 sqlrlc (ffffffff7e0f9fc0, 0, 60, c0, 4, 8) + 4
ffffffff7c253594 sqlbrl (ffffffff7e0f9fc0, 1004bc630, 1004bc658, 1004bc5d0, ffffffff7ffe1b30, 2) + 114
ffffffff7c2745ec sqlhvdsc (1004bc5c0, ffffffff7e0f9fc0, 8, ffffffff7fff27a0, 0, 1d676b0) + ac
ffffffff7c274e68 sqlshv (c, 0, e, 0, f, 1c) + 128
ffffffff7c25bd8c sqlsel (ffffffff7fff27a0, 1002d0850, 1002d0d80, 1, ffffffff7e0f9fc0, ffffffff7dd09d70) + 38c
ffffffff7c24ed18 sqlcmex (1, ffffffff7ffe1e80, 0, c, 1002d0850, 0) + 278
ffffffff7c24f724 sqlcxt (0, ffffffff74fd3800, ffffffff7fff27a0, ffffffff74e5d3e4, 16400, 0) + 44
ffffffff74c65aec selectCMF_XIDDB (788, 16450, 2, ffffffff74fbb978, ffffffff7fff4344, ffffffff7971de60) + f14
ffffffff79f5743c bp_AccountFind (0, 0, 1002b6118, 1002b6118, 1002b6118, 1002b6118) + 137c
000000010001748c commonServiceWrapper (30, 0, 558, 1, 100140428, ffffffff6fa08560) + cac
000000010001d1a4 I_AccountFind (100188220, 12336c, 2e60, 100186b80, ffffffff7fffa440, ffffffff6fa08560) + ec
ffffffff7f25ea34 _tmsvcdsp (100186b80, 0, 1001f7b60, 800, 100186b80, 1400) + 11ac
ffffffff7f28241c _tmrunserver (2bb4, 0, 100186b80, 10017c480, 10017d5a0, 0) + 11ac
ffffffff7f25d47c _tmstartserver (1, 2c00, 100144c90, 800, 10017ebe0, 1001444e0) + 1ac
0000000100014e4c main (1b, ffffffff7fffab18, ffffffff7fffabf8, ffffffff6e84b8e0, ffffffff75b05200, ffffffff75f00200) + 14
0000000100014d9c _start (0, 0, 0, 0, 0, 0) + 17c
Can you please help what is causing problem in the applications. Thanks in advanced.

This forum is about C programming in general, and about using Oracle Studio C in particular.
Your question seems to be about a database application that now crashes when run on an updated version of Oracle database.
You mention "Proc" and ProC". If you are referring to the Pro*C compiler, that would also be a database question, since the Pro*C compiler is not related to Oracle Studio or Oracle Studio C.
You are more likely to find a helpful answer in a database programming forum. Start here:
https://forums.oracle.com/forums/category.jspa?categoryID=18

List Format Different When Run In Background...

Hi Guys,
When I run a report in the Foreground my List displays normally. It is worth knowing that this list has 36 Columns (36 added to the Field Catalog).
But, when I run it in the background (F9), it seems to "wrap"/"split" the columns... The last few colums are sent to the next line so my field catalog is actually displayed over 2 lines!!!
When running the Report in the background (F9) I did choose the "Properties" button and I set the Rows to be 65 and the Colums to be 255 under the "Format" Parameter. This does not change anything...
We recently upgraded to ERP6.0. I wonder if it is some kind of SAP Standard that changed???
Please advise - Point will be rewarded for usefull awnsers.
Christiaan

Tks, But it is still not working.
I think it is SAP Standard not to go over the 255 limit when run in the background. My list DEFINATELY has more than the 255 limit...
Here is my statement:
REPORT /bsa/rp_purchaseorder_analysis MESSAGE-ID /bsa/mm LINE-SIZE 400.
This does not work. When I use F9, it gives a message : "Formatting is set to X_65_255". I run this WITHOUT overriding and it does not work. I also ran this overriding the settings... I made the columns 400 and it did not work.
I dont think it is possible????
tks
Christiaan

Parallel Processing when running in background

Hi
We have implemented a parallel processing solution using the Call Function Starting New Task Destination in Group format to split a large number of updates across an RFC Server Group.
This works well when running the ABAP in dialog, but when we schedule for background processing, the parallel processing does not seem to occur, we get a single background process.
Does anyone have any ideas why this may be occuring ?
Thanks
Paul

Paul,
Starting new task will start a new LUW in dialog process and not in background. This is the reason you are having a problem. While technically STARTING NEW TASK is used for parallel processing, you need to consider whether the program will be run in foreground or background mode.
In case of background, you need consider using multiple jobs via job open, submit, job close. This way you can initiate more than one process in your server group to do the work.
You will need to consider the # of background WP available and the # of WPs you can use for this program.
So if there are 100 WPs available and you can use only 10 at any give time, then you should schedule 10 jobs and then check the status of the 10 jobs before you can start scheduling the next jobs.
You can use the FM SPBT_INITIALIZE to check the # of WPs that are currently available in the server group.
Hope this helps.
Thanks,
Vikram.M

Dump when run in background

Similar Messages

Maybe you are looking for