Short dump for rsa3

Hi sapxperts,
I am getting error ,short dump when i execute the RSA3 for inventory management data Source 2LIS_03_BX.
Please somebody help with regards to Inventory management stuff .
thank you.

hi stalin,
Heres how to proceed.
execute tcode RSA3.Give your datasource name.In the below screen there is a Grid.
There you can see a list of characteristics available.You can put some values there for a characteristics.
For ex- If you see company code there. Try putting some values there.
This will filter out the selection and lesser values will be extracted.
hope it helps,
regards,
Parth.

Similar Messages

Short Dump for Dynamic Select Query

Hello all,
I get a short dump for my dynamic select query at the end of the code. The error is "The types of operands "dbtab" and "itab" cannot be converted into one another."
My code looks like below.
FORM get_ccnum_2 USING    p_tabname TYPE dd03l-tabname.
DATA: p_table(30) TYPE c.
FIELD-SYMBOLS: <dyn_wa>,
                               <t> TYPE table.
DATA: it_fldcat    TYPE lvc_t_fcat.
TYPE-POOLS : abap.
DATA: it_details   TYPE abap_compdescr_tab,
        wa_details   TYPE abap_compdescr.
DATA: ref_descr    TYPE REF TO cl_abap_structdescr.
DATA: new_table    TYPE REF TO data,
        new_line     TYPE REF TO data,
        wa_it_fldcat TYPE lvc_s_fcat.
p_table = p_tabname.
ref_descr ?= cl_abap_typedescr=>describe_by_name( p_table ).
it_details[] = ref_descr->components[].
LOOP AT it_details INTO wa_details.
    CLEAR wa_it_fldcat.
    wa_it_fldcat-fieldname = wa_details-name .
    wa_it_fldcat-datatype = wa_details-type_kind.
    wa_it_fldcat-intlen    = wa_details-length.
    wa_it_fldcat-decimals = wa_details-decimals.
    APPEND wa_it_fldcat TO it_fldcat .
ENDLOOP.
CALL METHOD cl_alv_table_create=>create_dynamic_table
    EXPORTING
      it_fieldcatalog = it_fldcat
    IMPORTING
      ep_table        = new_table.
ASSIGN new_table->* TO <t>.
CREATE DATA new_line LIKE LINE OF <t>.
ASSIGN new_line->* TO <dyn_wa>.
wa_cond = 'CCNUM <> '' '' '.
APPEND wa_cond TO tab_cond.
      SELECT * INTO TABLE <t>
               FROM     (p_table)
               WHERE    (tab_cond)
               ORDER BY (tab_ord).
ENDFORM.                    " GET_CCNUM_2

Hi,
I tried to execute the code using table BSEGC and it gave a short dump..
the actual exception that shows in ST22 IS ..UNICODE_TYPES_NOT_CONVERTIBLE..
I think there is something wrong in the internal table creation..
Instead of using the method cl_alv_table_create=>create_dynamic_table to create the dynamic table I used the following and it worked..
CREATE DATA new_table TYPE TABLE OF (p_table).
* Comment begin " Naren
* ref_descr ?= cl_abap_typedescr=>describe_by_name( p_table ).
* it_details[] = ref_descr->components[].
* LOOP AT it_details INTO wa_details.
*    CLEAR wa_it_fldcat.
*    wa_it_fldcat-fieldname = wa_details-name .
*    wa_it_fldcat-datatype = wa_details-type_kind.
*    wa_it_fldcat-intlen    = wa_details-length.
*    wa_it_fldcat-decimals = wa_details-decimals.
*    APPEND wa_it_fldcat TO it_fldcat .
* ENDLOOP.
* CALL METHOD cl_alv_table_create=>create_dynamic_table
*    EXPORTING
*      it_fieldcatalog = it_fldcat
*    IMPORTING
*      ep_table        = new_table.
* Comment End. " Naren
CREATE DATA new_table TYPE TABLE OF (p_table).   " New code by naren
Please Try this..
Thanks
Naren

How to keep short dumps for a longer time

Hi All,
I need to write a program to fetch all the below mentioned fields from the system dump tables and insert into a user defind table. Please help me with the code. Thanks in advance....
PROBLEM DESCRIPTION
ABAP runtime errors (also known as short-dumps) are kept in the system only for two days, mainly because every short-dump can use a lot of disk space depending on short-dump type. Problem is that this reduced time frame (two days) is not allowing us to focus in solve the more frequent ones and we do not have any statistic about:
    how many are we getting
    how often
    repetitive ones
PROPOSED SOLUTION
We need a program to be executed in a daily job right after midnight which will take the basic information of all todays short-dumps and store it in a custom table.
Information to be kept:
      DATE
      TIME
      HOST
      USER
      SYSTEM
      CLIENT
      ERROR ID
      TRANSACTION
      PROGRAM NAME
      PROGRAM NAME VERSION (TRANSPORT REQUEST NUMBER)
      PROGRAM NAME VERSION TIMESTAMP (transported to PPx)
      SCREEN
      SCREEN LINE
      MAIN PROGRAM NAME
      MAIN PROGRAM NAME VERSION (TRANSPORT REQUEST NUMBER)
      MAIN PROGRAM NAME VERSION TIMESTAMP (transported to PPx)
      PROGRAM LINE NUMBER AT TERMINATION
      SAP RELEASE
      SAP KERNEL
      PATCH LEVEL
      DATABASE VERSION
The program must have archiving capabilities implemented. In the month end run it will also perform the table house-keeping accordingly with a parameter like this:
     ERROR-ID
     MONTHS TO KEEP
We need to have the possibility of defining different retention periods for different kind of errors, for example our friend GETWA_TOO_MANY_SEGMENT could be stored for a year and a simple CONVT_NO_NUMBER only for a month. One of the parameters should be the default one, something like
        ERROR-ID **************
        MONTHS TO KEEP 01.

Aruna,
Following may be the action points for your requirements.
1. Create Custom table with all fields you required.
2. Create ABAP program to extract the data from SAP standard table where runtime error information is stored.
Like: select * from snap_beg into wa_snap_beg
          where seqno = '000'
          and   datum in s_datum
          and   uzeit in s_uzeit
          and   ahost in s_ahost
          and   uname in s_uname
          and   mandt in s_mandt.......
So SNAP_BEG is a table where you can find dump information.
After extracting the data from this table insert it into a Custom table which you have created in Step 1.
Use INSERT statement for this.
3. Create transaction for this report.
4. Schedule this program every day so that you will get all data into custom table.
I hope this will help you.
Regards,
Amey

TIME_OUT Short Dump for SAPLDSVAS_PROC report - BPM activation

Hello SOLMAN Experts,
I'm trying to activate BPM Business Process Monitoring and getting the following short dump:
Runtime Errors         TIME_OUT
Short text
     Time limit exceeded.
What happened?
     The program "SAPLDSVAS_PROC" has exceeded the maximum permitted runtime without
    interruption and has therefore been terminated.
Any advice please?
Thanks,
123

Hello,
For the time being (Temporarily), you can try to increase the parameter rdisp/max_wprun_time to some higher value and then try activation process. This parameter is I think 'dynamic' and so can be updated without system restart. You can verify this from rz11.
After you done, revert the value.
Thanks

Short dump in RSA3 --Z Data Source

Hi,
I created a Z data source based on view and i appended extract structure to insert ZZ fields.
When i execute the data source it is showing me short dump how shall i proceed
I checked the view conditions and it is extracting data and showing now error and i checked the enhancements i have written in CMOD and checked the program it is displaying No syntax errors
Please advise me on how to correct the errors....
If need further info of short dump please ask
Runtime Error          DBIF_RSQL_INVALID_RSQL
Exception              CX_SY_OPEN_SQL_DB
What happened?
Error in ABAP application program.
The current ABAP program "SAPLRSA3" had to be terminated because one of the
Statements could not be executed.
Error analysis
An exception occurred. This exception is dealt with in more detail belo.The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', waS neither                                                           caught nor passed along using a RAISING clause, in the procedure "RSA3_GEN_GET_DATA" "(FUNCTION)"
Since the caller of the procedure could not have expected this exceptio to occur, the running program was terminated.
The reason for the exception is:
The data read during a SELECT access could not be inserted into the target field.
Either conversion is not supported for the target field's type or the target field is too short to accept the value or the data are not in a form that the target field can accept.
Information on where terminated
The termination occurred in the ABAP program "SAPLRSA3" in "RSA3_GEN_GET_DATA".
The main program was "RSFHGEN2 ".
The termination occurred in line 226 of the source code of the (Include)
program "LRSA3U03"
of the source code of program "LRSA3U03" (when calling the editor 2260).
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "RSA3_GEN_GET_DATA" "(FUNCTION)" but was not handled locally, not
declared in the
RAISING clause of the procedure.
The procedure is in the program "SAPLRSA3 ". Its source code starts in line 5
of the (Include) program "LRSA3$03 ".
Program
002150
002160       CASE G_S_INTERFACE-UPDMODE.
002170         WHEN 'F' OR 'C' OR 'I'.
002180   * First data package -> OPEN CURSOR
002190           IF G_COUNTER_DATAPAKID = 0.
002200   * Open Cursor for dynamical SELECT
002210             OPEN CURSOR WITH HOLD G_CURSOR FOR
002220             SELECT * FROM (G_S_OLTPSOURCE-EXTRACTOR)
002230                    WHERE (L_T_DYNAMIC_SELECT).
002240           ENDIF.
002250   * Fetch first data package
>           FETCH NEXT CURSOR G_CURSOR
002270                        APPENDING CORRESPONDING FIELDS OF TABLE E_T_DATA
002280                        PACKAGE SIZE G_S_INTERFACE-MAXSIZE.
002290           IF SY-SUBRC <> 0.
002300             RAISE NO_MORE_DATA.
002310           ENDIF.
002320           G_COUNTER_DATAPAKID = G_COUNTER_DATAPAKID + 1.
002330         WHEN 'D'.
002340           PERFORM FETCH_GEN_DELTA IN PROGRAM (L_GEN_PROGID)
002350                           TABLES E_T_DATA
002360                                  L_T_DYNAMIC_SELECT
002370                                  G_T_FIELDS
002380                           USING G_S_INTERFACE-MAXSIZE
002390                           CHANGING L_FLG_NO_MORE_DATA.
002400           IF L_FLG_NO_MORE_DATA = 'X'.
002410             IF NOT L_T_BDCPS[] IS INITIAL.
002420               L_T_BDCPS-PROCESS = SBIWA_C_FLAG_ON.
002430               MODIFY L_T_BDCPS
002440                    TRANSPORTING PROCESS WHERE PROCESS = SBIWA_C_FLAG_OFF.

Hello,
This thread is answered. Was it the table space or something else?
We may have a similar issue as recently posted in thread:
"Short dump in SAP R/3: SQL statement buffer overflow?"
Best regards
Thomas

SAP GUI for HTML - Short dump for Office intehration

Hi Experts.
I am using portal to view the transaction and it needs to open a document, while opening a document through it getting an error. when using
SAPGUI for HTML.
But it is working fine for GUI for Windows. ( selected this option in iView). It also works fine when use the transaction SAP itself.
Getting an below error from portal.
A RAISE statement in program "C_OI_CONTAINER_CONTROL_CREATORCP" has rais
exception condition "JAVABEANNOTSUPPORTED".
Since the exception was not caught by a program higher up in the call
hierarchy, processing was terminated.
Thanks
Rag

Anurag,
I have gone through notes.
I am using 7.2 version and access transaction through portal. while opening MS-office document, it is giving an error like JAVABEANNOTSUPPORT. and OFFICEINTREGRATION issue.
While opening it in SAP its working fine as well as using GUY for Windows also good.
But giving a short dump while accessing through portal with GUI for HTML option.
Any idea or work around for the same.
Thanks
Rag

Getting Short Dumps for only 1 user - related to BAL logs

Just yesterday afternoon, 1 user began receiving short dumps in the FM BAL_INTERNAL_LOCK_ON_SAVE
This is happening on each message she's trying to process. I can process the exact same message and it works for me.
Termination occurred in the ABAP program "SAPLSBAL_DB_INTERNAL" - in "BAL_INTERNAL_LOCK_ON_SAVE".
The main program was "ZCSS_SCH_CREATE_DOCS ".
In the source code you have the termination point in line 65 of the (Include) program "LSBAL_DB_INTERNALU07".
In my main program, ZCSS_SCH_CREATE_DOCS, I just load up the AIF messaging structure and Call TRANSFER_TO_AIF method.
Any idea what's going on?

turns out it was a security issue.

Short Dump for Query in Quality server

Hi Experts,
i have a query, when i execute it in developement server, it successfully execute. But when i execute the same query in Quality,
it gets short dump, giving following error.
ABEND RSBOLAP (000): Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION
MSGV1: SAPMSSY1
MSGV3: UNCAUGHT_EXCEPTION
previously it was working fine in quality, but suddenly it gets shortdu while executing.
i transported again, but error still persists.
i tried execute this query in RSRT also, where it stops at a break point.
this query uses a custimer exit variable, but this variable is not the reason for short dump. without this variable also same error occurs.
please help me to resolve this.
Thanks
Saurabh

Hi,
Please try to provide max input in the variable screen, Don't execute the query based on single selection criteria. And also please perform cube compression before executing the query.
Hope this will solve the issue .
Thanks
PT

Short Dump for upgrade from 3.5 to 7.0

Hi All,
We have upgraded the BI system from 3.5 to 7.0 .
In the upgraded system , when i run the program RRINCLTAB_REBUILD , it throws the short dump as SAPSQL_WHERE_FOR_ALL_MISMATCH.
In the dump it says to check the field length and field type of LINKNO for the standard table and the internal table used in program.
Standard table - /BIC/KILIACG
Internal table - l_t_nodesid type standard table of RSDMHSITAB
I checked it , but unable to find any in-consistency there in two field definations.
Pls suggest the ways to resolve it.
Regards,
Sarang Kahu

Hi,
the error is not related to a standard table.
/BIC/KILIACG is the sid table of the hierarchy of infoobject ILIACG. I would recommend to check that infoobject in the target system and try to activate if it isn't active already. Otherwise, goto se14. for the that table and check the ddic object as well as the runtime object. Try to repair the table with se14. Then run the program again.
regards
Siggi

HU03 going to short dump for handling unit which has higher level handling

Hi,
I am ABAPer, i working on issue, HU03 is gong to short dump. i dubug the t code and find out that particular handling unit has higher level handling unit. I checked another handling unit which won't had higher level handling unit, that time it's not giving dump.
Note: in HU03 T CODE, function module V51P_HU_CONTENS is fetching values. when ever handling unit has higher level handling unit, it's not fetching further values.
venkey

Hi,
Goto NACE transaction code , there you select the application area then it will give you the list of output types then select specific output click processing routines then you will see the program name and script used.
Or esle goto SPRO tcode then you can find the functional tab there also you can get the details.
Thanks,
Aditya

Short dump for update function module

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

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

Short dump in SAP R/3: SQL statement buffer overflow?

Hello,
I hope someone can help us with the following problem:
A short dump in SAP R/3 (DBIF_RSQL_INVALID_RSQL, CX_SY_OPEN_SQL_DB)
occurred during a delta load, which worked fine for several month.
The custom code crashes at a FETCH NEXT CURSOR statement.
I assume, it might be a SQL statement buffer overflow in SAP R/3?
The problem can be reproduced by RSA3, and is therefore not time-dependent.
The problem did not occur before or on the quality assurance system.
Cursor code:
      Read all entries since last transfer (delta mechanism)
        OPEN CURSOR WITH HOLD s_cursor FOR
          SELECT * FROM ekko
            WHERE ebeln IN t_selopt_ekko.
t_selopt_ekko has up to 60.000 data sets, which worked fine in the past.
It is very likely that the amount of data during the first crash did not exceed this.
SQL-Trace of RSA3 call:
It seems that 25150 data set can be processed via fetch before the short dump occurs
After that object SNAP is written:
"...DBIF_RSQL_INVALID_RSQL...dynpen00 + 0xab0 at dymain.c:1645 dw.sapP82_D82
Thdyn...Report für den Extraktoraufruf...I_T_FIELDS...Table IT_43[16x60]TH058FUNCTION=
RSA3_GET_DATA_SIMPLEDATA=S_S_IF_SIMPLE-T_FIELDSTH100...shmRefCount = 1...
...> 1st level extension part <...isUsed       = 1...isCtfyAble   = 1...> Shareable Table Header Data
<...tabi         = Not allo......S_CURSORL...SAPLRSA3...LRSA3U06...SAPLRSA3...
During dump creation the following occurs:
"...SAPLSPIAGENTCW...CX_DYNAMIC_CHECK=...CRSFH...BALMSGHNDL...
DBIF_RSQL_INVALID_RSQL...DBIF_RSQL_INVALID_RSQL...DB_ERR_RSQL_00013...
INCL_ABAP_ERROR...DBIF_INCL_INTERNAL_ERROR...INCL_INTERNAL_ERROR...
GENERAL_EXC_WITHOUT_RAISING...INCL_SEND_TO_ABAP...INCL_SEARCH_HINTS...
INCL_SEND_TO_SAP...GENERAL_EXC_WITHOUT_RAISING...GENERAL_ENVIRONMENT...
GENERAL_TRANSACTION...GENERAL_INFO...GENERAL_INFO_INTERNAL...
DBIF_INCL_INTERNAL_CALL_CODE..."
Basis says, that the Oracle data base works fine. The problem seems to be a SAP R/3 buffer.
Does anyone had a similar problem or knows where such a buffer might be or how it can be enlarged?
Best regards
Thomas
P.S.
Found a thread that contains part of the dump message "dynpen00 + 0xab0 at dymain.c:1645":
Thread: dump giving by std prg contains -> seems not to be helpful
Found a similar thread:
Thread: Short dump in RSA3 --Z Data Source -> table space or somting else?
Edited by: Thomas Köpp on Apr 1, 2009 11:39 AM

Hi Thomas,
      Its due to different field length.
Just check it out in code after FETCH NEXT CURSOR what internal table you have mention.
that internal table shoul deffined by taking refrence of ekko, because your code is
OPEN CURSOR WITH HOLD s_cursor FOR
SELECT * FROM ekko
WHERE ebeln IN t_selopt_ekko.
hope you got solution.
Regards,

Short dump in r/3 in delta extraction

Hi all,
Today we got short dump in R/3 for delta extraction of data source
2LIS_13_VDITM.We want these data to do month end analysis.
I have tried to run extraction checker (rsa3) still it gives me short
dump for the same.
SAP r/3 4.6c
and bw 3.5
Regards,
Viren.

Hi,
please paste some more info about the dump...
Olivier.

Short dump in standard program

Hi Friends,
below description is short dump for standard program.
Please see the below and help me how to correct the program.
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:
Internal error: Program   , include   , form   .
Technical information about the message:
Diagnosis
     An unexpected error has occurred.
Procedure
     If you can reproduce the error, contact the SAP Hotline quoting the
     error number.
Message classe...... "GR"
Number.............. 214
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
"SAPFGRWE" or "FGRWEF80_F80_FILL_COL_TAB"
"F80_FILL_COL_TAB"
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.
Thanks & Regards,
Sree
Edited by: adepus on Oct 7, 2009 12:39 PM
Edited by: adepus on Oct 7, 2009 12:39 PM

Hi Clemens,
I am getting a dump error as shown below. Could you please find some resolution for this issue. we just made some changes to the transaction GS02(Just added a GL account to one of the sets).
Runtime Error MESSAGE_TYPE_X
ShrtText
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).
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.
is especially useful if you want to keep a particular message.
Error analysis
Short text of error message:
Internal error: Program , include , form .
Technical information about the message:
Diagnosis
An unexpected error has occurred.
Procedure
If you can reproduce the error, contact the SAP Hotline quoting the
error number.
Message classe...... "GR"
Number.............. 214
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Variable 3.......... " "
Variable 4.......... " "
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
"SAPFGRWE" or "FGRWEF80_F80_FILL_COL_TAB"
"F80_FILL_COL_TAB"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
Source Code
79 MESSAGE x214.
80 ENDIF.
81 PERFORM e08_read_object_index(sapfgsb0)
82 USING fcolumns-dim_index.
83 IF c-subrc 0. MESSAGE x214. ENDIF.
84 c_dsentry = c-tval-from.
85 IF c_dsentry '='.
86 READ TABLE data_fields BINARY SEARCH
87 WITH KEY tab = rep_table
88 dsentry = c_dsentry.
>>>> IF sy-subrc 0. MESSAGE x214. ENDIF.
90 ENDIF.
91 WHEN OTHERS.
92 c_dsentry = '*'.
93 ENDCASE.
94 ENDIF.
Regards,
Pavan

How to Fetch Cancelled Jobs info along with the Short Dump Text

Hi Gurus,
I need to develop a report to fetch the cancelled jobs information for the given period. I also need to display the "Error Analysis" part of the Short Dump if it exists.
I am able to fetch the Failed Jobs information and the Job log details using the FM "BP_JOBLOG_READ". But I need to show the "Error Analysis Text" on the report , if there is any Short Dump Exists for the Dump.
Please give me your ideas to fetch the Error Analysis part of the short dump for a given Batch Job Name.
Thanks in Advance.
Best Regards,
Sumalatha

The dump information is in table SNAP. You could identify which dump you want by the date & time of the failed job - let's hope you don't have more than one dump with the same time. If it is ambiguous you could also compare the program name of the failed step with the program name in the SNAP data.
The error analysis texts are in table SNAPT keyed according to which error occurred (which is data element code FC right at the start of the first record in the SNAP data). You will have to expand out the includes, and substitute the variable codes using values from the SNAP data. There is standard code to do this that you could copy - see program SAPMS380.
To find out the details of the SAP process you could run transaction ST22 via the debugger and use the same mechanism.
best wishes
Ed
PS Note these details apply to recent systems I think there may be differences if you go back to before ?2004, but I don't have such a system so can't check. You didn't say what release you have.

Short dump for rsa3

Similar Messages

Maybe you are looking for