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.

Similar Messages

Short Dump in SAP BW Sys while extracting data from R/3

HI All,
I am getting short dump problem in sap bw while extracting the data from r/3 to bw info cube.
the error message is like this,
Runtime Error          DBIF_RSQL_SQL_ERROR
Except.                CX_SY_OPEN_SQL_DB
Date and Time          11.05.2011 09:36:51
ShrtText
An SQL error occurred when accessing a table.
What can you do?
Make a note of the actions and input which 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.
How to correct the error
Database error text........: "ORA-14400: inserted partition key does not map to
any partition"
Internal call code.........: "[RSQL/INSR//BIC/B0000115000 ]"
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_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC
"GPCX2UNC5JG556R7DPSFJUGJS1Z" or "GPCX2UNC5JG556R7DPSFJUGJS1Z"
|    "INSERT_ODS"
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.
The exception must either be prevented, caught within the procedure
"INSERT_ODS"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
System environment
SAP Release.............. "640"
Application server....... "bwdev"
Network address.......... "10.10.100.36"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "8x AMD64 Level"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "BWDEV"
Database type............ "ORACLE"
Database name............ "BWD"
Database owner........... "SAPR3"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Aug 17 2008 20:56:58"
Created in............... "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version......... "OCI_10201_SHARE "
Patch level.............. "247"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
10.2.0.."
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,
Windows NT 6.0"
Memory usage.............
Roll..................... 16128
EM....................... 6265200
Heap..................... 0
Page..................... 0
MM Used.................. 5972296
MM Free.................. 289384
SAP Release.............. "640"
User and Transaction
Information on where terminated
The termination occurred in the ABAP program "GPCX2UNC5JG556R7DPSFJUGJS1Z" in
"INSERT_ODS".
The main program was "SAPMSSY1 ".
The termination occurred in line 41 of the source code of the (Include)
program "GPCX2UNC5JG556R7DPSFJUGJS1Z"
of the source code of program "GPCX2UNC5JG556R7DPSFJUGJS1Z" (when calling the
editor 410).
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "INSERT_ODS" "(FORM)" but was not handled locally, not declared in
the
RAISING clause of the procedure.
The procedure is in the program "GPCX2UNC5JG556R7DPSFJUGJS1Z ". Its source code
starts in line 21
|    of the (Include) program "GPCX2UNC5JG556R7DPSFJUGJS1Z ".

Hi,
This error occurs if you want to insert an entry in the table that does not match the value range of any partition. In such a case, you must compare the value of the entry with the definitions of the partitions to determine the cause of the error.
please run the following test/repair in transaction RSRV ,
RSRV -> All Elementary Test -> PSA Tables -> Consistency Between PSA Partitions and SAP Administration Information
-> include the PSA table
    /BIC/B0000115000
Check OSS note 339896 which explains the repair procedure.
Regards,
Lokesh

Short Dump:DBIF_RSQL_SQL_ERROR; Exception :CX_SY_OPEN_SQL_DB

Hi All,
I am getting the below short when i try to load the data into BI system. when I start the Info Package, it is immediately going to this short dump.
Runtime Errors         DBIF_RSQL_SQL_ERROR
Except.                CX_SY_OPEN_SQL_DB
Date and Time          15.12.2011 02:43:18
Short text
SQL error in the database when accessing a table.
Please find the short dump details below.
Runtime Errors         DBIF_RSQL_SQL_ERROR
Except.                CX_SY_OPEN_SQL_DB
Date and Time          15.12.2011 02:43:18
Short text
     SQL error in the database when accessing a table.
Missing RAISING Clause in Interface
     Program                                 SAPLBTCH
     Include                                 LBTCHFXX
     Row                                     1.525
     Module type                             (FORM)
     Module Name                             STORE_NEW_STEPLIST_IN_DB
Trigger Location of Exception
     Program                                 SAPLBTCH
     Include                                 LBTCHFXX
     Row                                     1.652
     Module type                             (FORM)
     Module Name                             STORE_NEW_STEPLIST_IN_DB
Source Code Extract
Line SourceCde
1622              ID 'DATA' FIELD jobinfo_egj.
1623
1624           rc = 1.
    EXIT.
ELSE.
    db_steplist-priparkey = tmp_key.
ENDIF.
ENDIF.
SEIF new_steplist-typ = btc_xcmd." Step executes external command
db_steplist-extcmd = new_steplist-program.
db_steplist-xpgparams = new_steplist-parameter.
db_steplist-xpgflag = 'X'.
SE. " Step führt ein externes Programm aus
db_steplist-xpgprog   = new_steplist-program.
db_steplist-xpgparams = new_steplist-parameter.
db_steplist-xpgflag   = 'X'.
DIF.
steplist-sdldate = newjob_head-sdldate.
steplist-sdltime = newjob_head-sdltime.
steplist-sdluname = newjob_head-sdluname.
PEND db_steplist.
ep_count = step_count + 1.
OOP.
liste in DB speichern
RT tbtcp FROM TABLE db_steplist ACCEPTING DUPLICATE KEYS."n952782
y-subrc NE 0.
dialog EQ btc_yes.
MESSAGE s120 WITH new_job_head-jobname.
ENDIF.
CONCATENATE new_job_head-jobname new_job_head-jobcount INTO
jobinfo_egj SEPARATED BY '/'.
CALL 'C_WRITE_SYSLOG_ENTRY' ID 'TYP' FIELD ' '
        ID 'KEY' FIELD tbtcp_insert_db_error
        ID 'DATA' FIELD jobinfo_egj.
rc = 1.
EXIT.
ENDIF.
rc = 0.
DFORM.                               " STORE_NEW_STEPLIST_IN_DB
I would like to know where exactly it is getting error. Please help me on this.
Regards,
Venkat.

Hi,
Check following
See the OSS Notes:
Note 1379839 - RuntimeError DBIF_RSQL_SQL_ERROR Exception CX_SY_OPEN_SQL_DB
Note 917927 - Status of transactional requests
Note 863054 - Correction: Missing packages not in the tree
And also check the following things.
1.Connections from BW to ECC and ECC to BW in SM59
2.Check Port,Partner Profiles,and Message Types in WE20 in ECC & BW.
3.Check Dumps in ST22, and SM21.
4.If Idocs are stuck i.e see the OLTP Idoc numbers in RSMO Screen in (BW) detials tab see in bottom, you can see OLTP Idoc number and take the Idoc numbers and then goto to ECC see the status in WE05 or WE02, if error then check the log else goto to BD87 in ECC and give the Idoc numbers and execute manually and see in RSMO and refresh.
5.Check the LUWs struck in SM58,User Name = * (star) and run it and see Strucked LUWs and select our LUW and execute manually and see in RSMO in BW.
There are many threads also on this.
Go through them
Runtime Errors DBIF_RSQL_SQL_ERROR & Exception: CX_SY_OPEN_SQL_DB
Short Dump in SAP BW Sys while extracting data from R/3
Thanks and regards

Short dump in BW for CRM load

Experts,
This is a strange situation. After upgrade to CRM 5.0, I have noticed that if we try to create or open info package to load data from CRM opportunity to BW, gives ABAP short dump and pointing to some delta load error. So, I don't get opportunity to reinit. delta load that way. It seems like source system has some issue that gives dump before even we open info packae to load data. I have ckecked RSA7 and RSA3 in CRM and found no problem at all. Tried to restore and activate and replicate data source into BW. Activated Transfer rule and Transfer structure. Nothing helped.
Can anybody suggest me anything please? Thanks.
Regards,
Nimesh

Hi NP
Please check the connectivity between CRM and BW systems. Go to source sytems and make sure that CRM system client is in active state or not? Go to sm59 and check with your source system is Unicode. If every thing is ok,then it is not a problem with systems. Serach for related SAP notes and apply that note with Transaction code: Snote. Hope this will help you,if yes assign some points
Regards
sriman

Regarding 2LIS_03_BF short dump

Hi Friends
Kindly help me in this regard, I got below short dump while executing "2LIS_03_BF" in RSA3 extract checker.
We wrote the customer exit for this data source, I put the debug point in my routine, but it not stopped. hope this error occuring before the routine. Please let me know the procedure what I should do here
Short dump:
Runtime Error          IMPORT_ALIGNMENT_MISMATCH
Exception              CX_SY_IMPORT_MISMATCH_ERROR
       Occurred on     31.07.2007 at   09:06:01
Error when importing object "MC03BF0_TAB".
What happened?
Error in ABAP application program.
The current ABAP program "SAPLMCEX" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
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_ERROR
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 importing object "MC03BF0_TAB", the structure did not match the
structure of the target object. The error occurred in component
no. 174.
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.
How to correct the error
The exception must either be prevented, caught within the procedure
"MCEX_BW_LO_API"
"(FUNCTION)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
There is a probably a new version of the program which does not
match the dataset. The data may not have been converted.
It is also possible that the field type of the imported field
has been changed in the ABAP/4 Dictionary.
Try to eliminate the error by regenerating the program "SAPLMCEX". To
do this, proceed as follows:
Call Transaction SE38 in the R/3 System, enter the program
name "SAPLMCEX" and then choose "Generate".
If the error occurred in one of your own programs or in an SAP program
that you modified, try to correct it yourself.
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:
"IMPORT_ALIGNMENT_MISMATCH" CX_SY_IMPORT_MISMATCH_ERRORC
"SAPLMCEX" or "LMCEXU06"
"MCEX_BW_LO_API"
Information on where terminated
The termination occurred in the ABAP program "SAPLMCEX" in "MCEX_BW_LO_API".
The main program was "RSFHGEN2 ".
The termination occurred in line 226 of the source code of the (Include)
program "LMCEXU06"
of the source code of program "LMCEXU06" (when calling the editor 2260).
Processing was terminated because the exception "CX_SY_IMPORT_MISMATCH_ERROR"
occurred in the
procedure "MCEX_BW_LO_API" "(FUNCTION)" but was not handled locally, not
declared in the
RAISING clause of the procedure.
The procedure is in the program "SAPLMCEX ". Its source code starts in line 5
of the (Include) program "LMCEX$06 ".
Thank & Regards
lasya

Hi Fiends
One more question regarding above problem?
will it be problem in my code which I wrote in Routine, let me know?
CASE i_datasource.
WHEN '2LIS_03_BF'.
    PERFORM 2lis_03_bf_exit
    TABLES c_t_data.
endcase.
FORM 2lis_03_bf_exit TABLES p_c_t_data STRUCTURE mc03bf0.
Endform.
Thanks & Regards
lasya

Short dump error when extracting delta records from R/3

I am working on BW 3.5 and I am facing some short dump error when extracting delta records from the r/3 to BW.
Below is the error message
Kindly do the needful ASAP.
Job started
Step 001 started (program SBIE0001, variant &0000000024277, user ID BWREMOTE)
Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
DATASOURCE = 0ISCM_PAYMENT_01
         Current Values for Selected Profile Parameters               *
abap/heap_area_nondia......... 2000000000                              *
abap/heap_area_total.......... 2000000000                              *
abap/heaplimit................ 40000000                                *
zcsa/installed_languages...... DE                                      *
zcsa/system_language.......... E                                       *
ztta/max_memreq_MB............ 2047                                    *
ztta/roll_area................ 6500000                                 *
ztta/roll_extension........... 2000000000                              *
2,454 LUWs confirmed and 2,454 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DAT
ABAP/4 processor: MESSAGE_TYPE_X
Job cancelled

Hi,
I look at the transaction ST22 to see which type of error has given you. Take a look at the notes to correct the error.
Another option is to look at OSS notes, because the error is giving you a standard extractor.
Greetings,

Short dump in delta extract using bgRFC in NW 2004s

Short dump in delta extract after Support Pack install, using bgRFC.
InfoSet Query extractor from Z-table residing on BW system into ODS.
Init and Full loads load successfully, delta loads short dump.
"MESSAGE_TYPE_X"
"SAPLARFC" or "LARFCU25"
"TRFC_SET_QUEUE_RECEIVER_LIST"
Problem began after support pack install, from SP 9 to SP 12.   Switched to Classic RFC in SM59, seemed to correct this extractor but caused problems in other extractors.

Hi Kevin,
check out this note: https://websmp205.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1054970&_NLANG=EN
it might help.
regards
Siggi

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 error when extracting from one of the datasource in R/3 to BW

When extracting from one of the datasource I am getting the short dump. below is the source code of the same.
Source code extract
Get boundaries of next TID block
L_FROM_INDEX = L_TO_INDEX + 1.
IF L_FROM_INDEX GT NFILL. EXIT. ENDIF.
L_TO_INDEX   = L_TO_INDEX + L_BLOCK_SIZE.
IF L_TO_INDEX GT NFILL.
L_TO_INDEX = NFILL.
L_BLOCK_SIZE = L_TO_INDEX - L_FROM_INDEX + 1.
ENDIF.
Create hashed index on TID of TID table
CLEAR L_TH_TID_IDX.
LOOP AT TIDTAB FROM L_FROM_INDEX TO L_TO_INDEX.
L_S_TID_IDX-TIDIX = SY-TABIX.
L_S_TID_IDX-TID   = TIDTAB-TID.
COLLECT L_S_TID_IDX INTO L_TH_TID_IDX.
ENDLOOP.
Select TID block from STATE table
SELECT * INTO TABLE L_T_STATE
       FROM ARFCSSTATE FOR ALL ENTRIES IN L_TH_TID_IDX
       WHERE ARFCIPID   EQ L_TH_TID_IDX-TID-ARFCIPID
         AND ARFCPID    EQ L_TH_TID_IDX-TID-ARFCPID
         AND ARFCTIME   EQ L_TH_TID_IDX-TID-ARFCTIME
         AND ARFCTIDCNT EQ L_TH_TID_IDX-TID-ARFCTIDCNT
       ORDER BY PRIMARY KEY.
Consistence check
DESCRIBE TABLE L_T_STATE LINES L_LINES.
IF L_LINES NE L_BLOCK_SIZE OR
   L_LINES EQ 0.
MESSAGE X097(SY).
ENDIF.
PERFORM DELETE_BATCH_JOB
        USING    L_T_STATE
        CHANGING L_S_TID1.
Update LUW-Status und Zeit
CLEAR L_T_STATE_IDX.
CLEAR L_TH_TID2_IDX.
CLEAR L_T_TID.
LOOP AT L_T_STATE INTO L_S_STATE.
L_S_STATE_IDX-TABIX = SY-TABIX.

Hi Pavan,
                 This is a table space error.
Regards,
rahul

Short dump error for delta load to 0CFM_C10 via 0CFM_DELTA_POSITIONS flow

hi all,
i am getting short dump error for delta load to 0CFM_C10 via 0CFM_DELTA_POSITIONS flow.
not able to figure out the actual issue and how to solve it.
can anyone suggest?
below is the details of the short dump
Short text
    Exception condition "UNKNOWN_TRANSCAT" raised.
What happened?
    The current ABAP/4 program encountered an unexpected
    situation.
What can you do?
    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
    A RAISE statement in the program "CL_SERVICE_TRG================CP" raised the
     exception
    condition "UNKNOWN_TRANSCAT".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
    Short description of exception condition:
    For detailed documentation of the exception condition, use
    Transaction SE37 (Function Library). You can take the called
    function module from the display of active calls.
How to correct the error
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "RAISE_EXCEPTION" " "
    "CL_SERVICE_TRG================CP" or "CL_SERVICE_TRG================CM003"
    "SORT_TRANSACTIONS"
    or
    "CL_SERVICE_TRG================CP" "UNKNOWN_TRANSCAT"
    or
    "SBIE0001 " "UNKNOWN_TRANSCAT"
    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.

Hi,
It seems like some routine are there and check your rotines , transformation etc.
Regards
sivaraju

Short dump in ECC 6.0 during delta load

Hi,
We are currently working in BI upgrade project
from BW 2.1c to BI 7.0
At the same time R/3 is being upgraded from 4.0B to ECC 6.0
During delta load we are getting short dump in R/3 system.
Below is the short dump detalis
The current ABAP prgm "SAPMSSY1" had to be terminated because it has come across a statement that unfortunately cannot be executed.
The following syntax error occured in program "/BI0/SAPLQI2LIS_11_VAITM" in include "/BI0/SAPLQI2LIS_11_VAITM" is not Unicode-compatible, according to its attributes.
If any help can be provided on this issue it would be great.
Regards,
Nikhil
Edited by: Nikhil Sakhardanday on Sep 11, 2008 1:58 PM

Hi,
did you made UCCHECK ?
/manfred

Regarding Short dump while data extraction

Hi All,
We are trying to extract data from DB Connect. When we try to pull the data by giving selections, we are getting short dump.
Name of Run time error.
PERFORM_CONFLICT_TAB_TYPE
Exception Name
CX_SY_DYN_CALL_ILLEGAL_TYPE
What could be the reason for this error.

Hi Jayanth,
Check these ...
Perform_conflict_tab_type error
Oracle to BW Load Runtime error CX_SY_DYN_CALL_ILLEGAL_TYPE
Raja

Short Dump while loading Delta from ODS to ODS

Hi Experts,
I have run into a short dump error while loading delta from one ODS to another via a process chain.
Following is the error message:
Error analysis
Short text of error message:
    Request 0000259294 is not completely activated. Please activate it again
Technical information about the message:
     Diagnosis
Activation of request 0000259294 has terminated, or is not yet
         complete.
System response
Procedure
If the process has terminated, all of the requests that the system
         was unabe to activate in the most recent activation process have to
         be reactivated before the new requests can be activated.
         If you are not able to carry out this activation step, delete the
         relevant requests from the administration of the ODS object (on the
         Requests tabstrip).
     Procedure for System Administration
    Message classe...... "RSM1"
    Number.............. 180
    Variable 1.......... 0000259294
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
Can someone help me resolve this?
Thank you

Check the status of request SID 259294 in ODS, whether the Activation got completed or not. If not wait till the activation completes.
If there is any problem in the activation process, correct that complete the activation process and load the ne request that you want to load..
Regards
VJ

Short Dump testing 0CRM_SALES_ACT_1 Datasource Extraction

Hi
Please can someone assist with the following problem in CRM 4.0. Using transaction RSA6-Extractor Checker S-API for 0CRM_SALES_ACT_1, we get a short dump when clicking on 'Extraction'. The following error message is displayed.
'An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_TYPE',
was neither
caught nor passed along using a RAISING clause, in the procedure "INSTANTIATE"
"(FORM)"
Any assistance is much appreciated.
Thanks
Neil

Resolved.

Short dump while DB Connect extraction(PERFORM_CONFLICT_TAB_TYPE)

HI ALL,
Here i am facing a problem while loading master data for one info object by using DB Connect source system, it is going to short dump with runtime error PERFORM_CONFLICT_TAB_TYPE and the exception is CX_SY_DYN_CALL_ILLEGAL_TYPE but for other info objects i can able to load the data. i have seen some of the related threads in SDN community, they have given some notes, in those they have mentioned that implementing support package 2 will resolve the problem, but we are very much ahead of support package 2. the below is the Error analysis from ST 22.
Error analysis
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_TYPE',
     was neither
    caught nor passed along using a RAISING clause, in the procedure
     "RSDBC_DB_DATA_RECEIVED" "(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:
    Incorrect call of FORM "CONVERT_ITAB_RFC".
    The FORM call is incorrect for parameter number 1.
    The current internal table passed to the formal table parameter has
    a type that is not compatible with the type of the formal parameter.
    The FORM "CONVERT_ITAB_RFC" is defined in the program
     "GP479V6EWNRI2LAHIG5C1GS5QFV".
This is very very urgent, please give me reply.
Many Thanks in Advance.
Jagadeesh

HI Pankaj/Chitrarth,
Thanks for your reply.
i am loading master data into our own defined infoobject and it's name is connection id(SFI_CONID). and the details of my bw system are
SAP BW Release : 350 Level : 0019 Support package:SAPKW35019
SAP BASIS Release : 640 Level : 0019 Support package : SAPKB64019.
Many Thanks in Advance.
Jagadeesh

Short dump in r/3 in delta extraction

Similar Messages

Maybe you are looking for