Short Dump-Syntax error program"CL_RSD_MULTIPROV==CP" after EHP1SP5 upgrade

Hi,
     MultiProvider Activation/Display data is resulting into short dump with following text
Error in the ABAP Application Program
The current ABAP program "CL_RSD_MULTIPROV_CHECK========CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program
"CL_RSD_MULTIPROV==============CP " in include
"CL_RSD_MULTIPROV==============CM010 " in
line 1:
"Method "CHECK_LINITFL" is not declared or inherited in class "CL_RSD_M"
"ULTIPROV". -"
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_RSD_MULTIPROV_CHECK========CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
          We have recently upgraded to EHP1SP5. We noticed this issue just after that.
Regards,
PD

Hi,
Please check the note 1461401.
1461401 - System error in the program CL_RSD_MULTIPROV_CHECK
This note should help you.
Regards,
Rafael

Similar Messages

  • St22 dump : Syntax error in program "SAPLCRM_KNOWLEDGE ".

    Hello experts,
    When i click on Define Template for folder in SPRO ( spro -> customer relation relationship management>
    basic function --> content management ---> define template for folder) it goes to dump.
    Runtime Errors         SYNTAX_ERROR
    Short text :Syntax error in program "SAPLCRM_KNOWLEDGE ".
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "SAPLSVIM" had to be terminated because it has
         come across a statement that unfortunately cannot be executed.
         The following syntax error occurred in program "SAPLCRM_KNOWLEDGE " in include
          "LCRM_KNOWLEDGEF03 " in
         line 71:
         ""ICFALIAS" must be a flat structure. You cannot use internal tables, s"
         "trings, references, or structures as components. -"
         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 "SAPLSVIM" had to be terminated because it has
         come across a statement that unfortunately cannot be executed.
    Error analysis
        The following syntax error was found in the program SAPLCRM_KNOWLEDGE :
        ""ICFALIAS" must be a flat structure. You cannot use internal tables, s"
        "trings, references, or structures as components. -"
    The version of CRM is crm 2007 with support stack sp02
    Regards
    Ranadhir

    Thanks Venkataramanan, after the implementing the note 1117598 and 1101434 the problem solved.
    Regards
    Ranadhir

  • SE80 Dump - Syntax error in program CL_GUI_ALV_GRID

    Hi,
    We have applied 2 sap notes and after this there were some inactive objects.
    1353846 & 875986.If i go ST22 /SE 80 i am getting thes dumps.. I tried checking inactive object via SE38/Environment Se24/Environment i get the same dump..
    Unkowingly We did it in wrong sequence so de-implemented but still have some inactive objects how do we activate those class files.
    Already logged a ticket with SAP but curious to know if there is anyway to resolve this issue.
    Short text
         Syntax error in program "CL_GUI_ALV_GRID===============CP ".
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "CL_DD_AREA====================CP" had to b
          terminated because it has
         come across a statement that unfortunately cannot be executed.
         The following syntax error occurred in program
          "CL_GUI_ALV_GRID===============CP " in include
          "CL_SALV_BS_DATA===============CU " in
         line 10:
         "Type "IF_SALV_BS_DATA" is unknown"
         The include has been created and last changed by:
         Created by: "SAP "
          Error in the ABAP Application Program
         The current ABAP program "CL_DD_AREA====================CP" had to b
          terminated because it has
         come across a statement that unfortunately cannot be executed.
    Rgds
    Vara

    Hi Vara,
    it depends on what notes you applied, what release you are on. Frequently notes have preconditions (i.e. applying other notes) or some manual work must be done like modifying function interfaces.
    Go through the notes again, tell us the numbers.
    Regards,
    Clemens

  • Getting short dumps "Sysntax error in program SAPLDNO_SAP

    Could anyone have idea what is it about

    This what I am getting on st22
    untime Errors         SYNTAX_ERROR
    Date and Time          22.09.2008 06:49:28
    Short text
    Syntax error in program "SAPLDNO_SAP ".
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "RNOTIFUPDATE01" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "SAPLDNO_SAP " in include
    "AI_SDK_GET_SAPNET_USER_ID=====E " in
    line 24:
    "The field "P_GUIDH" is unknown, but there is a field with the similar "
    "name "LV_GUIDH". "LV_GUIDH"."
    The include has been created and last changed by:
    Created by: "SAP "
    Last changed by: "DDIC "
    Error in the ABAP Application Program
    The current ABAP program "RNOTIFUPDATE01" 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 "SAPLDNO_SAP ".
    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 SAPLDNO_SAP :
    "The field "P_GUIDH" is unknown, but there is a field with the similar "
    "name "LV_GUIDH". "LV_GUIDH"."
    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.
    |

  • **Error** Scene 1, Layer 'actions', Frame 1, Line 664: 1087: Syntax error: extra characters found after end of program.

    Scene 1, Layer 'actions', Frame 1, Line 664: 1087: Syntax
    error: extra characters found after end of program.
    I am new to importing classes and I have been practicing
    making a photo gallery. I am stuck and I want to know if someone
    can help me with the error I am getting.
    If it is convenient, you can download and test my .zip at
    www.dhtmlguy.freeservers.com
    Thanks in advance!

    thanks...the small stuff gets me every time.

  • Short dump in standard program

    Hi Friends,
    below description is short dump for standard program.
    Please see the below and help me how to correct the program.
    The current application triggered a termination with a short dump.            
    What happened?
    The current application program detected a situation which really             
    should not occur. Therefore, a termination with a short dump was              
    triggered on purpose by the key word MESSAGE (type X).                      
    Error analysis
    Short text of error message:                                                  
    Internal error: Program   , include   , form   .                                                                               
    Technical information about the message:                                      
    Diagnosis                                                                    
         An unexpected error has occurred.                                        
    Procedure                                                                    
         If you can reproduce the error, contact the SAP Hotline quoting the      
         error number.                                                            
    Message classe...... "GR"                                                     
    Number.............. 214   
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.       
                                                                                    You may able to find an interim solution to the problem                       
    in the SAP note system. If you have access to the note system yourself,       
    use the following search criteria:                                                                               
    "MESSAGE_TYPE_X" C                                                            
    "SAPFGRWE" or "FGRWEF80_F80_FILL_COL_TAB"                                     
    "F80_FILL_COL_TAB"                                                            
    If you cannot solve the problem yourself, please send the                     
    following documents to SAP:                                                                               
    1. A hard copy print describing the problem.                                  
       To obtain this, select the "Print" function on the current screen.         
                                                                                    2. A suitable hardcopy prinout of the system log.                             
       To obtain this, call the system log with Transaction SM21                  
       and select the "Print" function to print out the relevant                  
       part.                                                                               
    3. If the programs are your own programs or modified SAP programs,            
       supply the source code.                                                    
       To do this, you can either use the "PRINT" command in the editor or        
       print the programs using the report RSINCL00.                                                                               
    4. Details regarding the conditions under which the error occurred            
       or which actions and input led to the error.                               
    Thanks & Regards,
    Sree
    Edited by: adepus on Oct 7, 2009 12:39 PM
    Edited by: adepus on Oct 7, 2009 12:39 PM

    Hi Clemens,
    I am getting a dump error as shown below. Could you please find some resolution for this issue. we just made some changes to the transaction GS02(Just added a GL account to one of the sets).
    Runtime Error MESSAGE_TYPE_X
    ShrtText
    The current application triggered a termination with a short dump.
    What happened?
    The current application program detected a situation which really
    should not occur. Therefore, a termination with a short dump was
    triggered on purpose by the key word MESSAGE (type X).
    What can you do?
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    is especially useful if you want to keep a particular message.
    Error analysis
    Short text of error message:
    Internal error: Program , include , form .
    Technical information about the message:
    Diagnosis
    An unexpected error has occurred.
    Procedure
    If you can reproduce the error, contact the SAP Hotline quoting the
    error number.
    Message classe...... "GR"
    Number.............. 214
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
    to correct the error
    Probably the only way to eliminate the error is to correct the program.
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "MESSAGE_TYPE_X" C
    "SAPFGRWE" or "FGRWEF80_F80_FILL_COL_TAB"
    "F80_FILL_COL_TAB"
    If you cannot solve the problem yourself and you wish to send
    an error message to SAP, include the following documents:
    1. A printout of the problem description (short dump)
    To obtain this, select in the current display "System->List->
    Save->Local File (unconverted)".
    2. A suitable printout of the system log
    To obtain this, call the system log through transaction SM21.
    Limit the time interval to 10 minutes before and 5 minutes
    after the short dump. In the display, then select the function
    "System->List->Save->Local File (unconverted)".
    3. If the programs are your own programs or modified SAP programs,
    supply the source code.
    To do this, select the Editor function "Further Utilities->
    Upload/Download->Download".
    4. Details regarding the conditions under which the error occurred
    or which actions and input led to the error.
    Source Code
    79 MESSAGE x214.
    80 ENDIF.
    81 PERFORM e08_read_object_index(sapfgsb0)
    82 USING fcolumns-dim_index.
    83 IF c-subrc 0. MESSAGE x214. ENDIF.
    84 c_dsentry = c-tval-from.
    85 IF c_dsentry '='.
    86 READ TABLE data_fields BINARY SEARCH
    87 WITH KEY tab = rep_table
    88 dsentry = c_dsentry.
    >>>> IF sy-subrc 0. MESSAGE x214. ENDIF.
    90 ENDIF.
    91 WHEN OTHERS.
    92 c_dsentry = '*'.
    93 ENDCASE.
    94 ENDIF.
    Regards,
    Pavan

  • What are the major situations  to go to the short dump in abap programming?

    What are the major situations  to go to the short dump in abap programming?

    Hi,
    The major situations that an ABAP Program can result a dumb are as follows...
    1) Poor coding i.e., if the data in the data base is less, then even a poor code can give you the result.  But when you transport the program into Production, then there the same program will give you a dump, resulting 'TIMED OUT' error.  So performance tunning is required for each and every program.
    2) while calling a function module.
    3) extracting of data into fields which are not type casted.
    4) in case of x/y value, one should check the value of 'y' should not be zero, else a dump will result.
    these are few which i can give for time being........

  • Application triggered a termination with a short dump(Assessment error)

    Hi,
    I created one accessment cycle with couple of segments. While executing this assessment cycle one of the segment is erroring out and it's throwing a runtime error. I searched in OSS and didn't find the right one. I really appreciate your thoughts and answers.
    Short text                                                                                |
    The current application triggered a termination with a short dump.
    Error analysis
    Short text of error message:
    Error ERROR_BW_REFBZ
    Long text of error message:
    Diagnosis
    The following program error or handling error has occurred.
    Error information:
    ERROR_BW_REFBZ
    System Response
    |         Processing is terminated. 
    Thanks
    Br

    Thanks for your quick response Baranyai and we set transfer prices indicator at controlling area level and it's related to profit center valuation. How is going to impact on Assessment cycle and it doesn't appear while creating and executing assessment cycle. I may be wrong and really appreciate your help.
    Thanks
    Br

  • Syntax error in program "CL_HTTP_SERVER=CP " after EHP4 Upgrade

    Hi All,
    Iam getting ABAP dumps after upgrading my system to EHP4  Windows ABAP+JAVA stack,
    Syntax error in program "CL_HTTP_SERVER================CP ".
    Error in the ABAP Application Program
    The current ABAP program "SAPLHTTP_RUNTIME" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program
    "CL_HTTP_SERVER================CP " in include
    "CL_HTTP_SERVER================CM00F " in
    line 15:
    "Field "C_IS_SHOW_SERVER_HEADER" is unknown. It is neither in one of th"
    "e specified tables nor defined by a "DATA" statement. ."
    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 "SAPLHTTP_RUNTIME" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    What can you do?
        Please eliminate the error by performing a syntax check
        (or an extended program check) on the program "CL_HTTP_SERVER================CP
        You can also perform the syntax check from the ABAP Editor.
        If the problem persists, proceed as follows:
        Note down which actions and inputs caused the error.
        To process the problem further, contact you SAP system
        administrator.
        Using Transaction ST22 for ABAP Dump Analysis, you can look
        at and manage termination messages, and you can also
        keep them for a long time.
    Error analysis
        The following syntax error was found in the program
         CL_HTTP_SERVER================CP :
        "Field "C_IS_SHOW_SERVER_HEADER" is unknown. It is neither in one of th"
        "e specified tables nor defined by a "DATA" statement. ."
    Regards
    Uday

    Hi,
    SPDD should be performed before ACT_UPG phase when system prompts you for SPDD. But now you cannot do SPDD phase. All the objects that came during SPDD phase has been resetted to new objects which SAP has delivered with EHP4.
    SPAU you can perform after upgrade and that too with in 14 days when upgrade finished without object key.
    I should suggest you to read upgrade guide on http://service.sap.com/erp-ehp.
    Thanks
    Sunny

  • How to resolve the dump Syntax error in program /1BCWDY/824VCAJI0ED4WMLLJ7N

    I have created 4 components and I have linked them to a single web dynpro application component through an interface.
    This is working fine in development.
    When we moved all these objects to quality and when i run the application it is opening the default component. However when i try to call any other component it is giving the following dump.
    Syntax error in program /1BCWDY/824VCAJI0ED4WMLLJ7NV==CP.
    When we debugged we found that this dump is arising in the CREATE COMPONENT method.
    Please suggest how to resolve this issue.

    Hi,
    Using the method prepare_dynamic_navigation i am calling all the components.
    After this method i have written the following code for deleting the active and create the new component.
    Delete the active componet if any before bind the called component
      IF wa_cmp_usage-component_usage->has_active_component( ) IS NOT INITIAL.
        wa_cmp_usage-component_usage->delete_component( ).
      ENDIF.
    Bind the compont called to this main component
      wa_cmp_usage-component_usage->create_component( lv_target_comp ).     -
    > when i debug, inside this am getting dump.
    In ST22 the error is occuring in the following place.
      call method (l_gen_class_name)=>if_wdr_classloader~create_instance
        receiving
          component_instance = me->component_factory.
    I am actually 5 components. The default and the fifth components are only having tab and a text view. There are no other UI elements. These two components are working.
    The remaining components are having many UI elements and these components are giving the above said dumps.
    Edited by: Mohamed Aslam on May 13, 2010 12:11 PM

  • Abap Dump Syntax error in program "/SSF/SLIB " occuring in SOLMAN 7.1???

    Hello Friends,
       After upgradation Solman 7.01 to 7.1, During EWA Alert management configuration in step 3 --> Check Software component level phase, we receiving below error.
       Also Syntax error in program "/SSF/SLIB " Dump is occurring inST22. Please find the Abap dump details attachment.
    Please help me to resolve this issue.
    Regards,
    Farkath C

    /SSF/SLIB comes from SP A/PI, if there were issues in old version then they should have been reported.
    Upgrading may be a solution.
    However, there references of ADD_CCDB_ABAP_EXTRACTOR
    Execute RFC                                                                            |
    |>>>>>|  CASE LS_OPT-RFC_CALLTYPE.                                                                 |
    | 1640|    WHEN 'SYNC'.                                                                            |
    | 1641|      CALL FUNCTION '/SSF/CALL_SUBROUTINE_RFC'                                              |
    | 1642|                                   DESTINATION LS_OPT-DESTINATION  
    That's why I am asking for the latest dump after the run of RTCCTOOL.
    Regards

  • A short dump in the program with a certain error message...

    Hi all,
    I'd run a program to do an insertion into a customized table.
    During the run, it popped up a short dump error messages below :
              value larger than specified precision allows for this column#TC020                    %M
    I've search for that column #TCO20 .... and i couldn't find it in my custom table...
    Why SAP gave such a hard description on the error found? I can't determine which field/column in my table that is causing the error dump during INSERT event in my program.
    Is there any explanation on that message that could help me?
    Thanks
    William Wilstroth

    Hi,
    Better u seee again where u r getting error i the code . still if u r not getting see in dump analysys(ST22) and select
    no:8 -- which is source code extract where u can get correct error inf.
    Plz reply me.
    Regards
    Durgaprasad.

  • IW31 Dump - Syntax error in program "SAPLCNTX ".

    Dear All,
    I am facing a strange problem, while creating a maitnenance order.
    Core modules had been implemented earlier and now SAP PM is getting implemented.
    Whenever i try to create a maintenance order, system gives below dump.
    I have checked with my ABAP team, but we are not able to find out any specific reason for this.
    I searched the threads also, but haven't found any thing.
    Would request you to please help.
    ShrtText
        Syntax error in program "SAPLCNTX ".
    What happened?
        Error in ABAP application program.
        The current ABAP program "SAPLCOZV" had to be terminated because one of the
        statements could not be executed.
        This is probably due to an error in the ABAP program.
        In program "SAPLCNTX ", the following syntax error occurred
        in the Include "LCNTXF19 " in line 195:
        ""LV_SUBJECT" is not type-compatible with formal parameter "I_SUBJECT"."
        Author and last person to change the Include are:
        Author "SAP "
        Last changed by "SAP "
    Error analysis
        In program "SAPLCNTX ", the following syntax error occurred:
        ""LV_SUBJECT" is not type-compatible with formal parameter "I_SUBJECT"."
    Trigger Location of Runtime Error
        Program                                 SAPLCOZV
        Include                                 LCOZVU01
        Row                                     2,549
        Module type                             (FUNCTION)
        Module Name                             CO_ZV_ORDER_POST
    Thanks & Regards,
    Mihir

    Hi,
    Please check (or paste here) "What you can do" section of dump. Search OSS notes.
    Regards
    Shrikant

  • ST22 - Short Dump in Sales and Distribution Configuration after Upgrade to EHP5

    Steps for Reconstruction
    In the IMG when trying to do Sales and Distribution customising i.e. when trying to
    create a new Sales Document Type the Short Dump above occurs.
    ST22 Long Text:
    Error in the ABAP Application Program
    The current ABAP program "SAPLSVIM" had to be terminated because it has come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "SAPL080O " in include"L080OF00" inline 345:
    "The data object "V_TVAK" does not have a component called "ABRVW"."
    Anybody have the same issue ?

    Hi
    We've had exactly the same error with the View "V_TVAK" and the field "RDP_PROFILE".
    An activation of V_TVAK solved our problem (before that we've found some inconsistencies in the object "V_TVAK").
    Best Regards
    Kevin

  • Short dump with error FORM "CLEAR_SPECIAL_TABLES" does not exist"

    Hi All,
    We are experiencing an issue in our development system. We have recently upgraded to ECC6 from ECC5. While executing FBL3N transaction, we are getting a dump with description Syntax error in program "RFEPOS00 ".
    The following syntax error occurred in program "RFEPOS00 " in include "RFPOSFZ0  "                                                                           
    line 1072:                                                                     
    "FORM "CLEAR_SPECIAL_TABLES" does not exist"                                   
    I checked in our previous systems, the subroutine CLEAR_SPECIAL_TABLES exists with an empty body in include RFPOSFC1.
    And it is created by DDIC.
    As per the comments in the include RFPOSFC1, we tried to generate the program RFXPRA33. But it is giving same error FORM "CLEAR_SPECIAL_TABLES" does not exist"  .
    Any help to resolving this issue will be appreciatable.
    Thanks in advance.
    Edited by: Kumar.ktk on Jun 8, 2010 1:36 PM

    Hi,
    We just had this issue after an upgrade and the solution was to compare the coding with an unupgraded system,
    there we found that this missing form exists in an include with this documentation:
    Function LINE_ITEMS_SPECIAL_FIELDS
    caller L0F14I01, AFTER_SAVE_T021S, tcode O7R3
    In case of errors: Start RFXPRA33
    FORM CLEAR_SPECIAL_TABLES.
    ENDFORM.
    After we executed program: RFXPRA33 all errors were resolved,
    Hope this helps,
    Mickey

Maybe you are looking for