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

Similar Messages

  • 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 when trying to open C-project due to status

    Hi,
    We have a daily batch job in CRM that reports all the project ID's and
    sends e-mails out to recipients.
    As part of this report it retrieves the statuses for the project ID's,
    however the report short dumps when retrieving the status for one of
    the projects because it is not finding an active status.
    When we try and open the project in C-projects we get the same short
    dump error: CX_DPR_FATAL_ERROR so we cannot view or update the status.
    When we investigate this issue we find that in table CRM_JCDS there are
    3 entries for this project ID. One of the statuses is inactive (I1703)
    but there is another status that is active (I1701). The two status
    entries were created at exactly the same date and time and by the same
    user.
    In table CRM_JEST there is only one entry shown which shows an inactive
    status and we believe this to be the wrong status. Please can you
    advise if this status conflict is causing the problem and also how to
    resolve this issue?

    Hi Paul,
    generally, the project and its elements must have an active status in table CRM_JEST, however, at this point it is not clear how this inconsistency arised. There is no SAP standard report or a 'generally valid' solution that could solve this issue, however, I found a customer message that you have opened in September with exactly the same problem. A colleague from the development team already provided you with a correction report, but there was no feedback from your side if it helped or not.
    It is very difficult to provide help as inconsistencies can have several different causes, so the best would be to have this checked in a customer message with an example.
    Regards,
    Silvia

  • Short Dump when the Bex-Report scheduled for Broadcast

    Hi Guru's
    I am getting the short dump when I am scheduling the Bex-Report for Broadcasting. Need your help to reslove this issue.
    Thanks
    Navin
    Note
    The following error text was processed in the system BDV : The current application triggered a termination with a short dump.
    The error occurred on the application server spdbwd01_BDV_05 and in the work process 0 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Form: INTERNAL_ERROR of program SAPLSDCL
    Form: PHIO_GET_CONTENT_ACCESS of program SAPLSDCI
    Function: SDOK_PHIO_GET_CONTENT_ACCESS of program SAPLSDCI
    Function: SKWF_PHIO_CONTENT_ACCESS_GET of program SAPLSKWF_CONTENT
    Method: COPY_MIME_TO_FOLDER of program CL_RSRA_KWF_UTILITIES=========CP
    Method: GET_STYLESHEET of program CL_RSRA_KWF_TMPL==============CP
    Method: CONSTRUCTOR of program CL_RSRA_KWF_TMPL==============CP
    Method: SET_TEMPLATE_FOLDER of program CL_RSRA_ENGINE_BC=============CP
    Method: CONSTRUCTOR of program CL_RSRA_ENGINE_BC=============CP
    Method: EXECUTE_SINGLE of program CL_RSRA_JOB===================CP

    HI Navin,
    Check the short dump analysis in T-code ST22.
    and also check the Information Broadcast Settings / Configuration
    Check the error for Emails in t-code SCOT. BASIS Consultants will help you on this issue.
    Regards
    Daya Sagar

  • Facing short dumps when trying to open session in CSA

    Hi
    All am facing Short dump when i am trying to open session in CSA
    Error detials:
    go to System Administration workcenter  task management up CSA. Choose the Solution
    got short dump:
    Short text
        Length error occurred in IMPORT statement.
    What happened?
        Error in the ABAP Application Program
        The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
        come across a statement that unfortunately cannot be executed.
    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 "LOAD" "(METHOD)", 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:
        During import the system discovered that the target object has
        a different length than the object to be imported.
    Missing RAISING Clause in Interface
        Program                                 SAPLDSVAS_PROC
        Include                                 LDSVAS_PROCTAI
        Row                                     1.431
        Module type                             (METHOD)
        Module Name                             LOAD
    Trigger Location of Exception
        Program                                 SAPLDSVAS_PROC
        Include                                 LDSVAS_PROCTAI
        Row                                     1.514
        Module type                             (METHOD)
        Module Name                             LOAD
    Please help me to solve this problem
    Regards,
    Neni

    Hello Neni
    According to the information I saw in that post it could be caused by a sort of inconsistency of the program code vs a structure.
    Wether that is a bug that is in your SAP Solution Manager release or something that is caused by administrative actions (perhaps solving SPAU entries after SP stack update or upgrade) I cannot tell.
    I would recommend you either try and find a relative SAP note (narrowing down result to only your SAP Solution Manager system) and searching using the dump keywords. If you cannot find anything I would recommend you to open a customer message so SAP can take a look at the specific error.
    If you give more information, perhaps someone on the forum can help you out abit better, which SAP Solution Manager version and so on.
    You also didn't answer my question, any recent changes you are aware of ?
    Kind regards
    Tom

  • GETWA_NOT_ASSIGNED short dump when load business partner master data

    Hi
    I've this error GETWA_NOT_ASSIGNED short dump when load business partner master data, it's running in BI 7.0 with support package 12.
    The error is because the field symbol is that pointed to the line of an internal table that was deleted.
    I think that it's an incompatibility between subroutine and unicode.
    Do you have idea about correct this error?
    Regards
    Jose.

    Hi Ravi
    Yes, it's a dump
    It's when running a process chain to load Business partner master data
    The error say:
    -.You address a field symbol that pointed to the line of an internal table that was deleted.
    -.You address a field symbol that was previously reset using UNASSIGN or that pointed to a local field that no longer exist.
    -. You address a global function interface, although the respective function module is not active - that is, is not in the list of active calls. the list of active calls can be taken from this short dump.
    I think that it's for the unicode corversion because I've the last support package 12 installed and the rest of the process chain are running perfect.
    My hotmail mail is [email protected] if you need the screen shot.
    Regards and thanks a lot
    Jose

  • 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

  • Short dump when we write more than 4 routines or formulas 4 one source fld

    Hi Experts ,
    We have one source field in a DSO which supplies data to 9 other characteristics present in the cube via formulas. But the system throws a short dump when we write more than 4 routines or formulas.
    Please let us know if there is any restriction in BI 7 as to let only 4 formulas to be written for one source field.
    The below is the description of the short dump
    RUNTIME ERROR : SAP SQL_ARRAY_INSERT_DUPREC
    EXCEPTION : CX_SY_OPEN_SQL_DB
    Help done would be assigned points ...
    Thanks,
    Santosh ...

    Hi,
    thanks for your input
    Rd, rt,re and rs are ranges.
    Select ranges
      RANGES: rd FOR ZMOBILEDATA-COMPID,
              rs FOR ZMOBILEDATA-SUBSCRIBERS,
              rt FOR ZMOBILEDATA-TURNOVER,
              re FOR ZMOBILEDATA-ENTRYDATE.
    thanks'

  • Short Dump When Installing Key Figure Catalog from BI Content

    Hi Friends,
                    I get a Short dump when trying to Install a Key Figure Catalog (in Purchasing) from the BI content. This is what the Error Says ,
    " You Attempted to Use a "NULL" object reference (Points to nothing) access a component (variable : "  "). An Object reference must point to an object (an instance of class ) before it can be used to access components.
    Any input will be greatly appreciated,

    Hi Michal,
    this bug hits only patch level 201 of the DBSL. Please update the DBSl.
    Regarding the ABAP code I do not believe that the hint helps in this case but it should not cause any problems either. If this hint is applied more PREPARE calls are neccessary since before every execution a new statement text is assembled.
    The advantage of SUBSTITUTE_VALUES hints is that the database optimizer get more information through the statement text. The downside is that a new statement is generated every time. E.g. you won't find the statement as a top scorer in a SQL cache analysis if the access plan is still bad.
    Regards
                   Frank

  • Short dump when assigning revision to notification (iw22)

    Hello!
    We have a short dump when we try to assign a revision to a notification in iw22.
    The dump occurs when we save after assigning a revision. We have the lollowing message:
    Message CO888 : Error when reading order header with index
    Include LCOBHIC2, line 39
    The OSS note 1101437 doesn't solve our problem.
    Can you help me?
    Thanks by advance,
    Laurent.

    I tried your tests.
    I haven't a dump neither for the first test nor for the second one.
    The dump occurs only when:
    - I create a notification
    - i create an order and assign it to this notification.
    - i save the notification and the order
    - i assign a revision to the notifiaction and save
    There isn't dump if i assign revision number before the order creation. In fact, the dump only occurs if a assign a revision number after the assignment of the order to the notifiation.
    I'm checking user exit.
    Thanks,
    Laurent.

  • Business Graphic working but short dumping when 'No Data' is available

    Dear Experts,
    I am trying to plot a graph (Bar chart) and it is working very well except when these is no data. In that instance instead of not displaying a data, it is giving short dump.
    I am trying to plot a graph for a project from a list of the projects. In the Context, List of projects is a parent node while the cost data (used for drawing graph) is on child node. Both are with the cardinality of 0..n
    When the project has cost data, graph is working beautifully but when the project does not have a cost data i get short dump.
    Here is the what I get in Internet explorer.
    The following error text was processed in the system UPG : Access via 'NULL' object reference not possible.
    The error occurred on the application server SAPSANDPIT_UPG_00 and in the work process 2 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Method: IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/CBUSINESS_GRAPHICS======CP
    Method: IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/C8STANDARD==============CP
    Method: IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/C8STANDARD==============CP
    Method: IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/C7STANDARD==============CP
    Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program CL_WDR_VIEW_ADAPTER===========CP
    Method: IF_WDR_NW7_DELTA_RENDERER~CALCULATE_DELTA_BLOCKS of program CL_WDR_VIEW_ADAPTER===========CP
    Method: IF_WDR_NW7_DELTA_RENDERER~CALCULATE_DELTA_BLOCKS of program CL_WDR_WINDOW_CONTENT_ADAPTER=CP
    Method: SET_CONTENT of program CL_WDR_NW7_INT_WIN_ADAPTER====CP
    Method: SET_CONTENT of program CL_WDR_NW7_MAIN_WIN_ADAPTER===CP
    Method: IF_WDR_CLIENT~SEND_RESPONSE of program CL_WDR_CLIENT_SSR_LS==========CP
    And here is what is in ST22
    Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED_NO
    Exception              CX_SY_REF_IS_INITIAL          
    Error analysis                                                                    
        An exception occurred that is explained in detail below.                      
        The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not     
         caught in                                                                    
        procedure "IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT" "(METHOD)", 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:                                              
        You attempted to use a 'NULL' object reference (points to 'nothing')          
        access a component.                                                           
        An object reference must point to an object (an instance of a class)          
        before it can be used to access components.                                   
        Either the reference was never set or it was set to 'NULL' using the          
        CLEAR statement.                                                              
    Problem is at following point
                                                                                    mv_CHARTDATA = mv_DATA->create_simple_element( name = 'ChartData' parent = mv_DATA ). "#
    *   >> END_UCA BUSINESS_GRAPHICS|BUSINESS_GRAPHICS|CHARTDATA                                                                               
    *   >> Property: Get BUSINESS_GRAPHICS-SERIES_SOURCE                                       
        mv_SERIES_SOURCE =  get_bound_node( i_binding = wd_BUSINESS_GRAPHICS->bp_SERIES_SOURCE )
                                                                                    *   >> Property: UCA BUSINESS_GRAPHICS-SERIES_ELEMENTS                                     
    *   >> UCA BUSINESS_GRAPHICS|BUSINESS_GRAPHICS|SERIES_ELEMENTS                                                                               
    mv_SERIES_ELEMENTS = mv_SERIES_SOURCE->get_elements( ).                                
    *   >> END_UCA BUSINESS_GRAPHICS|BUSINESS_GRAPHICS|SERIES_ELEMENTS                                                                               
    *   >> Property: UCA BUSINESS_GRAPHICS-SERIES_SOURCE_PATH                                  
    *   >> UCA BUSINESS_GRAPHICS|BUSINESS_GRAPHICS|SERIES_SOURCE_PATH                          
    mv_SERIES_SOURCE IN in above code is initial when data does not exists for a project.
    Thanks in advance for your help.
    ABAPer

    Forgot to add following info from ST22
    Information on where terminated                                                              
        Termination occurred in the ABAP program "/1WDA/CBUSINESS_GRAPHICS======CP" -            
         in "IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT".                                           
        The main program was "SAPMHTTP ".                                                                               
    In the source code you have the termination point in line 753                            
        of the (Include) program "/1WDA/CBUSINESS_GRAPHICS======CCIMP".                          
        The termination is caused because exception "CX_SY_REF_IS_INITIAL" occurred in           
        procedure "IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT" "(METHOD)", but it was               
         neither handled locally nor declared                                                    
        in the RAISING clause of its signature.                                                                               
    The procedure is in program "/1WDA/CBUSINESS_GRAPHICS======CP "; its source              
         code begins in line                                                                     
        390 of the (Include program "/1WDA/CBUSINESS_GRAPHICS======CCIMP ".                      
    Thanks
    ABAPer

  • Buffer Table Not Up To Date Short Dump When Publishing Change Version of Bid Invitation

    Hi experts,
    We are running SRM 5.5 with Support Level 16.
    We have a bid invitation for which a user is trying to publish a Change Version. This bid contains two bid outlines, with one line item in each bid outline:
    ITEM 1: HIER (Bid Outline)
    ITEM 2: Line Item
    ITEM 3: HIER (Bid Outline)
    ITEM 4: Line Item
    However, upon clicking on the Check or Publish button, the system throws a CX_BBP_PD_ABORT exception short dump. The reason for the exception given in ST22 is "Buffer table not up to date".
    Due to organisational system security restrictions, I am unable to copy-paste the dump from ST22, so I will be typing out some of the details here.
    Transaction: BBP_BID_INV
    Program: SAPLBBP_PDH
    Screen: SAPLBBP_BID_INV_1000
    Termination occurred in the ABAP program "SAPLBBP_PDH" - in "BBP_PD_ABORT". The main program was "SAPLBBP_BID_INV".
    In the source code you have the termination point in line 73.
    Active Calls/Events
    (formatted below as "No: Type: Name")
    24: Function: BBP_PD_ABORT
    23: Form: ABORT
    22: Form: ITMADM_UPDATE
    21: Form: ITMADM_MAINTAIN_SINGLE
    20: Form: ITEM_F_CHECK_FROM_WTAB
    19: Form: ITEMLIST_F_CHECK
    18: Function: BBP_ITEMLIST_CHECK
    17: Form: PROCDOC_DB_CHECK
    16: Form: PROCDOC_CHECK
    15: Function: BBP_PROCDOC_CHECK
    14: Form: SSIS_DOCUMENT_CHECK_COMPLETE
    13: Form: STATUS_SET_AND_INTERNAL_SAVE
    12: Form: PROCDOC_UPDATE
    11: Function: BBP_PROCDOC_UPDATE
    10: Form: CHANGE_VERSION_UPDATES_ACTIVE
    9: Function: BBP_PDCV_UPDATE_ACTIVE
    8: Form: PROCDOC_CHECK
    7: Function: BBP_PROCDOC_CHECK
    6: Function: BBP_PD_BID_CHECK
    5: Form: FCODE_DOCUMENT_CHECK
    4: Form: FCODE
    3: Function: BBP_BID_PROCESS
    2: Form: PROCESS
    1: Module (PAI): PROCESS
    The ABORT subroutine is being called in Step 22 (ITMADM_UPDATE), at the following line:
    * parent guids have to be identical ...
    if gt_itmadm-parent <> w_itmadm-parent.
      perform abort.
    endif.
    Upon tracing the variable values in the ST22 dump, it appears the program terminates when processing line 3 (i.e. the second Bid Outline). It appears that the first Bid Outline processes fine.
    In the iteration for Line 3, the dump provides that gt_itmadm-parent contains the GUID to the Change Version document header, whereas w_itmadm-parent contains the GUID to the original Bid Invitation document header, resulting in a mismatch and subsequently program termination.
    We have tried to replicate this bid invitation in our Development environment, but when executing, both gt_itmadm-parent and w_itmadm-parent contain GUIDs to the Change Version document header, hence the program does not abort.
    Any suggestions would be greatly appreciated.
    Thanks!
    Best regards,
    Kwong How

    Hi Janu,
    For Note 1561750, I have looked at the Correction Details and observed that it makes changes to an IF-ELSE block, but will result in the same path of code execution as before. I.e., the Note changes the code from "IF a THEN b, ELSE c" to just "c", but according to my code trace, we are already executing the "ELSE c" block in its current state.
    We will look further into Note 1877600. The unfortunate situation here is that since we are unable to replicate this issue in our Development/QA environment, and the Note description does not explicitly fit the situation we are facing, we need to be very sure that the Note can address the issue before bringing it into Production.
    Otherwise, we will raise a message as suggested.
    Thank you so much for your help!
    Best regards,
    Kwong How

  • Expand Info Provider

    I am trying to create a data transfer process to transfer data ,,
    However under my Info Area/Info Provider
    My InfoProvider is not expandable..
    I can share my screen short for further illustration..
    I don't know what i am doing wrongly.

    Hi
    Have you created Info cube under your Info area in Info provider tab.?
    Can you tell how you created your info cube.?
    If you don't have any data targets under your info area then you can not drill down your Info Area in Info provider tab.
    If you already created info Cube,i think it will be under NOT ASSIGNED FOLDER.
    Just search your Info Cube using find option in RSA1, see under which info area your info provider is.
    Just drag and drop your info provider into your info area.
    Regards,
    Venkatesh.

  • Getting Short dump When Executing MIGO:    SYNTAX_ERROR

    Please Help,
    I am getting this dump, when i hit MIGO transaction
    Runtime Errors         SYNTAX_ERROR
    Date and Time          10.12.2008 08:28:03
         Short text
              Syntax error in program "MB_MIGO_BADI==================CP ".
         What happened?
              Error in the ABAP Application Program
              The current ABAP program "CL_EX_MB_MIGO_BADI============CP" had to be
               terminated because it has
              come across a statement that unfortunately cannot be executed.
              The following syntax error occurred in program
               "MB_MIGO_BADI==================CP " in include
               "MB_MIGO_BADI==================CM000 " in
              line 0:
              "The specified type cannot be converted into the target variables."
              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_EX_MB_MIGO_BADI============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 "MB_MIGO_BADI==================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
               MB_MIGO_BADI==================CP :
              "The specified type cannot be converted into the target variables."
         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 700
              Application server... "DMATE"
              Network address...... "140.1.1.141"
              Operating system..... "Windows NT"
              Release.............. "5.2"
              Hardware type........ "4x AMD64 Level"
              Character length.... 16 Bits
              Pointer length....... 64 Bits
              Work process number.. 1
              Shortdump setting.... "full"
              Database server... "dmate"
              Database type..... "ADABAS D"
              Database name..... "AD0"
              Database user ID.. "SAPAD0"
              Char.set.... "C"
              SAP kernel....... 700
              created (date)... "Jun 23 2008 00:09:46"
              create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
              Database version. "SQLDBC 7.6.0.018 CL 119055 "
              Patch level. 166
              Patch text.. " "
              Database............. "MaxDB 7.6, MaxDB 7.7"
              SAP database version. 700
              Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
               NT 6.0"
              Memory consumption
              Roll.... 16192
              EM...... 8379680
              Heap.... 0
              Page.... 40960
              MM Used. 1627776
              MM Free. 2559440
         User and Transaction
              Client.............. 040
              User................ "LAKSHMI"
              Language key........ "E"
              Transaction......... "MIGO "
              Transactions ID..... "EE72C6DDC96BF1F99FA4001143E563CA"
              Program............. "CL_EX_MB_MIGO_BADI============CP"
              Screen.............. "SAPLMIGO 0001"
              Screen line......... 2
         Information on where terminated
              Termination occurred in the ABAP program "CL_EX_MB_MIGO_BADI============CP" -
               in "IF_EX_MB_MIGO_BADI~INIT".
              The main program was "SAPLMIGO ".
              In the source code you have the termination point in line 1
              of the (Include) program "CL_EX_MB_MIGO_BADI============CM001".
         Source Code Extract
         Line     SourceCde
         >>>>>     method IF_EX_MB_MIGO_BADI~INIT.
             2       CLASS CL_EXIT_MASTER DEFINITION LOAD.
             3     
             4       DATA l_badi TYPE REF TO MB_MIGO_BADI.
             5     
             6     
             7     
             8     
             9     
            10       TRY.
            11     
            12         GET BADI l_badi
            13          CONTEXT me.
            14     
            15         CALL BADI l_badi->INIT
            16     
            17          CHANGING
            18            CT_INIT = CT_INIT.
            19     
            20     
         Contents of system fields
         Name     Val.
         SY-SUBRC     0
         SY-INDEX     0
         SY-TABIX     1
         SY-DBCNT     1
         SY-FDPOS     1
         SY-LSIND     0
         SY-PAGNO     0
         SY-LINNO     1
         SY-COLNO     1
         SY-PFKEY     
         SY-UCOMM     
         SY-TITLE     
         SY-MSGTY     S
         SY-MSGID     VBDOCUBATCH
         SY-MSGNO     001
         SY-MSGV1     
         SY-MSGV2     
         SY-MSGV3     
         SY-MSGV4     
         SY-MODNO     0
         SY-DATUM     20081210
         SY-UZEIT     082802
         SY-XPROG     
         SY-XFORM     
         Active Calls/Events
         No.   Ty.          Program                             Include                             Line
               Name
             4 METHOD       CL_EX_MB_MIGO_BADI============CP    CL_EX_MB_MIGO_BADI============CM001     1
               CL_EX_MB_MIGO_BADI=>IF_EX_MB_MIGO_BADI~INIT
             3 METHOD       SAPLMIGO                            LMIGOGL2                               54
               LCL_MIGO_GLOBALS=>CLASS_CONSTRUCTOR
             2 FORM         SAPLMIGO                            LMIGOIN1                               11
               INITIALIZATION
             1 MODULE (PBO) SAPLMIGO                            LMIGOPBO                               11
               PBO_INITILIZATION
         Chosen variables
         Name
             Val.
         No.          4     Ty.      METHOD
         Name      CL_EX_MB_MIGO_BADI=>IF_EX_MB_MIGO_BADI~INIT
         CT_INIT
              Table[initial]
         %_DUMMY$$
                 2222
                 0000
                 0000
                 0000
         SYST-REPID
              CL_EX_MB_MIGO_BADI============CP
                 4454554454444544443333333333334522222222
                 3CF58FD2FD97FF2149DDDDDDDDDDDD3000000000
                 0000000000000000000000000000000000000000
                 0000000000000000000000000000000000000000
         SY-SUBRC
              0
                 0000
                 0000
         No.          3     Ty.      METHOD
         Name      LCL_MIGO_GLOBALS=>CLASS_CONSTRUCTOR
         SY-REPID
              SAPLMIGO
                 5454444422222222222222222222222222222222
                 310CD97F00000000000000000000000000000000
                 0000000000000000000000000000000000000000
                 0000000000000000000000000000000000000000
         LCL_MIGO_GLOBALS=>CNTL_ERROR
                 2
                 0
                 0
                 0
         ABAP_FALSE
                 2
                 0
                 0
                 0
         SYST-REPID
              SAPLMIGO
                 5454444422222222222222222222222222222222
                 310CD97F00000000000000000000000000000000
                 0000000000000000000000000000000000000000
                 0000000000000000000000000000000000000000
         GOSEARCH_PO
                 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
         TEXT-220
              Dest
                 46772222
                 45340000
                 00000000
                 00000000
         %_SPACE
                 2
                 0
                 0
                 0
         %_TAG*TS_GOITEM
              <initial>
                 <initial>
                 <initial>
         X
              X
                 5
                 8
                 0
                 0
         LCL_MIGO_GLOBALS=>IF_BADI
                 F0000000
                 70008000
         %_FL2*TV_GOFREIGHT
              <initial>
                 <initial>
                 <initial>
         %_PRINT
                  000                                                                                0###
                 2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
         LCL_MIGO_GLOBALS=>T_BADI
              Table[initial]
         /SPE/CL_INB_ACTION_INFO=>C_DIALOG_MIGO
         SCREEN
                 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
         OREF_TITLEBAR
                 F0000000
                 F0000000
         L_BADIS_1
              0
                 0000
                 0000
         SY-MSGID
              VBDOCUBATCH
                 54444544544222222222
                 624F3521438000000000
                 00000000000000000000
                 00000000000000000000
         OREF_TIP
                 F0000000
                 F0000000
         TV_GOSERIAL-CX
              <initial>
                 <initial>
                 <initial>
         SPACE
                 2
                 0
                 0
                 0
         SY-MSGNO
              001
                 333
                 001
                 000
                 000
         No.          2     Ty.      FORM
         Name      INITIALIZATION
         OREF_ARCH
                 F0000000
                 F0000000
         LCL_MIGO_GLOBALS=>KERNEL
                 F0000000
                 D0002000
         %_CX_TABLEVIEW_VERSION
              0
                 3
                 0
                 0
                 0
         GODEFAULT-DEF_XBOM
                 2
                 0
                 0
                 0
         LCL_MIGO_GLOBALS=>KERNEL->C_REFDOCTYPE_MATDOC
              MAT
                 445
                 D14
                 000
                 000
         No.          1     Ty.      MODULE (PBO)
         Name      PBO_INITILIZATION
         GOITEM-UMWRK
                 2222
                 0000
                 0000
                 0000
         GOITEM-UMNAME1
                 222222222222222222222222222222
                 000000000000000000000000000000
                 000000000000000000000000000000
                 000000000000000000000000000000
         Internal notes
              The termination was triggered in function "ab_genprog"
              of the SAP kernel, in line 1551 of the module
               "//bas/700_REL/src/krn/runt/abgen.c#10".
              The internal operation just processed is "CPOP".
              Internal mode was started at 20081210082802.
              Program name.........: "MB_MIGO_BADI==================CP ".
              Error message........: "The specified type cannot be converted into the target
               variables.".
         Active Calls in SAP Kernel
         Lines of C Stack in Kernel (Structure Differs on Each Platform)
         SAP (R) - R/3(TM) Callstack, Version 1.0
         Copyright (C) SAP AG. All rights reserved.
         Callstack without Exception:
         App       : disp+work.EXE (pid=5776)
         When      : 12/10/2008 8:28:3.84
         Threads   : 2
         Computer Name       : DMATE
         User Name           : SAPServiceAD0
         Number of Processors: 4
         Processor Type: EM64T Family 15 Model 4 Stepping 1
         Windows Version     : 5.2 Current Build: 3790
         State Dump for Thread Id 14f0
         FramePtr         ReturnAd         Param#1          Function Name
         0000000007eb8800 0000000077d7047f 00000000411b4070 ntdll!NtWaitForSingleObject
         0000000007eb88a0 000000000173b1d1 000000000000042c kernel32!WaitForSingleObjectEx
         0000000007eb8af0 00000000006179c5 0000000000000001 disp+work!NTDebugProcess [ntstcdbg.c (501)]
         0000000007eb8b20 0000000000b05d9c 0000000000000001 disp+work!CTrcStack [dptstack.c (182)]
         0000000007eb8b70 0000000000b0afc0 0000000000000001 disp+work!rabax_CStackSave [abrabax.c (7093)]
         0000000007eb9550 0000000000a51c94 0000000001d12320 disp+work!ab_rabax [abrabax.c (1231)]
         0000000007ebc220 00000000007f753a 0000000000000001 disp+work!ab_genprog [abgen.c (1555)]
         0000000007ebc2f0 00000000007f7dc8 00000000ffffffff disp+work!newload [abload1.c (336)]
         0000000007ebc350 00000000007f7e8e 0000000000000056 disp+work!ab_LoadProgOrTrfo [abload1.c (160)]
         0000000007ebc380 00000000007bc84d 000007fe725a5f70 disp+work!ab_LoadProg [abload1.c (78)]
         0000000007ebc450 00000000007be91a 00002a441022f402 disp+work!LoadGlobalClass [abobject.c (943)]
         0000000007ebc4a0 00000000007c1bdd 0000000000000000 disp+work!ab_FillCfix [abobject.c (1603)]
         0000000007ebc580 000000000083ae52 0000000000000000 disp+work!ab_jaboo [abobject.c (2248)]
         0000000007ebc700 0000000000a1ccb7 000000000000000d disp+work!ab_extri [abextri.c (554)]
         0000000007ebc750 0000000000ad50ac 000000000000000d disp+work!ab_xevent [abrunt1.c (281)]
         0000000007ebc7e0 0000000000679328 000000000000000d disp+work!ab_dstep [abdynpro.c (492)]
         0000000007ebc960 000000000067d02d 000007fe725d6f20 disp+work!dynpmcal [dymainstp.c (2396)]
         0000000007ebc9f0 000000000067ca2a 0000000000000000 disp+work!dynppbo0 [dymainstp.c (543)]
         0000000007ebcaa0 00000000006395c5 0000000000000000 disp+work!dynprctl [dymainstp.c (360)]
         0000000007ebfc30 00000000004dbc4c 000000000000000c disp+work!dynpen00 [dymain.c (1646)]
         0000000007ebfeb0 000000000042f096 0000000007f62ff0 disp+work!TskhLoop [thxxhead.c (4538)]
         0000000007ebfee0 000000000040108d ffffffff00000003 disp+work!DpMain [dpxxdisp.c (1136)]
         0000000007ebff10 00000000019e84b1 0000000000000000 disp+work!nlsui_main [thxxanf.c (84)]
         0000000007ebff70 0000000077d5966c 0000000000000000 disp+work!wmainCRTStartup [crtexe.c (498)]
         0000000007ebffa0 0000000000000000 00000000019e8340 kernel32!BaseProcessStart
         State Dump for Thread Id b94
         FramePtr         ReturnAd         Param#1          Function Name
         000000000c9dfe40 0000000077d5f651 0000000000000000 ntdll!NtFsControlFile
         000000000c9dfeb0 00000000018ce23f fffffffffffffffe kernel32!ConnectNamedPipe
         000000000c9dff40 000007ff7fc411c4 0000000000000000 disp+work!SigIMsgFunc [signt.c (679)]
         000000000c9dff70 0000000077d6b69a 0000000077d6b660 msvcrt!endthreadex
         000000000c9dffa0 0000000000000000 0000000000000000 kernel32!BaseThreadStart
         List of ABAP programs affected
         Index     Typ     Program     Group     Date     Time     Size     Lang.
              0     Prg     SAPLMIGO          0     04.05.2008     12:54:34       1561600     E
              1     Prg     SAPMSSYD          0     25.02.2008     17:02:32         21504     E
              2     Prg     SAPFSYSCALLS          0     09.09.2004     14:18:32          7168     E
              3     Prg     CL_MMIM_USERDEFAULTS==========CP          3     06.05.2002     10:42:38         21504     E
              4     Typ     ESDUS          0     01.03.1999     13:36:04          2048     
              5     Typ     GOHEAD          0     07.02.2006     10:07:36         11264     
              6     Typ     MKPF          0     25.08.2005     22:02:19          7168     
              7     Typ     KBEFU          0     16.03.2008     17:46:49          6144     
              8     Typ     LFA1          0     16.03.2008     17:47:20         22528     
              9     Typ     MIGO_CUST_ACTION          0     30.11.1999     10:19:14          3072     
             10     Typ     MIGO_CUST_REFDOC          0     30.11.1999     10:19:14          2048     
             11     Typ     X031L          0     05.07.2005     13:10:15          6144     
             12     Prg     SAPLSDIFRUNTIME         12     19.11.2006     16:35:34         96256     E
             13     Typ     DFIES          0     28.12.2004     17:06:45         10240     
             14     Prg     SAPLSDNT         14     09.03.2008     19:02:04        219136     E
             15     Prg     SAPLSUGS         15     31.03.2006     11:23:11         47104     E
             16     Prg     SAPLV01D         16     24.03.2008     17:03:30         40960     E
             17     Typ     IWRKZ          0     04.04.1995     15:56:46          2048     
             18     Typ     TCUCH          0     07.01.2002     15:50:54          3072     
             19     Typ     TCUBN          0     07.01.2002     15:50:53          2048     
             20     Typ     TCUWS          0     13.08.1997     13:57:58          2048     
             21     Typ     TCUDRV          0     07.01.2002     15:50:54          2048     
             22     Prg     SAPLVBDOCUBATCH_BF         22     16.01.2004     14:28:56         10240     E
             23     Typ     TCUDB          0     14.01.2004     10:05:59          2048     
             24     Prg     CL_GUI_CFW====================CP         24     28.02.2005     21:03:09        168960     E
             25     Prg     CL_GUI_PROPS_CONSUMER=========CP         25     18.03.2008     13:25:33         29696     E
             26     Prg     %_CCNTL         25     18.02.2005     14:15:08         15360     E
             27     Prg     SAPLTHFB         27     18.03.2008     13:24:52        394240     E
             28     Typ     EUDB          0     06.11.2003     20:28:08          8192     
             29     Typ     TCURM          0     01.03.2005     10:56:26          5120     
             30     Prg     CL_EXITHANDLER================CP         30     18.03.2008     13:11:35         30720     E
             31     Prg     SAPLSEXV         31     18.03.2008     13:12:58        117760     E
             32     Typ     SXS_ATTR          0     07.02.2006     10:09:24          5120     
             33     Typ     BADIISIMPLED          0     19.05.2005     19:10:34          3072     
             34     Prg     CL_ENH_BADI_TOOL_UTILITIES====CP         34     17.03.2008     11:03:36         13312     E
             35     Typ     BADI_MAIN          0     08.12.2004     18:01:11          2048     
             36     Typ     BADI_IMPL          0     09.12.2004     19:05:43          3072     
             37     Typ     TADIR          0     07.02.2006     10:08:38          5120     
             38     Prg     CL_SWITCH=====================CP         38     17.03.2008     11:13:47         19456     E
             39     Typ     SFW_PACKAGE          0     07.03.2008     12:18:16          2048     
             40     Prg     CL_ABAP_SWITCH================CP         40     14.10.2006     15:40:30         33792     E
             41     Prg     SAPLPA_PACKAGE_SERVICES         41     18.03.2008     13:12:54        152576     E
             42     Typ     TDEVC          0     08.12.2004     18:02:41          6144     
             43     Prg     CL_EX_MB_MIGO_BADI============CP         43     05.12.2008     17:09:58         30720     E
             44     Prg     IF_EX_MB_MIGO_BADI============IP         30     19.05.2005     19:30:39         14336     E
             45     Typ     SYST          0     09.09.2004     14:18:12         31744     
             46     Typ     GOSEARCH_PO          0     20.07.2001     19:17:34          4096     
             47     Prg     /SPE/CL_INB_ACTION_INFO=======CP         47     24.03.2008     20:30:06         20480     E
             48     Prg     /SPE/IF_CONST=================IP         47     14.10.2006     18:49:02          7168     E
             49     Typ     GODEFAULT          0     14.01.2004     10:04:46          5120     
             50     Typ     GOITEM          0     07.02.2006     10:07:36         65536     
         Directory of Application Tables
         Name                                     Date       Time       Lngth
             Val.
         Program      SAPLMIGO
         SYST            .  .            :  :          00004612
              \0\0\0\0\x0001\0\x0370\0\0\0\0\0\0\0\0\0\0\0\0\0\x0001\0
         GOITEM            .  .            :  :          00005524
                        00000000000000000000
         GOSEARCH_PO            .  .            :  :          00000492
         GODEFAULT            .  .            :  :          00000220
         Program      SAPLV01D
         TCUCH            .  .            :  :          00000122
              0401100020061029095148ANOOPJ      00000000000000
         TCUWS            .  .            :  :          00000060
              040020061227101454CONSULTANT     
         TCUBN            .  .            :  :          00000060
              040020061227101454CONSULTANT     
         TCUDRV            .  .            :  :          00000064
                    00000000000000     
         Program      CL_GUI_PROPS_CONSUMER=========CP
         EUDB            .  .            :  :          00004068
              %CAA72C6DDAD55F1179FA4001143E563CA         \0\0\0
         ABAP Control Blocks (CONT)
         Index     Name     Fl     PAR0     PAR1     PAR2     PAR3     PAR4     PAR5     PAR6     Source Code     Line
            94     BRAX     01     FFEB                                   CL_EX_MB_MIGO_BADI============CM001           15
            95     CLEA     00     0020                                   CL_EX_MB_MIGO_BADI============CM001           15
            96     EXCP     08     0000                                   CL_EX_MB_MIGO_BADI============CM001           22
            97     BRAX     00     0005                                   CL_EX_MB_MIGO_BADI============CM001           22
            98     EXCP     00     0007                                   CL_EX_MB_MIGO_BADI============CM001           22
            99     BRAX     00     0003                                   CL_EX_MB_MIGO_BADI============CM001           22
           100     EXCP     07     0000                                   CL_EX_MB_MIGO_BADI============CM001           22
           101     BRAX     00     0001                                   CL_EX_MB_MIGO_BADI============CM001           23
           102     EXCP     0B     0000                                   CL_EX_MB_MIGO_BADI============CM001           23
           103     METH     01     0000     0000     0000     0000     0000     0000     0000     CL_EX_MB_MIGO_BADI============CM001           24
           107     -
         00     0000                                   CL_EX_MB_MIGO_BADI============CM001           24
           108     ABOO     02     0000     0005     0000                         CL_EX_MB_MIGO_BADI============CM001            1
         >>>>>     CPOP     00     0000                                   CL_EX_MB_MIGO_BADI============CM001            1
           111     -
         00     0000                                   CL_EX_MB_MIGO_BADI============CM001            1
           112     METH     04     0000     0005     0002     0000     0003     0000     0000     CL_EX_MB_MIGO_BADI============CM002            1
           116     PAR2     04     0000     C000     0000                         CL_EX_MB_MIGO_BADI============CM002            1
           118     PAR2     04     0000     C001     0000                         CL_EX_MB_MIGO_BADI============CM002            1
           120     PAR2     14     0000     C002     0000                         CL_EX_MB_MIGO_BADI============CM002            1
           122     PAR2     14     0000     C003     0000                         CL_EX_MB_MIGO_BADI============CM002            1
           124     PAR2     14     0000     C004     0000                         CL_EX_MB_MIGO_BADI============CM002            1

    Hai,
    Seems to be problem with the Program.
    Please check the point 'What Happened' in the dump for more details.
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_EX_MB_MIGO_BADI============CP" had to be
    terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program
    "MB_MIGO_BADI==================CP " in include
    "MB_MIGO_BADI==================CM000 " in
    line 0:
    "The specified type cannot be converted into the target variables."
    Error in the ABAP Application Program
    The current ABAP program "CL_EX_MB_MIGO_BADI============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 "MB_MIGO_BADI==================CP
    You can also perform the syntax check from the ABAP Editor.
    Take help from a ABAP consultant and try to check the syntax of the Program.
    If you have access even you can check the syntax of the specified program from SE38.
    Goto SE38 and put the program name and select 'Source code' and press F8, IN THE SOURCE CODE PAGE, press control+F2 and check whether there is any problem with the syntax or not.
    If you find any take help from ABAP consultants.
    Hope this helps.
    Regards,
    Yoganand.V

  • Short dump when I do total or sub total in the ALV report

    Hi,
    When I do total or sub-total on the currency field in the ALV report, it'll give a short dump like
    " 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)".
       Short text of error message:
       Technical information about the message:
       Message classe...... "0K"
       Number.............. 000
       Variable 1.......... " "
       Variable 2.......... " "
       Variable 3.......... " "
       Variable 4.......... " "
       Variable 3.......... " "
       Variable 4.......... " "
    Trigger Location of Runtime Error
        Program                                 SAPLSLVC
        Include                                 LSLVCF36
        Row                                     2,726
        Module type                             (FORM)
        Module Name                             FILL_DATA_TABLE
    sometime when I do the page down on the ALV report, the same short dump is coming.
    Can anyone help me out.
    Thanks
    Selva

    Hi,
    I'm getting this short dump in the standard program.
    I'm getting ALV report display perfectly. the problem is, when I do total or subtotal on the currency fields.
    2704
    2705 ************************************
    2706 * Column per Fieldcat Entry
    2707 ************************************
    2708         ls_lvc_data-value = space.
    2709         clear ls_lvc_data-style.
    2710         loop at it_fcat_local assigning <ls_fcat>
    2711                 where tech ne 'X' and no_out ne 'X'.
    2712           if l_invisible eq 'X'.
    2713             clear l_invisible.
    2714             if <ls_fcat>-do_sum is initial.
    2715               continue.
    2716             else.
    2717               clear ls_lvc_data-col_pos.
    2718             endif.
    2719           endif.
    2720
    2721           add 1 to ls_lvc_data-col_pos.
    2722
    2723           assign component <ls_fcat>-fieldname
    2724                            of structure <ls_data> to <l_field_value>.
    2725           if sy-subrc ne 0.
    >>>>>             message x000(0k).
    2727           endif.
    2728
    in this standard program, I'm getting the dump. the line is mentioned above in the code.

Maybe you are looking for

  • CAN NOT OPEN  CANON EOS20D  RAW FILE IN PHOTOSHOP CS2

    I had Photoshop CS2 installed on my PC some years ago and could open my raw files from my canon eos 20d. I changed the hard drives in my pc to solid state drives and had to reinstall photoshop cs2. I could not activate photoshop as it was too old a v

  • After upgrading to Yosemite, I don't receive email from Gmail users

    Using a MacBook Pro, 2.8 GHz Intel Core 2 Duo, 8 GB RAM, 1 TB SSD internal hard drive.  OSX v10.10.2 My primary email address is an .mac/.me/.icloud email address. Recently upgraded to Yosemite.  After doing so, I am having trouble receiving emails f

  • How to add a title to button in flash?

    Hi, I have a button in flash and a action layer with the following script: button1.addEventListener(MouseEvent.CLICK,clickHandler); function clickHandler(event:MouseEvent):void{ navigateToURL(new URLRequest("http://mortimerhall.99k.org/homepage.htm")

  • Report conversion tool--Can we modify the query

    Hi all, I have some freehand SQL reports converted into WebI reports. I understand that report conversion tool, creates a new universe for each of the freehand SQL report. But if I try to edit the query, like add a filter condition, an error pops out

  • What is the message type in a bindingFault?

    I have an invoke that sometimes gets a bindingFault that I'd like to catch. What is the message type for the fault variable of a bindingFault? More generally, where does one go to find the message type for any of the standard system faults? Bret