Runtime Error SYNTAX_ERROR with MIGO tcode

Hi Gurus,
I got a new issue now. while executing MIGO tcode getting SYNTAX_ERROR dump, please check below dump details..
Category               ABAP Programming Error
Runtime Errors         SYNTAX_ERROR
ABAP Program           SAPLVBDOCUBATCH_DM
Application Component LO-BM
Date and Time          09.01.2012 16:27:51
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLMIGO" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "SAPLVBDOCUBATCH_DM " in include
     "LVBDOCUBATCH_DM$39 " in
    line 8:
    ""RL034" must be a flat structure. You cannot use internal tables, stri"
    "ngs, references, or structures as components."
    The include has been created and last changed by:
    Created by: "SAP "
    Last changed by: "SAP "
    Error in the ABAP Application Program
    The current ABAP program "SAPLMIGO" 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 SAPLVBDOCUBATCH_DM :
    ""RL034" must be a flat structure. You cannot use internal tables, stri"
    "ngs, references, or structures as components."
i have tried to check syntax of program SAPLVBDOCUBATCH_DM and it is giving error, please help me solve this issue.
Additional Information:ECC6.0 EHP5(recently upgraded from ECC6.0) nd DB:Oracle 10.2.0.2 OS:windows
Thanks,
Venkat

Hello Team,
This is Solved..
As per dump when we go n check table RL034 through SE11 there one Object type is wrong so with Abaper help it got corrected then the problem was solved.
Thanks all for your time.
Venkat

Similar Messages

Runtime Errors SYNTAX_ERROR in SAP Solution Manager 4.0

Hi every body,
     After in install of support packages SAP_BASIS SAP_ABA and ST. When I logon in the SAPGui I received this error:
Runtime Errors         SYNTAX_ERROR
Short text
    Syntax error in program "SAPLSCP2 ".
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLOLEA" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "SAPLSCP2 " in include "LSCP2U09
     " in
    line 66:
    "The field "ZCSA_SYSTEM_LANGUAGE" is unknown, but there is a field with"
    " the similar name "ZCSA_INSTALLED_LANGUAGES". "ZCSA_INSTALLED_LANGUAGE"
    "S"."
    The include has been created and last changed by:
    Created by: "SAP "
    Last changed by: "SAP "
Error analysis
    The following syntax error was found in the program SAPLSCP2 :
    "The field "ZCSA_SYSTEM_LANGUAGE" is unknown, but there is a field with"
    " the similar name "ZCSA_INSTALLED_LANGUAGES". "ZCSA_INSTALLED_LANGUAGE"
    "S"."
Trigger Location of Runtime Error
    Program                                 SAPLOLEA
    Include                                 LOLEAU13
    Row                                     71
    Module type                             (FUNCTION)
    Module Name                             AC_CALL_METHOD
Please help me
Regards.

Hi,
Have upgrade kernel?
Regards
Ben

Runtime Errors SYNTAX_ERROR in SAPLS_CODE_INSPECTOR after the ECC6.0 upgrad

we recently upgraded our development test sandbox from 46C to ECC6.0 using downtime minimized strategy for practice purposes.After a sucessful completion of the upgrade we applied all the support packages successfully upto the latest available. Upon testing we found that everything else works fine except code inspector. Everytime we go to transaction sci we get syntax error
Runtime Errors         SYNTAX_ERROR
Date and Time          08/20/2008 08:26:29
Short text
     Syntax error in program "SAPLS_CODE_INSPECTOR ".
What happened?
     Error in the ABAP Application Program
     The current ABAP program "????????????????????????????????????????" had to be
      terminated because it has
     come across a statement that unfortunately cannot be executed.
     The following syntax error occurred in program "SAPLS_CODE_INSPECTOR " in
      include "LS_CODE_INSPECTORTOP " in
     line 11:
     ""SCI_DYNP" must be a flat structure. You cannot use internal tables, s"
     "trings, references, or structures as components. ."
     The include has been created and last changed by:
     Created by: "SAP "
     Last changed by: "CRENSHAWDP "
     Error in the ABAP Application Program
     The current ABAP program "????????????????????????????????????????" had to be
      terminated because it has
     come across a statement that unfortunately cannot be executed.
What can you do?
     Please eliminate the error by performing a syntax check
     (or an extended program check) on the program "SAPLS_CODE_INSPECTOR ".
     You can also perform the syntax check from the ABAP Editor.
If the problem persists, proceed as follows:
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
r analysis
The following syntax error was found in the program SAPLS_CODE_INSPECTO
""SCI_DYNP" must be a flat structure. You cannot use internal tables, s
"trings, references, or structures as components. ."
to correct the error
Probably the only way to eliminate the error is to correct the program.
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
   To save the description, choose "System->List->Save->Local File
2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
    In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
tem environment
SAP-Release 700
Application server... "kiel"
Network address...... "138.254.140.161"
Operating system..... "AIX"
Release.............. "5.3"
Hardware type........ "000B7B2ED600"
Character length.... 8 Bits
Pointer length....... 64 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "kiel"
Database type..... "ORACLE"
Database name..... "UPD"
Database user ID.. "SAPR3"
Terminal................. "D800204486"
Char.set.... "en_US.ISO8859-1"
SAP kernel....... 700
created (date)... "Jun 22 2008 20:58:25"
create on........ "AIX 2 5 005DD9CD4C00"
Database version. "OCI_102 (10.2.0.2.0) "
Patch level. 166
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
Memory consumption
Roll.... 16128
EM...... 8379840
Heap.... 0
Page.... 40960
MM Used. 705904
MM Free. 3481488
r and Transaction
Client.............. 070
User................ "CRENSHAWDP"
Language key........ "E"
Transaction......... "SCI "
Transactions ID..... "48AB59A7D7E00112E10080008AFE8CA1"
Program............. "????????????????????????????????????????"
Screen.............. " "
Screen line......... 0
Information on where terminated
Contents of system fields
Name     Val.
SY-SUBRC 0
SY-INDEX 0
SY-TABIX 0
SY-DBCNT 0
SY-FDPOS 0
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY
SY-UCOMM
SY-TITLE
SY-MSGTY
SY-MSGID
SY-MSGNO 000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20080820
SY-UZEIT 082629
SY-XPROG
SY-XFORM
Internal notes
    The termination was triggered in function "ab_genprog"
    of the SAP kernel, in line 1551 of the module
     "//bas/700_REL/src/krn/runt/abgen.c#10".
    The internal operation just processed is " ".
    Internal mode was started at 20080820082629.
    Program name.........: "SAPLS_CODE_INSPECTOR ".
    Error message........: ""SCI_DYNP" must be a flat structure. You cannot use
     internal tables, s".
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
=> 64 bit R/3 Kernel
=> 64 bit AIX Kernel
=> Heap limit      = 2684354560
=> Stack limit     = unlimited
=> Core limit      = unlimited
=> File size limit = unlimited
=> Heap address = 0x11716f260
=> Stack address = 0xfffffffffff2a20
=> Stack low     = 0xfffffffffff2a20
=> Stack high    = 0xffffffffffff710
=> Stack Trace:
#AixStack() at 0x1000a2474
#CTrcStack2() at 0x1000a256c
#rabax_CStackSave__Fv() at 0x1000d0e04
#ab_rabax() at 0x1000cd7e4
#ab_genprog() at 0x100b3d5f8
#newload__FPCcP13TmpSubpoolDirUiPUi() at 0x1002194ac
#ab_LoadProgOrTrfo__FPCcUiPUi() at 0x10021905c
#ab_load() at 0x100218e2c
#ab_LoadMainProg() at 0x100820d6c
#dystartx() at 0x100ade944
#dy_cdiag() at 0x100833174
#ab_ctransaction__Fv() at 0x100ae1ef0
#ab_retdynp__Fi() at 0x100821c98
#ab_dstep() at 0x100821924
#dynpmcal() at 0x100e932e0
#dynppai0() at 0x100e905ec
#dynprctl() at 0x100e99d48
#dynpen00() at 0x100e8cc18
#Thdynpen00() at 0x1000f9ed4
#TskhLoop() at 0x1000fec7c
#ThStart() at 0x100115890
#DpMain() at 0x1017f4b14
#nlsui_main() at 0x1018e2b6c
We contacted SAP OSS about this problem and they suggested that we check our LS_CODE_INSPECTORTOP include in program SAPLS_CODE_INSPECTOR and revert it to the original version. We did that and still are getting this error. Any suggestions how to fix this issue. All advices are welcome.
Thanks.
Kamran

Nope... this is SAP standard code so I will reply to the OSS and wait for them to come back to you.
Regards
Juan

How to troubleshoot runtime error (termination with short dump)

hi all,
i'm new comer on crm. and i got a problem when i accessed tx: segment builder (runtime error: termination with short dump).
i've tried to troubleshoot this problem by set the java2 SDK GUI path on the client side.but it still didn't work.then i tried to activate the automation trace (just perform the procedure which wrote down on error analysis), but i confused when tried to read the trace file and still didn't get the point. FYI, i 'm using sap logon 710 and SAP crm 5.0.
what i've should to do?
should i have to re install my sap logon?
i really need ur assistance!
best regards,
agung

Hi Agung,
Please refer the following SAP Note for your information:
<b>SAP Note: 990263</b>
Best Regards,
Johnny.
Reward with points if it helps.

Runtime error while executing SE30 Tcode as CREATE_DATA_ILLEGAL_LENGTH

Hi Guys,
when I am executing a TCode SE30 I am getting following Runtime error .
Runtime Errors         CREATE_DATA_ILLEGAL_LENGTH
Except.                CX_SY_CREATE_DATA_ERROR
Date and Time          23.07.2010 12:28:30
Short text
     CREATE DATA: Illegal value for the length of an object of the type "X"
What happened?
     Error in the ABAP Application Program
     The current ABAP program "CL_ABAP_TRACE_FILE============CP" 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_CREATE_DATA_ERROR', was not
      caught in
     procedure "READ_INFO" "(METHOD)", nor was it propagated by a RAISING clause.
     Since the caller of the procedure could not have anticipated that the
     exception would occur, the current program is terminated.
     The reason for the exception is:
     A data object of the type "X" with length 0 was to be created using
     CREATE DATA. The value 0 is not within the allowed range.
     Allowed range for the length specification:
     Typ C, N, X: 1 .. 65535
     TYP P:       1 .. 16
Missing RAISING Clause in Interface
Please suggest me the solution .

You have to check that in the object(source code) which you are analysing via SE30 .

Runtime error SAPSQL_ARRAY_INSERT_DUPREC during migo

Hi Friends,
When I try doing MIGO with reference to a PO and save the document it gives me runtime error SAPSQL_ARRAY_INSERT_DUPREC.
I have check the buffer, and the no. range everything is perfect, but still i am getting this error.
Can anyone please give me the possible solution for this. Is there any SAP note that I need to apply.
Regards,
Wasim.

Hello Wasim,
The common cause of this termination is the material document
number range as per note 31793 - SAPSQL_ARRAY_INSERT_DUPREC.
So please check if the current numbers are synchronized with the
database tables:
OMBT trx x MKPF table
OMH6 trx x EKKO table
If it has the same number range the sort dump should not be raised
anymore.
The main root causes are:
-> when you are transporting number ranges from one client to another;
-> when you face a shut down in your system and you have defined a
buffer application server tolerance in transaction SNRO;
-> when you are doing the posting by using BAPI's and for some reason
the BAPI failed.
I hope it helps you.
Best Regards,
Fábio Almeida
MM Consultant

Runtime Error: CONVT_NO_NUMBER with MM01 BDC

Hi All,
I am creating Material Master using Call transaction Method for MM01 Tcode.
I am passing the value called Standard Price (MBEW-STPRS) in the BDC.
Standard price will be like 100.00 (Hundred Rupees)
While passing this value, I am getting Runtime Error with the following details.
Runtime Error: CONVT_NO_NUMBER
Unable to interpret "/" as a number.
258 ----
259 *        Insert field                                                  *
260 ----
261 FORM BDC_FIELD USING FNAM FVAL.
>>>   IF FVAL <> NODATA.
263     CLEAR BDCDATA.
264     BDCDATA-FNAM = FNAM.
265     BDCDATA-FVAL = FVAL.
266     APPEND BDCDATA.
267   ENDIF.
268 ENDFORM.
How to resolve this type of error???
Regards
Pavan

I have defined field STPRS as char(13 length) in the internal table as char.
The field NODATA is having value ' \ ' in the debugging mode.
The code mentioned in my above post is from the standard perform statement.
Even if i provide value as "100" in the flat file, while reaching the statment
perform bdc_field       using 'MBEW-STPRS'
it_mm01-stprs.
it shows as "100.00" in the debugger.
Any idea....????
Regards
Pavan

BAPI Runtime Error DBIF_RSQL_INVALID_REQUEST with module "KONV_BEARBEITEN"

Hi Experts
I am trying to create a sales order using BAPI FM BAPI_SALESORDER_CREATEFROMDAT1. After executing the program it shows in output screen that the sales order created and also displays the newly created sales order number. But when I want to check the order from VA03 it shows Express document "Update was terminated" received by author AAA, where AAA is login name.
I also analysis the sort dump for which the update process was terminated. I give the error details
Runtime Errors         DBIF_RSQL_INVALID_REQUES
Error analysis
    An invalid request was made to the SAP database interface in a statement
     in which the table "KONV " was accessed.
Below are the module name and report from where the error is coming.
Function Module name RV_SALES_DOCUMENT_ADD
Program Name SAPLV45U
Include LV45UF0K
Row 26
Source code from Rruntime Error
Line SourceCde
1 *****************************************************************
    2 * Unterroutinen RV-Auftragsabwicklung alphabetisch sortiert:
    3 * ----------------------------------------------------------
    4 * Buchstabe K:
    5 *
    6 *****************************************************************
    7
    8 *----------------------------------------------------------------
    9 *       FORM KONV_BEARBEITEN
   10 *----------------------------------------------------------------
   11 FORM KONV_BEARBEITEN.
   12
   13   CHECK: FKONV_GEAENDERT NE SPACE OR
   14          VORGANG = CHARH.
   15
   16   IF VORGANG NE 'H'.
   17     DELETE FROM KONV WHERE KNUMV = VBAK-KNUMV.
   18 ENHANCEMENT-POINT KONV_BEARBEITEN_10 SPOTS ES_SAPLV45U.
   19   ENDIF.
   20
   21   LOOP AT FXKOMV.
   22     FXKOMV-MANDT = VBAK-MANDT.
   23     FXKOMV-KNUMV = VBAK-KNUMV.
   24     MODIFY FXKOMV.
   25   ENDLOOP.
>>>>>   INSERT KONV FROM TABLE FXKOMV.
   27   IF SY-SUBRC NE 0.
   28     MESSAGE A100 WITH
   29   ENDIF.
   30
   31 ENHANCEMENT-POINT KONV
   32 ENDFORM.
   33 *eject
Below is my source code.
*& Report Z_BAPI_SALESORDER
REPORT z_bapi_salesorder.
* Sales document type
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
PARAMETERS: p_auart TYPE auart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Sales organization
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Distribution channel
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Division.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
PARAMETERS: p_spart TYPE spart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
* Sold-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
PARAMETERS: p_sold TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Ship-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
PARAMETERS: p_ship TYPE kunnr.
SELECTION-SCREEN END OF LINE.
SKIP 1.
* Material
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Quantity.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
PARAMETERS: p_menge TYPE dzmengc OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Plant
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
PARAMETERS: p_plant TYPE werks_d OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Data declarations.
DATA: v_vbeln            LIKE vbak-vbeln.
DATA: header             LIKE bapisdhead.
DATA: headerx            LIKE bapisdhead1x.
DATA: item               LIKE bapiitemin OCCURS 0 WITH HEADER LINE.
DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
DATA: partner            LIKE bapipartnr OCCURS 0 WITH HEADER LINE.
DATA: return             LIKE bapireturn1    OCCURS 0 WITH HEADER LINE.
DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                         WITH HEADER LINE.
DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapisdhedu
                         WITH HEADER LINE.
* Initialization.
INITIALIZATION.
v_text   = 'Order type'.
v_text1 = 'Sales Org'.
v_text2 = 'Distribution channel'.
v_text3 = 'Division'.
v_text4 = 'Sold-to'.
v_text5 = 'Ship-to'.
v_text6 = 'Material'.
v_text7 = 'Quantity'.
v_text9 = 'Plant'.
* Start-of-selection.
START-OF-SELECTION.
* Header data
* Sales document type
header-doc_type = p_auart.
headerx-doc_type = 'X'.
* Sales organization
header-sales_org = p_vkorg.
headerx-sales_org = 'X'.
* Distribution channel
header-distr_chan = p_vtweg.
headerx-distr_chan = 'X'.
* Division
header-division = p_spart.
headerx-division = 'X'.
headerx-updateflag = 'I'.
* Partner data
* Sold to
partner-partn_role = 'AG'.
partner-partn_numb = p_sold.
APPEND partner.
* Ship to
partner-partn_role = 'WB'.
partner-partn_numb = p_ship.
APPEND partner.
* ITEM DATA
itemx-updateflag = 'I'.
* Line item number.
item-itm_number = '000010'.
itemx-itm_number = 'X'.
* Material
item-material = p_matnr.
itemx-material = 'X'.
* Plant
item-plant    = p_plant.
itemx-plant   = 'X'.
* Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
APPEND item.
APPEND itemx.
*   Fill schedule lines
lt_schedules_in-itm_number = '000010'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty    = p_menge.
APPEND lt_schedules_in.
*   Fill schedule line flags
lt_schedules_inx-itm_number = '000010'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty     = 'X'.
APPEND lt_schedules_inx.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT1'
    EXPORTING
      order_header_in           = header
*     WITHOUT_COMMIT            = ' '
*     CONVERT_PARVW_AUART       = ' '
   IMPORTING
     salesdocument              = v_vbeln
*     SOLD_TO_PARTY             =
*     SHIP_TO_PARTY             =
*     BILLING_PARTY             =
*     RETURN                    =
    TABLES
      order_items_in            = item
      order_partners            = partner
*     ORDER_ITEMS_OUT           =
*     ORDER_CFGS_REF            =
*     ORDER_CFGS_INST           =
*     ORDER_CFGS_PART_OF        =
*     ORDER_CFGS_VALUE          =
*     ORDER_CCARD               =
*     ORDER_CFGS_BLOB           =
     order_schedule_ex          = lt_schedules_in
* Check the return table.
IF v_vbeln <> space.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    WRITE: / 'Document ', v_vbeln, ' created'.
ELSE.
    WRITE: / 'Error in creating document'.
ENDIF.
I am unable to trace the exact reason. Please help and thanks in advance.
Edited by: Joy Banerjee on Oct 12, 2009 7:47 AM

Hi Prashant,
Set the profile parameter abap/buffersize value to maximum.Get the virtual memory increased.
If it doesn't work, see in transaction db02 if there is sufficient tablespace.
Let me knoe the status of tablespaces.
Regards,
Sabita

Getting ABAP runtime error while doing MIGO-GR against PO.

Hi,
Getting ABAP runtime error message while doing GR against PO.
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.
Any pointers
Code Formatted by: Alvaro Tejada Galindo on Jan 14, 2010 6:00 PM

Hi ,
Any inputs
for this error
No RFC destination is defined for SAP Global Trade Services
Regards
Ashu

Runtime error/s with iOS

I've followed the build instructions for iOS in your documentation but I get an error at runtime with the following output:
Detected an attempt to call a symbol in system libraries that is not present on the iPhone:
stat$INODE64 called from function __os_exists in image Berkeley.
An Apple forum member suggested that I'm not building BDB against the iPhone Simulator system libraries. I have a few questions:
In your build instructions for iOS you refer to an $SDKROOT variable. What should this be set to for Simulator and device builds respectively?
I found a SO post from someone who suggests that I'd need quite extensive modification of my build script to set environment variables not mentioned in your build instructions. You can see his build script in the second answer in the following link to SO:
objective c - How can I use the Berkeley DB within an iOS application? - Stack Overflow
If I make use of his script, I get an error that tells me gcc isn't working correctly. His post is quite old, so I'm really hoping you can elaborate on your existing guidance for iOS builds that will help me get BDB working at runtime. Just to note, following your build instructions does lead to a successful build of BDB but it fails at runtime.
Any help at all would be great, thanks.

Hi Ray,
Could you try building the BDB library using the following configuration:
export DEVROOT=/Applications/Xcode.app/Contents/Developer
export SDKROOT=/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk
export SIMROOT=/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk
export CC=$DEVROOT/usr/bin/gcc
export LD=$DEVROOT/usr/bin/ld
export CXX=$DEVROOT/usr/bin/g++
export LDFLAGS="-L$SDKROOT/usr/lib"
export CFLAGS="-arch i386 -pipe -no-cpp-precomp -isysroot $SDKROOT -mios-simulator-version-min=7.1"
export CXXFLAGS="-arch i386 -pipe -no-cpp-precomp -isysroot $SDKROOT -mios-simulator-version-min=7.1"
export CPPFLAGS="-arch i386 -pipe -no-cpp-precomp -isysroot $SDKROOT -mios-simulator-version-min=7.1"
../dist/configure --host=arm-apple-darwin9 --prefix=$SDKROOT \
--enable-sql --enable-debug --enable-cxx --enable-sql_compat
With the BDB library built with this configuration, we couldn't reproduce the runtime error you mentioned in your original post on iOS simulator 7.1.

GETTING RUNTIME ERROR POSITNG GR-MIGO

Dear All,
While Posting GR thru MIGO, we'r getting short fump while posting the transaction after check made.
Pls advise what happened exactly and how to fix this......
We'r getting this error/short dump only from today and wants to know whether its getting affected by any patches implemented by Basis consultant.
FYR
The below description displaying in Runtime error while posting GR-MIGO after check completed OK.
Short Text
Syntax error in program "SAPLFAGL_MIG_OPITEMS ".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLGLIN" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPLFAGL_MIG_OPITEMS " in
include "LFAGL_MIG_OPITEMSTOP " in
line 42:
"The type "FAGL_MIG_BELNR_DOCNR" is unknown."
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "BS1SUDHA "
Error in the ABAP Application Program
The current ABAP program "SAPLGLIN" 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 SAPLFAGL_MIG_OPITEMS :
"The type "FAGL_MIG_BELNR_DOCNR" is unknown."
Trigger Location of Runtime Error
Program SAPLGLIN
Include LGLINF90
Row 3,340
Module type (FORM)
Module Name SET_DOCNR
Source Code Extract
Line SourceCde
3310 MOVE BEL_TAB-REFACTIVITY TO BEL_ST-REFACTIV.
3311 MOVE-CORRESPONDING BEL_ST TO TAB_FAGLFLEXA .
3312 IF T881-GLFLEX = '1'.
3313 MOVE BEL_TAB-DOCNR_GLFLEX TO TAB_FAGLFLEXA-DOCNR.
3314 ENDIF.
3315 MODIFY TAB_FAGLFLEXA .
3316 ELSE.
3317 CLEAR BEL_TAB.
3318 LOOP AT BEL_TAB WHERE BUKRS = TAB_FAGLFLEXA_ADD-BUCHKREIS
3319 AND ACTIVITY = TAB_FAGLFLEXA-ACTIV
3320 AND DOCNRVORL = TAB_FAGLFLEXA-DOCNR.
3321 IF T881-GLFLEX = '1'.
3322 IF UF-INTERFACE = GC_AC_INTERFACE.
3323 CHECK BEL_TAB-RLDNR = TAB_FAGLFLEXA-RLDNR.
3324 ENDIF.
3325 CHECK NOT BEL_TAB-DOCNR_GLFLEX IS INITIAL.
3326 ELSE.
3327 CHECK NOT BEL_TAB-DOCNR IS INITIAL.
3328 ENDIF.
3329 MOVE-CORRESPONDING BEL_TAB TO BEL_ST.
3330 MOVE BEL_TAB-REFACTIVITY TO BEL_ST-REFACTIV.
3331 MOVE-CORRESPONDING BEL_ST TO TAB_FAGLFLEXA .
3332 IF T881-GLFLEX = '1'.
3333 MOVE BEL_TAB-DOCNR_GLFLEX TO TAB_FAGLFLEXA-DOCNR.
3334 ENDIF.
3335 MODIFY TAB_FAGLFLEXA .
3336 EXIT.
3337 ENDLOOP.
3338 ENDIF.
3339 IF NOT TAB_FAGLFLEXA_ADD-GLSIP IS INITIAL.
CALL FUNCTION 'FAGL_MIG_GET_DOCNR'
3341 EXPORTING
3342 iv_rldnr = TAB_FAGLFLEXA-rldnr
3343 iv_bukrs = TAB_FAGLFLEXA-rbukrs
3344 iv_gjahr = TAB_FAGLFLEXA-gjahr
3345 iv_belnr = TAB_FAGLFLEXA-belnr
3346 iv_buzei = TAB_FAGLFLEXA-buzei
3347 IMPORTING
3348 ev_docln = TAB_FAGLFLEXA-docln.
3349 MODIFY TAB_FAGLFLEXA .
3350 ENDIF.
3351 ENDLOOP.

Hi Babu
Please check in SM12 what is the cause and probably you have to take this to an good ABAPER.
regards
Yogesh

Runtime Error CONVT_OVERFLOW in MIGO

Hi,
We have this issue:
When we try to do a Good Receipt for a particular material, the good receipt is posted, but the system show this message: Runtime Error CONVT_OVERFLOW (Overflow when converting from "2.1252e+09") and the good receipt can not be displayed.
This material has a price (VEF 64.400,00) and the material quantity has not decimals (for example: 1,00).
When we changed the price in the purchase order (for example: VEF 10,00) the good receipt was posted and the good receipt can be displayed.
Would you please help us with this situation?
Best Regards,
Marielita

Hi Mariela,
Please refer the below notes
SAP Note No. 192057 CONVT_OVERFLOW in MB_UPDATE_MATERIAL_VALUES <<<<<<<<<<<<<
SAP Note No. 831197>> Dump CONVT_OVERFLOW in goods movements with ML
SAP Note No. 192057 Should solve your issue .
Rgs
SB

Windows client gives runtime error R6034 with TMMONITOR=app,svc,tran,sys::

PLEASE REFER TO THE DUPLICATE POSTING IN THE "TUXEDO" FORUM FOR AN ANSWER TO THIS QUESTION.
Hi,
I'm testing TSAM on a Windows system. If I run without setting the TMMONITOR environmental variable set everything works fine, but when I set TMMONITOR=app,svc,tran,sys:: both the client and server programs give the runtime error R6034: "An application has made an attempt to load the C runtime library incorrectly". Clicking the "OK" button lets the programs continue, but the following messages appear in the ULOG:
142539.868.TUXMODEL!tuxmodelclient.5996.5860.0: GP_CAT:1345: ERROR: pif: can't load 'libmonplugin.dll'
142539.868.TUXMODEL!tuxmodelclient.5996.5860.0: GP_CAT:1341: ERROR: pif: can't load impl 'bea/performance/mongui' that is in InterceptorSequence for 'bea/performance/monfan'
142539.868.TUXMODEL!tuxmodelclient.5996.5860.0: LIBTUX_CAT:6623: ERROR: TMMONITOR failed to invoke the monitoring plug-in
142547.342.TUXMODEL!TuxModelServer.3220.728.0: GP_CAT:1345: ERROR: pif: can't load 'libmonplugin.dll'
142547.342.TUXMODEL!TuxModelServer.3220.728.0: GP_CAT:1341: ERROR: pif: can't load impl 'bea/performance/mongui' that is in InterceptorSequence for 'bea/performance/monfan'
142547.342.TUXMODEL!TuxModelServer.3220.728.0: LIBTUX_CAT:6623: ERROR: TMMONITOR failed to invoke the monitoring plug-in
142547.482.TUXMODEL!TuxModelServer.3220.728.0: LIBTUX_CAT:6623: ERROR: TMMONITOR failed to invoke the monitoring plug-in
142547.498.TUXMODEL!TuxModelServer.3220.728.0: LIBTUX_CAT:6623: ERROR: TMMONITOR failed to invoke the monitoring plug-in
142547.498.TUXMODEL!tuxmodelclient.5996.5860.0: LIBTUX_CAT:6623: ERROR: TMMONITOR failed to invoke the monitoring plug-in
Can anyone tell me what I need to do to overcome this problem? (I'm running Tuxedo Version 10.0 with VS2005, 32-bit, Patch Level (none) and TSAM version 1.1. Both programs were compiled with buildclient/buildserver, using Microsoft Visual C++ Express Edition 2008 (Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 15.00.30729.01 for 80x86)
Thanks & kind regards,
Malcolm.
Edited by: Malcolm Freeman on Oct 28, 2008 11:55 AM

As I know, the runtime rrror R6034 can be caused by Windows, not caused by TSAM, you need check your Windows system.
guggi

Runtime error 10401 with CWAOPoint1 control

I am trying to run an older application and it fails with Runtime error 10401...the specified device is not a NI product... I am trying to run this on a laptop that does not have the hardware. How can I get around this error so I can step through my code (VB6)? I have the both the latest DAQMX and traditional Nidaq software installed as well as Measurement Studio 8 installed.

The following is the subroutine used. Its giving the error on the SingleWrite commands. VB does not report any references missing in the project.
Sub cmdSetLEDVoltages_Click(Index As Integer)
    Select Case Index
        Case 0
            CWAOPoint1.ChannelString = "1"
            CWAOPoint1.SingleWrite cwnGlareLEDVoltage(Index).Value
            CWAOPoint1.ChannelString = "0"
            CWAOPoint1.SingleWrite cwnRefLEDVoltage(Index).Value
        Case 1
            CWAOPoint2.ChannelString = "1"
            CWAOPoint2.SingleWrite cwnRefLEDVoltage(Index).Value
            CWAOPoint2.ChannelString = "0"
            CWAOPoint2.SingleWrite cwnGlareLEDVoltage(Index).Value
    End Select
End Sub

Runtime Error:MESSAGE_TYPE_X in VA01 tcode

Hi All,
I got VA01 tcode Dump While Entering the Texts, in that dump it is showing use SAP note 158985 ,
By using That note number verifed finally i got one relevent note 1104496. And i applied that but still getting same dump. Can any body help me that please give another relevent note for this issue. The Dump is coming from SAPLOLEA include LOLEAU02 Function Module AC_SYSTEM_FLUSH.
Thnaks & Regards,
Rajasekhar.

generally with SAPOLEA-errors: apply latest version and patch of SAPGUI. this will solve most of those errors.

Runtime Error SYNTAX_ERROR with MIGO tcode

Similar Messages

Maybe you are looking for