RSA1 - Datasources ASSERTION_FAILED short dump

Hello,
We are getting a short dump (ASSERTION_FAILED) when clicking on Datasources tab in RSA1 -> Modeling. This was working fine till yesterday afternoon. The last action I performed was to activate all transfer structures in My self source system using RS_TRANSU_ACTIVATE_ALL. I searched on service marketplace but couldn't find any note relevant to our error.
Everything else works fine. Please advise.
We are on BI SP14.
This is the log from st22.
Short text
    The ASSERT condition was violated.
What happened?
    In the running application program, the ASSERT statement recognized a
    situation that should not have occurred.
    The runtime error was triggered for one of these reasons:
    - For the checkpoint group specified with the ASSERT statement, the
      activation mode is set to "abort".
    - Via a system variant, the activation mode is globally set to "abort
      for checkpoint groups in this system.
    - The activation mode is set to "abort" on program level.
    - The ASSERT statement is not assigned to any checkpoint group.
Error analysis
    The following checkpoint group was used: "No checkpoint group specified"
    If in the ASSERT statement the addition FIELDS was used, you can find
    the content of the first 8 specified fields in the following overview:
    " (not used) "
    " (not used) "
    " (not used) "
    " (not used) "
    " (not used) "
    " (not used) "
    " (not used) "
    " (not used) "
How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    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:
    "ASSERTION_FAILED" " "
    "CL_RSAWBN_TREE_VIEW===========CP" or "CL_RSAWBN_TREE_VIEW===========CM00K"
    "EXPAND_NODE"
Best Regards
RT
null

Hello Voodi,
998730 talks about the short dump when changing/activating transformations.
We got the short dump when trying to get into Datasources tab. Though we are on BI, as i mentioned earlier the last action i performed was to activate transfer structures (For 3.x statistical datasources).
Still, I checked the table contents as mentioned in the note. It was not of much help. Any other thoughts?
Thanks.
Message was edited by:
        SAPBI IP

Similar Messages

  • 0PROJECT_ATTR  datasource throws short dump in bw

    0PROJECT_ATTR datasource throws short dump in BW.  On checking the same at source system level in R3 using RSA3 transaction, the error has been cornered that "Project I0640-03/0001 does not exist".
    Now i would like to know the related transaction codes to even more corner the problem.
    Can anyone help me out in this.
    Regards
    Baskar
    Message was edited by: Baskar Rajagopalan

    For information, I dont have authorisation to use SE93.
    AS of now the problem has already been cornered that the issue is in R3 extraction only.
    Message was edited by: Baskar Rajagopalan

  • ASSERTION_FAILED short dump when Transporting Transformation from Dev to QA

    Hi Experts,
    I' am getting a short Dump when transporting the transformations, DSO & DTPs from Dev server to QA.
    I got RC=12, Please have a look below....
    Transport log...
        BCQ        System BCQ
                   Selection for Import                     08.07.2010 15:28:59    (0) Successfully Completed
                   Import                                   08.07.2010 15:35:14    (0) Successfully Completed
                   Check Versions                           08.07.2010 15:35:14    (0) Successfully Completed
                   Method Execution                         08.07.2010 15:36:20   (12) Canceled
                   Import                                   08.07.2010 15:45:39    (0) Successfully Completed
                   Check Versions                           08.07.2010 15:45:39    (0) Successfully Completed
                   Method Execution                         08.07.2010 15:46:45   (12) Canceled
    and the Log detalis.....
    Date        Time      Message
    08.07.2010  15:35:15  Job started
    08.07.2010  15:35:15  Step 001 started (program RDDEXECL, variant , user ID DDIC)
    08.07.2010  15:35:15  All DB buffers of application server sxcat136 were synchronized
    08.07.2010  15:35:21  STDO: Log  could not be written on output device T
    08.07.2010  15:35:30  Replication completed successfully
    08.07.2010  15:35:31  Struttura di comunicazione /BIC/CS8ZFIZIASA activated
    08.07.2010  15:35:40  Regola(e) di trasm. 8ZFIZIASA_AA activated
    08.07.2010  15:35:47  ABAP/4 processor: ASSERTION_FAILED
    08.07.2010  15:35:47  Job cancelled
    Even I've checked the entries on the table RSTRANRULE for those Transpormations but there I got...all the entries with...
    RULEID = all numbers
    GROUPID = '1' or '2'
    GROUPTYPE = 'S' or 'T'
    REF_RULE ='0'
    we are in to SAP_BW Release 700, Level 0013, SP -SAPKW70013, SAP NetWeaver BI 7.0
    Pls help if any one know's the solution for this.
    Thanks in adv.
    BR,
    Ajay Kumar
    Edited by: sap.ajaykumar on Jul 9, 2010 12:48 PM

    Follow the steps mentioned in OSS note 998730.
    FYI.. Solution:
    Call transaction SE16 (Table Browser) and the 'RSTRANRULE' table with the following selection parameters:
    GROUPID = 'space'
    GROUPTYPE = 'space'
    REF_RULE 'space'
    If there are inconsistent entries in the RSTRANRULE table such as this:
    TRANID *
    OBJVERS *
    RULEID *
    SEQNR *
    GROUPID 00
    GROUPTYPE space
    RULETYPE space
    REF RULE *
    Delete these entries from the table.
    Activate the affected transformations.
    Also check the OSS note: 1006658.
    Follow the steps mentioned in OSS note 998730.
    FYI.. Solution:
    Call transaction SE16 (Table Browser) and the 'RSTRANRULE' table with the following selection parameters:
    GROUPID = 'space'
    GROUPTYPE = 'space'
    REF_RULE 'space'
    If there are inconsistent entries in the RSTRANRULE table such as this:
    TRANID *
    OBJVERS *
    RULEID *
    SEQNR *
    GROUPID 00
    GROUPTYPE space
    RULETYPE space
    REF RULE *
    Delete these entries from the table.
    Activate the affected transformations.
    Also check the OSS note: 1006658.
    Follow the steps mentioned in OSS note 998730.
    FYI.. Solution:
    Call transaction SE16 (Table Browser) and the 'RSTRANRULE' table with the following selection parameters:
    GROUPID = 'space'
    GROUPTYPE = 'space'
    REF_RULE 'space'
    If there are inconsistent entries in the RSTRANRULE table such as this:
    TRANID *
    OBJVERS *
    RULEID *
    SEQNR *
    GROUPID 00
    GROUPTYPE space
    RULETYPE space
    REF RULE *
    Delete these entries from the table.
    Activate the affected transformations.
    Also check the OSS note: 1006658.
    Also check the oSS note : Note 975675 - Transformation cannot be activated

  • ASSERTION_FAILED, Short dump when activating Transformation in BI7.0

    Hi All,
    I have migrated 3.5 update rule to 7.0. And during transformation activation i am getting short dump giving following messges:
    "ASSERTION_FAILED"
    "CL_RSTRAN_GEN_STEP= = = = = CP"
    "CL_RSTRAN_GEN_STEP= = = = = CM005"
    "GET_CONTAINER"
    My system support pack is 15. I searched many OSS Notes but i am not able to get the exact soln.
    can anybody help me out with this problem?
    Regards,
    Harsh

    this error is generally due to inconsistency in metadata
    refer OSS note: 1071255, 1094266, 998730, 829353, 926854
    Try to implement this solution from OSS 998730:
    Call transaction SE16 (Table Browser) and the 'RSTRANRULE' table with the following selection parameters:
    GROUPID   =  'space'
    GROUPTYPE =  'space' or 'S'
    REF_RULE  <> 'space'
    If there are inconsistent entries in the RSTRANRULE table such as:
               TRANID        *
    OBJVERS        *
    RULEID        *
    SEQNR          *
    GROUPID        00
    GROUPTYPE      space  or  GROUPTYPE    'S'
    RULETYPE      space
    REF RULE       *
    Delete these entries from the table.
    Activate the affected transformations.
    Edited by: sam hennry on Feb 5, 2008 4:40 PM

  • Regarding short dump ASSERTION_FAILED

    Hi
    I tried to delete info object characteristcs from Info object from transaction RSA1. it gives short dump.
    pls advice how to avoid this.
    "ASSERTION_FAILED" " "
    "CL_RSAWBN_OBJ_IOBC_IOBJTREE===CP" or "CL_RSAWBN_OBJ_IOBC_IOBJTREE===CM002"
    "GET_IOBC"
    Termination occurred in the ABAP program "CL_RSAWBN_OBJ_IOBC_IOBJTREE===CP" -
    in "GET_IOBC".
    The main program was "RSAWBN_START ".
    In the source code you have the termination point in line 34
    of the (Include) program "CL_RSAWBN_OBJ_IOBC_IOBJTREE===CM002".
    is it patch problem ?
    Regards
    Chandra

    HI,
    Did you saw this?
    http://wiki.sdn.sap.com/wiki/display/BI/RuntimeErrorASSERTION_FAILEDinABAPProgramCL_RSAWBN_TREE_VIEW
    Regards
    Lucas

  • Short Dump while checking DataSource contents in R3 (Transaction RSA3)

    Hello all,
    I am having trouble with a DataSource (2LIS_11_VAITM) in the R3 Source System (IDES 6.0). When I try to view the contents of this DataSource through Transaction RSA3, I get the following Short Dump Error.....
    Could someone pls help me with this.
    Thanks,
    SD
    ============================================================================
    Runtime Errors         CONNE_IMPORT_WRONG_STRUCTURE
    Except.                CX_SY_IMPORT_MISMATCH_ERROR
    Date and Time          18.03.2009 09:56:23
    Short text
         Error when importing object "MC11VA0ITM_TAB".
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "SAPLMCEX" 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_IMPORT_MISMATCH_ERROR', was
          not caught in
         procedure "MCEX_BW_LO_API" "(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:
         When attempting to import data, the
         structure of the complex object "MC11VA0ITM_TAB" was not compatible with the
         target object. The error occurred with component no. 31.
    Missing RAISING Clause in Interface
         Program                                 SAPLMCEX
         Include                                 LMCEXU06
         Row                                     1
         Module type                             (FUNCTION)
         Module Name                             MCEX_BW_LO_API
    Trigger Location of Exception
         Program                                 SAPLMCEX
         Include                                 LMCEXU06
         Row                                     263
         Module type                             (FUNCTION)
         Module Name                             MCEX_BW_LO_API

    Hi SD,
    The 11_Vaitm is a LO datasource, before checking its data setup tables need to be filled for it.
    For filling the setup tables, first you have to delete the existing setup table data and ensure all the delta queues are empty.
    Delete the setup tables: Go to TCODE LBWG and in the application give 11 and execute.
    Delete all entries in Delta Queue, TCODE RSA7 for application 11.
    Delete the entries in logistic queue: Check in TCODE SMQ1, if there are any entries for application .
    Refill the setup tables: SBIW -> Settings for application specific datasources -> Logistics -> anaging extract strucutre -> Initilization -> Filling the setup table ->Application specific setup of data -> SD-Sales order perform setup.
    Then try RSA3. Hope it helps.
    Regards,
    Pankaj

  • Short Dump While Accessing RSA1 in BI7.0 with SP 21

    Hi,
    The following short dump occurs, while Accessing RSA1 in BI7.0
    Runtime Errors SYNTAX_ERROR
    Date and Time 26.10.2010 10:19:35
    Short text
         Syntax error in program "CL_RSTRAN_STAT================CP ".
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "CL_RSAWBN_OBJ_TRFN============CP" had to be
          terminated because it has
         come across a statement that unfortunately cannot be executed.
         The following syntax error occurred in program
          "CL_RSTRAN_STAT================CP " in include
          "CL_RSTRAN_STAT================CM00X " in
         line 34:
         "Der formale Parameter "E_TLOGO_MASK" existiert nicht."
         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 "CL_RSAWBN_OBJ_TRFN============CP" 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 "CL_RSTRAN_STAT================CP
        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
         CL_RSTRAN_STAT================CP :
        "Der formale Parameter "E_TLOGO_MASK" existiert nicht."
    i.e parameter E_TLOGO_MASK is not existing.
    I have gone through below old thread, but its for old SP
    Runtime Error SYNTAX_ERROR while accessing the T-code RSA1
    In our case, I guess it refers to our patch level as this SAP Note is referring to support package 17,
    but we have implemented support package 21.
    Please help <REMOVED_BY_MODERATOR> as this is blocking our next level in BI upgrade process.
    Thanks in advance.
    Regards,
    Manikandan Dhanakoti
    Edited by: Manikandan.D on Oct 29, 2010 8:37 AM
    Edited by: Pravender on Nov 1, 2010 12:30 PM

    See if below threat is any help.
    Runtime Error SYNTAX_ERROR while accessing the T-code RSA1

  • Short dump GETWA_NOT_ASSIGNED while transporting Datasource in BI 7.0

    Hi Friends,
    I am getting an error, while trying to transport Datasource into quality system. The Transport request log says that "Program terminated (job: RDDEXECL, no.: 11372100)"
    If I check the log in SM37 of target system it gives following steps
    29.06.2007 11:37:21 Job started
    29.06.2007 11:37:21 Step 001 started (program RDDEXECL, variant , user ID DDIC)
    29.06.2007 11:37:21 All DB buffers of application server bdhp4488 were synchronized
    29.06.2007 11:37:30 SQL: 29.06.2007 11:37:30 DDIC
    29.06.2007 11:37:30  CREATE UNIQUE INDEX "/BIC/B0000566001~0" ON
    29.06.2007 11:37:30 "/BIC/B0000566001" ("REQUEST", "DATAPAKID",
    29.06.2007 11:37:30 "PARTNO", "RECORD") PCTFREE 10 LOCAL INITRANS 002
    29.06.2007 11:37:30 TABLESPACE PSAPSR3 STORAGE (INITIAL
    29.06.2007 11:37:30 0000000016 K NEXT        0000000160 K MINEXTENTS
    29.06.2007 11:37:30 0000000001
    If I see the short dump in ST22 in target system (quality) The I get error
    "Runtime Errors         GETWA_NOT_ASSIGNED"
    Could somebody help me in resolving this?
    Thanks and regards,
    Balaraj

    Thanks Edwin,
    My issue is still not resolved.
    Now the error that I am getting while transporting the Transformation is
    Program terminated (job: RDDEXECL, no.: 12091300)
    The SM37 job log says that
    "Job started
    Step 001 started (program RDDEXECL, variant , user ID DDIC)
    All DB buffers of application server bdhp4488 were synchronized
    ABAP/4 processor: GETWA_NOT_ASSIGNED
    Job cancelled"
    When i see the dump in ST22. It says that it could not find entry in one of the tables
    "   READ TABLE p_t_mapping ASSIGNING <fs_map>
       WITH KEY target_stepid = 0
                targetsegid   = <fs_posit>-rulesegid
                targetposit   = <fs_posit>-ruleposit
                targetid      = 0.
    Sy-subrc <> 0 for this read.
    Could you please advise?
    Thanks and regards,
    Balaraj

  • 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 'ASSERTION_FAILED' during updating partner Functions

    Hi All,
    I am updating the Partner Functions for the Customers using FM 'SD_CUSTOMER_MAINTAIN_ALL' and passing the partner functions and numbers to the XKNVP structure.
    while running the program in am getting the short dump as ASSERTION_FAILED.
    Detailed Description:
    In the running application program, the ASSERT statement recognized a situation that should not have occurred.
    The runtime error was triggered for one of these reasons:
    - For the checkpoint group specified with the ASSERT statement, the   activation mode is set to "abort".
    - Via a system variant, the activation mode is globally set to "abort" for checkpoint groups in this system.
    - The activation mode is set to "abort" on program level.
    - The ASSERT statement is not assigned to any checkpoint group.
    The Dump is occuring in the method 'get_cvic_cust_to_bp1_line'.
    We have searched for a relevant SAP note but could not find any.
    can any one please help to solve this issue?
    Helpful answer will surely be rewarded.
    Thanks in Advance,
    Asif Ali Khan

    When you are (absolutely) sure you are using this function module in the correct way, only then opening a message for SAP is liable. However, most of the times this happens because not all (or all) parameters are not provided for the FM to work properly, or what ever reason that may be.
    It might be helpful to determine the checkpoint group and have a look at the log in transaction SAAB. This might give you a clue as to where the problems lies.

  • 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 error while loading data from R/3 to ODS

    Hello,
    while trying to load data into the ODS from R/3 I get the following short dump error message. How do I carry out step 1 in the below procedure. Where do i find the Activate Function. And idea?
    Thanks,
    SD
                                                                                    Diagnosis                                                                               
    Form routine CONVERT_ITAB_RFC is incorrect in transfer program         
         GP4C0LOLZ6OQ70V8JR365GWNW3K .                                                                               
    System Response                                                                               
    The IDoc processing was terminated and indicated as incorrect. The IDoc
         can be reimported at any time.                                                                               
    Procedure                                                                               
    1.  Go to the transfer rule maintenance for your InfoSource               
             ZFIN_TR_FLQITEM_FI and the source system DA_M_10 and regenerate the   
             transfer program using the function Activate. Remove possible syntax  
             errors on the basis of your conversion routines.                                                                               
    2.  Restart the processing of this IDoc.                                                                               
    3. If the error occurs again search for SAPNet R/3 notes, and create a 
            problem message if necessary.
    Edited by: Sebastian D'Souza on Jan 13, 2009 3:22 PM

    Hi.......
    Goto RSA1>> then to source system tab (on left side) >>  double click on the desired source system...........Then on the right side you have the Datasource tree..........there search the datasource and activate.......Also u can Replicate the datasource again.......and activate the Transfer rules using the program : RS_TRANSTRU_ACTIVATE_ALL
    After this operation when come back to source system (R/3).........I think  the error log line will be disappeared from SM58......... Then repeat the load.........
    Also u can try to Activate the infosource once...........in RSA1.........before repeating the load....
    Hope this helps......
    Regards,
    Debjani....

  • Short dump when expand info provide

    Dear all,
    I have 0GL_ACOOUNT info object that act as a master data.
    the problem is when I want to expand at the info provider instantly create short dump
    the overview of the short dump is :
    Runtime Errors         ASSERTION_FAILED
    Date and Time          12.08.2009 10:08:16
    Short text
         The ASSERT condition was violated.
    What happened?
         In the running application program, the ASSERT statement recognized a
         situation that should not have occurred.
         The runtime error was triggered for one of these reasons:
         - For the checkpoint group specified with the ASSERT statement, the
           activation mode is set to "abort".
         - Via a system variant, the activation mode is globally set to "abort"
           for checkpoint groups in this system.
         - The activation mode is set to "abort" on program level.
         - The ASSERT statement is not assigned to any checkpoint group.
    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.
    Information on where terminated
        Termination occurred in the ABAP program "CL_RSAWBN_OBJ_IOBJ_DATA=======CP" -
         in "GET_TRFN_AWBSUBOBJ".
        The main program was "RSAWBN_START ".
        In the source code you have the termination point in line 23
        of the (Include) program "CL_RSAWBN_OBJ_IOBJ_DATA=======CM005".
    Source Code Extract
    Line  SourceCde
        1 METHOD get_trfn_awbsubobj .
        2
        3   DATA: l_tranid   TYPE rstranid,
        4         l_s_source TYPE rstran_s_tlogo,
        5         l_s_target TYPE rstran_s_tlogo,
        6         l_objvers  TYPE rsobjvers.
        7
        8   l_tranid = i_objnm.
        9   l_objvers = rs_c_objvers.
       10
       11 * get the source and target for the tranid
       12   WHILE l_s_source IS INITIAL OR l_s_target I
       13     TRY.
       14         cl_rstran_stat=>get_objects(
       15           EXPORTING
       16             i_tranid   = l_tranid
       17             i_objvers  = l_objvers
       18           IMPORTING
       19             e_s_source = l_s_source
       20             e_s_target = l_s_target
       21                ).
       22       CATCH cx_rstran_not_found .
    >>>>>         ASSERT sy-index < 2.
       24     ENDTRY.
       25 * for possible second run set objvers
       26     l_objvers = rs_c_objvers-modified.
       27   ENDWHILE.
      29 * pass back the su
      30   IF i_target = rs
      31     re_awbsubobjec
      32   ELSE.
      33     re_awbsubobjec
      34   ENDIF.
      35
      36 ENDMETHOD.
    Please advice

    HI,
    I have read the sap notes and that is exactly what happen to me.
    but I don't understand how to correct it.
    It said :
    This error cannot be corrected automatically. Use the method DELETE_VERSION_FROM_DB of the class CL_RSTRAN_STAT to delete the existing A version of the transformation manually in the target system.
    Ensure that the transformation is permanently deleted from the database; therefore, you should verify that the correct transformation ID is specified (in the short dump, the TranID that is specified in the short dump is in the variable L_TRANID).
    anybody know how to use delete_version_from_db ?
    please advice

  • BCS Short Dumps after Upgrade (3.5 to BI7)

    Hi SDN,
    We have recently upgraded our dev system from BW3.5 to BW 7 (SEM BW 6) and following the upgrade none of the queries based on the BCS virtual info provider(Remote Cube) ZVBCS01 are working or the listcube transaction on cube ZVBCS01 in RSA1.
    Both the queries and listcube short dump with DATREF_NOT_ASSIGNED (Details  "DATREF_NOT_ASSIGNED" "SAPLUCR0"  "LUCR0U08" "PROVIDE_SEM_DATA_TABLE_3")
    We have raised a call with SAP OSS they recommended to activate the InfoObject 0BCS_REPMOD from business content and regenerate the data basis. We did all this but still experience the short dumps. (We havenu2019t assigned 0BCS_REPMOD to any Infoproviders or the data basis)
    We will be unable to upgrade to BI7 unless we can resolve this issue so any help would be appreciated.
    Kind regards,
    Jamie Flaxman

    Thanks for the responses, we have managed to get BCS working now following the upgrade.
    Following the activation of the business content, I had to regen the Data Basis but the way I did it originally wasnu2019t enough to force a regeneration. So I had to make a small change to the data basis (move of field names and back again) which was enough to do the re-gen.
    We have experienced quite a few issues with the upgrade from SEM 4 to 6.
    Thanks for the help.
    Jamie Flaxman

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

Maybe you are looking for