Run time error : TSV_TNEW_PAGE_ALLOC_FAILED report RSEIDOC2 in SELECT_EDIDC

Hi All,
We are getting a run time error with the text "No more storage space available for extending an internal table."
tcode executedd is we02.
kindly let me know if anyone has come acrossed this kind of error.
pointers will be appreciated

Hi Srikanth,
I have not come across this error. But lets see if we can solve this. Kindly let me know when you are getting this run time error.
It seems to be a memory allocation issue, with some IDOC processing.
Also, check the below given link, if it is of any help to you.
Link: [function module;.
Best Regards,
Ram.
Edited by: ram Kumar on Dec 3, 2008 3:14 PM

Similar Messages

Run time error in report for a particular month : " TIME_OUT"

hi frends, we have developed a report for PM module in SAP. it is a monthy report. and user have to enter the month for which he wants to see the report. we are facing runtime error for a particular oct. and nov month of 2009 only , all other months are working fine. The error is :
The program "ZPMR_EQUP_PERFORMANCE_REPORT" has exceeded the maximum permitted
runtime without
interruption and has therefore been terminated.
what could be the reason.

Hi Achalmehra,
By seeing the run time error "TIME_OUT", I suspect this is due to Performance issue.
There is a chance that they had huge data dump into PM server from other servers and there is also chance that
They have many records available for these 2 months.
IN any case, please chk with Run time analysis (SE30) by executing your program...
If it displays the graph more than 30 % for Database then it is an issue with the Performance.
Also chk with SQL trace.....
Second case :
Check you had not used Nested Loops, Select queries in Loop.
Make sure you use Binary search for Read Statements....
Third : Chk with the runtime error at which place of the code it is throwing Time_out error at Source code extract.
To help you further, please paste your code here and also paste the Run time error that you receive with the select queries.
Regards,
Kittu

UDM_DC_NOTES_GET -   run time error - TSV_TNEW_PAGE_ALLOC_FAILED

I am getting below run time error while program executing ( program execution time one hour ) .
   " No more storage space available for extending an internal table."
suspecting below code causing issue:
LOOP AT IT_ITEMS INTO WA_ITEMS.
CALL FUNCTION 'UDM_DC_NOTES_GET'
    EXPORTING
      im_guid   = WA_ITEMS-case_guid
    IMPORTING
      es_return = ls_return
      et_notes = lt_notes.
LOOP AT lt_notes INTO ls_notes TO 2.
    CONCATENATE p_p_wa_output_notes ls_notes-tdline INTO p_p_wa_output_notes.
ENDLOOP.
ENDLOOP.
More ST22 Details::__
5052 PAR2 00 0000 0001 0000                     CL_SCMG_CASE_API==============CM01O            78
5054 ABOO 03 0000 C007 0000                     CL_SCMG_CASE_API==============CM01O            78
5056 mvqk 40 8081 0058 0000                     CL_SCMG_CASE_API==============CM01O            86
5058 MOVE FF 024B C01C C007                     CL_SCMG_CASE_API==============CM01O            87
5060 mvqs 04 8000 00A0 0001                     CL_SCMG_CASE_API==============CM01O            88
>>>>> TAPP 00 0248 C011 C012                     CL_SCMG_CASE_API==============CM01O            89
5064 MOVE FF 0244 0062 C011                     CL_SCMG_CASE_API==============CM01O            90
5066 METH 13 0001 006A 8011 0000 0000 0000 0000 CL_SCMG_CASE_API==============CM01O            92
5070 PAR1 C5 C016                               CL_SCMG_CASE_API==============CM01O            92
5071 PAR2 00 0000 0001 0000                     CL_SCMG_CASE_API==============CM01O            92
5073 METH 13 0005 006B 8012 0000 0000 0000 0000 CL_SCMG_CASE_API==============CM01O            93
5077 PAR1 01 C007                               CL_SCMG_CASE_API==============CM01O            93
Active Calls/Events
Chosen variables
No.       7 Ty.          METHOD
Name CL_SCMG_CASE_API=>IF_SCMG_CASE_API~OPEN_CASE
IM_CASE_GUID
IT_DISPUTE_CASES
    Table IT_5934[30017x344]
    \PROGRAM=ZFR_185334_COLL_MGMT_EXTRACT\DATA=IT_DISPUT
    Table reference: 61
    TABH+ 0(20) = 000000011372F8B0000000000000000000000
    TABH+ 20(20) = 0000003D0000172E0000754100000158FFFFF
    TABH+ 40(16) = 040000000000158000102C9401800000
    store        = 0x000000011372F8B0
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 61    (0x0000003D)
    label        = 5934 (0x0000172E)
    fill         = 30017 (0x00007541)
    leng         = 344   (0x00000158)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000100
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 1     (ItIndexLinear)
ABAP Control Blocks (CONT)
No.   Ty.          Program                             Include                             Line
      Name
    7 METHOD       CL_SCMG_CASE_API==============CP    CL_SCMG_CASE_API==============CM01O    89
      CL_SCMG_CASE_API=>IF_SCMG_CASE_API~OPEN_CASE
    6 METHOD       CL_SCMG_CASE_API==============CP    CL_SCMG_CASE_API==============CM001     6
      CL_SCMG_CASE_API=>IF_SCMG_CASE_API~GET_CASE
    5 FUNCTION     SAPLUDM_DC_INTERFACES               LUDM_DC_INTERFACESU09                  38
      UDM_DC_NOTES_GET
    4 FORM         ZFR_185334_COLL_MGMT_EXTRACT        ZFR_185334_COLL_MGMT_EXT_FORM         666
      F_GET_NOTES
    3 FORM         ZFR_185334_COLL_MGMT_EXTRACT        ZFR_185334_COLL_MGMT_EXT_FORM         619
      F_GET_CASE_ATTR
    2 FORM         ZFR_185334_COLL_MGMT_EXTRACT        ZFR_185334_COLL_MGMT_EXT_FORM         104
      F_PROCESS_DATA
    1 EVENT        ZFR_185334_COLL_MGMT_EXTRACT        ZFR_185334_COLL_MGMT_EXTRACT           93
      START-OF-SELECTION
Please help how to fix this and let me know if you few more details..
or let me know if there any alternative for getting note..
Thanks
Sireesha

Hi sireesha,
Check SAP OSS NOTe :   [1470549 |https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361706E6F7465735F6E756D6265723D3134373035343926]
Resolution
Split the selection criteria and therefore the memory consumption of the report : Look at the definition of the reports causing the short dump and the number of drill down characteristics selected. If all or most of the characteristics are selected, then this will lead to many records in internal tables that contain the aggregated data.
Enlarge the user quote for Heap (abap/heap_area_dia) and re-start the R/3 instance (note 103747)
Change the memory parameters dynamically with report RSMEMORY - You can refer to the Online Documentation for the detail: [http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/b52963524c307be10000000a42189b/frameset.htm |http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/b52963524c307be10000000a42189b/frameset.htm ]
Regards,
koolspy.

Run time error : TSV_TNEW_PAGE_ALLOC_FAILED in st22

Hi All,
we are getting runtime error : TSV_TNEW_PAGE_ALLOC_FAILED in production system. for this report rsppfprocess we have batch jobs so may be its running all the action definition and coming up with consuming more memory ? we already checked with basis but they are saying its rsppfprocess program issue. can you please guide me how to solve this issue.
Jimmi.

Hi Jimmi,
The error TSV_NEW_PAGE_ALLOC_FAILED means that more memory was requested
because the program needed to expand an internal table, but is not available.
When Extended Memory is used up, the process will go into PRIV mode
as it starts using Heap Memory (or vice-versa). No other user will be able to use this work process while it is in PRIV mode.
If there is enough heap for it to finish, you will not see the error TSV_NEW_PAGE_ALLOC_FAILED and the work process will be freed.
This seems to be a problem with loading of shared memory.
Check value of parameter abap/shared_objects_size_MB in RZ11.
Set the parameter to minimum 250 and increase it when necessary, as per SAP note 1281896. You must start the system newly so that the change becomes effective.
Also take a look at SAP Note 1166259.
Gervase

Run-time error "TSV_TNEW_PAGE_ALLOC_FAILED" occurred

Hi all,
I am running BDLS report in background after system copy. Its getting failed. On checking the failed job log in SM37 am getting the TSV_TNEW_PAGE_ALLOC_FAILED runtime error and message as below.
I have checked and all memory parameters looks fine and similar to other systems, No other program/report is running on the server. Please help.
Memory low. Leave the transaction before taking a break!
Message no. 00072
Diagnosis
The memory on your application server is running low.
System Response
You are exclusively using one of the few work processes running on the application server. So that this does not hinder the other users too much, the work process is released if you do not work with it for a few minutes. The system terminates the transaction, causing you to lose data that you previously entered.
Procedure
Continue to work as normal and exit the transaction before you take a long break
memory parameter settings as below
ztta/roll_area                   3000320    Byte
ztta/roll_first                1024       Byte
ztta/short_area                    1600000    Byte
rdisp/ROLL_SHM             16384     8 kB
rdisp/PG_SHM          8192             8 kB
rdisp/PG_LOCAL        150             8 kB
em/initial_size_MB           6144       MB
em/blocksize_KB               4096       kB
em/address_space_MB    4092       MB
ztta/roll_extension               2000683008 Byte
abap/heap_area_dia               2147483648 Byte
abap/heap_area_nondia          2147483648 Byte
abap/heap_area_total             2147483648 Byte
abap/heaplimit                      83886080   Byte
abap/use_paging       0
WP trace info
A *** ERROR => User SSeeeN       reached avail. heapsize = 2047 MB: see ST22 [abstor.c     1766]
A *** ERROR => Increase abap/heap_area_total [abstor.c     1768]
A *** ERROR => heap memory WP0: 2047 MB [abstor.c     1771]
A *** ERROR => heap memory WP1: 0 MB [abstor.c     1771]
A *** ERROR => heap memory WP2: 0 MB [abstor.c     1771]
A *** ERROR => heap memory WP3: 0 MB [abstor.c     1771]
A *** ERROR => heap memory WP4: 0 MB [abstor.c     1771]
A *** ERROR => heap memory WP5: 0 MB [abstor.c     1771]
A *** ERROR => heap memory WP6: 0 MB [abstor.c     1771]
A *** ERROR => heap memory WP7: 0 MB [abstor.c     1771]
A *** ERROR => heap memory WP8: 0 MB [abstor.c     1771]
A *** ERROR => heap memory WP9: 0 MB [abstor.c     1771]
A *** ERROR => heap memory WP10: 0 MB [abstor.c     1771]
A *** ERROR => heap memory WP11: 0 MB [abstor.c     1771]
A *** ERROR => heap memory WP12: 0 MB [abstor.c     1771]
A *** ERROR => heap memory WP13: 0 MB [abstor.c     1771]
A *** ERROR => heap memory WP14: 0 MB [abstor.c     1771]
A *** ERROR => heap memory WP15: 0 MB [abstor.c     1771]
A *** ERROR => heap memory WP16: 0 MB [abstor.c     1771]
A *** ERROR => heap memory WP17: 0 MB [abstor.c     1771]
A *** ERROR => heap memory WP18: 0 MB [abstor.c     1771]
A *** ERROR => heap memory WP19: 0 MB [abstor.c     1771]
A *** ERROR => heap memory WP20: 0 MB [abstor.c     1771]
A *** ERROR => heap memory WP21: 0 MB [abstor.c     1771]
A *** ERROR => heap memory WP22: 0 MB [abstor.c     1771]
A *** ERROR => heap memory WP23: 0 MB [abstor.c     1771]
A *** ERROR => heap memory WP24: 0 MB [abstor.c     1771]
A *** ERROR => heap memory WP25: 0 MB [abstor.c     1771]
A *** ERROR => heap memory WP26: 0 MB [abstor.c     1771]
A *** ERROR => heap memory WP27: 0 MB [abstor.c     1771]
A *** ERROR => heap memory WP28: 0 MB [abstor.c     1771]
A *** ERROR => heap memory WP29: 0 MB [abstor.c     1771]
A *** ERROR => heap memory WP30: 0 MB [abstor.c     1771]
Please help.
Regards,
Sandeep

Hi Mho,
Yes i started BDLS in background and its getting cancelled after running for 2.5 hours.
The below WP trace is when i am seeing BDLS job log via SM37 which is a dialog and is getting terminated with TSV_NEW_PAGE-allocation failed.
the job log file is quite huge. Is that a problem ??
-rwxrwxrwx   1 sidadm     sapsys     1071026978 Jan 20 23:52 0001X21231200X62021
-rw-rw----   1 sidadm     sapsys     1071029688 Jan 21 05:28 0001X02591200X84343
I got this in SM21.
During background processing, the system was unable to read the
specified job log. This may be due to the following:
- The instance from which you wanted to read the job log does not
    have access to the central SAP directory containing the job logs:
    /usr/sap/<Systemname>/SYS/global/<client>JOBLG, for example
    /usr/sap/C11/SYS/global/000JOBLG for the job logs for client 000 in
    system C11. Make sure your instance has access to this
    directory. Examine the syslog for relevant entries.
- As job logs are written and read using the SAP TemSe subsystem,
    there may be problems within TemSe.
    Examine the syslog for relevant entries.
- The disk, on which the directory specified above is stored, is
    full. Consequently, no new job logs can be read or written.
However, i executed another small job which has finished fine and we can see the SM37 jobs

Run Time Error TSV_TNEW_PAGE_ALLOC_FAILED

Hi All,
I have a load failure due to No storage space available for extending an internal table.In ST22 it says as TSV_TNEW_PAGE_ALLOC_FAILED.
Can any one please suggest for fix.I spoke with basis they confirmits not related to space issue

Hi Karuna,
This error we get due to lack of temp sapce on the database level.Ask your basis or DBA team to add additional space.
You can check the table space in DB02 tcode.
here check for the PSAPTEMP table -utilisation.
If the temp space is there decrease the Data package size in the Infopack level and try to reload the data.If u are try to pull huge volume of data try to reduce the selection and reload it will work out.
Can you post the compelte dump details...
regards
KP

Run time error after starting eclipse

Hello,
after installation of the SAP Eclipse Theme Editor the following run time error is reported after each restart of eclipse:
java.lang.ClassCastException: com.sap.ur.plugins.ThemeEditor32Input cannot be cast to com.sap.ur.plugins.ThemeEditorInput
     at com.sap.ur.plugins.ThemeEditor.init(ThemeEditor.java:188)
     at org.eclipse.ui.internal.EditorManager.createSite(EditorManager.java:798)
     at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:647)
     at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:465)
     at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595)
     at org.eclipse.ui.internal.EditorAreaHelper.setVisibleEditor(EditorAreaHelper.java:271)
     at org.eclipse.ui.internal.EditorManager.setVisibleEditor(EditorManager.java:1429)
     at org.eclipse.ui.internal.EditorManager$5.runWithException(EditorManager.java:942)
     at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)
     at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
     at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
     at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4041)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660)
     at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803)
     at org.eclipse.ui.internal.Workbench$31.runWithException(Workbench.java:1567)
     at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)
     at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
     at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
     at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4041)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660)
     at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2548)
     at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
     at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
     at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
     at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
     at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
     at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
     at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
     at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
     at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
     at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
     at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
     at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
     at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
I can work with this editor anyway after choosing the project. But I still have a problem because the preview will not change when I choose a different UI element. The preview alway shows the text "welcome to the SAP ThemeEditor!". When I modify style parameters for the UI element Text the preview is modified in the right way. I already set the Internet Options for the Internet Explorer as suggested. Is it possible that the reported run time error is the reason for the preview problems? The external preview works fine.

Hi,
I would suggest you to remove NWDS, then ensure that nothing left on the disk related to NWDS, and then try a fresh install.
Best Regards,
Ervin

Run-Time error '-2147417848 (80010108) in Crystal Report on SAP BW Query

I have installed Crystal Report 2008 SP1 and the Business Objects Integration kit for 3.1 but when I try to create a report on top of an SAP BW query using the toolbar, after entering the logon parameters for SAP BW, I get a error message :
Run-Time error '-2147417848 (80010108)
Automation error
The object invoked has disconnected from its clients.
CR exits after this error message.
I have tried uninstalling the Kit and CR, cleaning up the registry, and installing it again and still got this error message - It is the same for all my SAP BWs.
Anyone ever had this?
Thank you,
R.

Is this still an issue?

Run time error while executing Project Info system Reports

Hi,
I would like to inform while running project infosystems reports (CN41/41N / cns41 etc), it is taking long time & most of the time run time errors are coming. I observed due to more objects in projects, run time error is coming. Request you to suggest to fix the issue.
Thank you for your cooperation.
Regards,
Rakesh Pradhan

Hi,
I would like to inform while running project infosystems reports (CN41/41N / cns41 etc), it is taking long time & most of the time run time errors are coming. I observed due to more objects in projects, run time error is coming. Request you to suggest to fix the issue.
Thank you for your cooperation.
Regards,
Rakesh Pradhan

Run time Error while executing Project Info system Reports (CN41/CN41N)

Hi,
I would like to inform while running project infosystems reports (CN41/41N / cns41 etc), it is taking long time & most of the time run time errors are coming. I observed due to more objects in projects, run time error is coming. Request you to suggest to fix the issue.
Thank you for your cooperation.
Regards,
Rakesh Pradhan

Hi,
I would like to inform while running project infosystems reports (CN41/41N / cns41 etc), it is taking long time & most of the time run time errors are coming. I observed due to more objects in projects, run time error is coming. Request you to suggest to fix the issue.
Thank you for your cooperation.
Regards,
Rakesh Pradhan

Run-time error while executing alv grid report

Hi everyone
I m trying to run a alv grid report it is giving a run time error while executing the statement CALL METHOD V_ALV->SET_TOOLBAR_INTERACTIVE.
Actually i added 2 buttons in the toolbar.after that when i execute the report i m getting errors.
<b>Error Analysis</b>
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
caught in
procedure "TOOLBAR_MENUS_INIT" "(METHOD)", nor was it propagated by a RAISING
clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
You attempted to use a 'NULL' object reference (points to 'nothing')
access a component (variable: "ME->M_CL_MENU_BUTTON_VARIANT").
An object reference must point to an object (an instance of a class)
before it can be used to access components.
Either the reference was never set or it was set to 'NULL' using the
CLEAR statement.

Hi Dinesh,
Seems you have not initialised ( Instantiated in OO ) the object and / or the parent container.
Check if you have create object for both the parent as well as the alv object.
So when you instatntiate the object of ALV you pass the object ( instantiated before hand ) in the parent container position.
Also you would have to register the events to the object using method. Then only the buttons will finction.
eg :
IF G_CUSTOM_CONTAINER IS INITIAL.
    CREATE OBJECT CUSTOM_CONTAINER_1
           EXPORTING CONTAINER_NAME = CONTAINER_1.
    CREATE OBJECT GRID1
           EXPORTING I_PARENT = CUSTOM_CONTAINER_1.
    CALL METHOD ALV_GRID1->SET_TABLE_FOR_FIRST_DISPLAY
         EXPORTING I_STRUCTURE_NAME = 'VBAK
         CHANGING IT_OUTTAB        = IT_VBAK.
Reward points if useful.

Run time Error while executing project infosystem reports (CN41/41N)

Hi,
I would like to inform while running project infosystems reports (CN41/41N / cns41 etc), it is taking long time & most of the time run time errors are coming. I observed due to more objects in projects, run time error is coming. Request you to suggest to fix the issue.
Thank you for your cooperation.
Regards,
Rakesh Pradhan

Hi Rakesh,
The memory which can be managed by the logical database is approx.
100 MB. You can use the following rule of thumb to calculate the
allocated memory of your selection:
[( sum of projectdefinitions + sum of WBS elements + sum of networks and orders ) * 1 KB + ( sum of activities     ) * 4 KB ] *2,5 = memory consumption
Further objects - as relationships, capacities, ... will increase
the memory consumption. (see note 107605)
You can find out the number of objects bein used using the "Test selection scope" (CTRL+F12) button in CN41
Other recommendations are:
1) Check the profile (parameter "rdisp/PG_MAXFS") with your Basis
   colleague and adjust upwards (Note 133909)
2) Select a smaller range of objects by using status schema
   or more dynamic selections. Please review SAP Note 206264.
3) Please review also 107605, which gives you further information
   concerning the selection in Project Information System.
Hope this helps!
Regards
Martina
Message was edited by:
        Martina Modolell

XL reporter launching in SAP 8.81 PL:00: run time error

Hello experts,
We have a customer who is on SAP 8.81 PL:00.
They are trying to use XL reporter but when they try using XL reporter, they get:
Run time Error 91
The system then freezes.
Have checked they have Microsoft.net 1.1 which they do and that they have the correct excel.exe config file which they do.
Any suggestions or known faults with 8.81?
Thank you in advance,
Andy

Hi Andrew,
'Object reference not set to an instance of an object ' is a known error, this usually happens because there was a previous install of the same add on which was not uninstalled completely. This can cause the error.
I would suggest you to go through sap notes 1247315, 1287193. These all suggests about run time errors, cleaning registry files and clean install etc.
Hope it helps
regards
Johnson

KE30 Report:-Takes very long time and ends in a Run time error

Hi Expert,
Since last three week (after up gradation of system) we are not able to run any of KE30 reports in Production system and its end with Run Time Error. Even in development system where data is minimum it is taking 45 Minutes to give output where it should take maximum 4-5 Minute. Before up gradation it was working fine
What could be the reason for this and how can i resolve this.
Thanks in Advance
Bipin Tiwari

HI Sridhara
Thanks for quick response. After Up Gradation we ran SGEN T-code but no impact on system performance. There after we build new summarisation level in KEDVP (system proposed) and activated it but still it is taking 30-.35 minute to generate the report in Development system which should normaly take 1-2 Munite.
Can you suggest what else we can do or is there any better way for build summarisation level in given scenario.
Best Regards
Bipin Tiwari

ABAP Run time Error whle executing the Balance sheet report in FGI0

Hi,
I am getting the below ABAP Run time error while executing the Balance Sheet report in FGI0.It was working before but now it is giving the error.Kindly help me in solving this.
Runtime Errors         MESSAGE_TYPE_X
Date and Time          06/12/2009 15:17:17
Short text
     The current application triggered a termination with a short dump.
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).
Error analysis
     Short text of error message:
     RAISE RKD_CONDITION_READ       (internal error)
     Long text of error message:
      Diagnosis
          The program was terminated because a situation occurred which
          should not have arisen.
      Procedure
          Analyze the situation and contact SAP.
     Technical information about the message:
     Message class....... "KH"
     Number.............. 299
     Variable 1.......... "RKD_CONDITION_READ"
     Variable 2.......... " "
     Variable 3.......... " "
     Variable 4.......... " "
Trigger Location of Runtime Error
    Program                                 SAPLKYPR
    Include                                 LKYPRU31
    Row                                     36
    Module type                             (FUNCTION)
    Module Name                             RKD_CONDITION_READ
Thanks
Supriya

Hello,
Please refer SAP
Note 971535 - dump when deleting characteristic with hierarchy
Regards,
Ravi

Run time error : TSV_TNEW_PAGE_ALLOC_FAILED report RSEIDOC2 in SELECT_EDIDC

Similar Messages

Maybe you are looking for