Short Dump while entering data in VF01

Runtime Errors         SAPSQL_INVALID_FIELDNAME
Except.                    CX_SY_DYNAMIC_OSQL_SEMANTICS
Program                               SAPLV61Z
Include                                 LV61ZU01
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_DYNAMIC_OSQL_SEMANTICS', was
     not caught in
    procedure "SEL_KONDTAB" "(FORM)", 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:
    An Open SQL clause was specified dynamically. The contained field name
    "WERKS" does not exist in any of the database tables from the FROM clause.
Error found in these codes.
if se_read_all_prestep is initial.
          select * from (t681-kotab) appending table <cond_tab>
                 up to 1 rows
                 where kappl  = se_kappl
                 and   kschl  = se_kschl
                 and   datbi >= se_date
                 and   datab <= se_date
                 and   (coding_tab).
          h_subrc = sy-subrc.
I had debug the codes and found that when t681-kotab = A752 and line in coding_tab is ALAND = 'DE' and WERKS = 'XX' and VSTEL = 'XX' and LLAND = 'NL'. I will hit error because in A752 table, field WERKS does not exists!
I guess this is a config problem but I do not know how to fix it.
Appreciate helps. Thanks a lot.

Hi,
I executed v/07 but I cannot find the 752 table.
T-code: v/07
Usage: A
Application: V
Access sequence: MWST
Access No: 08, Table = 78
Access No: 10, Table = 2
Access No: 20, Table = 11
Please assist. Thanks.

Similar Messages

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

  • 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 saving data after selecting '#' for variable in WI

    Hello All,
    We have a selection variable in our webinterface on company code.After selecting '#',i am entering data and while saving it goes to dump.
    but client wants to have an error message displayed after saving data instead of runtime error (dump).so that user can select required company code.
    Error analysis is:
    A RAISE statement in the program "SAPLRSDRI" raised the exception   
    condition "ILLEGAL_INPUT".                                          
    Since the exception was not intercepted by a superior program       
    in the hierarchy, 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.                   
    Is there any way to get desired  result?
    Thanks

    Hello Murali,
    What you would need to do is to change the attributes of the variable.
    1. In BPS0, you can make it as a mandatory entry.
    2. In the web layout, you can create a variable for Company code and force the user to choose a value from a dropdown list.
    The specific approach would depend on how the layout is being called and how it has been setup.
    Hope this helps.
    Sunil

  • Short dump while loading data

    Hi All,
    I am getting this error message while loading data in BW. The eeror message is below:
    Data not received in PSA Table.
    Diagnosis
    Data has not been updated in PSA Table . The request is probably still running or there was a short dump.
    Procedure
    In the short dump overview in BW, look for the short dump that belongs to your data request. Make sure the correct date and time are specified in the selection screen.
    You can use the wizard to get to the short dump list, or follow the menu path "Environment -> Short dump -> In Data Warehouse".
    Removing errors
    Follow the instructions in the short dump.
    When I checked the short dump it is as below.
    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/B0000541000 ]"                                 
        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:                                                           
    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/B0000541000 ]"                                 
        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    
        "DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC                                                     
        "GP12DW003276UZE34XM7O2QXLER" or "GP12DW003276UZE34XM7O2QXLER"                               
        "INSERT_ODS"                                                                               
    Can someone suggest me what should I check?
    Thanks in advance.

    Thanks a lot Manga. I did what you told and it gave me this error message.
    Inconsistency: High value for table /BIC/B0000541000: 0002 ; PARTNO value in RSTSODS: 0022          
    So you mean to say once I click on correct error button, it should be good. So after that if do the loading, it should not give me this problem if I am right.
    But can you tell me what exactly does that error message mean? Also is this not an table space issue. I have to wait to correct that error as DBA is currently looking into it.
    Assigned points. Will assign more points if the issue resolves.

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

  • Short dump while loading data in to Bw using Process Chain.

    got the problem in the Production System.......... I won't get any confirmation from my customer to debug the program in the Poduction.
    In BW I have to load the data every day using the process chain. in the monitor I can't find any problem every thing is working fine. status is green.. and loads the data into ODS successfully. But the job runs more than 6 Hrs and automatically an E-mail is sent to us that the processing takes long time.But it loads the data successfully into ODS.
    Since 10 days everyday we got a mail with the same problem. My customer asked me tTo analyse the problem.
    I check the short dump there I found that due to some problem the program get intrupted.
    <b>the short dump</b>
    ""Lokale Schnittstelle:
    *" IMPORTING
    *" VALUE(I_INFOCUBE) TYPE RSINFOCUBE
    *" EXCEPTIONS
    *" ILLEGAL_INPUT
    *" REQUEST_NOT_CLOSED
    *" INHERITED_ERROR
    DATA: l_s_cube TYPE rsd_s_cube,
    l_t_dummy TYPE rsdri_t_rfcdata,
    l_s_rsapoadm TYPE rsapoadm,
    l_nothing_found TYPE rs_bool.
    get type of cube
    CALL FUNCTION 'RSD_CUBE_GET_ONLY_DB'
    EXPORTING
    i_infocube = i_infocube
    i_objvers = rs_c_objvers-active
    i_with_atr_nav = rs_c_false
    i_with_message = rs_c_false
    IMPORTING
    e_s_cube = l_s_cube
    EXCEPTIONS
    infocube_not_found = 1
    illegal_input = 2
    OTHERS = 3.
    CASE sy-subrc.
    WHEN 0.
    WHEN 1.
    RAISE illegal_input
    WHEN OTHERS.
    RAISE inherited_error.
    ENDCASE.
    In the short dump I observed that the porgram get intrupted at RAISE illegal_input when sy-subrc = 1.
    I have to analyse this. problem........ whay is so happened...............
    Any one of you face the same problem............... if so please let me give your valuble suggestions regarding this.
    Cheers
    sailekha

    Looks like it  reaches the water mark level thats why you are getting message.

  • Short dump while loading data in ODS

    Hi,
    When i scheduled data load for ODS, a short dump was generated with following error:
    Error analysis
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
    neither
    caught nor passed along using a RAISING clause, in the procedure
    "RULE_BASED_MODIFY_RSMONMESS" "(FORM)"
    How to correct the error
    The exception must either be prevented, caught within the procedure
    "RULE_BASED_MODIFY_RSMONMESS"
    "(FORM)", or declared in the procedure's RAISING clause.
    To prevent the exception, note the following:
    Database error text........: "ORA-01654: unable to extend index
    SAPBD2.RSMONMESS~AXY by 128 in tablespace PSAPBD2"
    Internal call code.........: "[RSQL/INSR/RSMONMESS ]"
    Please check the entries in the system log (Transaction SM21).
    Please suggest what needs to be done.

    Hi Sneh,
    This is table space issue.
    You need to contact basis guys to get it resolved.
    Take a screen shot of this error and send the information to basis guys.
    Once they clear the problem. repeat the step.
    Hope this helps,
    Sri.....

  • Short Dump while checking Data in RSA7

    Hi
    My delta loads are failing with a dump in source system.
    I tried to check the delta Queue in source system ui got the same dump as i clicked on show data
    Dump Details
    Runtime Error          MESSAGE_TYPE_X
    Date and Time          18.01.2009 08:24:19
    ShrtText
    The current application triggered a termination with a short dump.
    What happened?
    The current application program detected a situation which really
    should not occur. Therefore, a termination with a short dump was
    triggered on purpose by the key word MESSAGE (type X).
    What can you do?
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    is especially useful if you want to keep a particular message.
    Error analysis
    Short text of error message:
    Abnormal termination after error
    Technical information about the message:
    Message classe...... "SY"
    Number.............. 097
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "MESSAGE_TYPE_X" C
    "SAPLRSC2" or "LRSC2U01"
    "RSC2_QOUT_READ_DATA"
    |    -

    Hi,
    Try this SAP note Note 498484 - BW extraction: Mult. delta records with qRFC 6.20.043
    It may fixe your problem, the problem is due to the reason LUWs are extracted from another qRFC outbound queue.This problem usually results in a termination of the delta extraction in the source system or a component of the transfer structure having an incorrect data format in BW (for example, due to the runtime error BCD_BADDATA).
    The extraction process may terminate in the RSC2_QOUT_READ_DATA function module with the MESSAGE_TYPE_X runtime error.The message for this runtime error is SY097 'Abnormal termination after an error'.The termination prevents you from loading incorrect data into the BW.
    Also,
    Try Note 498484
    https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=498484
    May help you in solving your issue based on your SP.
    Best Regards,
    VVenkat..

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

  • Regarding short dump while loading data

    Hi All,
    I am loading data using 0FI_GL_4. This is a periodic load which was working fine till March. There are lot of postings that happened in April and period was open till 20th. Now when I am trying to load that for 12th period April. I am getting the following error "ABAP/4 processor: DBIF_RSQL_SQL_ERROR" in short dump.
    This is the error analysis:
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
    neither                                                                
    caught nor passed along using a RAISING clause, in the procedure        
    "BWFIR_READ_BSEG_CPUDT_DATA" "(FUNCTION)"                              
    I am tried to load data 5 times till now and every time I am getting the same error. I checked with Basis people for the DB space and it is fine.
    Why I am suddenly getting this error???

    Hi,
    it looks like an internal table overflow in your source system.
    Try reducing the data_package size of your load or ask your basis guys to have a look on short dump and perhaps increase this memory.
    Try RSA3 in the source system and see if it works with your data_package size values from BW and see if it works. If not reduce the number of records...
    On which plugin release is your system running?
    hope this helps,
    Oliviier.

  • Short Dump while loading data into the GL ODS

    Hello Guyz
    I am getting a database error while loading the GL ODS in BW. I am performing an INIT load, and the error occurs during the activation stage:
    Database Error

    Hello Atul,
            PSAPTEMP has nothing to do with PSA. It is a temporary storage space and is present in all systems.
    You can check this in transaction DB02 if you are using Bw 3.x and DB02OLD if you are using BI 7.0. Once in DB02/DB02OLD, you will see a block which says tablespaces. In this block, there is a push button for freespace statistics, click on it and it will take you to a screen which shows the free space for all tablespaces.
    Hope this helps,
    Regards.

  • 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 displaying cube data in production

    Hi Folks,
    I'm getting a short dump while displaying cube data in production, please suggest
    Thanks and Regards
    Santhosh

    Hi Santosh,
    I'd suggest to follow as per SAP Note: 568768 - Analysis of SQL Errors causing Shortdumps or Error messages. The Note contains precise steps to analyze such an ABAP dump.
    cheers
    m./

Maybe you are looking for

  • Error while creating data source in bi for uc connect

    Hi Experts, we have using ud connect to pull the data from ms sql server using jdbc,we have maintained all the settings in the j2ee engine and also we performed the smoke test which showed the tables content in the ms sql data base. and also we have

  • Runtime Errors DBIF_RSQL_TABLE_UNKNOWN in BW system

    Hi Guys, We refreshed BW system from production to sandbox. SGEN finished successfully. Now I am strucked at bdls. when i ran bdls i am getting below dump pls help me to resolve this. Runtime Errors         DBIF_RSQL_TABLE_UNKNOWN Date and Time      

  • Insert date as dd/mm/yyyy

    How can I format a form so that I can insert a date as dd/mm/yyyy but it will save it in the database as yyyy-mm-dd?

  • Group Left Rpt - Dept Subtotal - S

    Have a Group Left Report - Have it set up with the Following Mgr Grp - Mgr Emp SumofXYZ Sumof123 Sumofabc, Sumofdfe, Date Grp - Date, XYZ, 123, ABC The report is set to Group on Mgr and Emp with Totals at Emp level, then a REPORT total generates at e

  • Why does Adobe Flash Player 11.9 keep installing over and over on Windows Internet Explorer?

    I am having a problem with Adobe Flash Player 11.9. When I visit a site that uses Adobe Flash Player (i.e. NBC News.com) the system keeps asking me to install Adobe Flash Player 11.9. However, Adobe Flash Player 11.9 is ALREADY installed on my system