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

Similar Messages

  • Short Dump while execuition of DTP.

    Hi,
    I got short dump while  execuiting the DTP.
    Error messages shows as below:
    1.The database returned a value containing an error
    2.An exception with the type CX_SY_OPEN_SQL_DB occurred, but was neither handled locally, nor declared in a RAISING clause
    3.Exception CX_SY_NO_HANDLER logged
    Could you please help us in solving this issue.
    Regards,
    Suman.

    hi,
    an error like this comes usually in 2 cases
    1) not enough resources are available to carry out loads.in this case increase no of parallel processes to 2-3 in dtp setting,check the option get delta request by request(if its a delta load) and decrease packet size to 10000(from default 50000)
    2)fileld to field assignment is not proper:
    u need to check if there is any source field with lenth lets say 5 ans is getting assisgned to a target field length lets say 4.in this case dumps will come
    please check the error message in st22 and here you can also check the termination point.please check in option Chosen variables /contents of system fileds where you can get temp values at point of termination.here you can pinpoint values at which prog is throwing dumps.

  • Short Dump Error while executing the DTP

    Hello Experts,
    I am facing an issue with DTP.
    Data has been loaded to PSA successfully but while executing the DTP for loading from PSA to DSO (WO) throwing a short dump RAISE_EXCEPTION.
    Short text
        Exception condition "NO_DS_LG_FOUND" raised.
    "RAISE_EXCEPTION" " "
    "SAPLRSSTATMAN" or "LRSSTATMANU1
    "RSSTATMAN_GET_PARTTAB_PSA"
    or
    "SAPLRSSTATMAN" "NO_DS_LG_FOUND"
    or
    "RSAWBN_START " "NO_DS_LG_FOUND"
    We are on BI support pack 14 SAPKW70014, searched for OSS notes but there are few for SP 12/ 13.
    Did any body faced the simlliar issues,,,, please help
    Appreicate your quick response.

    You may wish to check this
    Note 1083305 - P16:STATMAN:Dump in function module RSM_INFOCUBE_WRITE_CHECK
    Hope it Helps
    Chetan
    @CP..

  • 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

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

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

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

  • Short dump while executing info package in 3.5 data flow?

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

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

  • Getting a dump while executing the standard report BUSCHDOC

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

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

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

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

  • Dump while Executing the Report HINUINFU

    Dear All
            I am getting Dump while executing the T.Code - HRPBSIN_IN_INFU (HINUINFU). As per my Configuration it should update the IT0267 and the IT0582. While debugging the We found out that its updating the IT0267 internally. But while reaching to IT0582 its reflecting on the feature 40CEA and the T549D.
    here we are having the Telephone Reimbursement for this i copied the Tax code SEXM to ZTEL and assigned to my wage type
    I also maintaied this Subtype to the feature 40CEA.
    Checked also the IT0582 and its subtype time constraint.
    Still the the DUMP persisisting. Please provide the solutions if any of you come across with the same situation.
    Thanks & Regards
    Srikanth Reddy

    Hi
         Issue has been resoved internally. Return value to feature set as HINUOSD0 to MOLGA. hence closing the thread
    Regards
    Srikanth Reddy

  • Short dump while changing the end date of infotype 0167 through PA30

    Hi all,
    I am getting short dump while changing the end date of infotype 0167(Health Plans) through Tcode PA30.
    dump descript is as below
    An exception occurred that was not caught.
    Runtime Errors         UNCAUGHT_EXCEPTION
    Except.                CX_HRPA_VIOLATED_POSTCOND
    Date and Time          11.03.2010 07:06:26
    What happened?
        The exception 'CX_HRPA_VIOLATED_POSTCONDITION' was raised, but it was not
         caught anywhere along
        the call hierarchy.
        Since exceptions represent error situations and this error was not
        adequately responded to, the running ABAP program
         'CL_HRPA_SAPUP50R_ADAPTER======CP' has to be
        terminated.
    thanks
    shahid

    Search OSS Notes for that.

  • 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

  • Dump while executing the report in the background!!!

    Hi Experts,
    I have created one report which is calling the "HRASR_TEST_PROCESS" (HR form process) thru BDC.
    Its running fine while executing via SE38 (foreground) but getting dump while executing from the background with same variant.
    The dump is follows,
    Short Text
    Exception condition "CNTL_ERROR" raised.
    ERROR ANALYSIS
    A RAISE statement in the program "CL_GUI_CUSTOM_CONTAINER=======CP" raised the exception condition "CNTL_ERROR". Since the exception was not intercepted by a superior program, processing was terminated.
    Line        Source Code
    32         WHEN 1.
       33           RAISE CNTL_SYSTEM_ERROR.
       34         WHEN 2.
       35           RAISE CNTL_ERROR.
       36         WHEN 3.
       37           class cl_gui_cfw definition load.
       38           message id 'DC' type 'W' number cl_gui_cfw=>reason_no_init
       39             raising create_error.
       40         WHEN 4.
       41           RAISE LIFETIME_ERROR.
       42         WHEN 5.
       43           RAISE LIFETIME_DYNPRO_DYNPRO_LINK.
       44         WHEN OTHERS.
       45           RAISE CNTL_ERROR.
       46       ENDCASE.
       47     
       48       m_container_type = CONTAINER_TYPE_CUSTOM.
       49     
       50       CALL METHOD SET_VISIBLE
       51           EXPORTING
       52               VISIBLE = '1'
       53           EXCEPTIONS
       54               CNTL_SYSTEM_ERROR = 1
       55               CNTL_ERROR = 2.
       56     
       57       CASE SY-SUBRC.
       58         WHEN 0.
       59         WHEN 1.
       60           RAISE CNTL_SYSTEM_ERROR.
       61         WHEN 2.
    >>>>>           RAISE CNTL_ERROR.
       63         WHEN OTHERS.
       64           RAISE CNTL_ERROR.
       65       ENDCASE.
       66     
       67       m_name = container_name.
       68       call method set_window_property
       69            exporting property_id = property_name
       70                      value       = m_name
       71                      keep_cache  = 'X'
       72            exceptions others = 1.
       73       if sy-subrc ne 0.
       74         clear m_name.
       75         raise cntl_error.
       76       endif.
       77     
       78       CALL METHOD ME->REGISTER_CACHED_W_PROPERTY
       79         EXPORTING
       80           PROPERTY_ID             = property_height
       81         EXCEPTIONS
    Kindly let me know, what is the problem and how can i solve it.
    Thanks in advance.
    Regards,
    Harish

    Hello Zhou,
    indeed, as you mention the ALV grid, there are some workarounds in the system, but there is no global solution. For example, the function module REUSE_ALV_GRID_DISPLAY detects internally whether it is called in background mode, and in this case it forwards the call to REUSE_ALV_LIST_DISPLAY which is runnable in background mode, since it creates an ABAP list.
    But normally, when using objects of the control framework in your program, you are restricted to dialog mode.
    Kind regards,
    Rüdiger

  • Short Dump while executing costing run or production orders

    Hi Guys,
    While executing the costing run or production orders saving, we are getting short dump.  it is the debugging is showing its fingers at A035 which is related to maintenance of overhead rates.
    We have maintained the overhead rates correctly. There is no issue.
    This could be some thing related to OSS notes as well.
    Just wanted to know if it has got something to do with OSS notes or something else.
    Please throw some light in this regard
    Thanks in advance

    Hi,
    In what program there is a dump? I mean, what is the log saying?
    Regards,
    Eli

  • Dump while executing the query on MProvider on Stock and Billing

    Hi,
    I am getting this dump while executing a Query on Multiprovider. Here Multiprovider is on Billing cube(z-cube) and 0IC_C03 cubes. In the report , I have KF of both cubes. I am sure I never faced this type of problem in version 3.5. It seems we are going back day by day because of version 7.0.
    A:
    1) I am not getting any error if I take Kfs of only Billing cube in the
    report on the multiprovider.
    2) But I am getting this problem by taking only KF from 0IC_c03 on this multiprovider .
    3) And also this problem is not raising in any queries(ofcourse same type) of those 2 cubes.
    4) Here Fiscal Variant is constant filter, and User will enter the Fiscal year.
    5) In the Columns area ,I have taken 12 selections each one restricted with one CALMONTH2.
    6) in Rows part I have 3 selections. Here 2 selections have Billing KF and other selection has Blockd Stock qty KF.
    B:
    The above dump is not raising if I take 12 selections on columns with a restriction on 0CALMONTH with Customer exit varible , but different offsets in selections. Here the Customer exit variable gets April of the User entered Financial year as the value.  But the problem is For all columns it is giving same Value for Stock KF even though we have different values in the system. Surprisingly issue is , Sales figures are comming proper.
    I am on Version 7 and patch 13. And  I am using Querydesigner 3.5.
    Dump message: GETWA_NOT_ASSIGNED
    <i>Short text:
        Field symbol has not yet been assigned.
    What happened?
        Error in the ABAP Application Program
        The current ABAP program "RSDRC_NCUM_ROUTINES" had to be terminated because it has come across a statement that unfortunately cannot be executed.
    keywords:
    "GETWA_NOT_ASSIGNED" " "
    "RSDRC_NCUM_ROUTINES" or "RSDRC_NCUM_ROUTINES"
    "FILTER_SELDR"</i>
    Thanks and Regards,
    Anil Kumar Sharma .P
    Message was edited by:
            Anil Kumar Sharma
    Message was edited by:
            Anil Kumar Sharma

    OK,
    I come back to my question: you said "<i>But the problem is For all columns it is giving same Value for Stock KF even though we have different values in the system</i>"
    Can you say to which period this value correspond?
    This looks like you are missing some characteristic identification in your multi.
    Can you assess that?
    Do you have the same time periods in both cubes? I mean, do you have at least the periods used in your RKF / query in both cubes? Would you mind pasting your identification for time IObjs from table RSDICMULTIIOBJ?
    please see hereunder my identification for a sales and stock multicube
    INFOCUBE                       OBJVERS IOBJNM                         PARTCUBE                       PARTIOBJ                                                                               
    ZMC021                         A       0CALDAY                        ZICRT_C07                      0CALDAY                      
    ZMC021                         A       0CALMONTH                      ZICRT_020                      0CALMONTH                    
    ZMC021                         A       0CALMONTH                      ZICRT_C07                      0CALMONTH                    
    ZMC021                         A       0CALMONTH2                     ZICRT_020                      0CALMONTH2                   
    ZMC021                         A       0CALMONTH2                     ZICRT_C07                      0CALMONTH2                   
    ZMC021                         A       0CALQUART1                     ZICRT_020                      0CALQUART1                   
    ZMC021                         A       0CALQUART1                     ZICRT_C07                      0CALQUART1                   
    ZMC021                         A       0CALQUARTER                    ZICRT_020                      0CALQUARTER                  
    ZMC021                         A       0CALQUARTER                    ZICRT_C07                      0CALQUARTER                  
    ZMC021                         A       0CALWEEK                       ZICRT_C07                      0CALWEEK                     
    ZMC021                         A       0CALYEAR                       ZICRT_020                      0CALYEAR                     
    ZMC021                         A       0CALYEAR                       ZICRT_C07                      0CALYEAR                     
    ZMC021                         A       0FISCPER                       ZICRT_020                      0FISCPER                     
    ZMC021                         A       0FISCPER                       ZICRT_C07                      0FISCPER                     
    ZMC021                         A       0FISCPER3                      ZICRT_020                      0FISCPER3                    
    ZMC021                         A       0FISCVARNT                     ZICRT_020                      0FISCVARNT                   
    ZMC021                         A       0FISCVARNT                     ZICRT_C07                      0FISCVARNT                   
    ZMC021                         A       0FISCYEAR                      ZICRT_020                      0FISCYEAR                    
    ZMC021                         A       0FISCYEAR                      ZICRT_C07                      0FISCYEAR                    
    note that here ZICRT_020 is a monthly stock cube.
    hope that helps...
    Olivier.

Maybe you are looking for