Short dump on Report execution

Hi all,
I am facing an issue in reporting. Whenever I try to execute any report i get an error -
Error Group
RFC_ERROR_SYSTEM_FAILURE
Message
Exception condition "TABLE_NOT_EXISTS" raised.
Problem when writing tables - C_T_VARIABLES
If anyone can share some information on this, it would be highly appreciated.
Thanks & REgards,
Manisha

Hi Murali,
I am getting error for /BI0/02* external Hierarchy SID temporary tables. These tables don't exist in database.
Notes 698280 & 728022 are for /BI0/06* kind of tables.
I read note 1139396. But it says use SAP_DROP_TMPTABLES to delete temp tables, but i will not delete /BI0/02 type of tables.
Can you please share in detail, what can be done in such a case?
Thanks,
Manisha

Similar Messages

Short dump error report

What is the purpose of short dump error report generated by the system? What r the major parts/section of this report?

hi please look through this:
Whenever any transaction or any process is executed it hits an ABAP code.
If there is any issue in executing the code the situation is called "ABAP DUMP" or 'Short Dump'
Transaction ST22 is used to check any ABAP Dump within a given duration.
U can also fix the issue with the help of ABAP editor (Transaction Code SE38) if u r good with ABAP.
you can select back to the last 14 days if you are
running the SAP_REORG_ABAPDUMPS job (program RSSNAPDL) which deletes te
old ABAP dumps every day, possibly further if you run it weekly or
monthly.
sap-basis sap-basisAll Groups Ignore this text box. It is used to detect spammers.If you enter anything into this text box, no search results will be displayed.
SAP Groups > Technical-functional > sap-basis > Message
About This Group | Invite peers to join this group
<< Prev thread < Prev msg Next msg > Next thread >>
short dump----urgent
Reply from Keith Lewis on 5/2/2003 3:22:00 AM
Good explanation Joy, but it is not only limited to the current day and
yesterday. If you click on the Selection button you can select previous
days as well. In fact you can select back to the last 14 days if you are
running the SAP_REORG_ABAPDUMPS job (program RSSNAPDL) which deletes te
old ABAP dumps every day, possibly further if you run it weekly or
monthly.
Cheers
Keith
SAP R/3 Support Specialist
Information Services International
Tel +44 1664 41 6178 Mobile +44 7887 627818
E-mail email@removed
Archive Page - http://www.ittoolbox.com//I/sap-r3-basis.asp
Dear sreenivas
If you receive an error message in the R/3 System log (SM21), or if you
see
a terminated update in the update service analysis transaction (SM13), or
DB
realated error ,check for dumps using the dump analysis transaction
(transaction ST22), or choose Tools -> Administration -> Monitoring ->
Dump
analysis.
Transaction ST22 enables you to analyze short dumps from the current and
previous day.
The dump analysis function shows you:
What happened
What you can do
How to correct the error
The dump analysis function also provides an error ID and keywords that you
can use to search in SAPNet, as well as information about:
The system environment
Users and transactions
Transaction ST22 enables you to analyze the following data:
Date, time, user, client
Contents of system and data fields
Contents of internal tables and application tables
ST22 is a very nice feature in SAP. This is where all the system errors
and users mistakes showed up. If there is a problem that you cannot
solve and you contact SAP support, they look at this area to analyze it.
This gives us lead where to handle the problems.
Error analysis
How to correct the error
System environment
User, transaction...
Information on where termination occurred
Contents of system fields
Chosen variables
Active calls / events
Internal notes
Active calls in SAP kernel
List of ABAP programs affected
List of internal tables
Directory of application tables (contents)
Directory of data areas (administration information)
Directory of data areas (contents)
ABAP control blocks CONT
End of runtime analysis
i think this would be helpful
regards
sravani

Short Dump generating reports of EWA

Hi Experts,
I get the short dump MESSAGE_TYPE_X when I tried to see the Ewa report?
Any Idea?
Thanks in advance.

Hi,
Mi ST 400 level is 17.
Here is mi dump:
Err.tmpo.ejec.         MESSAGE_TYPE_X
Fecha y hora           10.08.2009 09:37:50
Texto breve
The current application triggered a termination with a short dump.
¿Qué ha sucedido?
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).
Anál.errores
Short text of error message:
    La creación de evento para la sesión EA0000000000881 ha fallado
Long text of error message:
     Diagnóstico
La creación de un evento ha fallado.
     Actividades en el sistema
         La transacción actual se cancela.
     Procedimiento
Procedimiento para la gestión del sistema
         El problema puede estar en el rango de números DSVASEVENT.
         Verifique si el intervalo "01" está creado y si tiene números
         libres. Notifique los resultados de esta exploración a SAP.
Technical information about the message:
    Message class....... "DSVAS"
    Number.............. 093
    Variable 1.......... "EA0000000000881"
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
Posición desencadenante de error tiempo ejecución
    Programa                                SAPLDSVAS_RPGEN
    Include                                 LDSVAS_RPGENU03
    Línea                                   672
    Tp.módulo                               (FUNCTION)
    Nombre módulo                           DSVAS_RPGEN_REPORT_GET_DATA
Detalle código fuente
Lín.      Txt.fte.
642        lf_chapno_old = 0.
643      * Fehlende Kapitelnummern verdichten
644        LOOP AT report_structure.
645          AT NEW chapter.
646            IF lf_chapno_old <> report_structure-chapter.
647              lf_chapno_old = report_structure-chapter.
648              ADD 1 TO lf_chapno.
649            ENDIF.
650          ENDAT.
651          report_structure-chapter = lf_chapno.
652          MODIFY report_structure.
653        ENDLOOP.
654
655
656      * Ereignis "Reportgeneriert" vermerken
657        DATA: ls_dsvassessinstid TYPE dsvassessinstid,
658              lf_event_parameter TYPE dsvasevent-event_parameter.
659      * AH 'SL' wird durch Aufrufer erst spaeter ausgeloest
660        if lf_iCount = 0 or sy-batch is initial.
661          ls_dsvassessinstid-sessitype = sessitype.
662        ls_dsvassessinstid-sessno    = sessno.
663        lf_event_parameter           = ls_dsvassessinstid.
664        CALL FUNCTION 'DSVAS_EVENT_RAISE'
665             EXPORTING
666                  pf_event_type      = 'SL'
667                  pf_event_parameter = lf_event_parameter
668             EXCEPTIONS
669                  failed             = 1
670                  OTHERS             = 2.
671        IF sy-subrc <> 0.
>>>>>          MESSAGE x093(dsvas) WITH ls_dsvassessinstid.
673      *     Ereigniserzeugung für Sitzung &1 fehlgeschlagen
674          ENDIF.
675        endif.
676      * AH
677
678        CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
679             EXPORTING
680                  TEXT = space.
681      ENDFUNCTION.
Thanks in advance!

Short dump in report generation for bex query

Hi,
I have e newly installed SAP NetWeaver 7.3 and I'm not able to run BEx-Queries. When I start transaction RSRT and try to generate the report for the selected bex query, I get the following short dump:
Category               ABAP Programming Error
Runtime Errors         RAISE_EXCEPTION
ABAP Program           SAPLRRSI
Application Component BW-BEX-OT
If I start the test in RSRV for that query I get:
Generation limits for the generated report
Unable to load report GPEM3XZBL2Y9VX9H6SN
Am I missing a profile parameter for that generartion limits or something else?
Thanks in advance!

Hi,
Check whether your SAP GUI is activated and installed correctly.
check following threads
Runtime error RAISE_EXCEPTION has occurred
Dump when activating Business Content 7.35
Thanks and regards
Kiran

Short dump in report CLEAN_REQREQ_UP

Hi,
I'm in classic scenario with SRM 5.5 . I've created a PO in backend and when I run this report, a short dump appears
Have anybody any idea?
Thanks in advance
Best Regards

hi dinesh
my business steps are :
I'm in srm server 5.5. and sap ERP 6.0
I'm in classic scenario with plan driven procurement.
I replicate my PR from PS to SRM, create a bid invitation. Receive bids and when I accept one of them I create a PO in backend.
These steps work fine, but I can't run this report.
The dump is as follows:
- " UNCAUGHT_EXCEPTION"
- "The exception 'CX_BBP_PD_ABORT' was raised, but it was not caught anywhere along the call hierarchy"
- Since exceptions represent error situations and this error was not adequately responded to, the running ABAP program 'SAPLBBP_PDH' has to be terminated.
Do you need anything more?
Thanks in advance
Best Regards

Dump in report execution after variable selection

hi everyone,
we got a query with a hierarchy variable and on the same characteristic we also got an exclusion of a specific value.
every time a user chooses this excluded value exclusively in the variable, a dump is received upon the execution of the report.
is there a way to solve the problem?
shouldn't the query just return "no data to display"?
thanks in advance,
BW team.

Hi,
The exclusion should be done in Cube level. Because you are trying to implement Variable and also exclusion together. Thus giving dump I believe.
Regards,
Suman

Load getting failed due to short dump

Hi All,
Process Chain is getting failed due to following short dump Include Report LFZI_CA_PCA_DERIVATIONSU37 not found. Please suggest on rectifying this dump. Its a delta load.
Regards,
Asim

Hi All
As requested please find details short dump below. And datasource name is this GECPC_GLPCP and its extractor is ZPCC_V_GLPCP.
Short text
   Syntax error in program "SAPLZFI_CA_PCA_DERIVATIONS ".
hat happened?
   Error in the ABAP Application Program
   The current ABAP program "GP9IQHCDEPFH201E24O25IAYXXW" had to be terminated
    because it has
   come across a statement that unfortunately cannot be executed.
   The following syntax error occurred in program "SAPLZFI_CA_PCA_DERIVATIONS " in
    include "LZFI_CA_PCA_DERIVATIONSUXX " in
   line 77:
   "INCLUDE report "LZFI_CA_PCA_DERIVATIONSU37" not found"
   The include has been created and last changed by:
   Created by: "SAP* "
   Last changed by: "SAP* "
   Error in the ABAP Application Program
   The current ABAP program "GP9IQHCDEPFH201E24O25IAYXXW" had to be terminated
    because it has
   come across a statement that unfortunately cannot be executed.
What can you do?
    Please eliminate the error by performing a syntax check
    (or an extended program check) on the program "SAPLZFI_CA
    You can also perform the syntax check from the ABAP Edito
    If the problem persists, proceed as follows:
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can lo
    at and manage termination messages, and you can also
   keep them for a long time.
Error analysis
    The following syntax error was
    "INCLUDE report "LZFI_CA_PCA_DE
How to correct the error
    Probably the only way to elimin
    If you cannot solve the problem
    notification to SAP, include th
    1. The description of the curre
       To save the description, cho
    (Unconverted)".
    2. Corresponding system log
Display the system log by callin
Restrict the time interval to 10
ter the short dump. Then choose "
nconverted)".
If the problem occurs in a probl
ogram: The source code of the pro
In the editor, choose "Utilities
ilities->Upload/Download->Downloa
Details about the conditions und
tions and input led to the error.
Information on where terminated
    Termination occurred in the ABAP program "GP9IQHCDEPFH201E24O25IAYXXW" - in
     "START_ROUTINE".
    The main program was "RSBATCH_EXECUTE_PROZESS ".
    In the source code you have the termination point in line 102
    of the (Include) program "ZFICA_DERIVE_PCA_OBJECTS_S".
    The program "GP9IQHCDEPFH201E24O25IAYXXW" was started as a background job.
    Job Name....... "BIDTPR_6726959_1"
    Job Initiator.. "ALEREMOTE"
    Job Number..... 17271800
Line SourceCde
   72 ASSIGN 'L_DERIVE_CHRT_ACCTS-UPD_CHRT_AC
   73 assign (<derive_chrt_accts_field>) to
   74 IF <derive_chrt_accts> IS ASSIGNED.
   75   zzi_attributes_upd-chrt_accts_upd = '
   76 ENDIF.
   77 zzi_attributes_upd-/bic/gactivity_upd
   78 zzi_attributes_upd-/bic/gfactv_upd
   79 zzi_attributes_upd-/bic/gglobacct_upd
   80 zzi_attributes_upd-/bic/ggforacc_upd
   81 zzi_attributes_upd-/bic/ggrracc_upd
   82 zzi_attributes_upd-/bic/ggra_code_upd
   83 zzi_attributes_upd-/bic/gsegmtion_upd
   84 zzi_attributes_upd-/bic/ggaapflg_upd
   85 zzi_attributes_upd-/bic/gsub_item_upd
   86 zzi_attributes_upd-/bic/gsegmnt_upd
   87 zzi_attributes_upd-/bic/gacctgrp_upd
   88 zzi_attributes_upd-comp_code_details_up
   89 zzi_attributes_upd-gbfi0600_upd
   90 zzi_attributes_upd-/bic/zaccsuf_upd
   91 zzi_attributes_upd-/bic/gconunit_upd
   92 zzi_attributes_upd-/bic/gtpunit_upd
   93 *--------------------------------------
   94 * Store a copy of the source fields if
   95 *--------------------------------------
   96 MOVE-CORRESPONDING <source_fields> TO z
   97 CLEAR zze_attributes.
Runtime Errors         SYNTAX_ERROR
Date and Time          04.08.2014 17:27:39
    98 *----------------------------------------------------------------------*
    99 * Derive all PCA fields for reporting
   100 *----------------------------------------------------------------------*
   101
>>>>> CALL FUNCTION 'ZFI_CA_DERIVE_PCA_ATTRIBUTESII'
   103   EXPORTING
   104     i_zfi_ca_pca_attributes     = zzi_attributes
   105     i_zfi_ca_pca_attributes_upd = zzi_attributes_upd
   106     msgty                       = 'I'
   107     recno                       = <source_fields>-record
   108   IMPORTING
   109     e_zfi_ca_pca_attributes     = zze_attributes
   110   TABLES
   111     monitor_recno               = lt_monitor_recno.
   112
   113 *----------------------------------------------------------------------*
   114 * On the recurrsive load delete entries where the data is the same
   115 *----------------------------------------------------------------------*
   116 IF zzg_realignment_run = 'X'.
   117   IF zzi_attributes = zze_attributes.
   118     DELETE source_package INDEX la_tabix.
   119   ELSE.
   120     MOVE-CORRESPONDING zze_attributes TO <source_fields>.
   121   ENDIF.
SY-SUBRC 0
SY-INDEX 3
SY-TABIX 1
SY-DBCNT 10
SY-FDPOS 0
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY
SY-UCOMM
SY-TITLE Execute Batch Proces
SY-MSGTY E
SY-MSGID R7
SY-MSGNO 057
SY-MSGV1 ZBAL_LC
SY-MSGV2 A
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20140804
SY-UZEIT 172720
SY-XPROG SAPCNVE
SY-XFORM CONVERSION_EXIT
No.   Ty.          Program                             Include                             Line
      Name
    8 FUNCTION     GP9IQHCDEPFH201E24O25IAYXXW         ZFICA_DERIVE_PCA_OBJECTS_S            102
      START_ROUTINE
    7 METHOD       GP9IQHCDEPFH201E24O25IAYXXW         ZFICA_DERIVE_PCA_OBJECTS_S            102
      LCL_TRANSFORM=>START_ROUTINE
    6 METHOD       GP9IQHCDEPFH201E24O25IAYXXW         GP9IQHCDEPFH201E24O25IAYXXW          1299
      LCL_TRANSFORM=>EXECUTE
    5 METHOD       CL_RSTRAN_TRFN_CMD============CP    CL_RSTRAN_TRFN_CMD============CM005    70
      CL_RSTRAN_TRFN_CMD=>IF_RSBK_CMD_T~TRANSFORM
    4 METHOD       CL_RSBK_PROCESS===============CP    CL_RSBK_PROCESS===============CM00Q    93
      CL_RSBK_PROCESS=>PROCESS_REQUEST
   3 METHOD       CL_RSBK_PROCESS===============CP    CL_RSBK_PROCESS===============CM002    13
      CL_RSBK_PROCESS=>IF_RSBATCH_EXECUTE~EXECUTE
    2 FUNCTION     SAPLRSBATCH                         LRSBATCHU13                           437
      RSBATCH_EXECUTE_PROCESS
    1 EVENT        RSBATCH_EXECUTE_PROZESS             RSBATCH_EXECUTE_PROZESS               374
      START-OF-SELECTION
REQUEST
    DTPR_1FR9TKO2U6M616ATG9C2EYKRH
    455553453544353433345434345454
    4402F16294BF256D61614793259B28
    000000000000000000000000000000
    000000000000000000000000000000
DATAPACKID
    000001
    333333
    000001
    000000
    000000
MONITOR
    Table[initial]
SOURCE_PACKAGE
    3000000001012P2013K4AU0ACD 2013005          00                                               0
    3333333333333533334345344423333333222222222233222222222222222222222222222222222222222222222223
    300000000101202013B415013402013001000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    3333333333333533334345344423333333222222222233222222222222222222222222222222222222222222222223
    300000000101202013B415013402013002000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    3333333333333533334345344423333333222222222233222222222222222222222222222222222222222222222223
    300000000101202013B415013402013003000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    3333333333333533334345344423333333222222222233222222222222222222222222222222222222222222222223
    300000000101202013B415013402013004000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000
00000000000000000000000000000000000
33333333333335333343453444233333332
300000000101202013B4150134020130050
00000000000000000000000000000000000
00000000000000000000000000000000000
Table IT_110723[600000x1144]
{A:114*\TYPE=%_T00003S00000115O0000
Table reference: 3570
TABH+ 0(20) = 90A161080000000060C1
TABH+ 20(20) = F20D000083B00100C027
TABH+ 40(16) = 03730000242D00000400
store        = 0x90A1610800000000
ext1         = 0x60C1190C00000000
shmId        = 0     (0x00000000)
id           = 3570 (0xF20D0000)
label        = 110723 (0x83B00100)
fill         = 600000 (0xC0270900)
leng         = 1144 (0x78040000)
loop         = 128   (0x80000000)
xtyp         = ROL.115.11556
occu         = 4     (0x04000000)
accKind      = 1     (ItAccessStand
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniNo)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
stMode       = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
isUsed       = 1
isCtfyAble   = 1
hasScndKeys = 0
hasRowId     = 0
scndKeysOutdated = 0
scndUniKeysOutdated = 0
----- Shareable Table Header Data -----
tabi         = 0xB008190C00000000
pgHook       = 0x404CE73B00000000
idxPtr       = 0x0000000000000000
id           = 61767 (0x47F10000)
shmTabhSet   = 0x0000000000000000
refCount     = 1     (0x01000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 606204 (0xFC3F0900)
lineAlloc    = 600004 (0xC4270900)
shmVersId    = 0     (0x00000000)
shmRefCount = 2     (0x02000000)
rowId        = 18446744073709551615
scndKeyAdmin = 0x0000000000000000
----- 1st level extension part --------
regHook      = 0xC8C0190C00000000
collHook     = 0x0000000000000000
ext2         = 0x0000000000000000
RI-CLUSTR
   0
   00
   00
ZE_ATTRIBUTES
                     00000
   22222222222222222233333
   00000000000000000000000
   00000000000000000000000
   00000000000000000000000
ZI_ATTRIBUTES
   AU0A    070221000020130
   45342222333333333333333
   15010000070221000020130
   00000000000000000000000
   00000000000000000000000
ZI_ATTRIBUTES_UPD
   XXXXX XXXXXX XX XXXX
   55555255555522552555522
   88888088888800880888800
   00000000000000000000000
   00000000000000000000000
SOURCE_FIELDS>-RECORD
   1
   0000
   1000
T_MONITOR_RECNO
   Table[initial]
ZG_REALIGNMENT_RUN
   2
Regards,
Asim
GECPC_GLPCP

Short dump when I do total or sub total in the ALV report

Hi,
When I do total or sub-total on the currency field in the ALV report, it'll give a short dump like
" 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)".
   Short text of error message:
   Technical information about the message:
   Message classe...... "0K"
   Number.............. 000
   Variable 1.......... " "
   Variable 2.......... " "
   Variable 3.......... " "
   Variable 4.......... " "
   Variable 3.......... " "
   Variable 4.......... " "
Trigger Location of Runtime Error
    Program                                 SAPLSLVC
    Include                                 LSLVCF36
    Row                                     2,726
    Module type                             (FORM)
    Module Name                             FILL_DATA_TABLE
sometime when I do the page down on the ALV report, the same short dump is coming.
Can anyone help me out.
Thanks
Selva

Hi,
I'm getting this short dump in the standard program.
I'm getting ALV report display perfectly. the problem is, when I do total or subtotal on the currency fields.
2704
2705 ************************************
2706 * Column per Fieldcat Entry
2707 ************************************
2708         ls_lvc_data-value = space.
2709         clear ls_lvc_data-style.
2710         loop at it_fcat_local assigning <ls_fcat>
2711                 where tech ne 'X' and no_out ne 'X'.
2712           if l_invisible eq 'X'.
2713             clear l_invisible.
2714             if <ls_fcat>-do_sum is initial.
2715               continue.
2716             else.
2717               clear ls_lvc_data-col_pos.
2718             endif.
2719           endif.
2720
2721           add 1 to ls_lvc_data-col_pos.
2722
2723           assign component <ls_fcat>-fieldname
2724                            of structure <ls_data> to <l_field_value>.
2725           if sy-subrc ne 0.
>>>>>             message x000(0k).
2727           endif.
2728
in this standard program, I'm getting the dump. the line is mentioned above in the code.

Short dump while filtering an ALV report

Hi ,
I have an ALV report which gives me short dump when I filter any of the 'P' type field. I tried to implement sap note 839839 in debug mode but in vain. Should I implement this note first and then check the chnage?
the short dump error "..........
Error in ASSIGN: Memory protection error.
The current program "SAPLSSEL " uses the ASSIGN statement.
However, the offset of the segment (20208) plus the length (69)
is greater than the length of the segment (20264).
This is not allowed.
If the error is in one of your own ABAP programs or an SAP program that
you have modified, try to correct it.
Reduce the offset and/or length that you are using.
If the error occurred in a non-modified SAP program, you may be
able to find a solution in the SAP note system.
If you have access to the note system yourself, use the following
search criteria:
"ASSIGN_OFFSET+LENGTH_TOOLARGE"
"SAPLSSEL " or "LSSELFDI "
"FILL_DYN_FROM_FIELD_SEL"               ........."
I appreciate ur inputs.
thanks in advance,
regards,
shan

Hi Guys,
I found the answer. I had to define all P type fields with eaxact length of 16 . Its working fine.
thanks for all your help.
regards,
shan

Short Dump when the Bex-Report scheduled for Broadcast

Hi Guru's
I am getting the short dump when I am scheduling the Bex-Report for Broadcasting. Need your help to reslove this issue.
Thanks
Navin
Note
The following error text was processed in the system BDV : The current application triggered a termination with a short dump.
The error occurred on the application server spdbwd01_BDV_05 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Form: INTERNAL_ERROR of program SAPLSDCL
Form: PHIO_GET_CONTENT_ACCESS of program SAPLSDCI
Function: SDOK_PHIO_GET_CONTENT_ACCESS of program SAPLSDCI
Function: SKWF_PHIO_CONTENT_ACCESS_GET of program SAPLSKWF_CONTENT
Method: COPY_MIME_TO_FOLDER of program CL_RSRA_KWF_UTILITIES=========CP
Method: GET_STYLESHEET of program CL_RSRA_KWF_TMPL==============CP
Method: CONSTRUCTOR of program CL_RSRA_KWF_TMPL==============CP
Method: SET_TEMPLATE_FOLDER of program CL_RSRA_ENGINE_BC=============CP
Method: CONSTRUCTOR of program CL_RSRA_ENGINE_BC=============CP
Method: EXECUTE_SINGLE of program CL_RSRA_JOB===================CP

HI Navin,
Check the short dump analysis in T-code ST22.
and also check the Information Broadcast Settings / Configuration
Check the error for Emails in t-code SCOT. BASIS Consultants will help you on this issue.
Regards
Daya Sagar

Short dump in custom report in production

Hi Experts,
I have a custom report which is run through SM37 as a background job. it takes long time to run and then get canceled with       short dump in production but it runs fine in development.
description of short dump.
Runtime Errors         DBIF_RSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Date and Time          03.05.2010 11:33:06
Short text
|    SQL error in the database when accessing a table.

Hi,
Please go through the below notes
[Note 1379839 - RuntimeError DBIF_RSQL_SQL_ERROR Exception CX_SY_OPEN_SQL_DB|https://service.sap.com/sap/support/notes/1379839]
[Note 1098183 - RunErr dbif_rsql_sql_error with exception CX_SY_OPEN_SQL_DB|https://service.sap.com/sap/support/notes/1098183]
[Note 1410849 - Runtime error DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"|https://service.sap.com/sap/support/notes/1410849]
This is mainly program error and need corrections...
Compare the Patch level on both DEV and PRD server. Also make sure, whether program you are using on developement is modified (Corrected) or standard one.
If you search for the SAP Notes with "DBIF_RSQL_SQL_ERROR Exception CX_SY_OPEN_SQL_DB" string, you will get several hits. See the notes which are applicable in your scenario...
Regards.
Sumit Nene

Short dump while executing report group.

Hi,
We are upgrading to ECC6.0 from 4.6C
Now while testing the report group i got short dump.
This is due to to the 'Exception condition "LOAD_PROBLEMS" raised.'
Error analysis
    A RAISE statement in the program "SAPLSLDB" raised the exception
    condition "LOAD_PROBLEMS".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
    Short description of exception condition:
    For detailed documentation of the exception condition, use
    Transaction SE37 (Function Library). You can take the called
    function module from the display of active calls.
Function module 'SELOPTS_AND_PARAMS' in this that statement was there.
Can some one help me out. what i have to do further.
Thanks in advance.
Regards,
Deepak.

Hi Hemanth,
Actually what I analysed is what ever the exception raised due to this sy-subrc that exception i think the superior program is not receiving. I think due to this it is going for short dump.
Let me know if you have any idea further.
Thanks,
Deepak.
Message was edited by:
        Deepak Kudaravalli

Report Painter GR214 generation error - Short dump 4.6C

While generating a report with more than twenty sections, the system short dumps with the error message GR214 pointing to "MESSAGE_TYPE_X"
"%_T01JR0 " or "########################################"
"INSERT_ROW_FORMULA_NEW"
Any leads to fix this?
The generation error happens only when I include a last line formula in the last section, Till then it is working fine.

Hi,
The error you are receiving could be caused by a large number of row blocks in your report definition, (you can check the report definition with report RGRRDC00). A report should not contain too many row and column blocks. It is not possible to give an upper bound for the number of row blocks (since the length of the coding depends on other parts of the report as well). However, even a complicated Report Writer or Report Painter report should not contain more than 50 row blocks, and reports with more than 100 row blocks should not be defined.
In this case the report(s) have to be redefined. Please also refer to the note 387916 for further information regarding this issue.
When there are more than 30 variables in a report, please have a look at the note 332091.
Please reduce the number of row blocks in the report by using the function 'Edit' -> 'Rows' -> 'Explode' in the Report Painter
definition. This function enables several rows to be created for one row block (in the Report Painter definition one row block is just one row). Report Painter (and Report Writer) are designed to display hierarchical reports where the rows in the few row blocks are built up using the 'Explode' function.
regards
Waman

REGARDING ALV REPORT SHORT DUMP

hI ALL,
IAM GETTING FOR THE FOLLOWING CODE,
PLEASE WHY THE ERROR IN ECC 6.0
TABLES AND DATA DECLARATION.
*TABLES: mara,makt.",marc.
data syrepid like sy-repid.
data sydatum(10). " LIKE sy-datum.
data sypagno(3) type n.
WHEN USING MORE THAN ONE TABLE IN ALV WE NEEED TO DECLARE THE TYPE
GROUP (TYPE-POOLS--------->SLIS)
type-pools : slis.
INTERNAL TABLE DECLARATION.
INTERNAL TABLE TO HOLD THE VALUES FROM THE MARA TABLE
data: begin of t_mara occurs 0,
matnr like mara-matnr,
meins like mara-meins,
mtart like mara-mtart,
matkl like mara-matkl,
end of t_mara.
INTERNAL TABLE TO HOLD THE CONTENTS FROM THE EKKO TABLE
data : begin of t_marc occurs 0,
matnr like mara-matnr,
werks like marc-werks,
minbe like marc-minbe.
data: end of t_marc.
INTERNAL TABLE TO HOLD THE VALUES FROM MAKT TABLE.
data : begin of t_makt occurs 0,
matnr like mara-matnr,
maktx like makt-maktx,
spras like makt-spras,
end of t_makt.
INTERNAL TABLE WHICH ACTUALLY MERGES ALL THE OTHER INTERNAL TABLES.
data: begin of itab1 occurs 0,
matnr like mara-matnr,
meins like mara-meins,
maktx like makt-maktx,
spras like makt-spras,
werks like marc-werks,
minbe like marc-minbe,
end of itab1.
THE FOLLOWING DECLARATION IS USED FOR DEFINING THE FIELDCAT
AND THE LAYOUT FOR THE ALV.
HERE AS slis_t_fieldcat_alv IS A INTERNAL TABLE WITHOUT A HEADER LINE
WE EXPLICITELY DEFINE AN INTERNAL TABLE OF THE SAME STRUCTURE AS THAT
OF slis_t_fieldcat_alv BUT WITH A HEADER LINE IN THE DEFINITION.
THIS IS DONE TO MAKE THE CODE SIMPLER.
OTHERWISE WE MAY HAVE TO DEFINE THE STRUCTURE AS IN THE NORMAL SAP
PROGRAMS.
IN THE FIELDCATALOG TABLE WE ACTUALLY PASS THE FIELDS FROM ONE OR
MORE TABLES AND CREATE A STRUCTURE
IN THE LAYOUT STRUCTURE WE BASICALLY DEFINE THE FORMATTING OPTIONS
LIKE DISPLAY IN THE ZEBRA PATTERN ,THE HOTSPOT OPTIONS ETC.
data: fieldcatalog type slis_t_fieldcat_alv with header line,
fieldlayout type slis_layout_alv.
DECLARING THE EVENTTABLE INTERNL TABLE FOR USING EVENTS LIKE
TOP-OF-PAGE ETC.
data : eventstab type slis_t_event with header line.
DECLARING AN INTERNAL TABLE TO HOLD THE DATA FOR THE TOP-OF-PAGE
data : heading type slis_t_listheader with header line.
data : heading1 type slis_t_listheader with header line.
data : heading2 type slis_t_listheader with header line.
data : heading3 type slis_t_listheader with header line.
data : heading4 type slis_t_listheader with header line.
data : heading5 type slis_t_listheader with header line.
data : heading6 type slis_t_listheader with header line.
data : heading7 type slis_t_listheader with header line.
data : heading8 type slis_t_listheader with header line.
STRUCTURE TO PASS THE COLOR ATTRIBUTES FOR DISPLAY.
data : colorstruct type slis_coltypes.
INITIALIZATION. *
initialization.
syrepid = sy-repid.
sypagno = sy-pagno.
clear fieldcatalog.
START-OF-SELECTION. *
start-of-selection.
SUBROUTINE TO POPULATE THE COLORSTRUCT
perform fill_colorstruct using colorstruct.
SUBROUTINE TO POPULATE THE FIELDS OF THE FIELD CATALOGUE
perform populate_fieldcatalog.
SUBROUTINE TO SELECT DATA FROM VARIOUS TABLES AND POPULATE IT IN THE
INTERNAL TABLE.
perform selectdata_and_sort.
SUBROUTINE TO POPULATE THE LAYOUT STRUCTURE.
perform populate_layout using fieldlayout.
SUBROUTINE TO CALL THE FUNCTION MERGE TO ENSURE PROPER DISPLAY.
perform merge_fieldcatalog.
SUBROUTINE TO POPULATE THE EVENTSTAB.
perform fill_eventstab tables eventstab.
SUBROUTINE TO POPULATE THE HEADING TABLES.
perform fill_headingtable tables heading using 'HEADING'.
perform fill_headingtable tables heading1 using 'HEADING1'.
perform fill_headingtable tables heading2 using 'HEADING2'.
perform fill_headingtable tables heading3 using 'HEADING3'.
perform fill_headingtable tables heading4 using 'HEADING4'.
perform fill_headingtable tables heading5 using 'HEADING5'.
perform fill_headingtable tables heading6 using 'HEADING6'.
perform fill_headingtable tables heading7 using 'HEADING7'.
perform fill_headingtable tables heading8 using 'HEADING8'.
SUBROUTINE TO DISPLAY THE LIST.
perform display_alv_list.
FORMS
IN THIS SUBROUTINE WE POPULATE THE FIELDCATALOG TABLE WITH THE NAMES
OF THE TABLE,FIELDNAME,WHETHER IT IS KEY FIELD OR NOT,HEADING AND
COLUMN JUSTIFICATION.
form populate_fieldcatalog.
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'MATNR' 'X' .
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'MEINS' ' '.
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'MAKTX' ' ' .
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'MTART' ' ' .
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'MATKL' ' ' .
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'SPRAS' ' ' .
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'WERKS' ' ' .
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'MINBE' ' ' .
endform. " POPULATE_FIELDCATALOG
FORM FILL_FIELDS_OF_FIELDCATALOG *
--> FIELDCATALOG *
--> P_TABNAME *
--> P_FIELDNAME *
--> P_KEY *
--> P_KEY *
form fill_fields_of_fieldcatalog tables fieldcatalog
structure fieldcatalog
using p_tabname
p_fieldname
p_key.
p_no_out.
fieldcatalog-tabname = p_tabname.
fieldcatalog-fieldname = p_fieldname.
fieldcatalog-key = p_key.
fieldcatalog-emphasize = '1234'.
*fieldcatalog-no_out = p_no_out.
append fieldcatalog.
endform. " FILL_FIELDSOFFIELDCATALOG
FORM POPULATE_LAYOUT *
--> FIELDLAYOUT *
form populate_layout using fieldlayout type slis_layout_alv.
fieldlayout-f2code = '&ETA' .
fieldlayout-zebra = 'X'.
FOR THE WINDOW TITLE.
fieldlayout-window_titlebar = 'ALV with Events'.
fieldlayout-colwidth_optimize = 'X'.
fieldlayout-no_vline = ' '.
*fieldlayout-no_input = 'X'.
fieldlayout-confirmation_prompt = ''.
fieldlayout-key_hotspot = 'X'.
This removes the column headings if the flag is set to 'X'
fieldlayout-no_colhead = ' '.
*fieldlayout-hotspot_fieldname = 'MAKTX'.
fieldlayout-detail_popup = 'X'.
fieldlayout-coltab_fieldname = 'X'.
endform. " POPULATE_LAYOUT
FORM SELECTDATA_AND_SORT *
form selectdata_and_sort.
select matnr meins mtart matkl from mara
into corresponding fields of t_mara
up to 500 rows .
select matnr maktx spras from makt
into corresponding fields of t_makt
where matnr = t_mara-matnr and
spras = sy-langu.
select matnr werks minbe from marc
into corresponding fields of t_marc
where matnr = t_mara-matnr.
append t_marc.
endselect.
append t_makt.
endselect.
append t_mara.
endselect.
perform populate_itab1.
sort itab1 by matnr.
endform. " SELECTDATA_AND_SORT
FORM MERGE_FIELDCATALOG *
form merge_fieldcatalog.
call function 'REUSE_ALV_FIELDCATALOG_MERGE'
exporting
i_program_name = syrepid
i_internal_tabname = 'ITAB1'
i_structure_name = 'COLORSTRUCT'
I_CLIENT_NEVER_DISPLAY = 'X'
i_inclname = syrepid
changing
ct_fieldcat = fieldcatalog[]
exceptions
inconsistent_interface = 1
program_error = 2
others = 3.
endform. " MERGE_FIELDCATALOG
IN THIS FUNCTION THE MINIMUM PARAMETERS THAT WE NEED TO PASS IS AS
FOLLOWS:-
i_callback_program --> CALLING PROGRAM NAME
i_structure_name --> STRUCTURE NAME.
is_layout --> LAYOUT NAME.
it_fieldcat ---> BODY OF THE FIELD CATALOGUE INTERNAL TABLE
form display_alv_list.
call function 'REUSE_ALV_LIST_DISPLAY'
exporting
I_INTERFACE_CHECK = ' '
i_callback_program = syrepid
I_CALLBACK_PF_STATUS_SET = ' '
I_CALLBACK_USER_COMMAND = ' '
i_structure_name = 'ITAB1'
is_layout = fieldlayout
it_fieldcat = fieldcatalog[]
IT_EXCLUDING =
IT_SPECIAL_GROUPS =
IT_SORT =
IT_FILTER =
IS_SEL_HIDE =
I_DEFAULT = 'X'
THE FOLLOWING PARAMETER IS SET AS 'A' INORDER TO DISPLAY THE STANDARD
TOOL BAR
i_save = 'A'
IS_VARIANT = ' '
it_events = eventstab[]
IT_EVENT_EXIT =
IS_PRINT =
I_SCREEN_START_COLUMN = 0
I_SCREEN_START_LINE = 0
I_SCREEN_END_COLUMN = 0
I_SCREEN_END_LINE = 0
IMPORTING
E_EXIT_CAUSED_BY_CALLER =
ES_EXIT_CAUSED_BY_USER =
tables
t_outtab = itab1
exceptions
program_error = 1
others = 2.
endform. " DISPLAY_ALV_LIST
*& Form POPULATE_ITAB1
text
--> p1 text
<-- p2 text
form populate_itab1.
loop at t_mara.
loop at t_makt where matnr = t_mara-matnr.
loop at t_marc where matnr = t_mara-matnr.
move-corresponding t_mara to itab1.
move-corresponding t_makt to itab1.
move-corresponding t_marc to itab1.
append itab1.
endloop.
endloop.
endloop.
endform. " POPULATE_ITAB1
*& Form FILL_EVENTSTAB
text
-->P_EVENTSTAB text *
form fill_eventstab tables p_eventstab structure eventstab.
WHEN THE FOLLOWING FUNCTION IS CALLED THE SYSTEM POPULATES THE
INTERNAL TABLE EVENTSTAB WITH A LIST OF EVENTS NAME.
AS SHOWN BELOW WHEN USING I_LIST_TYPE = 0 THE FUNCTION RETURNS 14
EVENTS NAME.
call function 'REUSE_ALV_EVENTS_GET'
exporting
i_list_type = 0
importing
et_events = p_eventstab[]
exceptions
list_type_wrong = 1
others = 2.
BY CALLING THE ABOVE FUNCTION WE FIRST POPULATE THE EVENTSTAB WITH
THE PREDEFINED EVENTS AND THEN WE MOVE THE FORM NAME AS SHOWN BELOW.
WE ASSIGN A FORM NAME TO THE EVENT AS REQUIRED BY THE USER.
FORM NAME CAN BE ANYTHING.THE PERFORM STATEMENT FOR THIS FORM
IS DYNAMICALY CALLED.
read table p_eventstab with key name = slis_ev_top_of_page.
if sy-subrc = 0 .
move 'TOP_OF_PAGE' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_top_of_coverpage.
if sy-subrc = 0 .
move 'TOP_OF_COVERPAGE' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_end_of_coverpage .
if sy-subrc = 0 .
move 'END_OF_COVERPAGE' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_foreign_top_of_page.
if sy-subrc = 0 .
move 'FOREIGN_TOP_OF_PAGE' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_foreign_end_of_page.
if sy-subrc = 0 .
move 'FOREIGN_END_OF_PAGE' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_list_modify.
if sy-subrc = 0 .
move 'LIST_MODIFY' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_top_of_list.
if sy-subrc = 0 .
move 'TOP_OF_LIST' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_end_of_page.
if sy-subrc = 0 .
move 'END_OF_PAGE' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_end_of_list .
if sy-subrc = 0 .
move 'END_OF_LIST' to p_eventstab-form.
append p_eventstab.
endif.
endform. " FILL_EVENTSTAB
*& Form FILL_HEADINGTABLE
text
-->P_HEADING text *
form fill_headingtable tables p_heading structure heading
using tablename.
case tablename.
when 'HEADING'.
p_heading-typ = 'H'.
concatenate
' REPORT NAME:-' syrepid
' ABB Industry Pte Ltd' into p_heading-info.
append p_heading.
write sy-datum using edit mask '__/__/____' to sydatum.
concatenate
' DATE:-' sydatum ' USER: ' sy-uname 'PAGE NO:' sypagno
into p_heading-info.
append p_heading.
when 'HEADING1'.
p_heading-typ = 'H'.
p_heading-info = 'TOP-OF-COVER-PAGE'.
append p_heading.
when 'HEADING2'.
p_heading-typ = 'H'.
p_heading-info = 'END-OF-COVER-PAGE'.
append p_heading.
when 'HEADING3'.
p_heading-typ = 'H'.
p_heading-info = 'FOREIGN-TOP-OF-PAGE'.
append p_heading.
when 'HEADING4'.
p_heading-typ = 'H'.
p_heading-info = 'FOREIGN-END-OF-PAGE'.
append p_heading.
WHEN 'HEADING5'.
P_HEADING-TYP = 'H'.
P_HEADING-INFO = 'LIST-MODIFY'.
APPEND P_HEADING.
when 'HEADING6'.
p_heading-typ = 'H'.
p_heading-info = 'END-OF-PAGE'.
append p_heading.
when 'HEADING7'.
p_heading-typ = 'H'.
p_heading-info = 'END-OF-LIST'.
append p_heading.
when 'HEADING8'.
p_heading-typ = 'H'.
p_heading-info = 'TOP-OF-LIST'.
append p_heading.
endcase.
endform. " FILL_HEADINGTABLE
FORM TOP_OF_PAGE *
form top_of_page.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading[]
exceptions
others = 1.
endform.
*& Form FILL_COLORSTRUCT
text
-->P_COLORSTRUCT text *
form fill_colorstruct using p_colorstruct type slis_coltypes .
p_colorstruct-heacolfir-col = 6.
p_colorstruct-heacolfir-int = 1.
p_colorstruct-heacolfir-inv = 1.
endform. " FILL_COLORSTRUCT
FORM TOP_OF_COVERPAGE *
form top_of_coverpage.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading1[]
exceptions
others = 1.
endform.
FORM END_OF_COVERPAGE *
form end_of_coverpage.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading2[]
exceptions
others = 1.
endform.
FORM FOREIGN_TOP_OF_PAGE *
form foreign_top_of_page.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading3[]
exceptions
others = 1.
endform.
FORM FOREIGN_END_OF_PAGE *
form foreign_end_of_page.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading4[]
exceptions
others = 1.
endform.
FORM LIST_MODIFY *
*FORM LIST_MODIFY.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
IT_LIST_COMMENTARY = HEADING5[]
EXCEPTIONS
OTHERS = 1.
*ENDFORM.
FORM END_OF_PAGE *
form end_of_page.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading6[]
exceptions
others = 1.
endform.
FORM END_OF_LIST *
form end_of_list.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading7[]
exceptions
others = 1.
endform.
FORM TOP_OF_LIST *
form top_of_list.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading8[]
exceptions
others = 1.
endform.
SHORT DUMP IS
This error may occur if
- You address a typed field symbol before it has been set with
   ASSIGN
- You address a field symbol that pointed to the line of an
   internal table that was deleted
- You address a field symbol that was previously reset using
   UNASSIGN or that pointed to a local field that no
   longer exists
- You address a global function interface, although the
   respective function module is not active - that is, is
   not in the list of active calls. The list of active calls
   can be taken from this short dump.
PLEASE GIVE ME ANSWER.
REGARDS

HI I MADE SOME CHANGES TO UR CODE...
RUN IF THIS IS THE REQ ...
IN SELECT QUERIES OF RETRIEVING DATA..
form selectdata_and_sort.
select matnr meins mtart matkl from mara
into corresponding fields of TABLE t_mara
WHERE MATNR = T_MARA-MATNR.
up to 200 rows .
IF SY-SUBRC = 0.
    MESSAGE I001 WITH ' DATA RET FROM MARA'.
ENDIF.
IF T_MARA[] IS NOT INITIAL .
select
       matnr
       maktx
       spras
       From
       makt
       into corresponding fields of TABLE t_makt
        FOR ALL ENTRIES IN T_MARA
       where matnr = t_mara-matnr and
       spras = sy-langu.
ENDIF.
IF SY-SUBRC = 0 .
MESSAGE I001 WITH ' DATA RET FROM MAKT'.
ENDIF.
IF T_MAKT[] IS NOT INITIAL.
      select matnr
             werks
             minbe
             from marc
             into corresponding fields of TABLE t_marc
             FOR ALL ENTRIES IN
             T_MAKT where matnr = t_maKT-matnr.
    ENDIF.
ENDFORM.                    "selectdata_and_sort
JUST TRY THIS CODE..

Exception Reporting failure due to short dump UNCAUGHT_EXCEPTION

Hi everyone,
Exception Reporting called u201CPO Price Deviationu201D failure due to short dump UNCAUGHT_EXCEPTION.
Need your reply on this urgently.
Thank you,
Prasad

Hi Andrew Zhou,
Actually the Exception reporting step failed because there was no applicable data for the selection criteria mentioned in the BEx report. And the data was stuck in the source system. We got it solved my contacting the R/3 cosultant.
I am giving you points for the response. And I would like to know one thing about RSRT if I select "use aggregates" option for a query it is showing aggregates while debuging even though there are no aggregates created on the Cube.
Thank you

Short dump on Report execution

Similar Messages

Maybe you are looking for