Short dump when opening the segment builder

After the upgrade from CRM 4.0 to 2007, we are no longer able to open the Segment Builder. We always get a short dump (Message_type_X). Anyone encountered this problem before and has a solution?
Thanx in advance!

Hi,
though it is true that in CRM 2007 the GUI transactions should not be used anymore I am able to start the segment builder directly via transactioin CRMD_MKTSEG. It is working without a shortdump.
For documentation I suppose you have to refer to SAP: Help or the documentation available under service.sap.com. The blog posted here might be an alternative as well.
cheers Carsten

Similar Messages

Short Dump when activating the Workflow

Hi,
I have a problem, when i try to activate the workflow I get a short dump with the error "SYSTEM_NO_ROLL". As I understand the error is because there is no enough memory to the transaction, this is not the case i have checked that, so the error must be from my workflow definition or from the SAP it self.
Here goes the description:
The location of the error is in the method "FIND_ELEMENTS" of class "CL_SWF_CNT_CONTAINER". By this I understand that the error was with my container elements in the workflow but I have reviewed all my elements and I cant find any fault element or error. I can check the definition but if i try to activate it i get the short dump.
In the Calls Stack, there is +/- 69297 calls to the above method, because that method is recursive the transaction just consume all the memory and then i get short dump.
I use many multi line elements, for parallel processing with block step mostly, maybe its my container elements but i can find no wrong bindings or faulty elements.
Any help would be greatly appreciated.
Regards,
Diogo Silva.

Hi,
Ok didn't know, thanks for the help, i will post in the other section.
PS: Could you tell me how to reach that component, I tried but without success.
Regards,
Diogo Silva.
Edited by: DiogoSilva on Jun 15, 2011 7:01 PM

Short dump while opening the infopackage............

Hi,
I am getting Short dump. This happens when I am opening any info package for one Infosource. I am not getting any error when I open other infopackages. There are 7 infopackages for this info source and when I open any of these , gets Short Dump with message ...
" 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)."
Has any body faced similar problem. Please let me know your ideas on , how to solve this short dump.
Best Regards,
Jeetu

Hi..
When you delete the update status of a request in an InfoCube, short dump
MESSAGE_TYPE_X occurs in program RSBLOGSTATE
You can use the attached program as a correction to check for data inconsistencies and to correct them.
Input parameter:
i_tablnm: ' ' all 'PSA' tables are processed
             '/BIC/B......... ' a special table
i_repair: 'X' data with Partno = 0 are corrected.
             ' ' Check whether data with Partno = 0 exists
i_debug    'X' Activation of default breakpoints
To implement the program, you must create the SAP_PSA_ZEROCORRECT program as an SAP advance correction, leave it empty (Package: RSDD) and then implement it using Transaction SNOTE. Alternatively, you can create the program using the CUT and PASTE method.
If you want to check or correct all tables, you should schedule the program in the background since the runtime (in particular for repairing the tables) may be very long.
In the spool output of the job, you also find the log of the program.
You should first check in check mode whether there is inconsistent data. If this is the case, you must execute the program with i_reapir = 'X'. SAP recommends that you create a variant for the CHECK job and a variant for the REPAIR job.

Short Dump when writing the file to Unix.

ST22 Dump Log.
Short text Error when writing to the file "/appl/data/backlog/outbound/bop_bwfcstngall_erp
What happened? Resource bottleneck
The current program "ZPS_BACKLOG_NEW_READ" had to be terminated because
a capacity limit has been reached.
_Error analysis
An error occurred when writing to the file
"/appl/data/outbound/bop_bwfcstngall_erp_20110919_151220.dat".
Error text: "A file, file system or message queue is no longer available."
Error code: 52

ask your basis collegues, the dump says that the file system was not available, so it is clear that your writing to Unix could not happen.
have a look into OSS Note 1100926 - FAQ: Network performance

Short dump when executing the query

Hello Friends,
I have a query from MM area which I have insalled from Business Content , and when I try to go to the edit mode or try to excute the query I get a short dump which says "Missing elements ..", I get the same dump when executing from query designer or RSRT . At this time I'm not able to do a "check" on the query also n query designer since it doesnot allow me to go to the edit mode also . Any inputs greatly appreciated .
thanks ,

Hi,
While activating it from the Business Content, have you activated all the underlying objects also. Pls check that. It might help.

Short dump when exporting the ALV grid report in to spread sheet

HI,
I am facing a problem when downloading ALV grid report in to spread sheet LIST>EXPORT>LOCAL FILE -->SPREADSHEET.
in shotdump the cursor shows : "assign cline+cbegin(clength) to <field_cont>."
In SAP internal table LIST,in the first record the value of the filed LENG is 0. when i have changed this value ex:10 etc it is coming properly.
Kindly help me
Nagendra

Is this a standard SAP report, or your own? Can you tell what your report does, if it is a custom ALV report?

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

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

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

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

Error_Exception dump while opening the report in RRMX

Hi All,
When User trying to open the report Error_Exception dump is coming for few Info Providers. Please find attached dump for your reference.

Issue is res loved, We have analyze the short dump ,when loads were running and at that if time user executed the queries then that dump was occuring.

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

Enhance output of Target Group opened in segment builder

Hello Experts,
We are implementing SAP CRM Lean Marketing using CRM 7.0. Our business requirement is to do segmentation based on Company attributes and Relationship Category. The output of the target group should enlist the persons related to the Company based on the relationship category selected while doing the segmentation.
Using standard InfoSet CORM_MKTTG_BP_ORG_CDE and while creating data source selecting BUT000_PER-PARTNER_GUID in the field business partner, we are able to get the list of persons matching the segmentation query (based on the relationship category e.g. Has Supplier, Has Contact Person, etc) . But the issue is , the output of the target group (shown as an ALV grid , when the target group is opened in segment builder) only enlists matching Persons, it does not enlist the related company ID /name in front of the Person ID in the output of the target group. And this Company BP ID is not available if I try to modify the output layout. So business is unable to understand the Person enlisted in TG belongs to which Company. Can we enhance this ALV grid output of the target group displayed in segment builder ? if yes , how can it be achieved ? If this is possible and we are able to add related company BP ID/ name in front of every person enlisted in the target group then our issue gets resolved. Or is there any alternative solution to resolve this issue ?
Highly appreciate your early response in order to resolve this critical issue.
Thanks and Regards
Ambar
Edited by: AMBAR ADHAV on Sep 10, 2011 11:52 AM
Edited by: AMBAR ADHAV on Sep 10, 2011 2:21 PM

Naresh,
Thanks for the response.
As per your suggestion I made additions to my z Infoset , and added all the fields you suggested.
While creating the data source I selected following fields
Business Partner: BUT000_PER-PARTNER_GUID (as my requirement is to return Persons and this field works with only GUID)
Reference Object: BUT051-RELNR
Reference Object Type: BUT051-RELTYP
Now when I create the target group with this data source unfortunately I am still not getting the the relationship number when I click in Show assigned Objects in the target group screen of web UI.
Please suggest where I am going wrong
Thanks
Ambar

Dump when opening RSA1

Hi,
When I am trying to open RSA1 I am getting the following dump,what has to be done to resolve this
Runtime Errors         MESSAGE_TYPE_X
Date and Time          23.12.2006 10:16:22
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).
Error analysis
Short text of error message:
Control Framework : Error processing control
Technical information about the message:
Diagnosis
An error occurred when the system tried to process the commands
from the Automation Queue on the presentation server.
There are several possible reasons for this:
- The installation of the SAP GUI on the presentation server is
faulty or obsolete.
- There is an error in the application program
- There is an error in the SAPGUI or an integrated control
Procedure
1. Make sure that you have imported the appropriate Support
Package, the current kernel, and GUI patch for the release of your
system
2. Check whether the error occurs locally on one or a few PCs, or
generally on all PCs. Note whether the error only occurs for some
users, for example because of a specific Customizing setting.
If it only occurs locally, this suggests an installation problem
with the PC. Check the installation; if necessary, reinstall the
software. In the dump, search for the SY-MSGLI field, since it may
point to the cause of the error.
3. Activate the Automation Trace (in accordance with SAP Note
158985).
4.Start the transaction and continue until the screen immediately
before the dump.
5. From the System -> Utilities menu, choose Autom. Queue,
Synchronous Processing.
The status bar of the GUI displays the text:
"Automation synchron flush mode on"
6. If you now proceed with the application, the short dump will
display the ABAP call that caused the error; the Automation Trace
will contain the error on the presentation server.
7. If necessary, load the short dump and trace files on to
sapservX, so that SAP can analyze them.
Message classe...... "CNDP"
Number.............. 006
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Variable 3.......... " "
Variable 4.......... " "
Trigger Location of Runtime Error
Program                                 CL_GUI_CFW====================CP
Include                                 CL_GUI_CFW====================CM002
Row                                     23
Module type                             (METHOD)
Module Name                             FLUSH
Source Code Extract
Line
SourceCde
1
2
METHOD FLUSH .
3
4
data: rc like sy-subrc, msgli like sy-msgli.
5
6
CALL FUNCTION 'AC_FLUSH_CALL'
7
EXPORTING
8
SYSTEM_FLUSH = ' '
9
IMPORTING
10
MESSAGE_NR   = rc
11
MESSAGE_TEXT = msgli.
12
13
sy-subrc = rc.
14
sy-msgli = msgli.
15
16
CASE SY-SUBRC.
17
WHEN 0.
18
WHEN 1.
19
    system_error
20
MESSAGE ID 'CNDP' TYPE 'X' NUMBER 007 RAISING CNTL_SYSTEM_ERROR.
21
WHEN 2.
22
    method_call_error
>>>>>
MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.
24
WHEN 3.
25
    property_set_error
26
MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.
27
WHEN 4.
28
    property_get_error
29
MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.
30
WHEN OTHERS.
31
RAISE CNTL_ERROR.
32
ENDCASE.
33
ENDMETHOD.
Regards,
Maya

Probably ur Tcode RSA1 is locked in something which causes a dump.
What u can do is try RSA11 or RSA12.
Regards

Short dump suggest me the solution

hi friends,
i am geeting the short dump when i execute the program
because here i am taking the ranges some times the ranges is very high in that time only i am getting the short dump
please suggest me any alter native
i am sending the samll code
Ranges;r_vbeln for vbap-vbeln,
            r_posnr for vbap-posnr.
if not ( it_vbap[] is initial).
select matnr werks strgr
from marc into table it_marc
for all entries in it_vbap
where matnr = it_vbap-matnr
and erks = it_vbap-werks.
select vbeln posnr vbelv posnv
from vbfa
inti corresponding field of table it_cont
for all entries in it-vbap
where vbeln eq it_vbap-vbeln
and posnn eq it_it_vbap-posnr
and vbtyp_v eq 'g'.
r_vbeln = r_posnr = 'IEQ'.
LOOP AT IT_CONT.
r_vbeln-low = it_cont-vbelv. collect r_vbeln.
r_posnt-low = it_cont-posnv. collect r_posnr.
endloop.
LOOP AT IT_vbap.
r_vbeln-low = it_vbap-vbelv. collect r_vbeln.
r_posnt-low = it_vbap-posnv. collect r_posnr.
endloop.
the below select statement time only i am geeting the short dump
select matnr werks lgort charg kalab vbeln posnr sobkz
     from mska
    into table it_mska
for all entries in it_vbap
where matnr = it_vbap-matnr
and werks = it_vbap-werks
and sobkz = 'e'
and vbeln IN r_vbeln
and Posnr in r_posnr.
i need the same output please suggest me the solution to write above select statement is ther any other way
Regards
srinu

Hi,
It is better not to use a range directly in the where condition. This is because when the range values are more it will give a dump. To avoid this, inside the program we need to build a logic to select records in a batch from the range.
For example,
a) if the range has say 10,000 records,
b) first take 1000 records from the range and then put it in an internal table and use this internal table for selecting records from the database (for eg MSKA).
c) Append the first 1000 records the database table into an itab.
d) Then take the next 1000 records from the range and select the data from database table and so on.
e) Repeat this process untill all the records in the ranges are finished.
This will definitely avoid a dump.
Please reward useful answers.
Regards
Vimal

Short dump when opening the segment builder

Similar Messages

Maybe you are looking for