Getting Shor Dump while DSO Activation

Hi Experts,
I am getting Error while DSO Activation, I checked in ST22 Error is (SYSTEM_CORE_DUMPED), Please suggest me.
Category               Internal Kernel Error
Runtime Errors         SYSTEM_CORE_DUMPED
Date and Time          25.02.2014 18:38:47
Short Text
     Process terminated by signal 10.
What happened?
     Error in the SAP kernel
     The current ABAP program "CL_RSODSO_DATASTORE=====
      terminated because the ABAP
     processor detected a system error.
Thanks
Sunil

Hi,
Take basis team help. error itself saying as related to internal kernel error.
recently any changes were applied on server? if yes then those might be causing.
please refer note - 517824.
Inform to basis team and sort it out.
Thanks

Similar Messages

Getting Short Dump while DSO Activation

Hi,
I am getting Error while DSO Activation, I checked in ST22 Error is (SYSTEM_CORE_DUMPED), Please suggest.
The kernel is latest version.
Also we had implemented a couple of SAP Notes while we searched on the SDN and service market place. But still no luck.
Category Internal Kernel Error
Runtime Errors SYSTEM_CORE_DUMPED
Date and Time 09.04.2014 16:14:13
Short Text
Process terminated by signal 10.
What happened?
Error in the SAP kernel
The current ABAP program
"CL_RSODSO_DATASTORE=====
terminated because the ABAP
processor detected a system error.
Thanks,
Sameer

Hi,
Yes this happens for a particular DSO only - 0FIAR_O03(DSO)
Also the kernel is the latest one.
I am from Basis. I have checked all the possibilities and have raised OSS message as well.
Thanks,
Sameer

Getting a dump while executing the standard report BUSCHDOC

Hi,
I am getting a dump while executing the standard report BUSCHDOC.
I am specifying the following values:-
Application Object : BUPA
Business partner:<some business partner>
Changed on: <some date>
Changed by:<some userid>
Below are the dump details
Short text
CREATE DATA: The specified type "BUSSRCH_401BUPAT" is no valid data type.
Any suggestions to avoid the dump are welcome.
Thanks,
Ravindra

Hi Ravindra,
Can you execute report BUP_BUSSRCHGF_REPAIR and try again ?
Also, go to transaction BUS10, click the button Geneate Selection. On next screen, give Application object = BUPA, Max no. of tables per view = 1.
Regards,
Rishu.

Getting short dumps while reading bulky data from excel sheet

Hi all,
We have converted our non-unicode based sap system (R/3 4.7, Windows 2003,
SQL 2000) into a unicode based system recently. We are facing two peculiar
problems for last few days.
*Problem 1 - *Whenever we want to upload the data from excel sheet, the
system throws a dump after reading about 400 entries, while last week the
same system used to read about 8000 entries in a single go.
*Problem 2 - *Also, whenever we realease a transport requst from development
containing a lot of changes, the request will reach the quality system but
without the changes. but if i ll try to import the changes into quality
system after generating more than one request containing small small
changes, they get reflected in QAS immediately. Is there any size
constraint in transporting a request fro DEV->QAS->PRD.
Please suggest some ways.
I am pasting the dump (that I am getting while data uploading from Excel).
~~~~~~~~~~~~~~~~~~
Runtime errors
MESSAGE_TYPE_X*
Occurred on
22.02.2008 at
13:21:02*
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.
Error analysis
Short text of error message:
Control Framework : Error processing control
Technical information about the message:
Diagnosis
An error occurred when the system tried to process the commands
from the Automation Queue on the presentation server.
There are several possible reasons for this:
- The installation of the SAP GUI on the presentation server is
faulty or obsolete.
- There is an error in the application program
- There is an error in the SAPGUI or an integrated control
Procedure
1. Make sure that you have imported the appropriate Support
Package, the current kernel, and GUI patch for the release of your
System
2. Check whether the error occurs locally on one or a few PCs, or
generally on all PCs. Note whether the error only occurs for some
users, for example because of a specific Customizing setting.
If it only occurs locally, this suggests an installation problem
with the PC. Check the installation; if necessary, reinstall the
software. In the dump, search for the SY-MSGLI field, since it may
point to the cause of the error.
3. Activate the Automation Trace (in accordance with SAP Note
158985).
4.Start the transaction and continue until the screen immediately
before the dump.
5. From the System -> Utilities menu, choose Autom. Queue,
Synchronous Processing.
The status bar of the GUI displays the text:
"Automation synchron flush mode on"
6. If you now proceed with the application, the short dump will
display the ABAP call that caused the error; the Automation Trace
will contain the error on the presentation server.
7. If necessary, load the short dump and trace files on to
sapservX, so that SAP can analyze them.
Message classe...... "CNDP"
Number.............. 006
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"MESSAGE_TYPE_X" C
"SAPLOLEA" or "LOLEAU02"
"AC_SYSTEM_FLUSH"
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.
System environment
SAP Release.............. "620"
Application server....... "nhbho930"
Network address.......... "192.168.0.30"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "4x Intel 801586"
Character length......... 16 Bits
Pointer length........... 32 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "NHBHO930"
Database type............ "MSSQL"
Database name............ "DEV"
Database owner........... "dev"
Character set............ "C"
SAP kernel............... "640"
Created on............... "Aug 17 2007 00:18:58"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "SQL_Server_8.00 "
Patch level.............. "196"
Patch text............... " "
Supported environment....
Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,
Windows NT 6.0"
User, transaction...
Client.............. 300
User................ "NHBABAP"
Language key........ "E"
Transaction......... "SE38 "
Program............. "SAPLOLEA"
Screen.............. "SAPMSDYP 0010"
Screen line......... 0
Information on where terminated
The termination occurred in the ABAP program "SAPLOLEA" in
"AC_SYSTEM_FLUSH".
The main program was "ZBDC_CONTRACT ".
The termination occurred in line 29 of the source code of the (Include)
program "LOLEAU02"
of the source code of program "LOLEAU02" (when calling the editor 290).
~~~~~~~~~~~~~~~~~~~~~
Thank you all.
Cheers.
Mitra __.____._

for the 50 millionth time: Excel spreadsheets are NOT databases, you should NOT try to use them as such and NEVER access them using JDBC.
You should also under NO condition use the JDBC-ODBC bridge driver (that was actually the 78 millionth time that was told someone).

Getting short dump while executing a background job

Hi ,
I have a issue in which i am executing the report in background and the while the job executes it is going into dump stating that the error "TSV_TNEW_PAGE_ALLOC_FAILED" it is happening as the internal table where all the data is getting appended does not have enough memory size to hold the details the internal table refers to the type of a standard structure.
Is there to solve this issue so that the execution of the program does not go into dump or regulating the memory the size of the internal table by any kind of optimization.

Hard to recommend without knowing the purpose of the program. The general approach would be to lower memory consumption by using block processing, i.e. read certain amount of data (block), do necessary processing, empty all tables, repeat with next block.
Thomas

I am getting an dump while executing open hub destination?

I did happened to delete a filed in the open hub and then activated and re-ran it i am getting the following error!!
error analysis
You attempted to assign a field to a typed field symbol,
but the field does not have the required type.
open hub is active, dtp is active and transformations is active too but still the same!!
Can anyone advise me on this!!
thanks
pooja

Hi,
See in
http://wiki.sdn.sap.com/wiki/display/profile/Surendra+Reddy
Open Hub Destination
Open Hub Destination: Part 1
http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/business-intelligence/m-o/open%20hub%20destination%3a%20part%201.pdf
Open Hub Destination: Part 2
http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/business-intelligence/m-o/open%20hub%20destination%3a%20part%202.pdf
Analysis Process Designer (APD)
Analysis Process Designer (APD): Part - 1
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f06353dd-1fe3-2c10-7197-dd1a2ed3893e?quicklink=index&overridelayout=true
Analysis Process Designer (APD): Part - 2
http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/business-intelligence/a-c/analysis%20process%20designer%20(APD)%20Part%20-%202.pdf
Analysis Process Designer (APD): Part - 3
http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/business-intelligence/a-c/analysis%20process%20designer%20(APD)%3a%20Part%20-%203.pdf
Thanks
Reddy

Getting Short Dump while executing PPOSE

Hi All,
I am working on software component SAP HR release 604 level 023 SAPKE60423.
When I am trying to run the TCode PPOSE, I am able to find the objects in the find objects area.
Once I double click on that object to get the full details, getting dump with the following details.
Short text
    Program " " not found.
What happened?
    There are several possibilities:
    Error in the ABAP Application Program
    The current ABAP program "SAPLRHOMDETAIL_APPL" had to be terminated because it
     has come across a statement that unfortunately cannot be executed.
    or
    Error in the SAP kernel.
    The current ABAP "SAPLRHOMDETAIL_APPL" program had to be terminated because the
    ABAP processor detected an internal system error.
Could any one please help on this.
Thanks
Prashanth

Hi Prashanth,
please try tcode ST22 to analyse the run time errors
execute ST22 tcode
choose by giving username for ex and the time period
you will get the details listed like current date,time,app server,username,client,name of runtime error,exception,appl.component etc
double click on the item listed
on the left hand side click source code extract and you will get the indicator on which line of code with >>>> to debug
it will take you to ABAp editor to debug by entering /h enter in command field
kindly enlist the help of an Abaper to explore this .
Hope it helps
Regards
KG

Getting ABAP dump while cancelling invoice through MR8M

Hi Experts,
When i try to cancel the invoice through MR8M i am getting the ABAP dump saying "Conversion error Occured".
Could u please help me to resolve this.
Infact the error is coming when i press "display doc" after giving the invoice details.
Thanks,
Amar Y.
Edited by: amaranath yerragunta on Apr 19, 2010 10:34 AM

Hi ,
Is the any enhanemnet done for MR8M Tcode?
I think in the enhancement code converion is wrong.
Regards,
Pravin

Getting Short Dump while using the FM"SAP_CONVERT_TO_TEX_FORMAT"

Hello Experts,
    I am using the FM SAP_CONVERT_TO_TEX_FORMAT to convert the data in text format and use
that converted data to create the file on application server. When I used this FM to convert the data from T0599Z table then it's giving me dump for other tables it's working fine.
Can anyone suggest why this is happening?
Thanks

Can you write the codes...
Try something of below sort..
CALL FUNCTION 'SAP_CONVERT_TO_TEX_FORMAT'
   EXPORTING
     i_field_seperator          = ','           "For CSV Files
    TABLES
      i_tab_sap_data             = gt_outtab1
   CHANGING
     i_tab_converted_data       = gt_outtab.

I am getting a dump while running va23 and got follwing error.

The system tried to access field "ALL_NINES" with type "C" and length
36 in the current program "ZVADQU01_NEW" using length 40.
Partial field access is not allowed with a length specification that is
larger than actual field length.
CODE EXTRACT:
DATA: index                      LIKE sy-index,
       f_type(1),
       length                     TYPE i,
       all_nines(36)             VALUE '99999999999999999999'.
FIELD-SYMBOLS: <fsin>,
                <fsout>,
                <fieldname>.
DO.
   index                           = index
                                   + 1.
   ASSIGN COMPONENT index OF STRUCTURE inrec
                                  TO <fsin>.
   ASSIGN COMPONENT index OF STRUCTURE outrec
                                  TO <fsout>.
   IF sy-subrc                    <> 0.
     EXIT.
   ENDIF.
   IF <fsin>                      <> space.
     MOVE <fsin> TO <fsout>.
   ELSE.
     DESCRIBE FIELD <fsout>     TYPE f_type.
     IF f_type                     = 'C'.
       MOVE 'ZZZZZZZZZZZZZZZZZZ' TO <fsout>.
     ELSEIF f_type                 = 'N'.
       DESCRIBE FIELD <fsout> LENGTH length in byte mode.
ERROR OCCURED HERE****
       MOVE all_nines(length)     TO <fsout>.
     ENDIF.
   ENDIF.
ENDDO.

This even works in my nw2004s system.
report zrich_0003.
data: begin of outrec,
      fld1(18) type c,
      fld2(10) type n,
      fld3(18) type c,
      fld4(10) type n,
      end of outrec.
field-symbols: <fs>.
data: f_type,
      length type i,
      all_nines(20) type c value '99999999999999999999'.
outrec-fld1 = 'ABCDEFGHIJKLMNOPQR'.
outrec-fld2 = '1234567890'.
outrec-fld3 = 'ABCDEFGHIJKLMNOPQR'.
outrec-fld4 = '1234567890'.
do.
assign component sy-index of structure outrec to <fs>.
if sy-subrc <> 0.
    exit.
endif.
describe field <fs> type f_type.
if f_type = 'C'.
    move 'ZZZZZZZZZZZZZZZZZZ' to <fs>.
elseif f_type = 'N'.
    describe field <fs> length length <b>in BYTE MODE</b> .
    move all_nines(length) to <fs>.
endif.
write:/ <fs>.
enddo.
Then only thing I changed was to add the IN BYTE MODE.
Regards,
Rich Heilman

Short Dump while activating Transformation through Program

HI All,
I am getting short dump while activating - Inactive Transformation through Program RSDG_TRFN_ACTIVATE.
However while i can activate single Transformation but if run without selection, I am getting this dump.
Short Description of Dump -
Category
ABAP Programming Error
Runtime Errors
ASSERTION_FAILED
ABAP Program
CL_RSAR_FORMULAS==============CP
Application Component BW-WHM-DST
Date and Time
Please Guide.
Prasad

Hi Prasad,
Have you changed the 'Object Status' from INA to ACT when using the program RSDG_TRFN_ACTIVATE?
You can also refer to the note SAP Note 1030987 - Activation of transformations dumps
regards,
Ashvin

Getting Dump while Mapping data source.

Hi Expert,
Am getting below DUMP while trying to map data source in SEGW transaction.
Could you please suggest what could be possible cause for this?
Category               ABAP Programming Error
Runtime Errors         SYNTAX_ERROR
ABAP Program           CL_SADL_GW_UI_ALV_SADL_MAPPINGCP
Application Component BC-ESI-ESF-GW
Date and Time          28.07.2014 18:30:59
Short Text
     Syntax error in program "CL_SADL_GW_UI_ALV_SADL_MAPPINGCP        ".
What happened?
     Error in the ABAP Application Program
     The current ABAP program "CL_SADL_GW_UI_PLUG============CP" had to be
      terminated because it has
     come across a statement that unfortunately cannot be executed.
     In include "CL_SADL_GW_UI_ALV_SADL_MAPPINGCM005     ", in line 14 of program
      "CL_SADL_GW_UI_ALV_SADL_MAPPINGCP        ", the following syntax errors
     have occurred:
Thanks & Regards,
Girdhari

Thanks Jasmin for the reply.
Yes.. Am following the E2E guide.
I tried by opening another external window by executing ok-code osegw but still getting same dump.
Below is the complete dump info.
Category               ABAP Programming Error
Runtime Errors         SYNTAX_ERROR
ABAP Program           CL_SADL_GW_UI_ALV_SADL_MAPPINGCP
Application Component BC-ESI-ESF-GW
Date and Time          29.07.2014 15:44:03
|Short Text                                                                                        |
|    Syntax error in program "CL_SADL_GW_UI_ALV_SADL_MAPPINGCP        ".                           |
|What happened?                                                                                    |
|    Error in the ABAP Application Program                                                         |
|                                                                                                  |
|    The current ABAP program "CL_SADL_GW_UI_PLUG============CP" had to be                         |
|     terminated because it has                                                                    |
|    come across a statement that unfortunately cannot be executed.                                |
|    In include "CL_SADL_GW_UI_ALV_SADL_MAPPINGCM005     ", in line 14 of program                  |
|     "CL_SADL_GW_UI_ALV_SADL_MAPPINGCP        ", the following syntax errors                      |
|    have occurred:                                                                                |
|    "CS_TABLE_LAYOUT" is not type-compatible with formal parameter "CS_TAB                        |
|    LE_LAYOUT".                                                                                   |
|                                                                                                  |
|                                                                                                  |
|                                                                                                  |
|    Author and last person to change the include are:                                             |
|    Author         SAP                                                                            |
|    Last changed by "SAP         "                                                                |
|Error analysis                                                                                    |
|    The following syntax error has occurred in program                                            |
|     CL_SADL_GW_UI_ALV_SADL_MAPPINGCP        :                                                    |
|    "CS_TABLE_LAYOUT" is not type-compatible with formal parameter "CS_TAB                        |
|    LE_LAYOUT".                                                                                   |
|                                                                                                  |
|    " "                                                                                           |
|Trigger Location of Runtime Error                                                                 |
|    Program                                 CL_SADL_GW_UI_PLUG============CP                      |
|    Include                                 CL_SADL_GW_UI_PLUG============CM002                   |
|    Row                                     11                                                    |
|    Module Type                             (METHOD)                                              |
|    Module Name                             /IWBEP/IF_SBUI_PLUGIN~CREATE_VIEW                     |
|Source Code Extract                                                                               |
|Line |SourceCde                                                                                   |
|    1| METHOD /iwbep/if_sbui_plugin~create_view.                                                 |
|    2|    CASE iv_name.                                                                           |
|    3|      WHEN if_sadl_gw_ui_c=>gc_dialog-mapping_container. " custom container for the ALV Grid|
|    4|        CREATE OBJECT ro_view TYPE cl_sadl_gw_ui_map_ds_sadl_c                              |
|    5|          EXPORTING                                                                         |
|    6|            io_controller = io_controller                                                   |
|    7|            iv_plugin     = if_sadl_gw_ui_c=>gc_ui_plugin                                   |
|    8|            iv_name       = iv_name.                                                        |
|    9|                                                                                            |
|   10|      WHEN if_sadl_gw_ui_c=>gc_dialog-entity_set_prop_map_alv_grid. " ALV GRID mapping table|
|>>>>>|        CREATE OBJECT ro_view TYPE cl_sadl_gw_ui_alv_sadl_mapping                           |
|   12|          EXPORTING                                                                         |
|   13|            io_controller = io_controller                                                   |
|   14|            iv_plugin     = if_sadl_gw_ui_c=>gc_ui_plugin                                   |
|   15|            iv_name       = iv_name.                                                        |
|   16|                                                                                            |
|   17|      WHEN if_sadl_gw_ui_c=>gc_dialog-entity_set_assoc_map_alv_grid. " ALV GRID mapping tabl|
|   18|        CREATE OBJECT ro_view TYPE cl_sadl_gw_ui_alv_map_assoc                              |
|   19|          EXPORTING                                                                         |
|   20|            io_controller = io_controller                                                   |
|   21|            iv_plugin     = if_sadl_gw_ui_c=>gc_ui_plugin                                   |
|   22|            iv_name       = iv_name.                                                        |
|   23|                                                                                            |
|   24|      WHEN if_sadl_gw_ui_c=>gc_dialog-data_source_tree. " SADL entity ALV tree              |
|   25|        CREATE OBJECT ro_view TYPE cl_sadl_gw_ui_tree_ds_sadl_c                             |
|   26|          EXPORTING                                                                         |
|   27|            io_controller = io_controller                                                   |
|   28|            iv_plugin     = if_sadl_gw_ui_c=>gc_ui_plugin                                   |
|   29|            iv_name       = iv_name.                                                        |
|   30|    ENDCASE.                                                                                |
|Active Calls/Events                                                                               |
|No.   Ty.          Program                             Include                             Line   |
|      Name                                                                                        |
|   23 METHOD       CL_SADL_GW_UI_PLUG============CP    CL_SADL_GW_UI_PLUG============CM002    11 |
|      CL_SADL_GW_UI_PLUG=>/IWBEP/IF_SBUI_PLUGIN~CREATE_VIEW                                       |
|   22 METHOD       /IWBEP/CL_SBUI_SETUP==========CP    /IWBEP/CL_SBUI_SETUP==========CM00E     7 |
|      /IWBEP/CL_SBUI_SETUP=>/IWBEP/IF_SBUI_SETUP_FACTORY~CREATE_COMPONENT_VIEW                    |
|   21 METHOD       /IWBEP/CL_SBUI_VIEW_COMPOSITE=CP    /IWBEP/CL_SBUI_VIEW_COMPOSITE=CM004     6 |
|      /IWBEP/CL_SBUI_VIEW_COMPOSITE=>CREATE_COMPONENT_VIEW                                        |
|   20 METHOD       CL_SADL_GW_UI_MAP_DS_SADL_C===CP    CL_SADL_GW_UI_MAP_DS_SADL_C===CM00B     2 |
|      CL_SADL_GW_UI_MAP_DS_SADL_C=>_ADD_COMPONENT_VIEW                                            |
|   19 METHOD       CL_SADL_GW_UI_MAP_DS_SADL_C===CP    CL_SADL_GW_UI_MAP_DS_SADL_C===CM008    11 |
|      CL_SADL_GW_UI_MAP_DS_SADL_C=>DO_SETUP_INSTANCE                                              |
|   18 METHOD       /IWBEP/CL_SBUI_VIEW===========CP    /IWBEP/CL_SBUI_VIEW===========CM003    58 |
|      /IWBEP/CL_SBUI_VIEW=>/IWBEP/IF_SBUI_COMMAND_HANDLER~EXECUTE_COMMAND                         |
|   17 METHOD       /IWBEP/CL_SBUI_SETUP==========CP    /IWBEP/CL_SBUI_SETUP==========CM00E    12 |
|      /IWBEP/CL_SBUI_SETUP=>/IWBEP/IF_SBUI_SETUP_FACTORY~CREATE_COMPONENT_VIEW                    |
|   16 METHOD       /IWBEP/CL_SBUI_SETUP==========CP    /IWBEP/CL_SBUI_SETUP==========CM00I    17 |
|      /IWBEP/CL_SBUI_SETUP=>CREATE_FRAMESET_EDITOR                                                |
|   15 METHOD       /IWBEP/CL_SBUI_SETUP==========CP    /IWBEP/CL_SBUI_SETUP==========CM00G    59 |
|      /IWBEP/CL_SBUI_SETUP=>/IWBEP/IF_SBUI_SETUP_FACTORY~CREATE_ELEMENT_EDITOR                    |
|   14 METHOD       /IWBEP/CL_SBUI_CONTROLLER=====CP    /IWBEP/CL_SBUI_CONTROLLER=====CM015    22 |
|      /IWBEP/CL_SBUI_CONTROLLER=>GET_ASSIGNED_EDIT_TOOL                                           |
|   13 METHOD       /IWBEP/CL_SBUI_CONTROLLER=====CP    /IWBEP/CL_SBUI_CONTROLLER=====CM00A    33 |
|      /IWBEP/CL_SBUI_CONTROLLER=>/IWBEP/IF_SBUI_CONTROLLER~ON_NAVIGATION_REQUESTED                |
|   12 METHOD       /IWBEP/CL_SBUI_DP_CMD_CREA_MA=CP    /IWBEP/CL_SBUI_DP_CMD_CREA_MA=CM001    53 |
|      /IWBEP/CL_SBUI_DP_CMD_CREA_MA=>DO_EXECUTE_COMMAND                                           |
|   11 METHOD       /IWBEP/CL_SBUI_COMMAND========CP    /IWBEP/CL_SBUI_COMMAND========CM002     4 |
|      /IWBEP/CL_SBUI_COMMAND=>/IWBEP/IF_SBUI_COMMAND_HANDLER~EXECUTE_COMMAND                      |
|   10 METHOD       /IWBEP/CL_SBUI_CONTROLLER=====CP    /IWBEP/CL_SBUI_CONTROLLER=====CM00E     9 |
|      /IWBEP/CL_SBUI_CONTROLLER=>HANDLE_COMMAND_OF_PLUGIN                                         |
|    9 METHOD       /IWBEP/CL_SBUI_CONTROLLER=====CP    /IWBEP/CL_SBUI_CONTROLLER=====CM00Y    97 |
|      /IWBEP/CL_SBUI_CONTROLLER=>HANDLE_COMMAND                                                   |
|    8 METHOD       /IWBEP/CL_SBUI_CONTROLLER=====CP    /IWBEP/CL_SBUI_CONTROLLER=====CM00C   138 |
|      /IWBEP/CL_SBUI_CONTROLLER=>/IWBEP/IF_SBUI_CONTROLLER~ON_COMMAND_REQUESTED                   |
|    7 METHOD       /IWBEP/CL_SBUI_SCREEN=========CP    /IWBEP/CL_SBUI_SCREEN=========CM001    18 |
|      /IWBEP/CL_SBUI_SCREEN=>ON_PAI_COMMAND                                                       |
|    6 MODULE (PAI) /IWBEP/SAPLFG_SBUI_SB_MAIN          /IWBEP/LFG_SBUI_SB_MAINI01             14 |
|      PAI_0100_COMMAND                                                                            |
|    5 METHOD       /IWBEP/SAPLFG_SBUI_SB_MAIN          /IWBEP/LFG_SBUI_SB_MAINCI1             34 |
|      LCL_SCREEN_0100=>DO_CALL_SCREEN                                                             |
|    4 METHOD       /IWBEP/CL_SBUI_SCREEN=========CP    /IWBEP/CL_SBUI_SCREEN=========CM003    17 |
|      /IWBEP/CL_SBUI_SCREEN=>START_SCREEN                                                         |
|    3 METHOD       /IWBEP/CL_SBUI_CONTROLLER=====CP    /IWBEP/CL_SBUI_CONTROLLER=====CM00U    50 |
|      /IWBEP/CL_SBUI_CONTROLLER=>START_SCREEN                                                     |
|    2 METHOD       /IWBEP/CL_SBUI_CONTROLLER=====CP    /IWBEP/CL_SBUI_CONTROLLER=====CM004    33 |
|      /IWBEP/CL_SBUI_CONTROLLER=>/IWBEP/IF_SBUI_SERVICE_BUILDER~START                             |
|    1 EVENT        /IWBEP/R_SBUI_SERVICE_BUILDER       /IWBEP/R_SBUI_SERVICE_BUILDER          19 |
|      START-OF-SELECTION                                                                          |
Thanks,
Girdhari

Short Dump while executing New Hire (action type) in PA40

Hi All,
i am getting short dump while executing PA40 for new hire action type can anyone look into this and guide as i am new to HCM.
Category               ABAP Programming Error
Runtime Errors         SYNTAX_ERROR
ABAP Program           /1PAPAXX/HDR_21000A
Application Component Not Assigned
Date and Time          21.08.2014 14:07:03
Short text
    Syntax error in program "/1PAPAXX/HDR_21000A ".
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPFP50M" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "/1PAPAXX/HDR_21000A " in
    include "/1PAPAXX/HDR_21000AO01 " in
    line 52:
    ""LV_LENGTH" has already been declared"
    The include has been created and last changed by:
    Created by: "HCM04 "
    Last changed by: "HCM03 "
    Error in the ABAP Application Program
    The current ABAP program "SAPFP50M" 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 "/1PAPAXX/HDR_21000A ".
    You can also perform the syntax check from the ABAP Editor.
    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 look
    at and manage termination messages, and you can also
    keep them for a long time.
Error analysis
    The following syntax error was found in the program /1PAPAXX/HDR_21000A :
    ""LV_LENGTH" has already been declared"
How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
System environment
    SAP Release..... 731
    SAP Basis Level. 0007
    Application server... "dc-ds-erp"
    Network address...... "172.16.23.111"
    Operating system..... "Linux"
    Release.............. "3.0.13-0.27-default"
    Hardware type........ "x86_64"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 1
    Shortdump setting.... "full"
    Database server... "dc-ds-erp"
    Database type..... "ORACLE"
    Database name..... "ECD"
    Database user ID.. "SAPSR3"
    Terminal.......... "NLC-HP"
    Char.set.... "C"
    SAP kernel....... 720
    created (date)... "Sep 14 2013 06:16:24"
    create on........ "Linux GNU SLES-11 x86_64 cc4.3.4 use-pr130820"
    Database version. "OCI_112, 11.2.0.3.0, V1, default"
    Patch level. 500
    Patch text.. " "
    Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"
    SAP database version. 720
    Operating system..... "Linux 2.6, Linux 3"
    Memory consumption
    Roll.... 0
    EM...... 37708200
    Heap.... 0
    Page.... 106496
    MM Used. 4666776
    MM Free. 3709976
User and Transaction
    Client.............. 210
    User................ "HCM03"
    Language key........ "E"
    Transaction......... "PA40 "
    Transaction ID...... "53EF470299AB5D67E1000000AC10176F"
    EPP Whole Context ID.... "005056A301D11EE48A9D08B337F884E3"
    EPP Connection ID....... 00000000000000000000000000000000
    EPP Caller Counter...... 0
    Program............. "SAPFP50M"
    Screen.............. "MP000000 1000"
    Screen Line......... 3
    Debugger Active..... "none"
Information on where terminated
    Termination occurred in the ABAP program "SAPFP50M" - in
    "GET_HEADER_WITH_TCLAS".
    The main program was "MP000000 ".
    In the source code you have the termination point in line 146
    of the (Include) program "FP50MDHD".
Source Code Extract
Line
SourceCde
116
CALL FUNCTION 'HR_HEADER_GET'
117
      EXPORTING
118
           DHDID                    = FHD_HID
119
           BEGDA                    = BEGDA
120
           TCLAS                    = TCLAS
121
* Es wird nur einer der folgenden 3 Parameter benutzt.
122
* Ausgewertet wird zunaechst MOLGA, dann P0001 dann PERNR.
123
* Der erste der nicht initial ist wird ausgewertet.
124
*           MOLGA                   =
125
           P0001                    = P0001
126
           PERNR                    = PSPAR-PERNR
127
      IMPORTING
128
           PROG                     = HEADER_PROG
129
           DNUM                     = HEADER_DYNNR
130
       EXCEPTIONS
131
            HEADER_DEACTIVATED          = 1
132
            HEADER_UNKNOWN              = 2
133
            HEADER_GENERATE_DEACTIVATED = 3
134
            HEADER_GENERATE_FAILED      = 4
135
            INTERNAL_ERROR              = 5
136
            OTHERS                      = 6.
137
138
IF NOT SY-SUBRC IS INITIAL.
139
* Bei Problemen gibt's eben ein leeres Dynpro.
140
    HEADER_PROG = 'SAPMP50A'.
141
    HEADER_DYNNR = '0090'.
142
ELSE. " NOT sy-subrc IS INITIAL.                                   "
143
* Dann setzen wir jetzt auch noch das Datum fest.
144
    PERFORM HEADER_BEGDA_SET IN PROGRAM (HEADER_PROG) USING BEGDA.
145
* Und schalten auf Uebergabe der PERNR mit globalen Variablen.
>>>>>
    PERFORM HEADER_LAZY_ON IN PROGRAM (HEADER_PROG).
147
ENDIF. " (ELSE) NOT sy-subrc IS INITIAL.                           "
148
* Merken wie der Header heisst. Damit MPPERS00 sich erinnern kann.

Hi,
Error Log: Syntax error
""LV_LENGTH" has already been declared"
please check LV_LENGTH variable declaration.
It may be declared more once!

Short dump while executing info package in 3.5 data flow?

Hi,
i am getting short dump while executing info package while executing info package. it was working perfectly 2 days back suddenly it is giving this problem. it is a full load for info object text data and i have only 600 records. when i tried with " only info package" it is working perfectly n bringing the data into PSA. But when i use "PSA and the into data target" it is giving short dump.
i replicated Data source and also i activated transfer rules, update rules still it is not working. When i check with another info objects it is working perfectly fine. i dont know what is wrong with only particular info object.
Please find attached short dump.
Thanks

Hi,
When you load transaction data I think there is a deadlock.
Check in the process overview (transaction SM50) the waiting processes are in program SAPLSENA .
The program SAPLSENA is the lock handler tool.
Also check if ACR is running on this target while your load is happening.
Check in SM12 if there are any lock entries for the Infoobject to which you are loading data and on RSICCONT table .
Try reloading after deleting the locks manually.
Regards.

Dump while executing FM based Gen extractor

Hi,
I am getting a dump while executing the FM based extractor in RSA3.
below is the dumps error analysis-
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_FUNC', was
     not caught in
    procedure "RSA3_GET_DATA_SIMPLE" "(FUNCTION)", 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:
    The program "SAPLRSA3" contains the CALL FUNCTION statement.
    The name of the function module to be called is "ZZRSAX_BIW_GET_DATA_SIMPLE".
    but "ZZRSAX_BIW_GET_DATA_SIMPLE" cannot be found in its function group.
    Possible reasons:
    a) The function module "ZZRSAX_BIW_GET_DATA_SIMPLE" has not been activated.
     Therefore,
       it cannot be found at runtime.
    b) The Function Library contains an incorrect entry for
     "ZZRSAX_BIW_GET_DATA_SIMPLE".
    c) The function module contains no code, even FUNCTION ... ENDFUNCTION
       is missing.
Pls tell me if u need the FM code or anything else...
Thanks in advance,
sandy,

And this is the FM...which was written
Pls tell me if i am missing anything?
Example: DataSource for table SFLIGHT
TABLES: vbak, vbap.
Auxiliary Selection criteria structure
DATA: L_S_SELECT TYPE SRSC_S_SELECT.
Maximum number of lines for DB table
STATICS: S_S_IF TYPE SRSC_S_IF_SIMPLE,
counter
          S_COUNTER_DATAPAKID LIKE SY-TABIX,
cursor
          S_CURSOR TYPE CURSOR.
Select ranges
RANGES: L_R_VBELN FOR VBAK-VBELN,
          L_R_AUDAT FOR VBAK-AUDAT,
          L_R_POSNR FOR VBAP-POSNR.
Initialization mode (first call by SAPI) or data transfer mode
(following calls) ?
IF I_INITFLAG = SBIWA_C_FLAG_ON.
Initialization: check input parameters
                buffer input parameters
                prepare data selection
Check DataSource validity
    CASE I_DSOURCE.
      WHEN 'ZSALES_DS'.
      WHEN OTHERS.
        IF 1 = 2. MESSAGE E009(R3). ENDIF.
this is a typical log call. Please write every error message like this
        LOG_WRITE 'E'                  "message type
                  'R3'                 "message class
                  '009'                "message number
                  I_DSOURCE   "message variable 1
                  ' '.                 "message variable 2
        RAISE ERROR_PASSED_TO_MESS_HANDLER.
    ENDCASE.
    APPEND LINES OF I_T_SELECT TO S_S_IF-T_SELECT.
Fill parameter buffer for data extraction calls
    S_S_IF-REQUNR    = I_REQUNR.
    S_S_IF-DSOURCE = I_DSOURCE.
    S_S_IF-MAXSIZE   = I_MAXSIZE.
Fill field list table for an optimized select statement
(in case that there is no 1:1 relation between InfoSource fields
and database table fields this may be far from beeing trivial)
    APPEND LINES OF I_T_FIELDS TO S_S_IF-T_FIELDS.
ELSE.                 "Initialization mode or data extraction ?
Data transfer: First Call      OPEN CURSOR + FETCH
               Following Calls FETCH only
First data package -> OPEN CURSOR
    IF S_COUNTER_DATAPAKID = 0.
Fill range tables BW will only pass down simple selection criteria
of the type SIGN = 'I' and OPTION = 'EQ' or OPTION = 'BT'.
      LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'VBELN'.
        MOVE-CORRESPONDING L_S_SELECT TO L_R_vbeln.
        APPEND L_R_vbeln.
      ENDLOOP.
      LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'POSNR'.
        MOVE-CORRESPONDING L_S_SELECT TO L_R_posnr.
        APPEND L_R_posnr.
      ENDLOOP.
Determine number of database records to be read per FETCH statement
from input parameter I_MAXSIZE. If there is a one to one relation
between DataSource table lines and database entries, this is trivial.
In other cases, it may be impossible and some estimated value has to
be determined.
      OPEN CURSOR WITH HOLD S_CURSOR FOR
      SELECT vbakvbeln vbakaudat vbakaugru vbakkunnr vbakvkbur vbakawahr
             vbakkvgr1 vbapvbeln vbapposnr vbapmatnr vbapkwmeng vbapvrkme
             vbapnetwr vbapwaerk
             FROM vbak INNER JOIN vbap ON vbakvbeln = vbapvbeln
             WHERE vbak~vbeln IN L_R_VBELN AND
                   vbap~posnr IN L_R_posnr.
    ENDIF.                             "First data package ?
Fetch records into interface table.
named E_T_'Name of extract structure'.
    FETCH NEXT CURSOR S_CURSOR
               APPENDING CORRESPONDING FIELDS
               OF TABLE E_T_DATA
               PACKAGE SIZE S_S_IF-MAXSIZE.
    IF SY-SUBRC <> 0.
      CLOSE CURSOR S_CURSOR.
      RAISE NO_MORE_DATA.
    ENDIF.
    S_COUNTER_DATAPAKID = S_COUNTER_DATAPAKID + 1.
ENDIF.              "Initialization mode or data extraction ?
ENDFUNCTION.

Getting Shor Dump while DSO Activation

Similar Messages

Maybe you are looking for