Transaction CC04 end up in a short dump

Hi All,
When we try to expand the Material Routing twities in CC04 transaction it ends up in a Dump.Does anybody know which OSS notes could solve the problem.
Thanks,
Sangeeta.

Hello Sangeeta,
Can YOU please post the Short dump description here. I agree with the above post
BR
Tanmoy
Edited by: Tanmoy Mondal on Aug 31, 2011 6:00 PM
Edited by: Tanmoy Mondal on Aug 31, 2011 6:00 PM

Similar Messages

Short Dump while checking DataSource contents in R3 (Transaction RSA3)

Hello all,
I am having trouble with a DataSource (2LIS_11_VAITM) in the R3 Source System (IDES 6.0). When I try to view the contents of this DataSource through Transaction RSA3, I get the following Short Dump Error.....
Could someone pls help me with this.
Thanks,
SD
============================================================================
Runtime Errors         CONNE_IMPORT_WRONG_STRUCTURE
Except.                CX_SY_IMPORT_MISMATCH_ERROR
Date and Time          18.03.2009 09:56:23
Short text
     Error when importing object "MC11VA0ITM_TAB".
What happened?
     Error in the ABAP Application Program
     The current ABAP program "SAPLMCEX" 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 "MCEX_BW_LO_API" "(FUNCTION)", 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:
     When attempting to import data, the
     structure of the complex object "MC11VA0ITM_TAB" was not compatible with the
     target object. The error occurred with component no. 31.
Missing RAISING Clause in Interface
     Program                                 SAPLMCEX
     Include                                 LMCEXU06
     Row                                     1
     Module type                             (FUNCTION)
     Module Name                             MCEX_BW_LO_API
Trigger Location of Exception
     Program                                 SAPLMCEX
     Include                                 LMCEXU06
     Row                                     263
     Module type                             (FUNCTION)
     Module Name                             MCEX_BW_LO_API

Hi SD,
The 11_Vaitm is a LO datasource, before checking its data setup tables need to be filled for it.
For filling the setup tables, first you have to delete the existing setup table data and ensure all the delta queues are empty.
Delete the setup tables: Go to TCODE LBWG and in the application give 11 and execute.
Delete all entries in Delta Queue, TCODE RSA7 for application 11.
Delete the entries in logistic queue: Check in TCODE SMQ1, if there are any entries for application .
Refill the setup tables: SBIW -> Settings for application specific datasources -> Logistics -> anaging extract strucutre -> Initilization -> Filling the setup table ->Application specific setup of data -> SD-Sales order perform setup.
Then try RSA3. Hope it helps.
Regards,
Pankaj

Short Dump GETWA_NOT_ASSIGNED while calling Transaction launcher in IC_WEB

Hi Folks,
We have a problem with Transaction Launcher profile in IC web client , after support pack implementation when i launch few R/3 transaction in Web client profile getting short dump.
when i check ST22 transaction , i found these information in Dump.
!) Error in ABAP application program.
The current ABAP program "CL_CRM_IC_ABOX_ABSTRACT_URL===CP" had to be
terminated because one of the
statements could not be executed.
we came to know below method not executing properly .
CL_CRM_IC_ABOX_ABSTRACT_URL method IF_CRM_IC_ACTION_HANDLER~GET_ACTION_PROPERTY
and also for
CL_CRM_IC_ABOX_CONSTANTS => Object_type
Any could you please advice on the same ....
Regards
raju....

Hello Raju,
Please apply the note 1101443. This should help you resolve the issue.
Thanks and Regards,
Varsha

Short dump error report

What is the purpose of short dump error report generated by the system? What r the major parts/section of this report?

hi please look through this:
Whenever any transaction or any process is executed it hits an ABAP code.
If there is any issue in executing the code the situation is called "ABAP DUMP" or 'Short Dump'
Transaction ST22 is used to check any ABAP Dump within a given duration.
U can also fix the issue with the help of ABAP editor (Transaction Code SE38) if u r good with ABAP.
you can select back to the last 14 days if you are
running the SAP_REORG_ABAPDUMPS job (program RSSNAPDL) which deletes te
old ABAP dumps every day, possibly further if you run it weekly or
monthly.
sap-basis sap-basisAll Groups Ignore this text box. It is used to detect spammers.If you enter anything into this text box, no search results will be displayed.
SAP Groups > Technical-functional > sap-basis > Message
About This Group | Invite peers to join this group
<< Prev thread < Prev msg Next msg > Next thread >>
short dump----urgent
Reply from Keith Lewis on 5/2/2003 3:22:00 AM
Good explanation Joy, but it is not only limited to the current day and
yesterday. If you click on the Selection button you can select previous
days as well. In fact you can select back to the last 14 days if you are
running the SAP_REORG_ABAPDUMPS job (program RSSNAPDL) which deletes te
old ABAP dumps every day, possibly further if you run it weekly or
monthly.
Cheers
Keith
SAP R/3 Support Specialist
Information Services International
Tel +44 1664 41 6178 Mobile +44 7887 627818
E-mail email@removed
Archive Page - http://www.ittoolbox.com//I/sap-r3-basis.asp
Dear sreenivas
If you receive an error message in the R/3 System log (SM21), or if you
see
a terminated update in the update service analysis transaction (SM13), or
DB
realated error ,check for dumps using the dump analysis transaction
(transaction ST22), or choose Tools -> Administration -> Monitoring ->
Dump
analysis.
Transaction ST22 enables you to analyze short dumps from the current and
previous day.
The dump analysis function shows you:
What happened
What you can do
How to correct the error
The dump analysis function also provides an error ID and keywords that you
can use to search in SAPNet, as well as information about:
The system environment
Users and transactions
Transaction ST22 enables you to analyze the following data:
Date, time, user, client
Contents of system and data fields
Contents of internal tables and application tables
ST22 is a very nice feature in SAP. This is where all the system errors
and users mistakes showed up. If there is a problem that you cannot
solve and you contact SAP support, they look at this area to analyze it.
This gives us lead where to handle the problems.
Error analysis
How to correct the error
System environment
User, transaction...
Information on where termination occurred
Contents of system fields
Chosen variables
Active calls / events
Internal notes
Active calls in SAP kernel
List of ABAP programs affected
List of internal tables
Directory of application tables (contents)
Directory of data areas (administration information)
Directory of data areas (contents)
ABAP control blocks CONT
End of runtime analysis
i think this would be helpful
regards
sravani

ECC 6.0 bar chart short dump

We are starting an upgrade from 4.7(non-Unicode) to ECC 6.0(Unicode), using SAPgui for Windows (version 7.10). In our 4.7 systems, the graphical bar chart on the Project Planning Board (txn CJ2C) works as expected. However, in the 6.0 development system, before displaying the gantt chart, the system short dumps with CREATE_ERROR.
I have searched the forums and looked through OSS notes and was unable to find anything that described the problem or was pertinent to our release. I have debugged through the transaction and am finding that the short dump occurs in method cl_gui_barchart=>constructor around the following code:
at line 83 if the system is unicode (which it is), the code calls method cl_gui_frontend_services=>check_gui_support, exporting 'ganttcontrol'/'usedataasstream' and expecting a result in variable l_guisupp_data_as_string. When it returns from the check_gui_support method, l_guisupp_data_as_string is blank, so the next "if" statement raises an error that is not handled:
     if l_guisupp_data_as_string = abap_true.
     .....code not executed because the variable = abap_false.
     else.
     .....raise create_error.    <<<<< this is where the dump occurs.
     endif.
Note that in the debugger, if I force l_guisupp_data_as_string to be = abap_true, the gantt chart/barchart displays as expected. (gotta love the debugger) But since it is standard SAP code I would prefer to resolve the problem without a modification and am hoping someone out there can point me in the right direction.
This short dump occurs with gui versions 710 and lower. (I personally am using sapgui version 710, patch level 7.) Has anyone had problems like this with the graphical elements in SAP or does anyone have a suggestion as to why the gui is not displaying the barchart correctly in our unicode system?
Sorry for the very long message, but thanks in advance for the help!
Amanda Salt
Edited by: Amanda Salt on Jun 17, 2008 11:14 PM

We are starting an upgrade from 4.7(non-Unicode) to ECC 6.0(Unicode), using SAPgui for Windows (version 7.10). In our 4.7 systems, the graphical bar chart on the Project Planning Board (txn CJ2C) works as expected. However, in the 6.0 development system, before displaying the gantt chart, the system short dumps with CREATE_ERROR.
I have searched the forums and looked through OSS notes and was unable to find anything that described the problem or was pertinent to our release. I have debugged through the transaction and am finding that the short dump occurs in method cl_gui_barchart=>constructor around the following code:
at line 83 if the system is unicode (which it is), the code calls method cl_gui_frontend_services=>check_gui_support, exporting 'ganttcontrol'/'usedataasstream' and expecting a result in variable l_guisupp_data_as_string. When it returns from the check_gui_support method, l_guisupp_data_as_string is blank, so the next "if" statement raises an error that is not handled:
     if l_guisupp_data_as_string = abap_true.
     .....code not executed because the variable = abap_false.
     else.
     .....raise create_error.    <<<<< this is where the dump occurs.
     endif.
Note that in the debugger, if I force l_guisupp_data_as_string to be = abap_true, the gantt chart/barchart displays as expected. (gotta love the debugger) But since it is standard SAP code I would prefer to resolve the problem without a modification and am hoping someone out there can point me in the right direction.
This short dump occurs with gui versions 710 and lower. (I personally am using sapgui version 710, patch level 7.) Has anyone had problems like this with the graphical elements in SAP or does anyone have a suggestion as to why the gui is not displaying the barchart correctly in our unicode system?
Sorry for the very long message, but thanks in advance for the help!
Amanda Salt
Edited by: Amanda Salt on Jun 17, 2008 11:14 PM
I just installed the latest patch on the SAPgui, so I am now running:
Release: 710 Final Release
File Version: 7100.2.8.1039
Build: 983952
Patch Level: 8
But I am still getting the short dump. I have done extensive searches of SAP Help, OSS notes, and this and other forums (even just looking up the problem on "google") but can't seem to find anything that applies to this scenario. I'm not very familiar with the methods in cl_gui_frontend_services, so if anyone can give me a pointer of where else I can look, I would greatly appreciate it!
I also have edited the Subject line to be more informative about the problem

Short dump "Time limit exceeded" when searching for Business Transactions

Hello Experts,
We migrated from SAP CRM 5.2 to SAP CRM 7.0. After migration, our business transaction search (quotation, sales order, service order, contract etc) ends with the short dump "Time limit exceeded" in class CL_CRM_REPORT_ACC_DYNAMIC, method DATABASE_ACCESS. The select query is triggered from line 5 of this method.
Number of Records:
CRMD_ORDERADM_H: 5,115,675
CRMD_ORDER_INDEX: 74,615,914
We have done these so far, but the performance is still either poor or times out.
1. DB team checked the ORACLE parameters and confirmed they are fine. They also checked the health of indices in table CRMD_ORDER_INDEX and indices are healthy
2. Created additional indices on CRMD_ORDERADM_H and CRMD_ORDER_INDEX. After the creation of indices, some of the searches(without any criteria) work. But it takes more than a minute to fetch 1 or 2 records
3. An ST05 trace confirmed that the selection on CRMD_ORDER_INDEX takes the most time. It takes about 103 seconds to fetch 2 records (max hits + 1)
4. If we specify search parameters, say for example a date or status, then again we get a short dump with the message "Time limit exceeded".
5. Observed that only if a matching index is available for the WHERE clause, the results are returned (albeit slowly). In the absence of an index, we get the dump.
6. Searched for notes and there are no notes that could help us.
Any idea what is causing this issue and what we can do to resolve this?
Regards,
Bala

Hi Michael,
Thanks. Yes we considered the note 1527039. None of the three scenarios mentioned in the note helped us. But we ran CRM_INDEX_REBUILD to check if the table CRMD_ORDER_INDEX had a problem. That did not help us either.
The business users told us that they mostly search using the date fields or Object ID. We did not have any problem with search by Object ID. So we created additional indices to support search using the date fields.
Regards,
Bala

Short Dump in MIGO transaction

When executing the transaction MIGO the transaction ends with the short dump as follows.
is it because of SAPNOTE 385830 ?
short text of error message : GET_SYTEM_BUSINESS_ERROR An error occurred while determining the business system ( No_business_system)
Technical information of error message
messgae class 00
number 001
variable 1 GET_SYTEM_BUSINESS_ERROR An error occurred while
variable 2 determining the business system ( No_business_system)
T CODE : migo
PROGRAM : SAPLMBWL
sceen no saplmigo 0001
screen line 18
the dump occurs at the line marked with -
>.
function mb_post_goods_movement.
""Local Interface:
*" IMPORTING
*"     VALUE(XBLNR_SD) OPTIONAL
*" EXPORTING
*"     VALUE(EMKPF) LIKE EMKPF STRUCTURE EMKPF
   data: l_mem_id(10) type c.                                   " 641365
Wurde zuvor eine Lieferung erzeugt, so ist kein MB_POST... nötig "HUM
   check not xdeliv = x.                                            "HUM
Control posting for external WM: Exit if BFWMS = 1 (Create delivery)
   check not mkpf-bfwms = 1.                                     "357661
   read table xmseg index 1.
   if not sy-subrc is initial.
     message a260.
   endif.
   if xmkpf-mblnr is initial.
     message a260.
   endif.
   xcommit = x.                                             "Performance
   if not xblnr_sd is initial.
     xmkpf-xblnr    = xblnr_sd.
     xmkpf-le_vbeln = xblnr_sd.                                 "XAN-SPM
     modify xmkpf index 1.
   when a goods movement for an inbound or outbound delivery is posted
   directly from VL31N/ VL01N, XBLNR is not yet known when we call
   CKMV_AC_DOCUMENT_CREATE, but the number is supposed to be stored in
   BKPF as well. There is no other way to forward XBLNR to FI as not
   every document is posted by MB_CREATE -> a new function module in
   MBWL for transferring the information, called by FI, meant to load
   the complete function group for all MBxx postings when this isn't
   required (Performance). Would be the better way to transport the
   information after switching off MBxx in later release.
   corresponding IMPORT ... FROM MEMORY ... can be found in
   AC_DOCUMENT_POST (FORM FI_DOCUMENT_PREPARE (LFACIF5D))
     l_mem_id = 'MKPF-XBLNR'.                                   " 641365
     export xblnr = xblnr_sd to memory id l_mem_id.             " 641365
   endif.
   if xmkpf-xabln is initial.                               "note 434093
       call function 'MB_XAB_NUMBER_GET'.                   "note 434093
   endif.                                                   "note 434093
enhancement-point mb_post_goods_movements_01 spots es_saplmbwl static.
$$-Start: MB_POST_GOODS_MOVEMENTS_01----
$$
enhancement 26 dimp_general_saplmbwl.    "active version
data: l_statics_lock type c.
endenhancement.
$$-End:   MB_POST_GOODS_MOVEMENTS_01----
$$
enhancement-point mb_post_goods_movements_02 spots es_saplmbwl.
$$-Start: MB_POST_GOODS_MOVEMENTS_02----
$$
enhancement 25 dimp_general_saplmbwl.    "active version
read table xvbfa index 1.
if sy-subrc is initial and
   g_vbtyp_v = '7'.
   perform get_mdiff_kenz(sapmm07m) changing l_statics_lock.
endif.
endenhancement.
$$-End:   MB_POST_GOODS_MOVEMENTS_02----
$$
   call function 'MB_CREATE_MATERIAL_DOCUMENT_UT'
        exceptions
          error_message = 4.
As soon as we have started to put things into UPDATE TASK, we must
ensure that errors definitely terminate the transaction.
MESSAGE A is not sufficient because it can be catched from
external callers which COMMIT WORK afterwards, resulting in
incomplete updates. Read note 385830 for the full story.
   if not sy-subrc is initial.
message id sy-msgid type x number sy-msgno with            "385830
                 sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    MESSAGE A263.
   endif.
Optische Archivierung
Spaete Erfassung mit Barcode
Redesign of barcode handling -> note 780365
perform barcode_update(sapmm07m) using xmkpf-mblnr
                                         xmkpf-mjahr
                                         barcode.
move-corresponding xmkpf to emkpf.
call function 'MB_MOVEMENTS_REFRESH'
    exceptions
      error_message = 4.
   move-corresponding xmkpf to emkpf.
   call function 'MB_MOVEMENTS_REFRESH'
        exceptions
          error_message = 4.
   if not sy-subrc is initial.
     message id sy-msgid type x number sy-msgno with             "385830
                sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
   MESSAGE A261.
   endif.
   perform buchen_initialisieren(sapmm07m).
   clear emkpf-subrc.
clear global fields when COMMIT WORK                     "Performance
   if not sy-oncom = p.
     perform clear_xcommit on commit.
   else.
     perform clear_xcommit.              "if this FB is called on commit
   endif.
   perform clear_xcommit on rollback.                       "note 303392
endfunction

hi
check SAP Note 556000 - Short dump due to note 385830
Summary
Symptom
   Consider the subsequent note 561872 !                             *
You want to post a goods receipt for a reference document (for example purchase order, delivery ...). The checks do not cause any error. Nevertheless, the system generates a short dump which is deliberately triggered by note 385830.
One known scenario is a stock transfer process via a delivery: You have entered a stock transport order assigned to a sales order and post a goods receipt for the delivery via transaction MIGO. The sales order must be in valuated. The material to which postings are to be made is valuated separately and to be handled in batches. And the batch, which was assigned via the delivery, already exists with a valuation type in the receiving plant which is different from the one specified in the purchase order.
Other terms
MB_CREATE_GOODS_MOVEMENT, MIGO, MCHA, BWTAR.
Reason and Prerequisites
Prerequisites: see above. This is a program error.
Solution
Implement the attached program corrections.
Then implement the subsequent note 561872.
After the implementation of the note, checks are carried out in the program flow - if a batch and a valuation type were entered for a goods movement (for instance with reference to the purchase order or delivery) - on whether the assignment of the batch and valuation type is correct.
regards
KI

Short dump in Z transaction code

Hi,
We have a Z transaction code 'ZPROFIT' for a report. After executing the report from output screen of report if i type 'se38' in command bar and if I press enter key it is going to short dump. But if I type '/nse38' it is working fine.The short dump description is as follows .
ShrtText
    An exception that could not be caught occurred.
What happened?
    The exception 'CX_SALV_OBJECT_NOT_FOUND' was raised but was not caught at any
     stage in the
    call hierarchy.
    Since exceptions represent error situations, and since the system could
    not react adequately to this error, the current program,
     'CL_SALV_FUNCTIONS=============CP', had to
    be terminated.
Error analysis
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assinged to the class 'CX_SALV_OBJECT_NOT_FOUND', was
     not caught,
    which led to a runtime error.
    The reason for this exception is:
    No text available for this exception
Trigger Location of Exception
    Program                                 CL_SALV_FUNCTIONS=============CP
    Include                                 CL_SALV_FUNCTIONS=============CM00J
    Row                                     28
    Module type                             (METHOD)
    Module Name                             IS_SALV_FUNCTION
Source Code Extract
Line SourceCde
    1 method is_salv_function.
    2   data: l_name      type string.
    3   data: l_msgtext   type string.
    4   data: ls_message type scx_t100key.
    5
    6 *get item
    7   try.
    8       call method get_item
    9         exporting
   10           function = name
   11         importing
   12           salv_function = value.
   13     catch cx_salv_object_not_found.
   14     try.
   15       call method get_group
   16         exporting
   17           group = name
   18         importing
   19           salv_function = value.
   20       catch cx_salv_object_not_found.
   21         l_name = name.
   22         message w026(salv_exception)
   23           with 'CL_SALV_FUNCTIONS' 'IS_SALV_FUNCTION' 'Function: ' l_name
   24           into l_msgtext.                                     "#EC NOTEXT
   25
   26         ls_message-msgid = sy-msgid.
   27         ls_message-msgno = sy-msgno.
>>>>>         raise exception type cx_salv_object_not_found
   29           exporting
   30             textid   = ls_message
   31             object   = 'Function'
   32             key      = l_name
   33             class    = 'CL_SALV_FUNCTIONS'                    "#EC NOTEXT
   34             method   = 'IS_SALV_FUNCTION'.                    "#EC NOTEXT
   35     endtry.
   36   endtry.
   37
Please let me know how we can solve this?
Is there anything wrong in report source code?
Thanks in advance.
Regards,
Brahma Reddy

hi brahma,
try to reinstall ur Front End...
it's not a error from ur Program, I think it's dumb because SAP GUI it's not all right working,
try to remove and install SAP GUI, maybe it's can solve ur problem...
Regards
Allan Cristian

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

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

Search OSS Notes for that.

Short Dump with VA22 transaction in ECC 6

Hi All,
We are on ECC 6 and facing a short dump whenever we are trying to save some quotation. We are getting the following error.
There is probably an error in the program "SAPLSYDB". The program is triggered in the update task. There, the following ABAP/4 statements are not allowed:
CALL SCREEN
CALL DIALOG
CALL TRANSACTION
SUBMIT
"POSTING_ILLEGAL_STATEMENT" " "
"SAPLSYDB" or "LSYDBU27"
"DB_COMMIT".
Is there a sap note for this. Any link or pointer to this will be highly appreciated.
Regards,
Jayant

Hello,
This looks like a problem for SAP. I assume that you have not modified the
program SAPLSYDB. I also assume that you have searched the Service Marketplasce
for any OSS notes. My next step would be to create a message to SAP to get them to
have a look.
Regards
Greg Kern

Short dump with the transaction CJ02

Hello, this is my first thread in the forum. I hope to solve my problem.
It is necesary to say you that my english is very poor, is not so good. Sorry for that.
When i use the transaction CJ02 to finish or close a project, appears an error when i save it. The steps are the followings:
1- Run the transaction CJ02 with a WBS element
2- Mark the line of the WBS element
3- Select then button Settlement rule
4- Fill 4 items in the next screen to distribution rules (the % is 100)
5- Back with green arrow
6- Fill the field Cost Center Req
7- Save
After a few seconds appears the dump:
<b>ABAP runtime errors    MESSAGE_TYPE_X
       Occurred on     20.11.2006 at 11:07:09
>> Short dump has not been completely stored. It is too big.
The current application triggered a termination with a short dump.
Error analysis
Short text of error message:
Nested call of PERFORM ON COMMIT:
Long text of error message:
Diagnosis
     During processing of a routine called using PERFORM ... ON COMMIT,
     the system attempted to call PERFORM ... ON COMMIT again. Nesting
     of this is not allowed.
System Response
Procedure
     The program indicated after "Caller:" must be changed. This is the
     program that calls the routine indicated after "Form:" during
     COMMIT processing. This routine is part of the program indicated
     after
     "Program:".
Procedure for System Administration
Technical information about the message:
Message classe...... 00
Number.............. 081
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
If the error is in one of your own ABAP programs or an SAP program that
you have modified, try to correct it.
If the error occurred in a non-modified SAP program, you may be
able to find a solution in the SAP note system.
If you have access to the note system yourself, use the following
search criteria:
"MESSAGE_TYPE_X"
"SAPMSSY0 " or "SAPMSSY0 "
"%_ORDER_FORM_FOR_ROLLBACK"</b>
There are several notes that apparently solve the problem with support packages that are applied in our system (for example 397011 or 614553). Inthis case our system is updated.
Can you help me please.
Thanks
Gabriel.-

Hi
Are you really sure https://websmp101.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=397011&_NLANG=E
is applied correctly ?
Try downloading with snote and see if it gets marked 'not relevant',
( are you on release 4.6 ? )
Given the nature of the problem ( and the fact that this issue is known ) , the best seems log an OSS support request
rgds
Dirk

Short dump in every transaction during support pack import - Solution Mgr

I am in the middle of applying support packs SP13 and SP14 for Solution Manager. In SPAM, during the import, I received short dumps. I get short dump for all transactions. The error message is 'Syntax error in program "SAPLWB_CUSTOMIZING", Field "G_DC_TABSTR" is unknown in INCLUDE LWB_CUSTOMIZINGDEV'.
Please help. Thanks !

Hi
My first question, would be, why are you performing other activities while importing patches?
This is not recommended.
Rahul

CONNE_IMPORT_WRONG_COMP_TYPE short dump in DB02OLD transaction

Hi,
We have recently upgraded to SAP ECC 6.0 and in solution manager system, I am getting CONNE_IMPORT_WRONG_COMP_TYPE short dump for DB02OLD transaction (Program RSORAT5M).
I searched few notes like 657981 and others but all are applicable for DB02 transaction. If anyone encountered same problem, please let me know how to resolve the issue.
Thanks in advance,
Ni3

Solved on my own

Short dumps in every transaction during the Support pack import

I am in the middle of applying support packs SP12 on NetWeaver 7.0. In SPAM, during the import, I received short dumps. I get short dump for all transactions i excute now. I am unable to go to SPAM to continue the SPAM, all I get short dumps. This is our new training system that we are building. I had same issues before, and I got help from SAP for this issue, where they suggested tp command wiht lots of options to run at the OS level. Since I moved company I am not able access the same ticket. Do anyone of you guys know the OS tp command to continue the SPAM import phase?
Please and thanks
Kumar

Hi,
SAP does not recommend to run SP's at OS level. Most of time when u r running SAP_BASIS , u will receive ABAP dumps. then option is to run SP at using tp command & you have to analyze many things before running this command.
<removed_by_moderator>
Please read the Rules of Engagement
Edited by: Juan Reyes on Jul 28, 2008 10:12 AM

Short Dumps in standard HR Business Event Group/Event creation transactions

Dear All,
I m getting short dumps whlile executing standard HR transactions for Creation of Business Event Groups and Business Event Types. Attaching the Short Dump text herewith. Can anyone plz. help...
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_DYNAMIC_OSQL_SEMANTICS', was
not caught in
procedure "RH_BASE_READ_INFTY_NNNN" "(FUNCTION)", 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:
Eine Open SQL-Klausel wurde dynamisch angegeben. Der darin auftretende
Feldname "SUBTY" kommt in keiner der Datenbanktabellen aus der
FROM-Klausel vor.
Thanks and Regards,
Sudipto.

Hi,
Check whether the OSS note 207515 is suitable for the below situation.
Summary
Symptom
A dump occurs in program SAPLRHDB: DBIF_NTAB_TABLE_NOT_FOUND
Additional key words
RH_BASE_READ_INFTY_NNNN, LRHDBU16
Cause and prerequisites
The system wants to access table HRPnnnn particularly by means of an entry in the infotype check table T777D. This access can be processed in various places, including in the profile generator. Here, a termination occurs if the 'ent' table/structure in the dictionary is no longer available. This generally affcts customer-specific infotypes. These have been created and possibly deleted again. However, the entry in table T777D is not available. You can also import the entry into another system with a transport of the table. If the HRP table/structure is then missing, a termination may also occur in this case.
Solution
You must check on an individual basis which infotype the termination refers to. If it is a customer-specific infotype, the customer is responsible for removing the cause of the termination. If the table entry is a 'remnant', the entry can simply be deleted.
If the termination refers to an SAP structure, you should consult SAP before carrying out any further activities.
Source code corrections
Header Data
Release Status: Released for Customer
Released on: 23.03.2000 23:00:00
Priority: Recommendations/additional info
Category: Customizing
Primary Component: PA-BC Basis
Releases
Release Independant
Satya

Transaction CC04 end up in a short dump

Similar Messages

Maybe you are looking for