Set variables - dump error

Hi,
am working in dev system.For any application if i select set variables button the system takes long time and finally give me dump error.any idea why this happens?
saggi

What is the replacement type of this variable? Also, sometimes, if you log out after defining the variables , it works.
Ravi Thothadri

Similar Messages

Set variables leads to dump error in SEM 4.0

Hi,
I am on SEM 4.0 system.In BPS, i am not able to use set variables feature.whenever i hit this button the system does the process for couple of minutes and finally gives a dump error.
I applied this note 806362.No success.
Any one to my rescue?

ravi,
the variable is of type user-defined values and input allowed by user.
"If the replacment type is user speficic values, then you can go to BPS0 - area - variable and set the values here also".- How i would do it here? Inorder to set the variable with a value i will choose SET VARIABLES option.
Whenever i choose this the system creates a dump.
Message was edited by:
ragav

Dump error after calling a global class from se24

this is the small code i did so far.
parameters: X type i,
                  Y type i.
data: Z type i.
data: con1 type ref to ZTEST1.
CALL METHOD con1->zm1
EXPORTING
    a      = x
    b      = y
IMPORTING
    c      = z.
write:/ z.
after executing iam getting a dump error-
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
caught and
therefore caused a runtime error.
The reason for the exception is:
You attempted to use a 'NULL' object reference (points to 'nothing')
access a component (variable: "CON1").
An object reference must point to an object (an instance of a class)
before it can be used to access components.
Either the reference was never set or it was set to 'NULL' using the
CLEAR statement.

Hi, Could you please tell me how to solve this issue?

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

Short Dump Error

Hi Everyone,
I'm loading 690k odd records to cube
I am facing short dump error while data request is processed to cube.
In ST22 i'm getting Timeout Error.
Buffer time is set for 10mins to process
Can anyone guide me in this issue.
Thanks in advance

Hi,
Due to data volume your load took more than 7hrs. in general time out time is 7hrs. so in your case its may exceeded.
Try to increase time out time for your info package.
Go to your info pack--> menu scheduler --> time out time--> increase 7 hrs to 14hrs and trigger your load again. if its full load delete failed load and retrigger.
Thanks

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

Dump error while creating Invoicing document

Moderator note - this is the same problem as identified in thread Error is generated in Print workbench function ISU_INV_BILL_PREPARE. Thread locked and poster notified of rules violation.
Hi Experts,
I am new to ISU application.Please provide solution for below mentioned dump error.
The error is generated in Print workbench function ISU_INV_BILL_PREPARE which is called from application form IS_U_BILL (/1PWB/SAPL20020100218092657) when I'm trying to generate invoice for the bill in EASIBI.
Error analysis
Short text of error message:
Unexpected ELSE case: field sy-subrc with value 0 (/1PWB/200201002180926
57 )
Long text of error message:
Something has occurred in a CASE or IF construct which the
developer did not expect, or which is not permissible here.
System Response
Procedure
Note the field name and field value from the message as well as the
data pattern which lead to the error. Create a problem message.
Technical information about the message:
Message class....... "E9"
Number.............. 898
Variable 1.......... "sy-subrc"
Variable 2.......... 0
Variable 3.......... "/1PWB/20020100218092657"
| Variable 4.......... " "
Thanks in Advance.
Vaseem
Edited by: William Eastman on Mar 9, 2010 2:34 PM
Edited by: William Eastman on Mar 9, 2010 2:36 PM

Hi Experts,
Please reply..... It's very important.
Thanks
Vaseem
Moderator note: DO NOT beg for answers, or suggest that you need an immediate reply. Read the rules of engagement here Research Resources and Rules of Engagement
Edited by: William Eastman on Mar 9, 2010 2:24 PM

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.

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

Dump error while running termination action

I'm facing a dump error while running termination action, please, if some one wud help me out of this error. here when im termination action the system is opening action infotype when given the date of termination and try to save, system shows a warning message that "Record valid from 08.08.1995 to 31.12.9999 delimited at end" then I press enter and system is asking me to save. when I do so, rather than it taking me to another screen its throwing a dump error.
Runtime Errors         SYNTAX_ERROR
Date and Time          21.10.2008 18:54:05
Short dump has not been completely stored (too big)
Short text
     Syntax error in program "SAPLCACS_BU_PARTNER ".
What happened?
     Error in the ABAP Application Program
     The current ABAP program "SAPLBUD_CHECK" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
     The following syntax error occurred in program "SAPLCACS_BU_PARTNER " in
      include "LCACS_BU_PARTNERU44 " in
     line 19:
     "The key of internal table "LT_BUT0BK" contains components of type "X" "
     "or "XSTRING". The "READ TABLE LT_BUT0BK" statement is not permitted fo"
     "r such tables in a Unicode context."
     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 "SAPLBUD_CHECK" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
Error analysis
     The following syntax error was found in the program SAPLCACS_BU_PARTNER :
     "The key of internal table "LT_BUT0BK" contains components of type "X" "
     "or "XSTRING". The "READ TABLE LT_BUT0BK" statement is not permitted for
"r such tables in a Unicode context."
ger Location of Runtime Error
Program                                 SAPLBUD_CHECK
Include                                 LBUD_CHECKF01
Row                                     1.129
Module type                             (FORM)
Module Name                             RLDEL_CHECK
ce Code Extract
SourceCde
9
0 *------ ... Funktionsbausteine ermitteln -
1   CALL FUNCTION 'BDT_TBZ1F_GET'
2     EXPORTING
3       iv_objcn = gc_objcn_bupa
4       iv_objap = gc_objap_bupa
5     TABLES
6       et_tbz1f = lt_tbz1f
7     EXCEPTIONS
8       not_found = 1
9       OTHERS    = 2.
0   READ TABLE lt_tbz1f INDEX 1.
1   IF sy-subrc = 0.
2     CALL FUNCTION 'BUP_PARTNER_GET'
3       EXPORTING
4         i_partner    = is_but100-partner
5         i_cp_exclude = gc_x
i_is_exclude = gc_x
PORTING
e_but000_int = ls_but000_int
CEPTIONS
OTHERS       = 1.
... Funktionsbausteine aufrufen -
T lt_tbz1f WHERE     ztpkt = 'RLDEL'
             AND NOT fname IS INITIAL.
Datümer alt = neu = SPACE => Löschung, sonst Update -
(Einschränkung der Gültigkeit)
FUNCTION lt_tbz1f-fname
PORTING
i_partner        = is_but100-partner
i_partnerguid    = ls_but000_int-partner_guid
i_role           = is_but100-rltyp
i_dfval          = is_but100-dfval
i_calltp         = iv_calltp
i_valid_from     = is_but100-valid_from_dats
i_valid_from_old = iv_valid_from_old
i_valid_to       = is_but100-valid_to_dats
i_valid_to_old   = iv_valid_to_old
PORTING
e_result         = lv_result.
... Ergebnis merken, wenn höher als bisheriges Zwischenergebnis-
v_result > gv_wu_result.                          "#EC PORTABLE
wuresult = lv_result.
F.
... Ergebnis ist 'Nicht löschen': Zeitpunkt abbrechen -

HI Mallik,
for termination action the operation that i've set is
lis9 0001
cop 0002
lis9 0007
cop 0008
lis9 0014
lis9 0015
lis9 0587
so just want to know if the set format for termination action is right
and other option is that if there is some change to settings of infotype charateristics in table v_t582A this may cause change in the date that is cause of error.
can u please suggest the above alignment of operations and infotype is right and provide me the idle settings for infotype characteristics which may solve my query.
thanks mallik.

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

Dump error while Testing the Workflow

Hi Friends,
I have developed workflow for Approve and Reject Scenerio. But when i press Approve, the user should get the mail, same for Rejected also. When Test the Workflow, I am getting the Dump Error as
*Dump Error*********
Unable to read RFC destination WORKFLOW_LOCAL_320
Long text of error message:
Technical information about the message:
Message class....... "SWF_RUN"
Number.............. 617
Variable 1.......... "WORKFLOW_LOCAL_320"
Variable 2.......... "RFC_READ_DESTINATION_TYPE"
Variable 3.......... "DESTINATION_NOT_EXIST"
Variable 4.......... " "
Thanks in Advance. Rewarded if useful.
Naveen

Naveen,
It seems someone might have deleted the corresponding RFC destination (which is created automatically). Check in SM59.
ss

Short dump error in MIGO transenction.

Hi all,
I am using sap client :800 for Ides. I am going to post GR using Transection MIGO. i get the dump ERROR as
Error analysis
    Short text of error message:
    No RFC destination is defined for SAP Global Trade Services
    Technical information about the message:
    Message classe...... "/SAPSLL/PLUGINR3"
    Number.............. 002
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
Program                                 SAPLMBWL
Include                                   LMBWLU21
Row                                       59
Module type                           (FUNCTION)
Module Name                          MB_POST_GOODS_MOVEMENT
With description of programme
29 *    when a goods movement for an inbound or outbound delivery is posted
30 *    directly from VL31N/ VL01N, XBLNR is not yet known when we call
31 *    CKMV_AC_DOCUMENT_CREATE, but the number is supposed to be stored in
32 *    BKPF as well. There is no other way to forward XBLNR to FI as not
33 *    every document is posted by MB_CREATE -> a new function module in
34 *    MBWL for transferring the information, called by FI, meant to load
35 *    the complete function group for all MBxx postings when this isn't
36 *    required (Performance). Would be the better way to transport the
37 *    information after switching off MBxx in later release.
38 *    corresponding IMPORT ... FROM MEMORY ... can be found in
39 *    AC_DOCUMENT_POST (FORM FI_DOCUMENT_PREPARE (LFACIF5D))
40      l_mem_id = 'MKPF-XBLNR'.                                   " 641365
41      EXPORT xblnr = xblnr_sd TO MEMORY ID l_mem_id.             " 641365
42    ENDIF.
43    IF xmkpf-xabln IS INITIAL.                               "note 434093
44        CALL FUNCTION 'MB_XAB_NUMBER_GET'.                   "note 434093
45    ENDIF.                                                   "note 434093
46
47 ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_01 SPOTS ES_SAPLMBWL STATIC.
48
49 ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_02 SPOTS ES_SAPLMBWL.
50    CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'
51         EXCEPTIONS
52           error_message = 4.
53 * As soon as we have started to put things into UPDATE TASK, we must
54 * ensure that errors definitely terminate the transaction.
55 * MESSAGE A is not sufficient because it can be catched from
56 * external callers which COMMIT WORK afterwards, resulting in
57 * incomplete updates. Read note 385830 for the full story.
58    IF NOT sy-subrc IS INITIAL.
>>>>       MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH            "385830
60                  sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
61 *     MESSAGE A263.
62    ENDIF.
63 * Optische Archivierung
64 * Spaete Erfassung mit Barcode
65 * Redesign of barcode handling -> note 780365
66   PERFORM barcode_update(sapmm07m) USING xmkpf-mblnr
67                                          xmkpf-mjahr
68                                          barcode.
69
70   MOVE-CORRESPONDING xmkpf TO emkpf.
71   CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
72     EXCEPTIONS
73       error_message = 4.
74    MOVE-CORRESPONDING xmkpf TO emkpf.
75    CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
76         EXCEPTIONS
77           error_message = 4.
78    IF NOT sy-subrc IS INITIAL.
How i can solve this Error.

Dear Baya,
If you do not want to use SAP GTS, please kindly deactivate it.
(or else you would have defined an Rfc destination for it).
Please check customzing below and deactivate GTS connection to the ERP
System:
Possibility to deactivate the GTS transfers (if currently the transfer
is active):
General deactivation of GTS calls using following path in IMG:
SAP Customizing Implementation Guide
-> Sales and Distribution
-> Foreign Trade/Customs
   -> SAP Global Trade Services - Plug-In
    -> Control Data for Transfer to SAP Global Trade Services
     -> Technical Activation of Document Transfer
If you execute these activities you are asked if you want to deactivate
the implementation of BAdI implementations. This has to be confirmed
with yes.
Hope this will help.
Ian Wong Loke Foong

Short dump Error in BAPI_BUS2054_SET_STATUS

I am trying to set status of wbs element and have the following sequence of calls based on the
Error in BAPI_BUS2054_SET_STATUS
CALL FUNCTION 'BAPI_PS_INITIALIZATION' .
CALL FUNCTION 'BAPI_PS_PRECOMMIT'
TABLES
et_return = it_bapiret.
CALL FUNCTION 'BAPI_BUS2054_SET_STATUS'
IMPORTING
return = l_return
TABLES
i_wbs_user_status = it_wbs_user_status
e_result = lt_e_result.
IF l_return-type EQ 'E'.
gv_flg_error = 'X'.
ENDIF.
CALL FUNCTION 'BAPI_PS_PRECOMMIT'
TABLES
et_return = it_bapiret.
READ TABLE it_bapiret INTO it_bapiret WITH KEY type = 'E'.
IF sy-subrc = 0.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
wait = 'X'.
ENDIF.
I am still getting the short dump :
Error analysis
    Short text of error message:
    Precommit did not run successfully
Information on where terminated
    Termination occurred in the ABAP program "SAPLPS_BAPI" - in "CHK_PRECOMMIT".
    The main program was "RS_TESTFRAME_CALL ".
In the source code you have the termination point in line 24
    of the (Include) program "LPS_BAPIF01".
Any help to make this work is appreciated.

suzzie
you are always calling precommit after set_status.you should call only if set_status is successfull.
This is how we are calling for network status.
        call function 'BAPI_PS_INITIALIZATION'.
        call function 'BAPI_BUS2002_SET_STATUS'
          exporting
            number                   = network
          tables
            i_activity_system_status = it
            e_result                 = itet.
        read table itet into wa_itet with key message_type = 'E'.
        if sy-subrc ne 0.
          call function 'BAPI_PS_PRECOMMIT'
            tables
              et_return = etit.
          call function 'BAPI_TRANSACTION_COMMIT'
            exporting
              wait = 'X'.
        else.
         MOVE wa_itet-message_text TO wa_error_tab-message_text.
         wa_error_tab-key1 = network.
         wa_error_tab-key2 = wa_itet-objectkey+12(4).
         wa_error_tab-object_type = c_activity.
         APPEND wa_error_tab TO e_error_tab.
        endif.

Error in creating Table Maintenance for TABLES: J_2IRG1BAL ,Dump error show

Dear Gurus
I have Created one Table Maintenance for TABLES: J_2IRG1BAL ,
1) I have take function group as same as table name like J_2IRG1BAL
3) Authorization Group &NC&
4) Authorization object S_TABU_DIS
5) Function group J_2IRG1BAL
6) Package J1I5
7) Maintenance type one step.
8) Maint. Screen No.    Overview screen 2009.
9) Recording routine STD recording routines .
I have assign screen single screen 1 but it will not take the screen so ill put screen 2009 ,the system will not not accept the screen but I proposed to Save and activate the table maintenance generator and created and save the function group ,the table is ready to save the entries
We have to go to SM30 then put 4-5 entries ,after that a dump error shows
Which i have attachéd in this mail kindly help me out
Its effect in production server.
I have found that the error is given below I have mentioned all the details
Kindly read this
I have created function group J_2IRG1BAL and assign Package J1I5 and function group,J1I5 is already a Function group so problem occurs a dump error message displays
Kindly give me the right solution all the Clients are effected
110,100 150,250 these all are effected development clients
300 is prod client this is also affected because I have created a table maintenance generator and send the req to production .
*Dump Error Shows in Production*
Runtime Errors         SYNTAX_ERROR
Date and Time          11.12.2008 09:26:30
What happened?
|    Error in ABAP application program.
Error analysis
In program "SAPLJ1I5 ", the following syntax error occurred:
"The program "SAPLJ1I5" is not Unicode-compatible, according to its pro"
"gram attributes."
The current ABAP program "SAPLSVIM" 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 "SAPLJ1I5 ", the following syntax error occurred
in the Include "SAPLJ1I5 " in line 0:
"The program "SAPLJ1I5" is not Unicode-compatible, according to its pro"
"gram attributes."
rigger Location of Runtime Error                                                                 |
Program                                 SAPLSVIM
Include                                 LSVIMU01
Row                                     107
Module type                             (FUNCTION)
|    Module Name                             VIEW_MAINTENANCE
Author and last person to change the Include are:
Author "TTLABAP2 "
Last changed by "TTLABAP2 "
105
Initialisierung des Abgleichsmandanten zum View                     *
106
>>>>>
vim_default_upgr_clnt-viewname = x_header-viewname.
108
vim_default_upgr_clnt-client   = client_for_upgrade.
109
PERFORM vim_set_global_field_value IN PROGRAM (fpool)
| 110|            USING 'VIM_DEFAULT_UPGR_CLNT' 'C' vim_default_upgr_clnt rc.

I have send you all the details regarding the table maintenance generator
error is shown below
                                       I have Created one Table Maintenance for TABLES: J_2IRG1BAL ,
1) I have take function group as same as table name like J_2IRG1BAL
3) Authorization Group &NC&
4) Authorization object S_TABU_DIS
5) Function group J_2IRG1BAL
6) Package J1I5
7) Maintenance type one step.
8) Maint. Screen No.    Overview screen 2009.
9) Recording routine STD recording routines .
I have assign screen single screen 1 but it will not take the screen so ill put screen 2009 ,the system will not not accept the screen but I proposed to Save and activate the table maintenance generator and created and save the function group ,the table is ready to save the entries
We have to go to SM30 then put 4-5 entries ,after that a dump error shows
Which i have attachéd in this mail kindly help me out
Its effect in production server.
I have found that the error is given below I have mentioned all the details
Kindly read this
I have created function group J_2IRG1BAL and assign Package J1I5 and function group,J1I5 is already a Function group so problem occurs a dump error message displays
Kindly give me the right solution all the Clients are effected
110,100 150,250 these all are effected development clients
300 is prod client this is also affected because I have created a table maintenance generator and send the req to production .
                                                                                Runtime Errors         SYNTAX_ERROR
Date and Time          11.12.2008 09:26:30
ShrtText
Syntax error in program "SAPLJ1I5 ".
What happened?
Error in ABAP application program.
The current ABAP program "SAPLSVIM" 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 "SAPLJ1I5 ", the following syntax error occurred
in the Include "SAPLJ1I5 " in line 0:
"The program "SAPLJ1I5" is not Unicode-compatible, according to its pro"
"gram attributes."
Author and last person to change the Include are:
Author "TTLABAP2 "
Last changed by "TTLABAP2 "
Error analysis
In program "SAPLJ1I5 ", the following syntax error occurred:
"The program "SAPLJ1I5" is not Unicode-compatible, according to its pro"
"gram attributes."
Trigger Location of Runtime Error
Program                                 SAPLSVIM
Include                                 LSVIMU01
Row                                     107
Module type                             (FUNCTION)
Module Name                             VIEW_MAINTENANCE
Source Code Extract
Line
SourceCde
77
TRANSPORTING NO FIELDS.
78
IF sy-subrc NE 0.
79
SELECT SINGLE * FROM tfdir WHERE funcname EQ <function_name>.
80
IF sy-subrc NE 0.
81
RAISE no_editor_function.
82
ELSE.
83
length = strlen( function_name1 ).
84
ASSIGN function_name1(length) TO <function_name>.
85
SELECT SINGLE * FROM tfdir WHERE funcname EQ <function_name>.
86
IF sy-subrc NE 0.
87
RAISE no_database_function.
88
ENDIF.
89
ENDIF.
90
INSERT x_header-viewname INTO alr_checked_views INDEX sy-tabix.
91
ELSE.
92
length = strlen( function_name1 ).
93
ASSIGN function_name1(length) TO <function_name>.
94
ENDIF.
95
96
Initialisierung der RFC-Destination zum View                        *
97
98
FPOOL+4 = X_HEADER-AREA.
99
fpool   = x_header-fpoolname.
100
vim_default_rfc_dest-viewname = x_header-viewname.
101
vim_default_rfc_dest-rfcdest = rfc_destination_for_upgrade.
102
PERFORM vim_set_global_field_value IN PROGRAM (fpool)
103
USING 'VIM_DEFAULT_RFC_DEST' 'C' vim_default_rfc_dest rc.
104
105
Initialisierung des Abgleichsmandanten zum View                     *
106
>>>>>
vim_default_upgr_clnt-viewname = x_header-viewname.
108
vim_default_upgr_clnt-client   = client_for_upgrade.
109
PERFORM vim_set_global_field_value IN PROGRAM (fpool)
110
USING 'VIM_DEFAULT_UPGR_CLNT' 'C' vim_default_upgr_clnt rc.
111
112
set flag if complex selection conditions in sellist                  *
113
114
IF complex_selconds_used NE space.
115
READ TABLE dba_sellist INDEX 1.
116
IF sy-subrc EQ 0 AND dba_sellist-cond_kind EQ space.
117
dba_sellist-cond_kind = 'C'. MODIFY dba_sellist INDEX 1.
118
ENDIF.
119
ENDIF.
120
121
direkter Vergleich: Flagge setzen usw.                              *
122
123
IF view_action EQ vim_direct_upgrade.
124
view_action = aendern.
125
PERFORM vim_set_global_field_value IN PROGRAM (fpool)
126
USING 'VIM_SPECIAL_MODE' 'C' vim_direct_upgrade rc.

Set variables - dump error

Similar Messages

Maybe you are looking for