Regarding dump error in MMBE

hi experts good morning,
                  when i execute tc mmbe it is showing dump error sometimes back it worked fine and now it is showing dump error ,,i m giving the error below plz have a look and help me.....
ShrtText
    Syntax error in program "SAPLMBBS ".
What happened?
    Error in ABAP application program.
    The current ABAP program "RMMMBESTN" 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 "SAPLMBBS ", the following syntax error occurred
    in the Include "LMBBSU07 " in line 75:
    "The column name "WAERS" has two meanings. ABAP/4 Open SQL statement."
    Author and last person to change the Include are:
    Author "SAP "
    Last changed by "SAP "
Error analysis
    In program "SAPLMBBS ", the following syntax error occurred:
    "The column name "WAERS" has two meanings. ABAP/4 Open SQL statement."
Trigger Location of Runtime Error
    Program                                 RMMMBESTN
    Module type                             (FORM)
    Module Name                             EKPO_LESEN

Hi,
Please find the SAP notes. There are several notes for this.
Regards,

Similar Messages

Regarding dump error in smartforms

hi experts,
               my one driver program along with smartforms is working fine in the development server after transportation to production server it is showing dump error :::
the error is:
Function module " " not found.
What happened?
The function module " " was called, but cannot be
    found in the Function Library.
Error in ABAP application program.
The current ABAP program "ZSD_DELIVERY_ORDER_DRIVER_PREP" had to be terminated
     because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
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
An exception occurred. This exception will be dealt with in more detail
    below. The exception, assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_FUNC', was
     not caught, which
led to a runtime error. The reason for this exception is:
    The program "ZSD_DELIVERY_ORDER_DRIVER_PREP" contains a CALL FUNCTION
     statement. The name
of the function module to be called is " ".
No function module exists with the name " ".
    All function modules are stored in the Function Library (SE37).
Possible reasons:
a) Wrong name specified. Particular attention should be paid
       to upper/lower case and underscores ("_")
    b) Transport error
c) If an enqueue/dequeue module has been used, the lock object
       may not have been activated (ABAP Dictionary)
       may not have been activated (ABAP Dictionary).
i have checked in the production server but i m not finding <b>" "</b> this thing in the program ..plz help me to solve this.

Hi Ravi,
Can you show me the code where you have called the smart form in driver program.Becaus the FM generated in Development server may differ from the FM generated in Production server.Make sure u r passing the FM which is generated from the function module SSF_FUNCTION_MODULE_NAME.

Runtime Error in MMBE- s yntax error occurred in program "SAPLMBBS " in inc

Hi Gurus,
Runtime Error in "MMBE" Transaction -
The following syntax error occurred in program "SAPLMBBS " in include "LMBBSU07
" in
line 76:
"The column name "MATNR" has two meanings . ."
Any Input is Highly appreciated.
Thanks and Regards,
Selva

Hi,
This looks like an ABAP runtime error and the program concerned is a standard program. Please check the include and try debugging, suggest a breakpoint in line 76.
Thanks

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

Getting a program Dump Error in Herarchial ALV

Hello All,
I am getting a dump error when I am executing the below program. Kindly help as I am not getting the output. However all the subroutines are getting properly populated with data. Getting a dump error while calling the function : REUSE_ALV_HIERSEQ_LIST_DISPLAY
Pasted below are both the question and solution. Copy the solution in SE38 and execute it to check out the dump error.
Kindly help.
Thanks,
Vinod.
QUESTION :-
Objective
     Hierarchical ALV for displaying Sales documents per customer
Design
     Create a program that will allow the user to display all customers that have placed Sales Orders in the given date range. The user will have an ability to drill-down to see the sales order items per customer.
     Selection screen fields
          Sales order creation date (range)
          Customer number (range)
     Output
          Header
               Customer Number
               Customer Name
               Total Order value (sum of order values from items below)
          Details
Sales order number
Material number
Order quantity
Order value
Reference
     Tables: KNA1, VBAK, VBAP
     Transaction VA03 (Sales order)
SOLUTION :-
*& Report Z_HALV_32722                                                *
REPORT Z_HALV_32722                            .
TYPE-POOLS: slis.
TABLES : kna1,
         vbak.
SELECT-OPTIONS: s_cst_no FOR kna1-kunnr.
SELECT-OPTIONS: s_cr_dt FOR vbak-erdat.
DATA : BEGIN of ty_hdr,
        kunnr TYPE vbak-kunnr,
        name1 TYPE kna1-name1,
        netwr TYPE vbak-netwr,
        END of ty_hdr,
        gt_hdr LIKE TABLE OF ty_hdr,
        gs_hdr LIKE LINE OF gt_hdr.
DATA : BEGIN of ty_ln,
        kunnr TYPE vbak-kunnr,
        vbeln TYPE vbap-vbeln,
        matnr TYPE vbap-matnr,
        kwmeng TYPE vbap-kwmeng,
        netwr TYPE vbap-netwr,
        END of ty_ln,
        gt_ln LIKE TABLE OF ty_ln,
        gs_ln LIKE LINE OF gt_ln.
DATA : BEGIN of ty_hdr1,
        kunnr TYPE vbak-kunnr,
        END of ty_hdr1,
        gt_hdr1 LIKE TABLE OF ty_hdr1,
        gs_hdr1 LIKE LINE OF gt_hdr1.
DATA : gt_fc TYPE slis_t_fieldcat_alv,
       gs_fc LIKE LINE OF gt_fc,
       gs_k_fld TYPE slis_keyinfo_alv,
       gt_layout TYPE slis_layout_alv,
       gv_repid TYPE sy-repid.
START-OF-SELECTION.
gv_repid = sy-repid.
perform fetch_data.
perform prepare_fc.
perform prepare_layout.
perform show_output.
*&      Form fetch_data
      text
--> p1        text
<-- p2        text
form fetch_data .
SELECT kunnr
INTO CORRESPONDING FIELDS OF TABLE gt_hdr1
FROM vbak
WHERE vbak~kunnr IN s_cst_no
AND vbak~erdat IN s_cr_dt.
DELETE ADJACENT DUPLICATES FROM gt_hdr1 COMPARING kunnr.
LOOP AT gt_hdr1 INTO gs_hdr1.
SELECT SINGLE vbakkunnr kna1name1 SUM( vbak~netwr )
INTO (gs_hdr-kunnr, gs_hdr-name1, gs_hdr-netwr)
FROM vbak INNER JOIN kna1
ON vbakkunnr = kna1kunnr
WHERE vbak~kunnr = gs_hdr1-kunnr
GROUP BY vbakkunnr kna1name1.
APPEND gs_hdr TO gt_hdr.
SELECT vbakkunnr vbapvbeln vbapmatnr vbapkwmeng vbap~netwr
INTO CORRESPONDING FIELDS OF TABLE gt_ln
FROM vbap INNER JOIN vbak
ON vbapvbeln = vbakvbeln
WHERE vbak~kunnr = gs_hdr1-kunnr.
ENDLOOP.
endform.                    " fetch_data
*&      Form prepare_fc
      text
--> p1        text
<-- p2        text
form prepare_fc .
CLEAR gs_k_fld.
gs_k_fld-header01 = 'KUNNR'.
gs_k_fld-item01   = 'KUNNR'.
CLEAR gs_fc.
gs_fc-fieldname = 'KUNNR'.
gs_fc-tabname   = 'GT_HDR'.
gs_fc-seltext_l = text-001.
APPEND gs_fc TO gt_fc.
CLEAR gs_fc.
gs_fc-fieldname = 'NAME1'.
gs_fc-tabname   = 'GT_HDR'.
gs_fc-seltext_l = text-002.
APPEND gs_fc TO gt_fc.
CLEAR gs_fc.
gs_fc-fieldname = 'NETWR'.
gs_fc-tabname   = 'GT_HDR'.
gs_fc-seltext_l = text-003.
APPEND gs_fc TO gt_fc.
CLEAR gs_fc.
gs_fc-fieldname = 'VBELN'.
gs_fc-tabname   = 'GT_LN'.
gs_fc-seltext_l = text-004.
APPEND gs_fc TO gt_fc.
CLEAR gs_fc.
gs_fc-fieldname = 'MATNR'.
gs_fc-tabname   = 'GT_LN'.
gs_fc-seltext_l = text-005.
APPEND gs_fc TO gt_fc.
CLEAR gs_fc.
gs_fc-fieldname = 'KWMENG'.
gs_fc-tabname   = 'GT_LN'.
gs_fc-seltext_l = text-006.
APPEND gs_fc TO gt_fc.
CLEAR gs_fc.
gs_fc-fieldname = 'NETWR'.
gs_fc-tabname   = 'GT_LN'.
gs_fc-seltext_l = text-007.
APPEND gs_fc TO gt_fc.
endform.                    " prepare_fc
*&      Form prepare_layout
      text
--> p1        text
<-- p2        text
form prepare_layout .
gt_layout-colwidth_optimize = 'X'.
gt_layout-expand_fieldname = 'TST'.
endform.                    " prepare_layout
*&      Form show_output
      text
--> p1        text
<-- p2        text
form show_output .
CALL FUNCTION 'REUSE_ALV_HIERSEQ_LIST_DISPLAY'
EXPORTING
I_INTERFACE_CHECK              = ' '
    I_CALLBACK_PROGRAM             = gv_repid
I_CALLBACK_PF_STATUS_SET       = ' '
I_CALLBACK_USER_COMMAND        = ' '
    IS_LAYOUT                      = gt_layout
    IT_FIELDCAT                    = gt_fc
IT_EXCLUDING                   =
IT_SPECIAL_GROUPS              =
IT_SORT                        =
IT_FILTER                      =
IS_SEL_HIDE                    =
I_SCREEN_START_COLUMN          = 0
I_SCREEN_START_LINE            = 0
I_SCREEN_END_COLUMN            = 0
I_SCREEN_END_LINE              = 0
I_DEFAULT                      = 'X'
I_SAVE                         = ' '
IS_VARIANT                     =
IT_EVENTS                      =
IT_EVENT_EXIT                  =
    i_tabname_header               = 'GT_HDR'
    i_tabname_item                 = 'GT_LN'
I_STRUCTURE_NAME_HEADER        =
I_STRUCTURE_NAME_ITEM          =
    is_keyinfo                     = gs_k_fld
IS_PRINT                       =
IS_REPREP_ID                   =
I_BYPASSING_BUFFER             =
I_BUFFER_ACTIVE                =
IMPORTING
E_EXIT_CAUSED_BY_CALLER        =
ES_EXIT_CAUSED_BY_USER         =
tables
    t_outtab_header                = GT_HDR[]
    t_outtab_item                  = GT_LN[]
EXCEPTIONS
PROGRAM_ERROR                  = 1
OTHERS                         = 2
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
endform.                    " show_output

Everything looks fine with the gt_layout, it is not an internal table, so no need to append to it, it is simply a structure, but you do tell it that TST is the expand field, but there is no field of this name in your internal for the header, so add it like this.
DATA : BEGIN of ty_hdr,
kunnr TYPE vbak-kunnr,
name1 TYPE kna1-name1,
netwr TYPE vbak-netwr,
<b>TST type c,</b>
END of ty_hdr,
Doing so should make you program work correctly.
Regards,
Rich Heilman
Message was edited by:
        Rich Heilman

Dump error when clicked on text elements in SAP Script window

Hi All,
There is an inclusion in SAP Script. I have written the code in driver program. I need to pass the value to SAP Script in the requested position. But when I go to SE71 > Form Name > Change or Display > MAIN Window > Text Elements > I get a dump error.
Category               ABAP Programming Error
Runtime Errors         DATA_LENGTH_TOO_LARGE
Except.                CX_SY_RANGE_OUT_OF_BOUNDS
ABAP Program           SAPLSTXK
Application Component BC-SRV-SCR
Date and Time          30.04.2014 20:00:08
Short text
     Invalid partial field access: Length is too large
What happened?
     Error in the ABAP Application Program
     The current ABAP program "SAPLSTXK" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
What can you do?
     Note down which actions and inputs caused the error.
     To process the problem further, contact you SAP system
     administrator.
     Using Transaction ST22 for ABAP Dump Analysis, you can look
     at and manage termination messages, and you can also
     keep them for a long time.
Error analysis
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_RANGE_OUT_OF_BOUNDS', was not
      caught in
     procedure "TOKEN_COMMENT" "(FORM)", 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:
    In the executed program "SAPLSTXK", the system attempted to access the field
    "ITF_TOKEN" of the type "C" and with the length 255 using the length 272.
    However, a partial field access with a length specification that is
    larger than the field length is not allowed.
How to correct the error
    Reduce the length used to access the field.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "DATA_LENGTH_TOO_LARGE" "CX_SY_RANGE_OUT_OF_BOUNDS"
    "SAPLSTXK" or "LSTXKFRN"
    "TOKEN_COMMENT"
    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
2937 * todo empty comment ???
2938       if g_tm_open    eq true or     " Section
2939          g_tm_b_close eq true.
2940         l_token = '\chcbpat0'.
2941         l_len = strlen( l_token ).
2942         token_control = true.
2943         assign l_token to <itf1>.
2944         perform put_itf1_new using l_len.
2945         perform token_line_begin changing l_next_token.
2946       else.                          " without section
2947         concatenate '\chcbpat0\line' g_cf_string l_cbpat_token into l_token.
2948         l_len = strlen( l_token ).
2949         token_control = true.
2950         assign l_token to <itf1>.
2951         perform put_itf1_new using l_len.
2952       endif.
2953     elseif l_next_token-code eq ')L'.         " \par
2954       l_token = '\par'.
2955       l_len = strlen( l_token ).
2956       token_control = true.
2957       assign l_token to <itf1>.
2958       perform put_itf1_new using l_len.
2959     elseif l_next_token-code eq '(C' or       " \par + format
2960            l_next_token-code eq ')C' or
2961            l_next_token-code eq '(&' or
2962            l_next_token-code eq 'TA' or
2963            l_next_token-code eq 'SC' or
2964            l_next_token-code eq 'ST'.
2965       concatenate '\chcbpat0\par' g_pf_string g_cf_string l_cbpat_token into l_token.
2966       l_len = strlen( l_token ).
>>>>>       itf_token(l_len) = l_token.
2968       token_control = true.
2969       assign l_token to <itf1>.
2970       perform put_itf1_new using l_len.
2971     endif.
2972
2973 * Step 7: (L to disarm
2974   if g_compose eq true and
2975      l_next_token-code eq '(L'.
2976     perform read_next_itf_token(rstxscan) using p_token.
2977   endif.
2978
2979 ENDFORM.                    " token_comment
2980 *&---------------------------------------------------------------------*
2981 *&      Form create_lang_info
2982 *&---------------------------------------------------------------------*
2983 *       add default language to rtf
2984 *----------------------------------------------------------------------*
2985 *      -->P_HEADER text
2986 *      <--P_RESULT text
How do I open the text elements? I need to pass the variable inside SAP Script.
Please Help. The requirement is pending from very long. Not able to rectify this issue.
Regards,
Rekha

Hi,
There is a SAP Note about this problem
566794 - Runtime error: STRING_OFFSET_TOO_LARGE during conversion
Correction Instructions
Correction Instructions
Software Component
Valid from
Valid to
Number
SAP_BASIS
46B
46D
473267
SAP_BASIS
610
620
473185
Support Packages & Patches
Support Packages
Software Component
Release
Support Package
SAP_BASIS
46B
SAPKB46B48
46C
SAPKB46C39
46D
SAPKB46D28
610
SAPKB61027
620
SAPKB62014
Regards
Miguel

I am getting dump error while running one report in one select query

Hi,
While running a report program, I am getting a dump error in one select query. So could you please correct the select query so that I can't face the dump error.
SELECT vbeln parvw kunnr INTO CORRESPONDING FIELDS OF TABLE l_t_vbpa
FROM vbpa
FOR ALL ENTRIES IN l_t_backorder_item
WHERE vbeln = l_t_backorder_item-vbeln AND
( ( parvw = c_we AND kunnr IN rng_shipto ) OR ( parvw = c_ag AND
kunnr IN rng_soldto ) ) .
<removed by moderator>
Best Regards,
BDP
Edited by: Thomas Zloch on Apr 30, 2010 12:31 PM

Hi Bansidhar,
It would be helpful if you could tell what type of dump it is.
If it is a timeout you should check whether l_t_backorder_item is empty - in this case ALL document numbers are selected. f you get the timeout with a populated table consider converting the l_t_backorder_item table into one ore more ranges tables - the select with ranges tables is way quicker than 'for all entries'. But take care the ranges table has not to many entries - the SAP SQL converter puts this into one huge SQL statement and this might become too big to be handled by the database (depends on the actual underlying database).
I would also consider splitting the SELECT into two (2nd one with 'appending into table') to make the code easier to understand It also helps the database system determining a strategy for the select.
Regards,
Gerd Rother

Dump error while creating or double click the info package

Hello experts,
I have actived infocube 0FIAR_C03 in BI content. Ago, The creation infopackage have been deleted in the past , today, I created a infopackage, while I update mode selected u2018initialize delta processu2019, then click save button , the system prompt u2018Deltas already loaded for request REQU_D64R47LDUSZHY9CBIB86WMLFJ init.selection; no 2. initu2019, I canoti save it for my setting. Why is this?
Then I have search cause in SDN, and I have reference OSS Note 852443 to do .
Note 852443 have mention some table: RSSELDONE、RSSDLINIT、RSSDLINITSEL、ROOSPRMSC、ROOSPRMSF.
I have to delete that request of record using se16 in these tables: RSSELDONE、RSSDLINIT、RSSDLINITSEL.
in my BI 7.0 system, ROOSPRMSC、ROOSPRMSF is no any data.
I was no found delta queue in RSA7.
Now . Dump error while creating or double click the info package, how can I change this?
Please let me know the solution.
Thanks for your help.
Best Regards
Steve

Here are some links which deals with same issue.
Re: Dump In Infopackage
Re: Getting into Short dump at the time of selecting InfoPackage to execute for
Short dump while performing init in infopackage
Re: Infopackage going into short dump
Thanks.

Short Dump error while loading data from R/3 to ODS

Hello,
while trying to load data into the ODS from R/3 I get the following short dump error message. How do I carry out step 1 in the below procedure. Where do i find the Activate Function. And idea?
Thanks,
SD
                                                                                Diagnosis
Form routine CONVERT_ITAB_RFC is incorrect in transfer program
     GP4C0LOLZ6OQ70V8JR365GWNW3K .
System Response
The IDoc processing was terminated and indicated as incorrect. The IDoc
     can be reimported at any time.
Procedure
1. Go to the transfer rule maintenance for your InfoSource
         ZFIN_TR_FLQITEM_FI and the source system DA_M_10 and regenerate the
         transfer program using the function Activate. Remove possible syntax
         errors on the basis of your conversion routines.
2. Restart the processing of this IDoc.
3. If the error occurs again search for SAPNet R/3 notes, and create a
        problem message if necessary.
Edited by: Sebastian D'Souza on Jan 13, 2009 3:22 PM

Hi.......
Goto RSA1>> then to source system tab (on left side) >> double click on the desired source system...........Then on the right side you have the Datasource tree..........there search the datasource and activate.......Also u can Replicate the datasource again.......and activate the Transfer rules using the program : RS_TRANSTRU_ACTIVATE_ALL
After this operation when come back to source system (R/3).........I think the error log line will be disappeared from SM58......... Then repeat the load.........
Also u can try to Activate the infosource once...........in RSA1.........before repeating the load....
Hope this helps......
Regards,
Debjani....

ABAP dump error while updating product master in APO

Hi All,
Greetings from Vijay!
I need to your help to resolve below issue ;
I am getting error '
No simulation parameters could be set for the
active version'
While i am updating and trying to assign active version to my product master in APO which are created in APO for regression testing
and also sometimes system throwing dump error'
Error in the ABAP Application Program
The current ABAP program "/SAPAPO/SAPLDM_LC_SQL" had to be terminated because
it has
come across a statement that unfortunately cannot be executed.;
I appreciate your help
Thanks
Vijay Job

Hi Vijay,
Can you check note 1465462 ?
The same problem is mentioned in the note with correction .
Regards,
Mukesh pandey

Abap dump error while release Production order

Dear Gurus,
Abap dump error is creating while release production order , pour some light on this issue.
Regards,
Kamal

Hello,
use transaction ST22 to analyze the error type. There you have the detail of the error message, the program and the line of the ABAP code where the dump was triggered.
Best regards,
Andrea

ABAP dump Error while creating service order in PCUI.

Hi Experts,
                 We are getting following ABAP dump error while creating service order in PCUI which is working fine in GUI.
Runtime Errors         RAISE_EXCEPTION
Date and Time          02.01.2008 14:55:38
Short text
Exception condition "TYPE_NOT_FOUND" raised.
What happened?
The current ABAP/4 program encountered an unexpected
situation.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
A RAISE statement in the program "CL_CRM_ELEMDESCR==============CP" raised the
exception
condition "TYPE_NOT_FOUND".
Since the exception was not intercepted by a superior
program, processing was terminated.
Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
|    function module from the display of active calls.
We have added custom fields in the service application. these custom fields with Z-structure & data elements are included in BSP structure CRMT_BSP_SRV_OIC_SRCHRES in development system.But the same Z structure & custom fields are exist in the production system but not included in BSP Structue CRMT_BSP_SRV_OIC_SRCHRES.
This may be the reason resulting this ABAP dump error in PCUI while creating Service order.
How these Z structures can be included in the BSP Structure CRMT_BSP_SRV_OIC_SRCHRES in production system?
Helpful answers would be rewrded max points as it is high priority issue.
Regards,
Basavaraj Patil

Hi Thirumala,
Thnaks for the reply.
            I have enhanced service application using transaction EEWB to add new custom fields. these fields are there in Z structure created by the system in production system. All the transports are moved to target system. Problem is that Z structure( contains custom fields) created while doing EEWB is not included in BSP structure.
I f transports are missed to move to target system, Is there any other alternative to solve this problem?
Regards,
Basavaraj Patil

Dump Error while creating Business Partner in FPP1

Dear Experts,
I am using the EHP5 IS-U component. I am getting the below dump error, when I am trying to create Business partner in T.Code: FPP1.
**Error in the ABAP Application Program**
**The current ABAP program "ISU_BUPA_EVENT_DINP1==========FT" had to be terminated because it has come across a statement that unfortunately cannot be executed.**
**The following syntax error occurred in program "SAPLES02 " in include "LES02U14 " in line 30:**
**"The data object "BUS0DIINIT" does not have a component called "MUSTER_KUN".**
I have searched SAP notes, but I am unable to find any suitable notes to resolve this issue.
Could anyone help me to resolve this issue.
Thanks in Advance,
Regards,
Aswin

Hi,
Please don't go adding fields. Aren't we talking about SAP-standard structures here?
Have you actually checked (in transaction SE11) that the structure ISU_EKUNINIT is included in the BUS0DIINIT?
If it is, and the field MUSTER_KUN is missing, then you should raise an OSS note.
If the structure is not included, you should also talk to OSS. Your ISU installation might be incomplete?
cheers
Paul Bakker

At the time of RFQ creation dump error

Dear All,
                    At the time of RFQ creation one Dump error is coiming... please advise to solve this issue...
the error message is :
Runtime errors         SYNTAX_ERROR
       Occurred on     09.09.2009 at   12:10:27
Syntax error in program "SAPLV61A ".
What happened?
The following syntax error occurred in the program SAPLV61A :
"Incorrect logical expression: Instead of "X" a field, a function or "("
Error in ABAP application program.
The current ABAP program "SAPLMEVA" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Please eliminate the error by performing a syntax check
(or an extended program check) on the program "SAPLV61A ".
You can also perform the syntax check from the ABAP/4 Editor.
If the problem persists, proceed as follows:
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.
Error analysis
The following syntax error was found in the program SAPLV61A :
"Incorrect logical expression: Instead of "X" a field, a function or "("
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, 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.
System environment
SAP Release.............. "620"
Application server....... "ARCHIVAL"
Network address.......... "172.26.2.145"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "4x Intel 80686"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "ARCHIVAL"
Database type............ "MSSQL"
Database name............ "EDP"
Database owner........... "dbo"
Terminal................. "cheeid92corit"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Mar 9 2009 22:54:07"
Created in............... "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version......... "SQL_Server_9.00 "
Patch level.............. "274"
Patch text............... " "
Supported environment....
Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,
Windows NT 6.0"
User, transaction...
Client.............. 777
User................ "MMCORE"
Language key........ "E"
Transaction......... "ME47 "
Program............. "SAPLMEVA"
Screen.............. "SAPMM06E 0311"
Screen line......... 54
Information on where terminated
The termination occurred in the ABAP program "SAPLMEVA" in
"ME_LOAD_VARIANTS_PRICING".
The main program was "SAPMM06E ".
The termination occurred in line 55 of the source code of the (Include)
program "LMEVAU08"
of the source code of program "LMEVAU08" (when calling the editor 550).
Source code extract
000250       ENDIF.
000260   *--> Initialisieren
000270   *--> not necessary anymore (Raimond Buchholz)
000280   *   CALL FUNCTION 'CUD0_CONFIGURATION_INITIALIZER'.
000290   *--> Preisteile der Varianten besorgen
000300       CALL FUNCTION 'CEI0_GET_CONDITIONS'
000310            EXPORTING
000320                 INSTANCE    = I_CUOBJ
000330                 APPLICATION = 'MM'
000340            TABLES
000350   *              CONDITIONS = T_VCKEY.                 "del 194053
000360                 CONDITIONS = T_VCKEY                   "ins 194053
000370            exceptions                                   "ins 194053
000380                 error_message = 01                     "ins 194053
000390                 others         = 02.                    "ins 194053
000400   *--> Preisteile der Varianten mit Belegnummer versorgen
000410       LOOP AT T_VCKEY.
000420         T_VCKEY-KAPPL = 'M '.
000430         T_VCKEY-VBELN = I_EBELN.
000440         T_VCKEY-POSNR = I_EBELP.
000450         MODIFY T_VCKEY.
000460       ENDLOOP.
000470     ENDIF.
000480
000490   *--> Preisteile der Varianten an Preisfindung übergeben
000500   *- pricing_load_variant_key muß auch bei Positionen ohne Konfiguration
000510   *- laufen, da die Logik im PRICING zu 4.0 umgestellt wurde
000520     IF I_NO_LOAD IS INITIAL.
000530       DATA: I_POSNR LIKE VBAP-POSNR.
000540       I_POSNR = I_EBELP.
      CALL FUNCTION 'PRICING_LOAD_VARIANT_KEYS'
000560            EXPORTING
000570                 APPLICATION = 'M '
000580                 VBELN       = I_EBELN
000590                 POSNR       = I_POSNR
000600            TABLES
000610                 TVCKEY      = T_VCKEY
000620            EXCEPTIONS
000630                 OTHERS      = 1.
000640     ENDIF.
000650
000660   ENDFUNCTION.
Contents of system fields
SY field contents..................... SY field contents.....................
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 GVP
SY-UCOMM
SY-TITLE Maintain Quotation : Item 00001
SY-MSGTY E                             SY-MSGID AIPLOC
SY-MSGNO 002                           SY-MSGV1 303632
SY-MSGV2                               SY-MSGV3
SY-MSGV4
Kind regards
P.Anandhakumar

Hi Anandhakumar,
Debugg the transaction with help of ABAPER.
System will show you the reason for the above error.
Hope this should solve your problem.
Thanks and regards
Gitesh

While saving the delivery no in VA02 dump error showing (Arithmatic overflo

Hi,
while saving the delivery no in VA02, one dump error getting displayed.
Arithmatic over flow occurs.
Can any one can say how to rectify the program to avoid dump error
The below lines are showing in dump.
Waiting for quick response.
Error analysis
               An exception occurred that is explained in detail below.
               The exception, which is assigned to class 'CX_SY_ARITHMETIC_OVERFLOW', was not
                caught in
               procedure "USEREXIT_SAVE_DOCUMENT_PREPARE" "(FORM)", 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:
               An overflow was discovered in an ongoing arithmetical operation with
               operands of type P. Possible causes are:
               1. The result field of type P is too small for the result.
               2. The result or a intermediate result has more than 31 decimal places.
     How to correct the error
               The result field must be enlarged, if this is still possible. It may
               also be possible to break up the current process into subprocesses so
               that only smaller values occur.
               There may already be a solution to the error in the SAP notes system.
               If you have access to the SAP notes system first try searching with the
               following keywords:
                "COMPUTE_BCD_OVERFLOW"
                "BCD_FIELD_OVERFLOW" (Until release 4.0a, this runtime error occurred at this
                position)
                "SAPMV50A" or "ZSDI_MV50AFZ1_CRPC_CALC_4QA"
                "USEREXIT_SAVE_DOCUMENT_PREPARE"               ***----
     Information on where terminated
               Termination occurred in the ABAP program "SAPMV50A" - in
                "USEREXIT_SAVE_DOCUMENT_PREPARE".
               The main program was "SAPMV50A ".
               In the source code you have the termination point in line 666
               of the (Include) program "ZSDI_MV50AFZ1_CRPC_CALC_4QA".
               The termination is caused because exception "CX_SY_ARITHMETIC_OVERFLOW"
                occurred in
               procedure "USEREXIT_SAVE_DOCUMENT_PREPARE" "(FORM)", but it was neither handled
                locally nor declared
               in the RAISING clause of its signature.
               The procedure is in program "SAPMV50A "; its source code begins in line
               208 of the (Include program "MV50AFZ1 ".
657                           ADD: xvbap-brgew TO l_w_tot_list_vals-brgew,
     658                                xvbap-zzlogpoint TO l_w_tot_list_vals-zlogpoint,
     659                               xvbap-zztotgrossvalue TO
     660                               l_w_tot_list_vals-totgrossvalue.
     661
     662
     663                           l_w_tot_list_vals-gewei = xvbap-gewei.
     664
     665                           IF NOT xvbap-pstyv IN zzt_free.
     >>>>>                             ADD xvbap-volum TO l_w_tot_list_vals-volum.
     667                           ELSE.
     668                             ADD xvbap-volum TO l_w_tot_list_vals-volum_f.
     669                           ENDIF.
     670                           ADD 1 TO l_w_tot_list_vals-zw_nbitem.
Best Regards,
BDP
Edited by: Bansidhar Padhy on Jan 26, 2010 8:24 AM

ADD xvbap-volum TO l_w_tot_list_vals-volum.
Declare l_w_tot_list_vals-volum as "like vbap-volum" or (preferably) "type volum_ap".
If you're using a packed decimal, you've done something like.... volum(5) type p decimals 2, which is a great way to get an overflow...if you use packed decimals in a program...declare <field> type p decimals <n> without a length attribute, so that SAP can use the full 8 bytes for the calculation.....the put it into a alpha field for display, if needed....

Regarding dump error in MMBE

Similar Messages

Maybe you are looking for