System Throws short dump while executing data source 2LIS_11_VASCL in RSA3.

Hello Experts,
I got short dump while executing data source 2LIS_11_VASCL in RSA3.
The details are as follow.
When importing object "MC11VA0SCL_TAB", the structure did not match the
structure of the target object. The error occurred in component
no. 567.
This may be due to one of the following reasons:
- the structure is actually different (the next field has, for
example, a different data type) or
- the same sequence of components were exported and imported,
but the fields were from other include units.
I have checked source and target fields and those are of same length and data type.
Could you please give some points why this short dump occurs.
Thanks
Konda Reddy

Hi,
This error is not between BI and R/3. It is within R/3. You may have setup data and then modified the datasource.
Delete setup data, generate your datasource again. Setup data and try again.
If you are on a live system with data setup after a downtime and you do not want to delete it, then bring your datasource to the original state when you setup data and pull data.
Cheers....

Similar Messages

Short dump while generating data sources

Hi all,
I've created a source system for MSSQL database. Now, when I'm trying to Generate the Data Source from SQL into BW using 'Select database tables' option in the Source system and execute it for a table (SAMTEST) in the SQL database, the program terminates with a dump as follows.
Error in ABAP application program.
The current ABAP program "RSDL_META_UPLOAD" had to be terminated because one of
the
statements could not be executed.
This is probably due to an error in the ABAP program.
In program "SAPLRSDBC ", the following syntax error occurred
in the Include "LRSDBCO01 " in line 58:
"The field "RSDBC_C_RSADMIN" is unknown, but there are the following fi"
"elds with similar names: "RS_C_RSADMIN" and "RSDRO_C_RSADMINA"."
Author and last person to change the Include are:
Author "SAP "
Last changed by "SAP "                                                -
I think I've missed some custom settings to be done. I'm clueless. Can anyone help in this regard.
Thanks in advance,
Sam

This is a bug in the code. Check oss note 729243 -
"Symptom
The attempt to load data from an external database results in a runtime error with a syntax error in the SAPLRSDBC program.
Other terms
DB Connect, DBC, DBC SYNTAX_ERROR, dump, short dump
Reason and Prerequisites
This is due to a program error.
The LRSDBCO01 include is inconsistent in the corrections of the currency translation for DB Connect in BW 3.5 Support Package 13. This results in the dump with a syntax error in the SAPLRSDBC program.

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.

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 DTP.

Hi Gurus,
I have got a short dump while executing DTP the Error is as Follows.
Runtime Error: MESSAGE_TYPE_X.
Reasons for Error: 1.The installation of the SAP GUI on the present server is faulty or obselete
2.There is a error in the application program
And i have sent the sreen shot of the Short Dump to BASIS TEAM and they have replied me that they have to install some patches and it will take some time.
But i have no much time and i have to someway or the other execute the DTP and load the data.
Is there any shortcuts for this i mean to say without the involvement of Basis team that i can do in th BI System
Regards
Amar.

Hi Amar,
If the problem is with with System itself, how can we all have a short cut in that case. You may give it another trial, but you have to wait for the patches to be applied. Ask your basis team to get it done ASAP.
Thanks..
Shambhu

Regarding Short Dump While loading data from DB Connect

Dear All,
We are having an issue of getting short dump while loading data from DB Connect to BW. We were able to load the data into BW Dev using the same data source without any problem. Whereas in Production, I am getting the following error:
Runtime Error PERFORM_CONFLICT_TAB_TYPE
Except. CX_SY_DYN_CALL_ILLEGAL_TYPE
What could be the reason for the error that I am getting

hi,
Refer Note 707986 - Writing in trans. InfoCubes: PERFORM_CONFLICT_TAB_TYPE
Summary
Symptom
When data is written to a transactional InfoCube, the termination PERFORM_CONFLICT_TAB_TYPE occurs. The short dump lists the following reasons for the termination:
("X") The row types of the two tables are incompatible.
("X") The table keys of the two tables do not correspond.
Other terms
transactional InfoCube, SEM, BPS, BPS0, APO
Reason and Prerequisites
The error is caused by an intensified type check in the ABAP runtime environment.
Solution
Workaround for BW 3.0B (SP16-19), BW 3.1 (SP10-13)
Apply the attached correction instructions.
BW 3.0B
Import Support Package 20 for 3.0B (BW3.0B Patch20 or SAPKW30B20) into your BW system. The Support Package is available oncenote 0647752 with the short text "SAPBWNews BW3.0B Support Package 20", which describes this Support Package in more detail, has been released for customers.
BW 3.10 Content
Import Support Package 14 for 3.10 (BW3. 10 Patch14 or SAPKW31014) into your BW system. The Support Package is available once note 0601051 with the short text "SAPBWNews BW 3.1 Content Support Package 14" has been released for customers.
BW3.50
Import Support Package 03 for 3.5 (BW3.50 Patch03 or SAPKW35003) into your BW system. The Support Package is available once note 0693363 with the short text "SAPBWNews BW 3.5 Support Package 03", which describes this Support Package in more detail, has been released for customers.
The notes specified may already be available to provide advance information before the Support Package is released. However, in this case, the short text still contains the term "Preliminary version" in this case.
Header Data
Release Status: Released for Customer
Released on: 18.02.2004 08:11:39
Priority: Correction with medium priority
Category: Program error
Primary Component: BW-BEX-OT-DBIF Interface to Database
Secondary Components: FIN-SEM-BPS Business Planning and Simulation
Releases
Software
Component Release From
Release To
Release And
subsequent
SAP_BW 30 30B 30B
SAP_BW 310 310 310
SAP_BW 35 350 350
Support Packages
Support
Packages Release Package
Name
SAP_BW_VIRTUAL_COMP 30B SAPK-30B20INVCBWTECH
Related Notes
693363 - SAPBWNews BW SP03 NW'04 Stack 03 RIN
647752 - SAPBWNews BW 3.0B Support Package 20
601051 - SAPBWNews BW 3.1 Content Support Package 14
Corrections Instructions
Correction
Instruction Valid
from Valid
to Software
Component Ref.
Correction Last
Modifcation
301776 30B 350 SAP_BW J19K013852 18.02.2004 08:03:33
Attributes
Attribute Value
weitere Komponenten 0000031199
Thanks
(Activate ODS/Cube and Transfer rules again..)

Short dump while executing few queries , which has got created on Infoset.

Hi,
We went to BI7.0 upgrade from BW3.x now.
We are getting short dump short dump while executing few queries and work book, which has got created on Infoset.
When i was executing work book where i was geting popup message saying that "Erro ZSD_XST_F00121 is invalid".When i click that message it went to dump.
I was getting this error while executing query on infoset.
We are currently SP Stack 13(Patch level 15).
I found some note 1067918 as per the shortdum,where it is saying that you need to apply SP Stack14(patch level16).
Please some one who had earlier this kind of issue.
I appreciate your answer.

Dear Krish,
Yes, It is the patch problem.
We too faced the same issue on Infosets.
Apply SP 15.
Regards,
Ram.

Short Dump while executing ALV Grid.

Hi All,
I m getting a short dump while trying to execute an ALV.
The dump exception is of type
CX_SY_DYN_CALL_ILLEGAL_TYPE class.
The message displayed is : " Call to form 'GI_FIELDCAT' is incorrect .The actual parameter in PERFORM is different data type than requested for form GI_FIELDCAT " .
The part of programe included is as follows:
FORM build_fieldcat .
    PERFORM gi_fieldcat USING 'MBLNR' text-014 '1' '20'.
    PERFORM gi_fieldcat USING 'ZEILE' text-005 '2' '4'.
    PERFORM gi_fieldcat USING 'MATNR' text-006 '3' '18'.
    PERFORM gi_fieldcat USING 'MAKTX' text-028 '4' '40'.
    PERFORM gi_fieldcat USING 'MATKL' text-029 '5' '40'.
    PERFORM gi_fieldcat USING 'BUDAT' text-027 '6' '10'.
    PERFORM gi_fieldcat USING 'MENGE' text-026 '7' '9'.
    PERFORM gi_fieldcat USING 'DMBTR' text-025 '8' '13'.
    PERFORM gi_fieldcat USING 'WAERS' text-011 '9' '5'.
    PERFORM gi_fieldcat USING 'RSNUM' text-012 '10' '10'.
    PERFORM gi_fieldcat USING 'PSPHI' text-013 '11' '10'.
ENDFORM.                    " build_fieldcat
FORM gi_fieldcat USING    fieldname TYPE slis_fieldcat_alv-fieldname
                           colmname TYPE slis_fieldcat_alv-seltext_m
                           colmpos   TYPE slis_fieldcat_alv-col_pos
                           outputlen TYPE slis_fieldcat_alv-outputlen.
wa_fieldcat-fieldname   = fieldname.
wa_fieldcat-seltext_m   = colmname.
wa_fieldcat-col_pos     = colmpos.
wa_fieldcat-outputlen   = outputlen.
wa_fieldcat-
APPEND wa_fieldcat TO it_fieldcat.
CLEAR wa_fieldcat.
ENDFORM.                    " gi_fieldcat
Can ayone gimmi a solution for the same.

Hi,
Try to change ur code like the below.
Attached: sample code
Building field catalog
PERFORM modify_catlog USING:
'GT_OUTPUT' 'AUART' text-t02 '1',
'GT_OUTPUT' 'KUNNR' text-t03 '2',
'GT_OUTPUT' 'NAME'   text-t04 '3',
'GT_OUTPUT' 'KWMENG' text-t05 '4',
'GT_OUTPUT' 'VRKME' text-t06 '5',
'GT_OUTPUT' 'LFIMG' text-t07 '6',
'GT_OUTPUT' 'GEWEI' text-t08 '7',
'GT_OUTPUT' 'VOLUM' text-t09 '8',
'GT_OUTPUT' 'VOLEH' text-t10 '9',
'GT_OUTPUT' 'BRGEW' text-t11 '10',
'GT_OUTPUT' 'UOMGW' text-t12 '11',
'GT_OUTPUT' 'VARCE' text-t13 '12',
'GT_OUTPUT' 'UOMVR' text-t14 '13'.
FORM modify_catlog USING    pa_tabname TYPE string
                            pa_field   TYPE string
                            pa_text    TYPE string
                            pa_pos     TYPE string.
CLEAR gs_fieldcatalog.
*Modifying field catalog
gs_fieldcatalog-col_pos = pa_pos.
gs_fieldcatalog-fieldname = pa_field.
gs_fieldcatalog-tabname = pa_tabname.
gs_fieldcatalog-seltext_m = pa_text.
APPEND gs_fieldcatalog TO gt_fieldcatalog.
CLEAR gs_fieldcatalog.
l_repid = sy-repid.
To call function to display ALV output
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
       EXPORTING
            i_callback_program = l_repid
            it_fieldcat        = gt_fieldcatalog
                 TABLES
            t_outtab           = gt_output
       EXCEPTIONS
            program_error      = 1
            OTHERS             = 2.
IF sy-subrc <> 0.
    MESSAGE e000 WITH text-t16.
ENDIF.
Reward if helpful.
Regards,
Ramya

Short dump while executing job SM:EXEC SERVICES for EWA alert generation

Hello All,
I'm getting short dump error while executing job SM:EXEC SERVICES for EWA alert generation.I'm using EHP1@SP22 of Sol Man.
Please find the logs
Error in the ABAP Application Program
The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "RDSVASCABAP_TRANS__________073
" in include "RDSVASIABAP_TRANS__________073 " in
line 1782:
"Field "STATEMENT_SUMMARY001019" is unknown. It is neither in one of th"
"e specified tables nor defined by a "DATA" statement. "DATA" statement"
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 "SAPLDSVAS_PROC" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
If anyone came across such kind of dump, please reply asap, due to this, i could not generate EWA report for R/3 system 6.04.
Thanks,
Anand.

>
Anand Tigadikar wrote:
> Thx Paul, but i already did checked this note and its not solving my issue
Dear Anand,
Did you perform a complete service definition replacement for SDCC/SDCCN as described in the note?
These are manual steps you need to perform on the system and are not code corrections.
I would suggest you perform it, if you have not, and check the SDCCN logs to review the process ran cleanly.
Note: Please make sure SDCC_OSS is functioning and a connection to SAP can be made before
deleting the service definitions.
If you have already replaced the service defintions on the Solution Manager system, then no point doing it again. However checking a note and applying it are not the same thing. So I am uncertain if you replaced the service definitions or not. The dump you are getting in SM:EXEC SERVICES suggests its due to a problem with the service definitons. The recommendation is to replace them according to the process described in SAP Note 727998. If you have not done so please do so.
If you have successfully replaced the service definitions are you still getting the same dump, or has it possibly changed?
Regards,
Paul

DBIF_REPO_SQL_ERROR short dumps while activating data in ODS

Hi All,
We are using BW3.5 with Oracle 9.2 on AIX 5.3 box, from the past few days we are getting DBIF_REPO_SQL_ERROR short dumps frequently while activating data in ODS.
Runtime Error          DBIF_REPO_SQL_ERROR
Date and Time          08.01.2008 13:01:08
     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.
     Internal call code.........: "[REPO/*/43/LOAD/CX_SY_OPEN_SQL_DB=============CP
     Please check the entries in the system log (Transaction SM21).
     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:
     "DBIF_REPO_SQL_ERROR" C
     "SAPLRSSM_PROCESS" or "LRSSM_PROCESSF04"
     "CHECK_IF_ANALYZE_IS_NESSESSARY"
System environment
    SAP Release.............. "640"
    Application server....... "psapdb"
    Network address.......... "158.58.65.11"
    Operating system......... "AIX"
    Release.................. "5.3"
    Hardware type............ "00CD615C4C00"
    Character length......... 16 Bits
    Pointer length........... 64 Bits
    Work process number...... 22
    Short dump setting....... "full"
    Database server.......... "psapdb"
    Database type............ "ORACLE"
    Database name............ "BWP"
    Database owner........... "SAPBWP"
    Character set............ "C"
    SAP kernel............... "640"
    Created on............... "Oct 29 2006 20:49:57"
    Created in............... "AIX 1 5 00538A4A4C00"
    Database version......... "OCI_920 "
    Patch level.............. "155"
    Patch text............... " "
    Supported environment....
    Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
     10.2.0.."
    SAP database version..... "640"
Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
Memory usage.............
Roll..................... 16192
EM....................... 16759424
Heap..................... 0
Page..................... 24576
MM Used.................. 6604384
MM Free.................. 1772536
SAP Release.............. "640"
User and Transaction
    Client.............. 200
    User................ "R3REMOTE"
    Language key........ "E"
    Transaction......... " "
    Program............. "SAPLRSSM_PROCESS"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
Information on where terminated
    The termination occurred in the ABAP program "SAPLRSSM_PROCESS" in
     "CHECK_IF_ANALYZE_IS_NESSESSARY".
    The main program was "RSPROCESS ".
    The termination occurred in line 1143 of the source code of the (Include)
     program "LRSSM_PROCESSF04"
    of the source code of program "LRSSM_PROCESSF04" (when calling the editor
     11430).
    The program "SAPLRSSM_PROCESS" was started as a background job.
    Job name........ "BI_PROCESS_ODSACTIVAT"
    Job initiator... "RPRIYANKA"
    Job number...... 02010102
Also we have a failed job here. Here is the job log.
Job log overview for job:    BI_PROCESS_ODSACTIVAT / 02010102
Date       Time     Message text
08.01.2008 13:01:00 Job started
08.01.2008 13:01:00 Step 001 started (program RSPROCESS, variant &0000000000188, user ID R3REMOTE)
08.01.2008 13:01:02 Activation is running: Data target HBCS_O25, from 1,758 to 1,767
08.01.2008 13:01:02 Data to be activated successfully checked against archiving objects
08.01.2008 13:01:02 SQL: 01/08/2008 13:01:02 R3REMOTE
08.01.2008 13:01:02 ANALYZE TABLE "/BIC/AHBCS_O2540" DELETE
08.01.2008 13:01:02 STATISTICS
08.01.2008 13:01:02 SQL-END: 01/08/2008 13:01:02 00:00:00
08.01.2008 13:01:02 SQL: 01/08/2008 13:01:02 R3REMOTE
08.01.2008 13:01:02 BEGIN DBMS_STATS.GATHER_TABLE_STATS ( OWNNAME =>
08.01.2008 13:01:02 'SAPBWP', TABNAME => '"/BIC/AHBCS_O2540"',
08.01.2008 13:01:02 ESTIMATE_PERCENT => 1 , METHOD_OPT => 'FOR ALL
08.01.2008 13:01:02 INDEXED COLUMNS SIZE 75', DEGREE => 1 ,
08.01.2008 13:01:02 GRANULARITY => 'ALL', CASCADE => TRUE ); END;
08.01.2008 13:01:05 SQL-END: 01/08/2008 13:01:05 00:00:03
08.01.2008 13:01:05     SQL-ERROR: 603 ORA-00603: ORACLE server session terminated by fat al error
08.01.2008 13:01:05 System error: RSDU_ANALYZE_TABLE_ORA/ ORACLE
08.01.2008 13:01:08 ABAP/4 processor: DBIF_REPO_SQL_ERROR
08.01.2008 13:01:08 Job cancelled
Listener is working fine, Checked the RFC connections, Tried restarting the system, tried adding space to the TEMP tablespace as well as PSAPBWP, but they didn't work.
Please help.

The problem got solved as there were DB errors like ORA-01114: IO error writing block to file 256 (block # 126218).
Here the point to be notes is file 256. The number greater than 255 indicates a temp datafile. This indicates an issue with PSAPTEMP tablespace. When checked on PSAPTEMP tablespace, one of the filesystems where one temp data file sitting was full. The filesystem was 100% full. This will prevent the temp datafile to grow and shrink as and when required.
So, adding more space to the filesystem solved the problem.
Thanks to everyone who have shown interest in solving my problem.

SEM-BCS Short Dump while executing Manual Posting Task

Hi SEM-BCS Colleagues,
I am having a peculiar problem with relation to the settings for Manual Postings. I have three scenarios for which I have defined manual document types and tasks 1) Standardizing Entry (Data Collection) 2) Manual Document in IU for adjustment 3) COI Group level manual postings. I am just creating and not changing any settings for document field properties also. I have configured monthly consolidation frequency and period category and I am posting document type 1 in Local Currency and 2 and 3 in Group Currency since they are after currency translation.
Have any of you faced similar problem and help me please?

Hello,
I am also getting short dump during data collection in BCS.
we recently upgraded the system to SP20. Is it anyway related to upgrade.
I also checked the MYSELF as a source system, but not found one.
Could you please let me know how you have solved this issue.
short dump:
Runtime Errors         PERFORM_TOO_MANY_PARAMETERS
Exception              CX_SY_DYN_CALL_PARAM_NOT_FOUND
Date and Time          04.12.2009 05:21:11
Short text
     Too many parameters specified with PERFORM.
What happened?
     In a subroutine call, there were more parameters than in the
     routine definition.
     Error in the ABAP Application Program
     The current ABAP program "SAPLRSDRI" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
Error analysis
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_DYN_CALL_PARAM_NOT_FOUND', was
      not caught in
     procedure "RSDRI_CUBE_WRITE_PACKAGE_RFC" "(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:
     A PERFORM was used to call the routine "CUBE_WRITE_PACKAGE" of the program
      "GPD1S8520HM8UV0U2XBDVPADF03".
     This routine contains 7 formal parameters, but the current call
     contains 10 actual parameters.

Short dump while executing the DTP

Dear Experts,
While executing the DTP the system is generated short dump and it is Quality server not in Development system.
The error details are in method Calculate_keyfigure_ds and the data is loaded for IS retails from POSDM.
The error details:
"The MOVE-CORRESPONDING statement can only be used on operands with a
structured type.
In the case at hand, this condition is not fulfilled: Operand "<L_STRUC>" has
the type "C"."
Regards,
Amit

Hi Amit ,
Move corresponding statements can be used for structures only and from the error message it seems that there is datatype mismatch.
Check for the errors ion link :
http://help.sap.com/abapdocu/en/ABAPMOVE-CORRESPONDING.htm
Hope it helps ,
Regards,
Supriya

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 extracting data

Hi,
When i extract the data from the datasource 2lis_05_item in rsa3 i m getting the following short dump. Can anyone tell what to do in this case?
Runtime Errors         CONNE_IMPORT_WRONG_STRUCTURE
Exceptn                CX_SY_IMPORT_MISMATCH_ERROR
Date and Time          06.12.2006 09:42:15
ShrtText
     Error when importing object "MC05Q00ITM_TAB".
What happened?
     Error in ABAP application program.
     The current ABAP program "SAPLMCEX" had to be terminated because one of t
     statements could not be executed.
     This is probably due to an error in the ABAP program.
     When attempting to import data, the
     structure of the complex object "MC05Q00ITM_TAB" was not compatible with
     target object.
Error analysis
     An exception occurred. This exception is dealt with in more detail below
     . The exception, which is assigned to the class 'CX_SY_IMPORT_MISMATCH_ER
      was neither
     caught nor passed along using a RAISING clause, in the procedure
      "MCEX_BW_LO_API" "(FUNCTION)"
     Since the caller of the procedure could not have expected this exception
      to occur, the running program was terminated.
     The reason for the exception is:
     When attempting to import data, the structure of the complex object
      "MC05Q00ITM_TAB"
     was not compatible with the target object. The error occurred with
component no. 32.
sing RAISING Clause in Interface
Program                                 SAP
Include                                 LMC
Row                                     5
Module type                             (FU
Module Name                             MCE
gger Location of Exception
Program                                 SAP
Include                                 LMC
Row                                     241
Module type                             (FU
Module Name                             MCE
rce Code Extract
e SourceCde
11         endif.
12       enddo.
13     END-OF-DEFINITION.
14 ***** end macro *****

I suppose that you are doing enhancement to your datasource 2LIS_02_ITM
Have you done the following steps in the extractor:
1. Append the new field in MC02M_0ITM structure
2. Append the new field in MCEKPO structure
3. Use Tcode LBWE and expand the Purchsing to get 2LIS_02_ITM and click on the Datasource to uncheck the 'hide' and 'fields only'
4. Activate the data source, by using Tcode RSA5
3. After that I have make changes to the user-exit to add logic for the new field
Do remember to carry out the following steps before you modify the Extraction structure:
1. Make sure that the following steps are carried out at a time when no updates are performed so that no data is lost.
2. Start the update collective run directly from within the Customizing Cockpit. Up to PI(-A) 2001.2 , this collective run exclusively concerns the V3 update. As of PI(-A) 2002.1, depending on the update mode setting of the application, the collective run concerns either the V3 update or the update from the extraction queue ("Delta Queued", see Note 505700).
3. Load all data of the respective DataSource into the BW System.
Hope it helps.
regards
Vinod

Short dump while executing APD

Hi Experts,
We have a requirement to populate key and text values for 23 charecterstics in to a flat file. For this we have created a APD with query as source, This query will bring key values. And text values are populated using APD routine which will look up respective text tables and all the result data is downloaded in to a flat file.
When testing this APD i have come across a short dump, as all the charecterstics are placed in rows. Then i have applied static filters in the query for some of charecterstics and executed the APD. It worked. But if try to execute APD with no filters in the query it gives me short dump. Request you to suggest strategy which will avoid the short dump and improve the performance, where i can display all the 23 charecterstics key and text values.
Thanks in advance.

Hi Javed
Here are couple of things what you can try
- You can apply filters in the APD and split the data into small chunks and later collate the data into one final file, this can be done by decisions in APD
- There is a difference how you have created your query and applied the filters/restrictions,In case of 7x queries none of the filters should be in Default tabs and all of them should be in Filters tab only
- From my previous experiences I have seen that at times you add a dummy "Filter" type be applied in APD to avoid such issues, so give this a try as well
Thanks
Abhishek Shanbhogue

System Throws short dump while executing data source 2LIS_11_VASCL in RSA3.

Similar Messages

Maybe you are looking for