Short dump in VF01 transaction with error id SAPSQL_ARRAY_INSERT_DUPREC

Hi,
We are getting shortdump SAPSQL_ARRAY_INSERT_DUPREC when running VF01 transaction.
The ABAP/4 Open SQL array insert results in duplicate database records.
The termination occurred in the ABAP/4 program "SAPLV60U " in
"VBUK_BEARBEITEN".
Line Number 536
>>>>> INSERT vbuk FROM TABLE da_xvbuki.
Could some one please reply me when you have the time.
Regards,
Vishal
Moderator Message: De-prioritized.
Edited by: kishan P on Aug 29, 2011 2:05 PM

Duplicate records is being tried to enter in table VBUK, which is not allowed due to primary key concept. Hence the error.
For details, you can get help of the technical person in your team

Similar Messages

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

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

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

Short Dump in CO02 Transaction

Hi ,
     I am getting short Dump in CO02 Transaction . Please see following detail .
     Runtime Errors         MESSAGE_TYPE_X
    Trigger Location of Runtime Error
    Program                                   SAPLCOKO1
    Include                                     LCOKO1F4H
    Row                                         614
    Module type                             (FORM)
    Module Name                           ORDER_CHANGE
>>>>>       MESSAGE x901.                                             "n779835
Please help me.
Thanks in Advance.
Sai

Hi Sai,
I get an similar Error after I have upgrade from 6.20 to ERP6 EHP4. Could you solve your problem?
Tanks
Bernd
Syntax error in program "SAPLCOKO1 ".
The current ABAP program "????????????????????????????????????????" had
terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPLCOKO1 " in include "LCOKO1FW2 " in line 27:
"The data object "LS_REF" down not have a component called "OBMAT"."

Get error from SQL AGENT: The SSIS Runtime has failed to enlist the OLE DB connection in a distributed transaction with error 0x8004D024

I am running SQL Agent that executes an SSIS process from sql server1. The SSIS process executes its SQL/tables/sp’s against another sql server2.
I get an error after adding data flow tasks with transaction supported within a sequence with transaction required. The error, “The SSIS Runtime has failed to enlist the OLE DB connection in a distributed transaction with error 0x8004D024 "The transaction
manager has disabled its support for remote/network transactions"
Prior to adding this sequence everything was working from sql agent, and there were other sequences with oledb destinations.
Everything works when running within SSIS Package.
I see this article on similar issue,
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/0bfa2569-8849-4884-8f68-8edf98a9b4fe/problem-to-execute-a-package-and-tasks-with-a-certain-transactionoption-property-i-need-help?forum=sqlintegrationservices
“I had similar issue and solved by setting the following on both the machines. Allow Remote Clients, Allow Remote Administration,
Allow Inbound Clients, Allow Outbound Clients, and TIP are enabled in Component Services/My Computer/Properties/MSDTC/Security Configuration.”
I don’t want to remove transaction required for the “Remove Duplicates from Staging” sequence.
Anyone seen this?
Greg Hanson

DTC was running on remote computer. The problem was it was no longer accepting transactions from remote servers. This was in SSIS so I had to turn to "Transaction Supported" for all Data Flow Transactions.
Greg Hanson

CONNE_IMPORT_WRONG_COMP_TYPE short dump in DB02OLD transaction

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

Solved on my own

Short dumps in every transaction during the Support pack import

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

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

Dont save a transaction with Error

Hi,
I am working on CRM 5.0. I have a scenario where If lead is created and few entries are not made still I can save the transaction with errors.I hope this is a standard feature of CRM 5.0. Now my client want the transaction not to be saved in case any error is coming. I tried controlling thru Incompleteness but there also after error , the transaction is getting saved.
Request immediate help on the matter. Helpfull answers will be rewarded.
Thanks,
Ambrish

Hi Ravi,
I also tried to find out some BADI that triggers on saving the lead but couldnt get the same. there is one BADI that gets trigger on Incompletion i.e PROC_DETERMINE but this is not useful in the same.
Can you suggest me some place where I could figure out the relevant BADI for lead saving.
Thanks ,
Ambrish

Short dump in VF01 - Syntax error in program "RKEAK9RECP3000001"

Helo all,
We recently copied our production client to a QA client and when we try to save an SD invoice (VF01), we get a short dump titled - Syntax error in program "RKEAK9RECP3000001".
The dump long text states:
"The Dictionary structure or table "K9RECP3000001" is either not active"
" or does not exist."
and
NOTE in case of a SHORT DUMP:
if the following perform statement should lead to a short dump, then
the report stated in the short dump is missing (RKEAK9Rsssmmmnnnn)
Check if table K9Rsssmmmnnn exists. If not it should be transported
from the original system.
Regenerate the missing reports by using transaction SE37, entering
function KEDR_REGENERATE_ALL_REPORTS and pressing button 'Test' and
'Execute'.
but I tried to run function KEDR_REGENERATE_ALL_REPORTS in SE37 and the problem persists.
Maybe I'm not running it correctly - there is no execute option when pressing "Test" so I enter the function and press F8, which takes me to a screen titled "Test function module" and then I execute.
My suspicion is that table "K9RECP3000001" cannot be created or generated since it it a system specific naming convention K9RSSSCCC0001 in which SSS is system ID (in our case ECP is production and ECQ is QA) ans CCC is client number (300 in prod, and should be 286 in ECQ).
Has anyone encountered this type of a problem and knows how to fix it?
Needless to say, I looked at OSS notes, but did not find the solution there.
Any thought will be appreciated,
Yoel.

Shalom Yoel,
This problem may be caused by the fact that some derivation rules
that were originally created once in a system have been transported
into target system without transporting the dependent objects
as well (the generated tables for the derivation rule entries).
You can see this by execution of program RKEDRCHECK with only
parameter 'Check in all clients' marked. You will then get
inconsistent derivation steps (which refer to a generated table
table for the rule entries that doesn't exist because it was
not transported).
There are two ways to solve the problem:
1.) If you don't need these steps any more in derivation you can get
    rid of them by executing program RKEDRCHECK with both parameters
    marked ('Check in all clients' and 'Delete inconsistent steps').
2.) If these steps should remain you have to retransport the missing
    tables from the source system in which these tables have to exist
    (creating transport requests for the customizing of derivation by
    pushing on the 'Transport' icon in the source system in transactions
    KEDR and KEPC).
For each derivation step,the system generates a program RKEAK9R *
and a table K9R+ System ID+ Mandant+ a number of five figures
from the object number in KEDR.
br, Guido

A short dump in the program with a certain error message...

Hi all,
I'd run a program to do an insertion into a customized table.
During the run, it popped up a short dump error messages below :
value larger than specified precision allows for this column#TC020 %M
I've search for that column #TCO20 .... and i couldn't find it in my custom table...
Why SAP gave such a hard description on the error found? I can't determine which field/column in my table that is causing the error dump during INSERT event in my program.
Is there any explanation on that message that could help me?
Thanks
William Wilstroth

Hi,
Better u seee again where u r getting error i the code . still if u r not getting see in dump analysys(ST22) and select
no:8 -- which is source code extract where u can get correct error inf.
Plz reply me.
Regards
Durgaprasad.

Short Dump in MIGO transaction

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

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

Short dump in Z transaction code

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

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

Short dump during ME23N transaction due to missing field in KOMP table

Hi All,
We have just upgraded to Business Suite 7.0 and are experiencing the following error:
Short dump during processing of transaction ME23N - error is in program SAPLV61A when the system calls the following field: KOMP_SERVICE_PARAM2 (this does not exist in KOMP). We need to get this resolved as soon as possible, It appears that SAP have removed this field from the table KOMP but the standard programme is still looking for this field. Can anyone provide an oss note number or insight into how to resolve this issue please.
Many Thanks
Amanda

Dear,
This problem is caused by a missing initialization of the structure KOMP in the program SAPLV61A.
The problem may also occur during , when the "Create PO automatically" indicator (TVAP-ALEKZ) is set for the relevant item category in the item category Customizing (transaction VOV7). In this case, the data of the purchase order item that was previously processed is used for the back update of the sales order from the purchase order in KOMP.
Add the following import parameter to the function module RV_KONV_SELECT:
    Parameter name        COMM_ITEM_I
    Typing          LIKE
    Associated type            KOMP
    Optional        X
    Pass Value       X
Please refer the OSS note 1261566.
Regards,
R.Brahmankar

Explicit Search Helps Short-Dump in Editable ALV with included structure

I have an editable ALV grid defined as follows:
TYPES: BEGIN OF gs_outtab200.
    TYPES: row_indx(4)      TYPE n.
    TYPES: multipurp        TYPE c.
    INCLUDE structure zxrfwc_test.
TYPES: end of gs_outtab200.
DATA:
    gt_outtab200             TYPE TABLE OF gs_outtab200,
    wa_outtab200             TYPE gs_outtab200.
The included structure zxrfwc_test has a component (field) which is defined with a data element that has an explicit search helps associated with it.
I know that this search help is working properly because it works fine in the program's selection screen.
But when I invoke the search help from within a column of the ALV itself, I get a short dump with a "GETWA_NOT_ASSIGNED" error.
I have done plenty of editable ALVs with search helps defined on the data elements and never encountered this problem.
Am I hitting this problem because the zxrfwc_test structure is defined within the
gs_outtab200 structure ??
If not, what is causing this problem. (Please note that I have set ls_fcat-F4AVAILABL = 'X' in the fieldcat routine - this doesn't seem to help at all.)
Please advise!!!!
I'm really stuck on this one because it's always worked before when I'm not dealing with a dictionary structure that's included within a larger ALV structure.
Thanks.

Hi,
How you are creating your field catalog?
Try to create a field catalog in the following way giving reference to your structure. is it possible for you create a DDIC structure as same as
TYPES: BEGIN OF gs_outtab200.
    TYPES: row_indx(4)      TYPE n.
    TYPES: multipurp        TYPE c.
    INCLUDE structure zxrfwc_test.
TYPES: end of gs_outtab200.
* Form f_generate_fieldcatalog                                         *
* Form generate the field catalog table                                *
form f_generate_fieldcatalog.
* Private variable
data : v_structure like dd02l-tabname.   " Table Name
v_structure = c_yatt_alv.                      " Structure Name
* Build the fieldcat according to DDIC structure YATT_ALV:
call function 'LVC_FIELDCATALOG_MERGE'
    exporting
      i_structure_name       = v_structure
      i_client_never_display = c_x
    changing
      ct_fieldcat            = i_fieldcat[].
endform.                                 " F_generate_fieldcatalog
a®

Short dump while PO creation with Tax Code

we are facing problem while creation PO, while providing the Tax code(Example V0), its going for short dump, check the below
the program SAPLV61Z and
The exception must either be prevented, caught within the procedure
"SEL_KONDTAB"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Check the field names in the SELECT clause.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"SAPSQL_INVALID_FIELDNAME" CX_SY_DYNAMIC_OSQL_SEMANTICSC
"SAPLV61Z" or "LV61ZU01"
"SEL_KONDTAB"
The termination occurred in the ABAP program "SAPLV61Z" in "SEL_KONDTAB".
The main program was "RM_MEPO_GUI ".
The termination occurred in line 537 of the source code of the (Include)
program "LV61ZU01"
of the source code of program "LV61ZU01" (when calling the editor 5370).
Processing was terminated because the exception "CX_SY_DYNAMIC_OSQL_SEMANTICS"
occurred in the
procedure "SEL_KONDTAB" "(FORM)" but was not handled locally, not declared in
the
RAISING clause of the procedure.
The procedure is in the program "SAPLV61Z ". Its source code starts in line 254
of the (Include) program "LV61ZU01 ".
005360           IF se_read_all_prestep IS INITIAL.
     >             SELECT * FROM (t681-kotab) APPENDING TABLE <cond_tab>
005380                    UP TO 1 ROWS
005390                    WHERE kappl = se_kappl
005400                    AND   kschl = se_kschl
005410                    AND   datbi >= se_date
005420                    AND   datab <= se_date
005430                    AND   (coding_tab).
005440             h_subrc = sy-subrc.
In the above statement execution its going for dump, when the (t681-kotab) value is A980 when i checked at debugging
Kindly help me out to solve the issue
Thanks in advance
Regards
Kesav

Hi,
Do you have an integer field in the condition table A980? It looks like a field in the table is integer one and the system during creation of custom dynamic select statement adds as many spaces as possible before the integer value (integer values are right justified), so the statement exceeds the maximum length with an 'AND' or another condition clause.
Please check and provide more details if the issue is not resolved.
Regards,
Marcin

Short dump in every transaction during support pack import In PRD server

HI
While trying to applying support pack stack, get short abap dump, but after this in every tx same dump is there.
Following is the Support stack that we are applying
SAPKA70020
SAPKB70020
SAPKIPYM10
SAPKW70022
SAPKNA7017
SAPKH60012
SAPK-60008INFINBASIS
SAPKGS6008
following is dump
Syntax error in program "SAPLPA_PACKAGE_SERVICES
Error in the ABAP Application Program
The current ABAP program "SAPLSFW_COMMON" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPLPA_PACKAGE_SERVICES " in
include "CL_PACKAGE_HELPER=============CU " in
line 179:
"Type "SLS_PACKAGE_INFO" is unknown"
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 "SAPLSFW_COMMON" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Thanks
YogRaj

Hi
I have applied support Pack successfully. But after this my one of SD user getting short dump in Tx VL01N, VA01.
Syntax error in program "SAPLDG95 "
What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_IM_EHS_DG_002_IMPL=========CP" had to be
     terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "SAPLDG95 " in include "LDG95U01
     " in
    line 29:
    ""X_DGMSD_TAB" and "E_DGMSD_TAB" are not mutually convertible. In Unico"
    "de programs, "X_DGMSD_TAB" must have the same structure layout as "E_D"
    "GMSD_TAB", independent of the length of a Unicode character."
    The include has been created and last changed by:
    Created by: "SAP "
    Last changed by: "SAP "
    Error in the ABAP Application Program
    The current ABAP program "CL_IM_EHS_DG_002_IMPL=========CP" 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 SAPLDG95 :
    ""X_DGMSD_TAB" and "E_DGMSD_TAB" are not mutually convertible. In Unico"
    "de programs, "X_DGMSD_TAB" must have the same structure layout as "E_D"
    "GMSD_TAB", independent of the length of a Unicode character."
Thanks
YogRaj

Short dump in VF01 transaction with error id SAPSQL_ARRAY_INSERT_DUPREC

Similar Messages

Maybe you are looking for